Googlebot vs Chrome Diff
Fetch the page twice in parallel, one with Googlebot UA, one with Chrome. We compare HTML, words, title, H1 and tags. The diff reveals cloaking or JS-only rendering.
URL to diff
Two fetches in parallel. Googlebot UA vs Chrome desktop.
Also worth exploring
All toolsTest your robots.txt against 18 user-agents: Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot, Applebot and other AI crawlers. Path × bot matrix.
Verify your hreflang tags: valid ISO codes, reciprocity between language versions, x-default, conformance with Google's recommendations.
Inspect HTTP response headers: x-robots-tag, cache-control, HSTS, link, vary, server. SEO + security annotations on impactful headers.
Validate your sitemap.xml: structure, URL count, lastmod outliers, sitemap-index recursion. Conforms to sitemaps.org and Google.
Frequently asked questions
What is cloaking? +
Serving different content to Googlebot vs real users, forbidden by Google guidelines and heavily penalized when detected. Cloaking is rarely intentional, it is often a side effect of a CDN that serves a different cache per UA, a WAF firewall that blocks bots, or a misconfigured A/B test that excludes crawlers. This tool detects divergences without judging, it is up to you to investigate whether it is intentional or a bug.
Very low HTML size on Googlebot side, is it bad? +
Often yes. Three typical cases: (1) Client-side JS rendering, the app loads an empty HTML skeleton then hydrates with React/Vue/Svelte. Googlebot sees the skeleton, the user sees the app. If Google does not trigger rendering (which costs compute), your page is invisible. Fix: SSR or pre-rendering. (2) Anti-bot WAF that serves a minimal page to crawlers. (3) UA-specific CDN cache, typical of aggressive anti-scraping sites.
My tool detects a different title/H1, is it a problem? +
Possibly intentional cloaking (bad idea), or more often an A/B test bug, UA-based personalization, a stale cache fragment. Either way: Google will index its own version of the title, so if it is not optimized while the one served to users is, you lose in SERPs.
Which Googlebot UA do you use? +
This tool uses Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html), the main desktop bot. To test Googlebot mobile (now dominant via mobile-first indexing), change the UA in your dev server. This tool only tests desktop, but 95% of problems already show up at that level.
Actually buying backlinks?
Our network catalog is browsable without signup. Publisher pricing shown, no commission, no middleman.