Case study · Online store
Hundreds of products were flagged in Google's shopping feed. We cleared them in the right order.
Several problems at once, and every earlier fix had only revealed the next one. We grouped them by cause and worked through them in order.
- Who
- An online retailer with a few thousand products, advertising them through Google's shopping feed.
- The problem
- Hundreds of products were warned or disapproved for different reasons, with a sale coming. Each earlier fix cleared one problem and showed another.
- What we did
- Grouped the flagged products by cause and fixed the groups in the order that works, checking Google's reports after each.
- The result
- Most groups cleared and showed clear in Google's reports. The rest were listed with the reason each needed the retailer or Google.
- Time
- Three weeks, most of it waiting for Google to reprocess after each fix.
What was going on.
The retailer sends its product list to Google every day so its products can appear in shopping results. Several hundred products were flagged, and the reasons did not match: some had file errors, some showed a different price or stock level on the website than in the list, some had picture problems.
A sale was a few weeks away. The retailer's earlier attempts had each cleared one kind of problem and then revealed another, and every change meant days of waiting for Google to look again.
What we found.
Flagged products rarely share one cause, and the causes hide each other. A problem with the file itself can stop Google reading anything else, so the price and stock problems cannot even show up until it is fixed. Fixing them in the wrong order wastes the waiting time between each check.
So we read Google's reports first and grouped the products by cause. Then we worked in the order that does not waste a wait: the file first, then price and stock, then pictures.
The technical detail
Order of work: file fetch and processing errors; price and availability mismatches between the feed, the product page and the checkout; image address, file type and size problems against Google's image rules. After each group, we waited for the data source's report to show processing completed before moving on.
What we did.
How we checked it.
These had to pass before we asked for sign-off.
- The data source's latest report shows processing completed with no file-level errors, and the number of products read matches the file.
- For each price and stock group in the agreed scope, Google's reports show no mismatch, or the product is listed with the reason it needs the retailer's action.
- Where pictures were flagged, each one shows no address, file-type or size problem in the reports, or is listed as needing a replacement.
- The retailer accepted every group in the agreed scope, or removed it from the list in writing.
What they have now.
The retailer received a grouped list of every flagged product with its cause, the corrected feed rules and change lists for the parts it controls, before-and-after reports for each group, and a final summary in three parts: cleared, needs the retailer's action, needs Google's review.
Most groups cleared. A group of products whose pictures were too small could not be fixed from the feed side, so they were listed with links for the retailer's team to replace.
What we did not do.
- We did not promise approval. Google decides that, and some items needed Google's review.
- We did not touch the retailer's advertising campaigns, budgets or billing.
- We did not decide the retailer's prices, promotions or stock. Where they disagreed between the website and the file, the retailer chose which was right.
- Account suspensions and policy appeals were outside this job.
The service behind this.
When many products are flagged for different reasons, the order you fix them in matters as much as the fixes.
Project
Clear Merchant Center disapprovals
We work through the flagged products in one Merchant Center data source by cause (file errors, price and stock mismatches, images) and return each group fixed or explained, with diagnostics.
From $2,450. The payment schedule is set in the written proposal. Nothing is charged until you have agreed it.
More case studies.
One-off job
Checkout stopped taking orders after an update
Customers could fill a basket but not pay. We found the cause on a copy of the shop, fixed it and proved it with test orders.
Online store · Two days
One-off job
Genuine payment messages were being rejected
Paid customers still showed as unpaid. The company's code was checking the wrong thing. We fixed it without switching the check off.
Software team · Three working days
Monthly service
Supplier payment runs checked before they go out
A second pair of eyes on every payment run, with the evidence for each flag, so a duplicate or a changed bank detail is found before the money leaves.
Finance and back office · Ongoing, monthly
Get a price for something like this
You are asking about: Clear Merchant Center disapprovals.
Sending this is not an order. We check we can help, then agree what is included, safe access and the price in writing before any work. Prefer email? hello@syntheticindustry.ai.