Why this page exists
The site already has GMC misrepresentation and identifier tooling. This page packages those checks into a suspension timeline without promising reinstatement.
Build a Google Merchant Center suspension evidence pack covering policy pages, product data, feed diagnostics, account links, Google Customer Reviews, appeal timeline, and proof screenshots.
Policy, contact, identity, product page, schema, price, availability, or merchant trust proof is weak or inconsistent.
Run public-page precheckFeed evidence firstAffected-products CSV, item count, feed diagnostics, GCR, product URL, or feed owner evidence is part of the suspension context.
Build feed evidenceSuspension owner mapPublic trust proof, feed diagnostics, account screenshots, and appeal history disagree before the next response.
Send store URL firstThe site already has GMC misrepresentation and identifier tooling. This page packages those checks into a suspension timeline without promising reinstatement.
Shopify and ecommerce merchants dealing with Merchant Center suspension, misrepresentation, account warnings, product disapprovals, or appeal preparation.
Merchant Center suspension work can start from trust proof, feed diagnostics, identifiers, Google channel account state, or appeal timeline. Route the case by evidence, not panic.
Policies, contact details, business identity, price, availability, schema, or merchant proof may not be strong enough for review.
Run the GMC public-page precheckFeed or product evidence gapAffected-products CSV, item count, feed diagnostics, product URLs, GCR, or feed ownership needs to be organized before appeal.
Build Google channel evidenceIdentifier row issueSuspension or disapproval evidence includes invalid GTIN, missing identifiers, MPN, brand, barcode, or identifier_exists rows.
Group identifier evidenceSuspension owner mapPublic trust proof, feed diagnostics, affected-products rows, account screenshots, support replies, and appeal timeline need one review packet before another response.
Send store URL firstFeed sync root causeThe account problem may be downstream of product count mismatch, stale feed fetches, app inclusion, or Content API ownership.
Trace the sync owner firstThe report connects each visibility problem to crawl evidence, AI answer samples, competitor risk, and a concrete repair step.
Policy edits, feed fixes, screenshots, account settings, and support messages need one timeline so reviewers and support teams can follow the case.
A clean policy page does not fix product data, and clean feed rows do not fix merchant trust. Suspension work needs both tracks.
Start with a store-URL-first Google Truth owner map when public merchant trust proof, affected-products CSV rows, feed diagnostics, Google channel account state, GCR evidence, and appeal timeline disagree. Move to a reviewed Google Truth Snapshot only when the unresolved gap depends on private screenshots, account state, or a cross-system evidence conflict.
Use this packet when Merchant Center warnings, product disapprovals, GCR state, public trust proof, and appeal history are mixed together. The goal is to separate what Google can verify publicly from what needs private screenshot review.
Use this when a suspension, warning, disapproval, or appeal response depends on public trust pages, feed diagnostics, account state, GCR, and repair history at the same time.
Attach public URLs, affected-products CSV, diagnostics screenshots, account-link screenshots, Google channel state, GCR status, support replies, and dated repair notes.
Decide whether the next owner is public merchant trust, product/feed data, Google channel account state, GCR evidence, appeal wording, or a focused suspension evidence pack.
This is the public surface a reviewer can verify without private access, so it should be separated from account screenshots.
This shows whether the suspension context includes item-level data quality, feed ownership, or landing-page mismatch.
This keeps account configuration, GCR, and Google channel state out of generic policy-page edits.
This turns scattered screenshots into a chronological file that can be reviewed before another appeal or support handoff.
Suspension evidence timeline:
Public trust proof: contact/About/business identity URLs; shipping, returns, refund, warranty, price, availability, and policy screenshots.
Product and feed evidence: affected-products CSV, diagnostics screenshot, feed name, item count, destination, last fetch time, sample product URLs.
Account and Google channel state: domain claim, website verification, Google & YouTube app or feed app state, linked accounts, MCA/subaccount context, GCR status.
Appeal timeline: warning date, repair date, screenshot date, appeal submission date, support replies, and remaining evidence gaps.
Decision needed: public merchant trust, product/feed data, Google channel account state, GCR evidence, appeal wording, or focused suspension evidence pack.A useful evidence pack reads like a timeline, not a pile of screenshots. It should show what Google could verify publicly, what Merchant Center received, what changed, and what still needs owner review.
Start with contact, About, business identity, shipping, returns, refund, warranty, price, availability, and policy pages that a reviewer can see without private access.
Add affected-products CSV rows, feed diagnostics, item counts, identifiers, product URLs, images, price, availability, and last fetch timing.
Document domain claim, website verification, Google & YouTube app state, Content API source, GCR status, linked accounts, and any MCA or subaccount context.
List warning date, repair date, screenshots captured, appeal message, support replies, and what changed before each submission.
Use the free pages for visible public checks and organized intake. Start the owner map when public trust proof, feed diagnostics, account state, screenshots, several Google channel symptoms, or the next appeal message need one routing decision.
Good enough when the suspected issue is visible merchant trust proof, policy clarity, product page consistency, or schema drift.
Best when affected-products rows, item count, feed app ownership, GCR evidence, or product URLs need one Google channel file.
Useful before another appeal when screenshots, account links, diagnostics, and public evidence need triage before a full reviewed snapshot.
Reserve this for stores with account review, repeated disapprovals, appeal history, or cross-system repairs that require a support-ready timeline.
Use the $79 reviewed Google Truth Snapshot when one unresolved blocker needs a second pass. Move to a $299+ focused suspension evidence pack only when the case needs a support-ready timeline across public URLs, feed rows, private screenshots, account state, and appeal history.
Best for one unclear decision: whether the next owner is public merchant trust, product/feed data, Google channel account state, GCR evidence, appeal wording, or a focused suspension evidence pack.
Attach store URL, warning or suspension date, affected-products CSV, diagnostics screenshot, Google channel or feed app state, GCR status, public policy URLs, two product URLs, and the next appeal question.
Best when the evidence crosses repeated disapprovals, account review, support replies, policy repairs, feed diagnostics, domain verification, GCR, screenshots, and a dated appeal change-log.
Prepare the full timeline: warning date, repair date, screenshot date, appeal submission date, support response date, public trust proof, product/feed evidence, account-link proof, and remaining gaps before the next response.
A public trust precheck is not the same as an account evidence file. Escalate only when the evidence crosses public pages, feed diagnostics, account state, and appeal history.
| Workflow | Best for | Evidence required | Boundary |
|---|---|---|---|
| GMC public-page precheck | Visible trust, policy, contact, product, schema, price, and availability issues | Public URLs and storefront evidence | No account-state review |
| Feed Truth report | Product feed, item count, affected rows, GCR, identifier, and feed ownership issues | Shopify export, GMC diagnostics, feed app mapping, product URLs | No reinstatement promise |
| $79 reviewed Google Truth Snapshot | Private screenshots and cross-system evidence before another appeal or focused audit | Account screenshots, CSV rows, public URLs, support messages, timeline | One-page review map only |
| $299+ focused suspension evidence pack | Repeated disapproval, account review, appeal timeline, or support handoff | Full change-log, screenshots, policy proof, feed evidence, appeal history | Still no reinstatement guarantee |
The pack improves evidence quality and repair order, but Google controls suspension decisions and appeal outcomes.
Include policy pages, contact and business identity proof, affected-products CSV, feed diagnostics, product screenshots, account-link status, domain verification, and an appeal timeline.
It includes misrepresentation evidence, but adds feed, account, GCR, domain, appeal, and change-log evidence so the case is easier to review.
No. It cannot guarantee reinstatement. It helps organize what changed, what evidence exists, and what gaps should be fixed before another appeal.
Request one when the decision depends on private Merchant Center screenshots, account links, feed diagnostics, appeal history, or several Google channel symptoms at once.
Start with a store-URL-first Google Truth owner map when public merchant trust proof, affected-products CSV rows, feed diagnostics, Google channel account state, GCR evidence, and appeal timeline disagree. Move to a reviewed Google Truth Snapshot only when the unresolved gap depends on private screenshots, account state, or a cross-system evidence conflict.