Contents 10
A Merchant Center suspension for Misrepresentation usually calls for a review of the whole buyer journey and of your business identity, not just a rewrite of product descriptions. Google's policy states plainly that the assessment can look at promotional materials, the website, accounts and third-party sources (Misrepresentation). So the audit should be built broadly: who you are as a company, whether contact details match, whether the full cost and payment terms are disclosed, whether shipping, returns and refund terms are easy to find. Product data remains part of the picture, since the title and description have to describe the product accurately and match the landing page (product data specification), yet on their own they do not cover every account-level check.
What Google means by Misrepresentation
The policy sets expectations fairly broadly: offers must be accurate, realistic and truthful, and material information has to be disclosed before the user commits (Misrepresentation). This is not a requirement for one feed attribute; it is a requirement for the integrity of what the shopper sees and agrees to.
Among the examples Google lists as prohibited are a false business identity or untruthful contact details, misleading claims about affiliation, unavailable offers, hiding the full cost or payment terms, and shipping, returns and refund terms that are unclear or hard to find (Misrepresentation). Each of those has a very concrete counterpart on the site, and that is where an audit yields the most material.
The recommendation part of the policy is just as specific. Google advises keeping contact information current, describing the business clearly, using your own branding, being transparent about affiliate status, delivering what shoppers paid for, and submitting a thorough and accurate appeal (Misrepresentation). The wording about "your own branding" and "affiliate status" matters especially for dropshipping and reseller models, where the shop is effectively working with someone else's assortment.
How the site, feed, account and business signals interact
Google's help documentation splits issues into product level and account level. Product-level issues can stem from a mismatch between submitted data and site content, or from violations of the specification or policies, while account-level issues affect all products (issues in Merchant Center). For a shop owner that means something simple: if the status applies to the account, sifting through individual SKUs is unlikely to change anything until the general signals have been checked.
Website problems, per Google, include placeholder text, broken links, missing or inconsistent information, inaccurate descriptions, blocked crawling, unavailable pages and generic redirects (issues in Merchant Center). Part of that list looks technical, but it reads as a question of trust: a page that redirects to the home page instead of the product, and a page carrying demo text straight out of the CMS, both break the match between the promise in the feed and reality.
The specification adds another layer. Data must be accurate and correctly formatted, the title and description must describe the product and match the landing page, and the link must point to a verified domain with no interstitial page unless one is legally required (product data specification). Language or region selection pop-ups, consent windows that cover the product page, or a hop through a tracking domain are all worth checking in exactly this context.
Account level versus product level
The practical takeaway: first work out which level the issue sits at, and only then decide on the scope of work. Google describes account-level issues as visible through the Products and Needs attention sections and through the settings and policies view (request a review), while Needs attention generally serves as the place where issues surface (issues in Merchant Center).
| Signal | Where to look | What to watch for |
|---|---|---|
| Business identity | Site, About and Contact pages | Legal entity name, address, working contact channels, consistency with account data (policy) |
| Terms of the deal | Product page, cart, checkout | Full cost, payment terms, shipping, returns and refunds before the point of commitment (policy) |
| Feed to site consistency | Feed and landing pages | Title and description matching the product on the page, verified domain in link (specification) |
| Page availability | Logs, spot checks of URLs | Broken links, unavailable pages, generic redirects, blocked crawling (issues) |
| Account readiness | Merchant Center settings | Shipping where required, a feed for the target country, a claimed and verified URL, a verified address (issues) |
What to check before requesting a review
Google lists the prerequisites for a review: shipping set up where applicable, a feed for the target country, a claimed and verified URL, and a verified business address (issues in Merchant Center). It separately notes that the feed must not be empty, and that in some cases identity verification may be needed (request a review).
Close these items before you press the request button, not alongside it. The logic is simple: if the basic conditions are not met, an audit of site content never becomes relevant.
Before the main pass, open the shop as a new customer in a browser where you are not signed in. Check mobile and desktop, switch the delivery region, and add a product to the cart. This is an editorial check, not a separate Google requirement. It helps expose the discrepancies a shop owner misses in a familiar session: an automatic currency, a hidden mandatory charge, an unavailable shipping method, or a policy that only appears after login. Record the URL, the step and the actual text on screen rather than your impressions. That makes the issue easier to reproduce once it has been fixed.
Step by step audit
The sequence below is an audit method, not an official Google procedure. It orders the checks that follow from the help pages cited here.
- Record the starting state. Write down exactly which issues the account shows and at which level, using Products, Needs attention and the settings and policies view (request a review). Screenshots and dates will come in handy later when you describe the fixes.
- Match the genuine business name, address and working contact details across the website, Merchant Center and payment profile. Google’s current review guidance asks for accurate business information to be visible on the site. Do not substitute an invented address for the actual operating or shipping location. Complete identity verification before appealing when the account requests it. Google Merchant Center Help ↗
- Describe what the business does. Google advises a clear business description and your own branding (Misrepresentation). If the site was built on a template carrying someone else's logos or leftover demo content, clear that out. Treat the uniqueness of supplier-provided descriptions separately, as an editorial and SEO recommendation, rather than presenting duplicated text itself as a Misrepresentation violation.
- Disclose affiliate status. If you sell someone else's assortment, operate as a reseller or have affiliate relationships, the policy expects clarity about it (Misrepresentation).
- Walk the buyer journey to the end. From the product page to order confirmation, look at when the shopper first sees the full cost and the payment terms. Hidden fees and late disclosure of costs are among the examples in the policy (Misrepresentation).
- Check how visible the shipping, returns and refund terms are. The policy calls out unclear or hard-to-find terms as a separate example (Misrepresentation). The audit method here: try to reach those pages from the product page in as few clicks as possible and without using site search.
- Compare the feed against the site on a sample. Take a representative set of products and match title, description and link against what the user sees. The title and description must correspond to the product and the landing page, and link must point to a verified domain with no interstitial page except where legally required (specification).
- Check that offers exist and are available. Unavailable offers are named among the prohibited examples (Misrepresentation), and unavailable pages and generic redirects appear among website problems (issues in Merchant Center).
- Remove technical barriers. Blocked crawling and broken links belong to the same list (issues in Merchant Center), so check
robots.txt, whether product pages are reachable by the crawler, and whether response codes are correct. - Handle data quality separately. For disapprovals tied specifically to product data quality, Google maintains a dedicated help article on resolving them (fixing data quality disapprovals).
- Close the review prerequisites. Shipping, a feed for the target country, a claimed and verified URL, a verified address (issues in Merchant Center), a feed that is not empty, and readiness for identity verification if it is requested (request a review).
Large scale diagnosis through the API
With a big assortment, manual sampling can miss systemic discrepancies. The Merchant API lets you retrieve product data together with the list of issues and filter disapproved products programmatically (Merchant API). This is an optional way to speed up diagnosis, not a condition for getting the account back. The practical value is that you see how issues are distributed across categories, brands or page types, and can fix the cause rather than individual listings.
What to do after the fixes
Google describes the review option as appearing either in the product details or in the account issues, with the merchant able to choose "I fixed the issue" or "I disagree with the issue" (request a review). Choose between them deliberately. The first means the changes are already in place and publicly visible. The second fits when you believe the assessment is mistaken, and in that case Google may ask for the reason for the appeal or for documents (request a review).
The policy recommends submitting a thorough and accurate appeal (Misrepresentation). A method that makes this easier: prepare a short list of what exactly changed, with links to the specific pages, and make sure every change is already published rather than planned. A description along the lines of "we updated the site" gives the reviewer less to work with than a list of sections with concrete URLs.
Once the request is submitted, avoid starting new structural changes to the site, because the state you described and the state that gets reviewed may drift apart. If further edits are needed, log them separately. The outcome of a review can vary, and phrasing such as "fixing this particular item will restore the account" has no backing in the help documentation: Google describes the assessment criteria, while the specific conclusion depends on the state of the whole account.
Keep in mind separately that an account can carry several issues at once. Account-level issues affect all products, while some discrepancies apply only to individual items (issues in Merchant Center). Closing one category does not automatically clear another.
Checklist before requesting a review
- The business address is verified in Merchant Center where the account review requires it (issues); the name and the public contact channels the shop advertises on the site are accurate and working (policy).
- The site carries a clear description of the business, uses your own branding, and discloses affiliate or reseller status (policy).
- The full cost, fees and payment terms are visible before the shopper commits (policy).
- Shipping, returns and refund terms are stated clearly and reachable from the product page (policy).
- Feed titles and descriptions match the products and the landing pages, and links point to a verified domain without unnecessary interstitial pages (specification).
- There is no placeholder text, no broken links, no unavailable pages, no generic redirects and no blocked crawling (issues).
- Data quality disapprovals have been handled per the dedicated help article (fixing disapprovals).
- Shipping is set up where applicable, the feed matches the target country, the URL is claimed and verified, and the business address is verified (issues).
- The feed is not empty, and you are ready for identity verification (request a review).
- A description of the fixes is prepared with specific pages, and all changes are published before the request is submitted (request a review).
Related UPLIFY resources
Document a problem, not just a score
This is a UPLIFY working template, not an official Google form. One row represents one reproducible problem. Add it to the change log, then verify the result without signing in on mobile and desktop.
On mobile, scroll the table horizontally.
| Where | What to record | Completion criterion |
|---|---|---|
| Account | Exact issue, level, country and date | The owner understands what Google is reviewing |
| Page | URL, shopper step and actual visible text | Another specialist can reproduce the issue |
| Product data | Product ID and values in source and on site | The discrepancy is fixed in both locations |
| Work | Owner, correction and publication date | The shopper sees the change, not just the admin |
| Readback | URL or screenshot after the correction | Result and remaining limitations documented |
Questions before an appeal
Is rewriting product descriptions enough?
Not always. Misrepresentation can concern how the store presents its business and purchase terms, not just titles or descriptions. Check offer accuracy, genuine contacts, total cost and product availability. Then compare the product data source with landing pages. Do not substitute bulk text generation for diagnosing the whole shopper journey and the account’s actual issues.
Why is Request review greyed out?
Open the issue details in Needs attention: identity verification, a non-empty product source or the end of a waiting period may be required. Follow the message and date in your own account. Do not send identity documents through third-party links in unverified emails. Complete the required actions, record the status and use official Google help if the reason is unclear.
How long does an account review take?
Official guidance gives an indication of up to seven business days; complex reviews can take longer. That is not an agency’s guaranteed reinstatement deadline. Monitor Google’s status and emails, retain the submission date and describe published corrections. If your account notification specifies different conditions, follow them and clarify the next step through official support rather than relying on a vendor’s promise.
Can an agency guarantee reinstatement?
No. An audit can identify supported findings and help prepare corrections, but Google retains the decision. Agree the review and implementation scope with a vendor, not a guaranteed account status. Request findings with evidence, owners and completion criteria. After implementation, verify the changes again. The conclusion should explicitly state uncertainty, incomplete access and remaining risks rather than hide them behind a score.
What should I prepare for a Merchant Center audit?
Prepare the store URL, exact issue notification, target countries and available product data. Grant access through standard invitations rather than sending passwords or identity documents in an open chat. Before paying, agree which pages, feeds and settings are included. The UPLIFY audit page explains the scope, price and sample report; implementation is not automatically included in an audit.
Need help with Merchant Center?
Commission an audit of the store, product data and settings. Receive evidence-backed findings, a prioritized plan and review limitations. Implementation and appeal preparation are scoped separately; we do not guarantee Google’s decision.