3 min read
In brief
- Redesigns trigger suspensions because they change the things Google compares — policy page URLs, business details in the footer, checkout structure, and sometimes the domain itself.
- The suspension is rarely about the new design being worse; it is about the account and the site no longer matching each other.
- A rollback is the wrong first move. Capture what the crawler sees now, fix the mismatches, and keep the design.
Why a redesign breaks an account
Merchant Center is a comparison engine with a long memory. It holds your business details, your policy pages, your prices and your checkout behaviour, and it periodically re-checks them against the site. A redesign can change all four in an afternoon.
The most common breakage is mundane: policy pages moved and the old URLs now 404, the footer lost the registered address, the contact page became a form with no email, the checkout moved to a different subdomain, or prices now display in a different currency format. None of these look like a redesign problem to the person who did the redesign.
- Policy URLs changed without redirects — the crawler lands on a 404 where a refund policy used to be.
- Business name or address edited in the footer during a copy pass, so the site no longer matches the Merchant Center account.
- A new checkout flow that hides shipping cost until later, or applies tax differently.
- A migration that changed the domain, the subdomain structure, or the trailing-slash behaviour of product URLs.
- Product pages rewritten by a new theme, dropping the structured data that used to carry price and availability.
What to compare, in order
- 1
Footer and contact details
Business name, address, phone and email against the Merchant Center account, character by character. This is the mismatch that produces a misrepresentation finding rather than an item disapproval.
- 2
Policy pages
Every policy URL that existed before the redesign should still resolve. If it moved, redirect it permanently — do not rely on the new navigation alone.
- 3
Product page data
Price, availability and currency as rendered, and in the structured data. A theme that drops structured data leaves Google comparing the feed against nothing.
- 4
Checkout behaviour
Shipping cost, tax and currency at the point of payment, against what the product page promised.
- 5
Domain and URL structure
Any change here is a change to what the account thinks it is advertising. Claim the domain, and update the feed's landing page URLs.
Recovering without reverting
A rollback restores the old site and, if the redesign was not the cause, wastes the work. Worse, a second large change in a fortnight gives a reviewer two candidate causes and no way to distinguish them.
The better sequence is to freeze the new design, fix the mismatches it introduced, document the change in one page, and make a single request that names the redesign and each fix. Reviewers can evaluate that. They cannot evaluate 'we changed everything back'.
Keep the deploy log
The date of the redesign, the theme or platform version, and the list of changes is the most useful document in this recovery. It is what turns 'we do not know what happened' into a dated cause.
A redesign does not fail because it is new. It fails because the account and the site stop agreeing. Compare the five surfaces, fix what the design broke, keep the design, and make one request that names the change and the fixes.
