Review changes where they enter the system.
Identify who controls product prices, stock, variants, and delivery settings. If several apps or people can update them, document which system owns each field. After a change, check the values actually reaching Merchant Center.
Use the product data specification for the relevant attributes. Avoid invented identifiers and confirm that each value refers to the correct item and variant.
Use representative checks, then expand when needed.
A small, consistent sample can reveal a broken integration or template. Include a standard product, a variant, a discounted item, and an item with different shipping conditions where those cases exist. If the sample reveals a recurring problem, expand the review to the affected products.
| When something changes | Check the following |
|---|---|
| Price or promotion | The submitted value, product page, cart, and promotion conditions. |
| Stock or supplier | Availability and whether the order can actually be fulfilled. |
| Shipping or returns | The published terms, delivery estimates, destinations, and charges. |
| Theme or app | Policy links, product details, access, and checkout behavior. |
| Business details | The website, account fields, support information, and relevant records. |
Keep policies connected to real operations.
Ask the people handling orders and support whether the website still describes the process accurately. Delivery promises, return instructions, and support availability should not be left behind when operations change.
Google’s misrepresentation policy addresses concealed transaction conditions and misleading offers. Make important conditions understandable before the customer commits, and check that the experience matches the stated terms.
Add a short check before store changes go live.
For a theme release or integration update, identify which parts of the buying journey may be affected. Test the relevant pages and checkout, then verify product data after the change. Keep a rollback or correction owner for any issue found.
Document what was tested and any limitations. A complete desktop check does not establish that the mobile menu, a regional checkout, or every variant behaves the same way.
Give notices and review tasks an owner.
Choose who monitors Merchant Center and who can act on policy or verification requests. Preserve important notices, dates, and task outcomes in a shared business record.
If a restriction appears, stop treating the routine as sufficient evidence of compliance. Review the actual issue and use the current account process. The ongoing log helps the investigation by showing what changed and who can explain it.
Common questions.
How often should we run these checks?
Choose a cadence based on how often products, prices, policies, and integrations change. High-change stores need more frequent checks than stable catalogs. Review affected areas whenever a material change is released.
Can automated feed updates replace a store review?
Automation can keep fields synchronized, but it does not establish that the business information, policy wording, and checkout experience are accurate. Check the actual output.
Does a checklist guarantee that the account stays approved?
No. It helps your team maintain accurate information and investigate issues. Google can still review the account and apply its policies.
Go to the source
Official policies & guidance.
Google’s requirements are linked below. The review steps on this page are RID Marketing’s practical guidance, not an exhaustive Google checklist. Sources checked September 24, 2026; follow any newer instructions in your account.