See exactly what Googlebot sees when it crawls your store. Get a scored report with 14 GMC-critical checks and actionable fixes.
Three simple steps to find out exactly why Googlebot may be flagging your store
Paste any page from your store, your homepage, a product page, or your checkout page.
Our tool fetches your page using Googlebot’s user-agent, just like the real crawler does.
Receive a score out of 10 with detailed results for all 14 GMC-critical checks and actionable fixes.
14 signals that Google Merchant Center uses to evaluate your store’s trustworthiness and compliance
Product, Organization & breadcrumb schema validation
Return, refund, shipping & privacy policy presence
Secure connection and valid certificate check
Viewport meta tag and mobile-friendly signals
Page title length, meta description and robots directives
Phone, email or contact page visibility to Googlebot
Scanning with Googlebot user-agent...
These signals directly affect your Google Merchant Center approval and shopping ad eligibility.
Full Fix Guide Appeal a SuspensionA Google crawler simulator fetches your store page using Googlebot's own user-agent and shows you the result exactly as Google receives it. That sounds simple, but it answers a question most store owners cannot answer on their own: does Google see the same page my customers see? When the answer is no, your Merchant Center account is at risk, and the gap is usually invisible until a suspension lands.
The simulator on this page checks 14 signals that Google Merchant Center uses to judge whether your store is trustworthy. It reads your title tag and meta description, looks for Product and Organization structured data, confirms your policy pages are reachable, tests your SSL certificate, checks the viewport tag for mobile readiness, and scans for contact information. Each check returns pass, warning, or fail, and the report scores the page out of 10 so you know where you stand in seconds.
None of this requires a login or a credit card. Paste a URL, and the tool crawls it the way the real Googlebot would.
Google Merchant Center does not review your store by hand. It reviews your store with a crawler. When a reviewer or an automated system checks your account, it reads the version of your page that Googlebot fetches, not the version your browser renders after every script has run. If a JavaScript app injects your return policy link after the page loads, or a geo-redirect serves a different page to crawlers, Google can miss signals that you can see clearly.
That mismatch is the root of many suspensions. A store flagged for misrepresentation often has policy pages that exist for humans but are unreachable for the crawler. A store flagged for circumventing systems often serves different content to Googlebot than to visitors. The simulator exposes both patterns before Google does.
The 14 checks map directly to the most common technical suspension triggers:
Run the simulator on three pages, not one. Start with your homepage, because that is the first thing a reviewer opens. Then scan a product page, because that is where structured data and pricing live. Then scan your checkout or cart page, because a broken checkout is a fast route to a website-quality suspension.
For each page, work through the failed checks first, then the warnings. Fix the issue, wait for your site to redeploy, and re-run the scan to confirm the check now passes. A clean run on all three pages means the technical signals Googlebot reads are in good shape.
The simulator is a page-level tool. It is the fastest way to catch a crawler-visibility problem, but it does not cover every account-level or feed-level policy. When you are preparing an appeal, or when you want the full picture, run the complete GMCSuspension audit, which checks 43 plus GMC policy requirements across your whole store and returns a step-by-step fix report in about 60 seconds. Shopify merchants can start with the free Shopify scan, and anyone facing an active suspension should read the full fix guide before submitting a review request.
In April 2026 Google switched Merchant Center reviews to a new AI verification flow. Instead of a reviewer opening your store in a browser, the system fetches your pages with Googlebot and runs a language model over the crawler view to score policy compliance. The store the AI sees is the store Googlebot returns, not the store your customers see in Chrome.
That changes the cost of every crawler-only failure. A policy page that loads cleanly for human visitors but renders blank to Googlebot is no longer just a search-engine indexing problem. It is the version of your store the AI grades when it decides whether to lift a suspension. The same applies to product pages where structured data does not match the rendered price, to checkout pages that hide content behind a script, and to contact pages where the phone number is an image rather than text.
Running the simulator on three pages before you submit an appeal answers the only question that matters in the new flow: does the version of my store the AI will read look like a compliant store? If the simulator returns warnings or fails, fix them before you appeal. The full breakdown of how the verification works and how to prepare for it lives in our 2026 AI verification guide.
A Googlebot simulator fetches your page using Google's crawler user-agent and shows you the HTML, structured data, and policy signals exactly as Googlebot receives them. It is the fastest way to spot a gap between what a human visitor sees and what Google sees, which is the gap that causes Merchant Center suspensions.
Google Merchant Center reviews your store using a crawler, not a human browser. If Googlebot cannot find your policy pages, your structured data, or your contact details, Google treats those signals as missing even when they are visible to you. A simulator surfaces that difference before it triggers a disapproval or suspension.
Yes. The GMCSuspension Googlebot simulator is free and needs no signup. Enter any URL from your store and it returns a scored report covering 14 GMC-critical checks in seconds.
It surfaces the technical signals that most often trigger a suspension: missing schema, absent policy pages, no SSL, blocked content, and mismatches between the page and the crawler view. For a full picture across all 43 plus GMC policy requirements, run the complete GMCSuspension audit.
The simulator focuses on one page and the 14 signals Googlebot reads on it. The full audit checks 43 plus policy requirements across your whole store, including feed-level and account-level factors, and produces a step-by-step fix report. Use the simulator for a fast page-level check and the audit before you appeal.
Yes. The new flow runs an LLM over the crawler view of your store, so any mismatch between what humans see and what Googlebot fetches now lands directly in the AI's input. Run the simulator on your homepage, a product page, and your checkout page before you appeal. The full AI verification guide covers the rest.