SSR Inspector

SSR Inspector — Server-Side Rendering & SEO Audit for Any Website See exactly what Googlebot and other crawlers can and cannot see on your page. SSR Inspector runs a 3-way comparison between your live browser DOM and the raw HTML served by your server alongside the Google-rendered HTML from GSC URL Inspection or the Rich Results Test. The extension highlights the exact content Google is missing right on the page. If Google can't see your content, it can't rank it in Search or cite it in AI answers from generative search engines. SSR Inspector finds those gaps in seconds. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHO THIS IS FOR ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • SEO specialists auditing JavaScript-heavy websites • Developers debugging server-side rendering and hydration issues • Technical SEO consultants running SSR audits for clients • Marketing teams verifying that Googlebot can read their content • Anyone doing GEO and AEO work (Generative Engine Optimization) who needs to check LLM crawler visibility ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT PROBLEM THIS SOLVES ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Modern websites built as single-page applications and JavaScript-rendered apps often render content client-side. Your users see the page correctly in their browser. Googlebot may see an empty shell. The debate of server-side rendering vs client-side rendering matters because every major search and AI crawler has limits on JavaScript execution during crawling. Content that appears only after JS runs can be completely invisible to search engines if your SSR setup isn't working. This includes product listings rendered after the initial paint. It includes prices fetched by client-side scripts. It includes review widgets loaded asynchronously. It includes FAQ answers populated from APIs. And it includes schema markup injected by JavaScript helpers. Common SSR and rendering problems this extension detects: • Content rendered client-side that never makes it into Google's rendered HTML • Hydration mismatches between server HTML and the client-rendered DOM • Missing H1 and H2 headings that Google can't see • Schema markup (JSON-LD) that exists in your browser but not in Google's view • Canonical URL drift between your live page and Google's crawled version • Internal links added by JavaScript that crawlers miss • Property listings or product cards that fail to render for bots • Review widgets that load too late for search engine indexing • Dynamic rendering vs server-side rendering discrepancies • React server-side rendering issues with dynamic content • Framework-level SSR gaps that hurt SEO when hydration breaks • Mobile vs desktop content parity issues that hurt mobile-first indexing ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ HOW IT WORKS — 3-WAY RENDERING COMPARISON ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SSR Inspector compares three HTML snapshots for any URL: 1. RAW HTML — The HTML your server sends before any JavaScript executes. This is what a simple crawler sees first. SSR Inspector fetches this using the User-Agent you choose. 2. LIVE DOM — Your browser's fully-rendered HTML after all JavaScript has run. This is what your human users see. 3. GOOGLE-RENDERED HTML — The HTML produced by Google's Web Rendering Service. You paste this from Google Search Console URL Inspection (View Crawled Page → HTML tab) or from the Rich Results Test (View Rendered HTML). The extension runs a detailed diff across these three snapshots and shows you: ✓ Content visible in Google's rendered HTML (green outlines) ✗ Content in your browser that's missing from Google's view (red outlines) ⚡ JavaScript-added content that Google successfully rendered (blue outlines) ⚠ Content in raw HTML that Google's renderer dropped (yellow outlines) Every difference is outlined directly on the page just like Chrome DevTools inspect mode. Click any item in the side panel to scroll to it on the page with a flashing highlight. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ KEY FEATURES ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ► Mobile vs Desktop Parity Audit Google indexes the mobile version of your pages by default. Content served only to desktop crawlers is invisible for ranking. SSR Inspector runs an automatic parity check whenever you audit with a Googlebot user-agent. The extension fetches both mobile and desktop versions and surfaces every difference. A dedicated parity tab shows what's only on desktop (the mobile-first indexing risk) alongside what's only on mobile and where rich-result eligibility could be lost. ► User-Agent Switcher Test your page with multiple crawler user-agents. Google's mobile crawler is the default since mobile-first indexing went live. The dropdown also includes Google's desktop crawler for comparison. Search engine bots from Bing are available for cross-engine checks. LLM crawlers from major AI assistants are included so you can verify your content is accessible for generative search citations. You can also paste any custom user-agent string. This feature is essential for validating that all major crawlers can access your content and for detecting cloaking. ► Auto-Opening Side Panel Click "Run audit" and the detailed audit panel opens automatically alongside your page. Live progress shows as the audit runs through each stage. There's no two-step "click to open panel" workflow. ► Detailed Side Panel Audit Nine tabs cover every SEO-critical area: • Overview — verdict and key stats at a glance • Content — text missing from Google's view, with click-to-locate • Meta & Canonical — comparison of title and description and canonical and robots tags • Headings — every H1 and H2 with visibility status • Schema — JSON-LD types detected in each source • Links — internal links Google can and can't see • Mobile/Desktop Parity — mobile-first indexing audit • Flags — prioritized issues sorted by severity • How to / FAQ — built-in tutorial and vocabulary guide ► Click-to-Locate Click any flagged element…