Site Audit
Your site audit tool is only
reading half your site.
Most crawlers hit the raw HTML response and stop there. VisibilityIQ also runs a full headless-browser pass and diffs the two outputs — surfacing the SEO issues that only exist after JavaScript executes.
What render-parity diff finds
JavaScript frameworks — React, Vue, Next.js, Nuxt, Angular — modify the DOM after the initial HTML response. The gap between what your server returns and what a browser actually renders is where SEO issues hide.
| Raw HTML State | JS-Rendered State | Severity |
|---|---|---|
| Title present | Title overwritten by JS framework | Critical |
| noindex absent | noindex injected dynamically | Critical |
| No canonical tag | Canonical injected via React Helmet | High |
| Structured data absent | JSON-LD injected after render | Medium |
| Body text: 0 words | Body text: 2,400 words (JS-rendered) | High |
Full audit scope
Title tag presence + render-parity
Meta description presence + length
Canonical chain analysis
noindex detection (raw + rendered)
Redirect chain analysis
Broken internal links
Missing or duplicate H1
Image alt text coverage
Lazy-loaded structured data
Core Web Vitals (via CrUX)
PageSpeed score integration
robots.txt and sitemap consistency
Hreflang validation
Orphaned pages detection
Crawl depth mapping
Fix it in your editor, not a spreadsheet
Every audit exports a machine-actionable Markdown remediation plan — structured so your AI coding assistant can ingest it directly and apply the fixes without guesswork.
What the export contains
- Every finding with WHAT / WHERE / TARGET — the exact file and selector
- Current vs expected values, quoted verbatim — no interpretation needed
- SKIP-IF guard per finding so the assistant can detect whether it is already fixed
- Generated apply-ready artifacts (robots.txt, llms.txt, JSON-LD, canonical tags)
- Risk level per finding (Safe / Review / Destructive) so the AI knows how cautious to be
- Ordered by severity → confidence so high-impact fixes come first
How to use it with your AI IDE
- 1 Run your audit and click Export Remediation Plan — choose Full (with generated files) or Lean (scoped edits only).
- 2 Drop the
.mdfile into your project root and open it in Cursor, Claude Code, Windsurf, or VS Code + Copilot. - 3 Tell your assistant to work through the findings top-to-bottom. Each finding is self-contained — the AI makes exactly the change described and nothing else.
- 4 Re-crawl in VisibilityIQ to verify. The SKIP-IF guards mean re-running the plan later is safe — fixed issues are skipped automatically.
Works with any AI IDE that accepts a Markdown context file: Cursor, Claude Code, Windsurf, GitHub Copilot Workspace, JetBrains AI Assistant.
Render-Parity Diff View
Side-by-side diff of raw HTML vs. headless-rendered DOM with highlighted delta — missing tags, injected directives, and structural changes flagged by URL.
Frequently asked questions
What is render-parity diff and why does it matter for SEO?
Render-parity diff is VisibilityIQ's dual-pass crawl: it fetches each URL as raw HTML (what Googlebot sees on a fast first pass) and again with a headless browser that executes JavaScript (what the page actually renders). The diff between the two outputs surfaces SEO issues that only exist in the rendered DOM — dynamically injected noindex tags, canonicals set by React Helmet, structured data added after page load, and body text that only appears after JS executes. Single-pass crawlers miss these entirely.
How does VisibilityIQ handle JavaScript-rendered pages during site audits?
VisibilityIQ runs a full headless browser pass (Chromium via Cloudflare Browser Rendering) alongside the standard raw HTML crawl. Each URL gets both treatments, and the results are stored separately. The audit engine then diffs the two: if the title, canonical tag, robots directive, structured data, or primary body text differs between raw and rendered, a finding is flagged with evidence showing both the raw value and the rendered value so you can see exactly what changed and why.
Does the site audit check AI crawler access as part of the standard crawl?
Yes. The site audit checks robots.txt directives for AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) on every crawl pass. It also flags pages where AI bots would be unable to access the primary content because it is JavaScript-rendered — since most AI crawlers do not execute JavaScript the way Googlebot does. llms.txt presence and validity is also checked at the site root. All of this is included in the standard $39.95/mo subscription, not a paid add-on.
Find what your current audit tool misses.
Full technical site audit included. $39.95/mo, everything included.
Start your audit — $39.95/mo