Google Merchant Center · Status at source date: Merchant Centre and feeds
Merchant Center policy rewrites stress catalogue fixes before bulk appeals
Reported rewrites to seven Merchant Center policy pages emphasise account-level consequences, removing violations before bulk appeals and a standard fix path.

What changed
Google has rewritten seven Merchant Center policy pages, including pages covering dishonest behaviour, dangerous products, counterfeit goods and misrepresentation. Search Engine Roundtable reports increased emphasis on account-level consequences and remediation steps.
Reported appeal sequence
The revised guidance reportedly says violating items should be removed before bulk appeals. It also describes a standard “Needs attention, View fix” path and includes guidance for platforms such as Shopify. Catalogue correction is therefore presented as a prerequisite to an appeal strategy rather than work to postpone until after submission.
The source does not enumerate all seven rewritten pages in the available account. The named policy areas should not be treated as the complete list, and the reported interface path may need to be checked against the current Merchant Center account.
Review patterns beyond one item
Where documentation stresses account-level consequences, a policy problem should not be approached solely as an isolated SKU error. A flagged item can reveal a repeated claim, feed transformation, product category or site-content pattern affecting additional listings.
Editorial suggestion: use the first violation to define a catalogue query. Search related products for the same brand, source field, claim wording, category or landing-page template. This can reveal whether the correct unit of remediation is one item, a feed rule or a broader site process. It is an investigation method, not evidence that every single-item issue is systemic.
Remediation before appeal
Identify and remove or correct violating items, validate that feed and destination data agree, and then decide whether the catalogue is ready for a bulk appeal. Keep a dated record of affected items, root cause, changes and validation.
For platform-managed feeds such as Shopify, determine whether the correction belongs in the source catalogue, an integration setting or Merchant Center. Fixing only the displayed symptom may allow the next synchronisation to restore the problem.
The reporting does not establish appeal timelines, review standards or success rates. A clean, documented catalogue supports a better submission but cannot guarantee reinstatement.
Why it matters for advertisers
Submitting an appeal before the catalogue is corrected may prolong policy problems. Pattern-based review can address repeated feed or site causes instead of repeatedly fixing only individual listings.
What to check next
- Use the “Needs attention” and “View fix” path to identify affected items and stated reasons.
- Remove or correct violating items and inspect related products for the same source pattern.
- Validate source, feed and destination changes before submitting a documented bulk appeal.
Sources & contributor credit
- Reporting or practitioner sourceSearch Engine Roundtable
Source cited in the published Week 40 newsletter. Article observation/reporting date is shown separately; this page’s original publication date is not inferred.
- Newsletter coverage · Paid Media Collective Week 40
Published edition used for story selection, copy, source credits and media; curation is distinct from original authorship.
Original creator unverified
Contributor roles follow the published newsletter and its linked evidence. Reporting, official discussion and visual authorship are kept separate; no independently unverified first-reporting priority is awarded.
Attribution evidence and limitations
Published story and credit line reconciled with the expanded article.
Original post, primary documentation and secondary reporting links retained.
Visible image content inspected for story relevance; image credit retained separately from reporting credit.
Attribution checked . This is a review date, not the original publication date.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.



