Googlebot vs Chrome Diff

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.

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.

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.

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.