Standing service merchant-center-keep-feed-approved · revised 11 October 2026
Standing service
Keep your Merchant Center product data fetched, approved and in step with your site
We watch the Merchant Center data source you name. When fetch, processing, price, availability or image problems appear, we find the cause and propose the fix, or say what only you can change.
This starts a conversation by email. Nothing is charged, and nothing is watched, until we have agreed scope and terms with you in writing. Google's approval is never promised.
The responsibility you hand over
A product data source is a moving target: prices change, stock sells out, images move and the file generator changes. Merchant Center flags problems after the fact, and they come back unless someone watches the cause and the refresh route.
Who it’s for: Store owner or e-commerce manager whose products drop out of Shopping listings after sales, stock changes or feed changes, and who has no time to watch diagnostics.
Usually starts when: Warnings arrive by email after each promotion, the feed lags the site, or nobody owns the data source when it fails.
The result: The named data source keeps being fetched and processed, and the price, availability and image problems that appear are investigated; each ends in a proposed fix, an explanation of what only you can change, or a note that Google must review. Each month you see what appeared and how it ended.
What stays true, and what we do about it
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock, so we do not offer round-the-clock cover. No response-time guarantee is published for this new service; a target is agreed in writing before it starts, set to what a service at this stage can keep.
Hours are agreed in writing before the service starts. The service is not staffed round the clock.
What must remain true
- The named data source is being fetched and processed on its schedule
- Every new price, availability, image or processing problem in the diagnostics ends in a proposal, an explanation or a note for Google review
What we watch
- Item diagnostics and data source reports for the named source, shared by an agreed route
- The behaviour of the public file address when requested from outside
- Your notes of changes made to the site, prices or feed
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| The data source's fetch or processing fails, or items read fall far below the file. | We request the file address, read the report and the file and propose the cause and fix. Priced as: Merchant Center feed file errors |
| Products are warned or disapproved for a price or availability that differs from the page. | We compare feed, page, checkout and markup for the flagged products and propose the feed-side change and refresh route. Priced as: Merchant Center price mismatch |
| Product images fail to load, redirect or return a page that is not an image, or Merchant Center flags an image address, type or size. | We check each flagged image address, file type and size and whether Google can reach the image host, against Google's published image rules, and propose the feed-side fix or a host change list. Overlays, watermarks, placeholders and pictures below Google's minimum size need new pictures or your decision, so we list them as needing your action. |
| A month ends. | We send a short written summary: problems seen, proposals made and what is still open. |
We do on our own
- Read the diagnostics and reports you share
- Request the public file address
- Reproduce and prepare corrected feed rules on a copy
We ask you first
- Anything that changes your live feed, account settings, prices or page templates
- Requesting a Google review
- Any access beyond diagnostics
We escalate to you when
- The cause is an account-level or policy issue
- A fix needs a change to prices, stock or promotions
- Problems pass the agreed monthly number
How you know it held. Each month you get what appeared and how each case ended. The processed diagnostics for the affected products are the evidence for each fix.
How we keep it true
This service is never finished. Each month's summary shows whether the named data source stayed fetched and processed, and it continues until you end it.
Get your product file fetched and processed by Merchant Center without errors Job Each time it fires
Merchant Center fetches your named product file on schedule and processes it, with file-level errors in the data source report cleared or explained and the item count matching your file.
Within the shared monthly number
Each fix is the same job you can buy on its own.
Fix Merchant Center price and stock mismatches between your feed and your product pages Job Each time it fires
For an agreed set of products the feed's price and availability match the page, checkout and markup, and processed diagnostics show no mismatch. Google's approval is not guaranteed.
Within the shared monthly number
What is included, and what is not
- A proposed fix or change list for each problem within the agreed monthly number
- An explanation of what you must change or request from Google, when the cause is outside the feed
- A written monthly summary
Included
- One named Merchant Center data source, watched through diagnostics and data source reports that you share or give least-privilege access to
- Investigation of each new fetch, processing, price, availability or image problem, with a proposed feed-side fix or an explanation
- Written change lists for page markup or settings that you control
- A written monthly summary of what appeared, what we proposed and what is still open
Not included
- Applying changes to your feed, account, site or prices, which stays with your team
- Google account suspensions, policy appeals or promises of approval
- Advertising campaigns, budgets or billing
- Deciding your prices, promotions or stock
- Out-of-hours cover or any guaranteed response time
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
For each proposed fix, the cause is shown with before and after comparison of the feed value, page and checkout or of the file address behaviour.
Evidence: The comparison attached to the proposal.
After you apply a change and Merchant Center has processed the data, the diagnostics for the affected products no longer show the problem we named.
Evidence: Redacted before and after diagnostics with dates.
Each month's summary lists every new problem on the named data source and how it ended.
Evidence: The written monthly summary, which you can compare with your own diagnostics history.
Sign-off. You review each proposal and the monthly summary. A proposal counts as delivered when you accept it.
If it fails. If we cannot find or fix a cause, we say so, explain what we found and what it would take, and it does not count against the monthly number. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- You can share redacted diagnostics and data source reports, or grant the least access that lets us read them
- The feed is produced by a generator, export or rules that you or your developer can change
- A person on your side applies proposed changes and requests any review
We stop and tell you if
- The data source cannot be changed by anyone you can reach
- Most problems are account-level or policy issues that no feed change can fix
- Safe watching would need advertising or billing access
What could go wrong
Every proposal is a change your team applies, so you can restore the earlier feed rule as you would for any change. Ending the service leaves your feed and account as they are.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A feed fix makes the data match a page price that is wrong. | You tell us which source is authoritative, and you apply every change. |
| Fixes are read as a promise Google will approve the products. | No approval is promised. The evidence is the processed diagnostics and Google's own review decides. |
| Shared reports expose advertising or customer information. | We ask only for diagnostics and data source reports, never advertising, billing or customer data. |
Each proposal is checked by a reviewer separate from the work that produced it before it reaches you. No human supervisor is included unless your agreement names one. At launch the work is largely automated, and we say so.
Stays with a person
- You apply every proposed change and request any Google review
- You approve any change to prices, stock or account settings
Access we would need
- Diagnostics and reports shared by an agreed route, or least-privilege read access
- A copy of the feed rules through a company-controlled route
Questions
Will this keep my products approved?
We cannot promise approval. We find and propose fixes for the problems the diagnostics show, and we show the processed result.
Do you need admin access to Merchant Center?
No. We use redacted exports or the least access that lets us read diagnostics. We never need advertising or billing access.
How is this different from one fix?
A one-off job fixes one problem once. This watches the data source you name and takes each new problem through to a proposal or explanation, month after month.
Also part of
Send an enquiry
Send us
- The name of the data source and how its file is produced and fetched
- How often products are flagged today, as best you know
- Who applies changes and requests review. No logins, advertising access or customer data in the first enquiry
Later, once you agree
- Diagnostics and data source report access at the least level that lets us read them, or redacted exports on an agreed schedule
- The feed generator or export rules through an agreed company-controlled route
- The agreed number of problems a month and who to tell when something is outside the feed
Your Merchant Center account, store, prices and data stay yours. We read the diagnostics and reports you share and work on a copy of the feed rules, returning proposed changes for your team to apply. We never hold advertising or billing access.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “merchant-center-keep-feed-approved” as the subject.