Understand the suspension: what it really means
A suspension usually signals that Google sees a high-risk combination of trust, policy clarity,
and data consistency issues. It’s rarely a single “technical flag”.
The fastest recoveries treat the store as an ecosystem: site + product pages + policies + structured data + feed.
Objective: make the experience self-explanatory. A reviewer should understand in ~30 seconds: who sells, how shipping works, how refunds work.
First 24 hours: what to do (in the right order)
- Stop random changes: don’t change theme + pricing + feed simultaneously without tracking.
- Read the exact policy name in Merchant Center diagnostics (wording matters).
- Map your perimeter: domain, subdomain, checkout domain, policy URLs, tracking.
- Validate core pages: contact/support, returns/refunds, shipping, terms, privacy/cookies.
- Sample product pages: check price/stock consistency across UI + markup + caching.
- Only after site trust is clean: adjust feed attributes and scale fixes.
Rule of thumb: if the site is not review-proof, feed-only work often won’t recover the account.
Trust signals & policy pages: what matters most
Policy pages aren’t “legal bureaucracy”. They are trust signals that reduce ambiguity and make your store verifiable.
They must be public, readable, and linked from the footer (and ideally from key pages).
Pages that must always be accessible
- Contact/support: real email/helpdesk, response expectations, seller identity references.
- Returns/refunds: timeline, conditions, process, exceptions, who pays return shipping.
- Shipping: costs, delivery times, carriers, tracking, serviced areas.
- Terms + privacy/cookies: consistent with checkout and tracking behavior.
Common trust mistakes
- Policies exist but are hard to find, thin, or broken.
- Returns/refunds are generic or contradictory.
- Corporate domain and store subdomain feel like two different companies (no clear cross-links, inconsistent identity).
- External checkout without clear explanation.
Product page consistency: price, stock, condition
A common recovery blocker is a contradiction between what the user sees and what Google reads.
Top causes: variants, dynamic JavaScript pricing, caching/CDN, and duplicated structured data.
Fast checks on one product page
- Price: visible price matches structured Offer price and feed price (currency + taxes).
- Availability: UI matches Offer availability.
- Variants: switching variants updates price/stock (and doesn’t leave stale markup).
- Condition: new/used/refurbished is explicit and consistent.
- Decision support: warranty, returns and shipping are easy to reach from the product page.
Operational tip
If multiple apps/plugins output Product JSON-LD, you may have two Products with different Offer values.
Even when the page looks fine, Google can read the contradiction. Reduce to one authoritative source.
Feed red flags that re-trigger the issue
Once trust and product pages are stable, move to feed cleanup with discipline.
Test on a small sample before mass updates.
Top 10 feed issues during recovery
- Wrong condition or inconsistent with the product page.
- Price mismatch (sale price, currency, tax settings).
- Availability mismatch (stock propagation delays, variant mapping).
- Non-compliant images (watermarks/overlays/placeholders).
- Missing/invalid GTIN/brand where required.
- Shipping attributes not aligned with your shipping policy page.
- Misleading titles/claims that hide condition or constraints.
- Duplicates and broken variant grouping.
- Destination URLs that redirect/404/geo-redirect or get blocked.
- Large catalog changes without sample testing.
Full recovery checklist
Use this as a work plan: trust & policy first, product pages second, feed third.
A) Trust & policy
- Contact/support works and is easy to find.
- Returns/refunds are specific and consistent.
- Shipping costs/timelines match the policy page.
- Terms + privacy/cookies are accessible and updated.
- Seller identity is consistent across domain/subdomain.
B) Product pages
- Visible price = Offer price in structured data.
- Visible stock = Offer availability.
- Variants: price/stock coherent per variant.
- Condition is explicit and consistent.
- Warranty/returns/shipping reachable from the product page.
C) Feed
- Images compliant and accurate.
- Brand/GTIN/SKU correct where applicable.
- Shipping/tax coherent with policies.
- Variants mapped correctly (no duplicates).
- Sample test 10–20 items before full updates.
D) After recovery
- Keep a changelog of fixes.
- Run an audit after theme/checkout/plugin changes.
- Reduce duplicate structured data sources.
- Automate price/stock consistency checks where possible.
Prevention: the 30-minute monthly check
Stability comes from routine. Run this once a month and after major deployments.
- Open 3 product pages: bestseller, a variant product, a promo product.
- Verify visible price/stock and check for obvious structured data contradictions.
- Confirm policies are reachable: returns/refunds, shipping, contact/support.
- Spot-check 3 feed items (title, image, condition, shipping).
- Repeat after theme/checkout/pricing/plugin changes.
Want to find the critical issues before requesting a review?
Generate a free report: trust signals, policy visibility, product-page consistency and feed/schema red flags — in ~60 seconds.