Media
1 item
Description
3-way SEO audit: live DOM vs raw HTML vs Google-rendered HTML. See what Googlebot can and cannot see on any page. 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 in the panel and SSR Inspector auto-focuses the page. The extension scrolls to the element and pulses a bouncing arrow above it. No more hunting through the DOM. ► One-Click Rich Results Test A built-in button pre-fills Google's Rich Results Test with your current page URL so you don't have to copy-paste. Saves three clicks per audit. ► Works With Any JavaScript Framework Works with any JavaScript framework or static site generator. SSR Inspector reads the rendered DOM output. The underlying framework doesn't matter — anything that produces HTML in the browser is auditable. ► Smart Matching Engine Handles dynamic values intelligently. Property counts that change every minute won't trigger false positives. Dates and timestamps are normalized before comparison. Substring containment and fuzzy word-overlap fallbacks keep flags meaningful even when content rewords slightly between crawls. ► Privacy-First All audit processing happens locally in your browser. No URLs or HTML or audit results are sent to any external server. Pasted HTML is stored in local browser storage only. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ COMMON SSR AUDIT USE CASES ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Verifying React server-side rendering on Next.js pages • Auditing Angular server-side rendering with Angular Universal • Checking Vue.js server-side rendering setups for SEO • Validating that prerendering is working for SPAs • Finding hydration mismatches in client-side React apps • Comparing dynamic rendering vs server-side rendering outcomes • Debugging SEO for server-side rendering across different frameworks • Measuring content visibility differences between server-side rendering and client-side rendering • Testing whether edge rendering or CDN prerendering matches Googlebot's view • Auditing LLM crawler visibility for generative search citations • Catching mobile vs desktop content drift before mobile-first indexing penalizes your rankings ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHY SERVER-SIDE RENDERING MATTERS FOR SEO ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Server-side rendering (SSR) means the HTML is fully assembled on the server before it reaches the browser. Client-side rendering (CSR) means the server sends a mostly-empty shell and the browser assembles the page using JavaScript. Google's crawler can execute JavaScript but with real-world limits. There are budget timeouts. There are resource caps. There is a two-wave crawl process where rendered content is processed separately from initial HTML. Complex CSR pages often have content that arrives too late for the renderer. Other major search and AI crawlers have even stricter JavaScript handling. This is why LLM-first SEO increasingly demands proper SSR or static generation. The difference between client-side and server-side rendering directly affects time-to-first-meaningful-paint for the crawler. It affects whether schema markup is detected. It affects whether internal links are followed. It affects whether your title and headings and meta tags are read correctly. It affects whether your page is eligible for rich results. And it affects whether your content gets cited by generative search engines. SSR Inspector makes these invisible differences visible. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ QUICK START ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1. Install SSR Inspector and pin it to your toolbar 2. Open any page you want to audit 3. Get Google's rendered HTML using the easy option (click "Open Rich Results Test for this URL" in the popup → wait for Google's test → click "View Rendered HTML" → copy) or by using GSC URL Inspection → View Crawled Page → HTML tab 4. Click the SSR Inspector icon and paste the HTML and click "Run 3-way audit" 5. The audit panel opens automatically. Review the colored outlines on the page or browse the detailed tabs in the panel. Total time: under two minutes per page. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT MAKES THIS DIFFERENT ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Most SEO tools only check the raw HTML server response. Rendering crawlers like Screaming Frog and Sitebulb can execute JavaScript but don't compare against what Google's specific renderer produces. SSR Inspector is built around one critical fact: Google's rendered HTML is the ground truth for SEO. Nothing else matters. If your content isn't in that HTML, it doesn't rank. By making you paste Google's actual rendered HTML — instead of simulating it — SSR Inspector gives you a comparison that's accurate and fast. It works on any page without API keys. It works without rate limits. And it works without guessing. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ TECHNICAL DETAILS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • Manifest V3 modern Chrome extensions architecture • Uses declarativeNetRequest for user-agent rewriting • Detects JSON-LD schema and Open Graph tags and Twitter Card metadata and hreflang and canonical tags • Normalizes href comparison by stripping UTM parameters and trailing slashes • Deduplicates nested DOM segments for accurate content diff • Smart heading-match logic handles dynamic counts and date drift • Push-based panel updates with no polling and instant rendering • Export audit results as JSON for reporting ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FAQ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Q: Does this work with my JavaScript framework? A: Yes — SSR Inspector works with any framework or static site generator because it reads the rendered DOM output and not the source code. If your framework produces HTML in the browser the extension can audit it. Q: Why do I need to paste Google's rendered HTML manually? A: Neither the GSC URL Inspection API nor the Rich Results Test expose rendered HTML programmatically. Pasting ground-truth HTML from Google's own tools is more accurate than simulating a renderer. Q: Does this send my data anywhere? A: No. All processing is local. No data leaves your browser. The extension does not collect any personally identifiable information. Q: Can I audit pages behind login? A: Yes as long as Google can also crawl them. The extension reads your current browser session. Q: Does this detect cloaking? A: Yes. Switch between Googlebot UA and Chrome UA to compare what bots vs users see. Q: Will this replace Screaming Frog or Sitebulb? A: No — those tools are for site-wide crawling. SSR Inspector is for deep page-level SSR audits. Q: Does the mobile/desktop parity audit work for all sites? A: It works whenever the site responds differently to mobile and desktop user-agents. If both UAs receive identical HTML the parity tab will show "Parity OK" — which is the ideal state. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SUPPORT & FEEDBACK ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Found a bug or have a feature idea? Email devendra@serpmonks.com Built with care for the SEO community. Developed in India by Devendra Saini.