SEO Rendering & Indexability Inspector
Local processing with network featuresCompare Static HTML with the Rendered DOM and find indexability issues
Request
Inspect sends this URL to CodingTool servers, which fetch the page and its robots.txt and render it in an isolated Chromium. The target site receives these requests. Nothing is stored.
Static HTML and the Rendered DOM use the browser emulated user agent on a desktop viewport. robots.txt is evaluated for the Googlebot token.
Findings
Details
Enter a public URL to compare Static HTML with the Rendered DOM.
Related Tools
What the inspector compares
The inspector fetches a public URL twice: once as Static HTML, the raw server response, and once as the Rendered DOM after JavaScript runs in a headless Chromium. It extracts the same signals from both sides (title, meta description, canonical, meta robots, H1, language, word count, links, JSON-LD types, hreflang and Open Graph) and shows which ones are the same, changed or present on only one side.
Indexability evidence
Findings are built from evidence: HTTP status and redirects, the live robots.txt decision for the Googlebot token with the matched rule and line, noindex in meta robots or the X-Robots-Tag header, canonical consistency, and content that exists only after rendering. Each finding is labelled as an error, warning or note. The tool never claims that a page is indexed; it reports potential indexability issues observed at inspection time.
Advanced comparison
After an inspection, Advanced comparison renders the URL as two variants. Each variant chooses an emulated request user agent (browser, Googlebot, Bingbot or OAI-SearchBot), a desktop or mobile viewport and an optional Accept-Language value. Use it to spot mobile-first gaps, locale-adaptive content or user-agent based differences. Emulated user agents are not authentic crawler requests, and country geolocation is not emulated.
Privacy and limits
Inspect sends the URL to CodingTool servers. The server fetches the page and robots.txt, renders the page in an isolated Chromium that blocks private and internal addresses, and returns the results without storing them. The target site receives these requests. Renders are time-limited and rate-limited to 5 per minute, HTML is size-limited, and the screenshot covers the first viewport only. Exports exclude HTML bodies, page text and the screenshot.
Rendering guidance
Results come from CodingTool's Chromium and are a diagnostic approximation, not the Google, Bing or AI provider renderers, which have their own queues, budgets and feature support. When important content, links or tags appear only in the Rendered DOM, prefer server-side rendering, static generation or fixing hydration so every client receives them, rather than bot-only dynamic rendering.
