Questions, answered.

It's one of Google's Shopping policies and covers a broad set of trust signals. Examples include false urgency, claims you can't support, missing contact details, or inconsistent shopper-facing information. StoreVerifier can show public site evidence; it cannot say why Google made an account decision.

Read more: Check your store against the policy before a review, What is Google Merchant Center misrepresentation?

Yes. A scan shows the site-level risks it found instead of claiming to know Google's private suspension decision. The fix guides in the full report are written to help you build an appeal you can back up with evidence, not just "we think it's fixed."

Read more: How to fix Google Merchant Center misrepresentation, How to write a GMC reinstatement appeal letter

No. You can scan before submitting your store to Merchant Center, after making changes, or while checking a live store for new risks. The result is a snapshot of the site-level issues StoreVerifier can see when the scan runs; you do not need to wait for a suspension notice.

The active, documented, source-backed public-store checks across seven layers. That includes technical signals such as SSL, schema and redirects; rendered pages such as popups and timers; public policy, product, cart and checkout evidence; and visible consistency checks. Unsupported rules are withheld. The scan reports what it captured and could verify at that time. It does not inspect your Merchant Center account, product feed, payment processor, registry, or review-platform data.

Read more: Technical Compliance checks, Policy Compliance checks, Product & Catalogue checks

No. Scan any public store URL; no account connection is required. StoreVerifier does not connect to Merchant Center or compare a private product feed with live pages. If you use a feed, compare its prices, variants, shipping and return settings with the live store yourself.

Yes. The full report comes with 3 more scans of that store, in full, within 30 days of paying, so you can check your fixes before you submit an appeal. A free scan shows the counts and the same few small findings each time. On Daily Monitor, a check runs automatically every 24 hours.

Up to 1 a day, and 1 of any one store a day, whoever runs it. The count is kept for your internet connection, your account and the store, and starts again at midnight UTC. A free account is also limited to 3 scans a month. A store you have bought the full report for has its own allowance: 3 more scans in total, within 30 days after you pay.

Scan time varies with store size, server response time and how many pages can be reached. Keep the tab open; the progress view shows each of the seven layers as it finishes.

No. You can run 1 scan a day for free without signing up. You can also begin a one-off report purchase without creating an account first; the email used at checkout is then used to give you secure access to the report. An account is required for Daily Monitor and Manual Review.

No platform plugin or admin connection is required. StoreVerifier starts from the public store URL and reads the pages a browser can reach, so the important requirement is that the storefront and its policy pages load publicly — not which platform generated them.

It can identify a password gate or coming-soon page, but it cannot meaningfully review the store hidden behind it. For a useful scan, the storefront and its policy pages need to be publicly reachable. Remove the gate or launch the store, then run a fresh scan.

Read more: Technical Compliance checks

No. It may use public storefront controls such as add to cart to inspect the checkout, but it never signs in to your store admin, installs code, publishes changes, or places an order. It records findings; you decide which fixes to apply.

The wording checks run in the languages the capture supports, and the Languages and markets page lists every language and market we have tested and how far each one is covered. If your store is in a language that is not listed, the technical and structural checks still run, and the wording checks mark the gap instead of guessing.

Read more: Languages and markets the scanner reads

It says so, rather than reporting a clean result. The usual reasons are a site that is down, a bot challenge or firewall that blocks the capture, or an address that redirects somewhere unexpected. Check that the storefront and its policy pages load in a private browser window with no login, then run the scan again. If it still cannot get in, send us the address through the contact form.

Yes, completely. If the scan passes, there is no payment step or report charge. When it reports issues, you see the count and severity before deciding whether to buy the full report.

Every reported finding, ordered by priority, with the evidence captured, affected URLs where available, our reading, and a recommended next step. It also includes a short account-side checklist for facts the scanner cannot see. One-time payment covers the report and 3 more scans of that store, in full, within 30 days of paying; Daily Monitor is a separate monthly purchase.

After your first report, Daily Monitor schedules a daily re-scan of the same store. It costs $25 a month and repeats the public-store checks. An email only when a scan finds more issues than the one before. Cancel whenever; no minimum term.

The automated scan runs its documented public-store checks and reports what it can verify from the store. Manual Review adds a human compliance expert, a personalised remediation plan, and a 45-minute consultation call. It is a separate one-time service for cases that need judgement or a second pair of eyes.

Yes. A full report is for one store, with or without “www.”. It opens every finding in the scan you bought, and it comes with 3 more scans of that store, in full, within 30 days of paying, each one showing whatever has changed on the live site. A different store needs its own report.

Cancel from your Dashboard at any time. Monitoring continues until the end of the current paid billing period and then stops; there is no minimum term and no partial refund for the unused part of a billing period.

No. It re-scans your store every day, but it only writes to you when a scan finds more issues than the one before. A quiet inbox means the daily scan came back no worse than the last one, not that nothing ran.

Payments go through Stripe. Your card details are entered on Stripe's payment form and stay with Stripe; we never see or store them. Stripe keeps its own payment records where financial rules require it, which is why deleting your account removes your data from us but not the payment record from them.

No. A pass means the checks that ran did not detect an issue at that moment. It is not a Google approval, and Google may consider account, feed, or other information that is not available to the scan. Google's review decisions remain independent of StoreVerifier.

Detailed scan findings are kept for 90 days, then automatically cleared. A summary containing the score, URL, and scan date remains in account history. If you delete your account from the Dashboard, your profile, scan history, and reports are removed immediately; Stripe keeps its own payment records where financial rules require it.

No. StoreVerifier does not connect to your Merchant Center account or file a review request. The full report gives you captured evidence and fix steps so you can make the changes and submit your own appeal; Manual Review adds expert guidance, not appeal submission.

Read more: How to write a GMC reinstatement appeal letter

You see a verdict, how many findings there are, and how severe they are. If the store passes, that is the end of it and nothing is charged. If it reports issues, the free result names each finding and the layer that read it; the evidence, affected URLs and the step-by-step fix are in the full report, and you decide whether you want them.

Auto-fixable means the finding is mechanical: a technical or rendering problem a developer can correct without deciding anything about your business. Manual fix means someone has to make a call first, such as which of two return windows is the true one. The report flags each finding one way or the other, so you can hand the mechanical ones to whoever runs your site and keep the decisions for yourself.

Why Google made a decision about your account, because nobody outside Google can. Anything inside your Merchant Center account or product feed, because we do not connect to it. Anything behind a login or a password gate. And whether a stock count or a viewer count on your page is true, since that comes from your own systems; the scan can only show you what the page claims, and checking it against your analytics stays a merchant-side check.

Because the scan reads your store against Google's Merchant Center policies, not against the law where you trade. Google can be stricter than the law, and stricter in different ways for different countries. A claim that is lawful can still be a misrepresentation finding under Google's rules, and a suspension is Google's decision, not a court's. If a finding names a policy, read the policy it names before deciding it does not apply to you.

Because the scan could not read the page well enough to be sure, and it marks blocked or unclear evidence instead of guessing. The usual causes are a bot challenge that stops the capture, a page that serves one thing to a crawler and another to a shopper, or wording in a language the capture does not support. It is a gap in what we could see, not a finding against you. Check that the page loads publicly, then run a fresh scan.

No. StoreVerifier is completely independent: no partnership and no access to Google accounts or private review systems. It reads public storefront pages and policy material.

Tell us. Automated checks can be wrong. Use the contact form and include the evidence you think the scan missed. If we cannot reproduce a paid-report finding, request a full refund within 30 days.

Not on your behalf. We never submit anything to Google for you, report your store, or tell anyone you ran a scan. One check does send Google the store's address: we look it up in Google's Safe Browsing list of unsafe sites, the way a browser does. The companies that handle any of your data for us, such as Stripe for billing, are all named in the Privacy Policy.