JavaScript Visibility Analysis

CSR Content Gap Analyser

Compare what a "dumb" AI agent sees immediately on load (Raw HTML) versus what a "smart" browser agent sees after full JavaScript execution (Rendered DOM). Identify critical text and markup that relies heavily on Client-Side Rendering (CSR), which may prevent bots from discovering or citing your content.

DOMINIC_BRYCE_CLI v2.0 - CSR GAP Analyser
~ System ready. Awaiting instructions.
Common Questions

Frequently Asked Questions

It makes a live HTTP request to your URL using two distinct bots: a "dumb" bot that extracts raw HTML without executing JavaScript, and a "smart" headless browser that fully renders the DOM. It then compares the DOM text length and outputs a side-by-side snippet preview to highlight the exact visual text gap. If the "smart" bot sees more content, that means your framework relies heavily on Client-Side Rendering (CSR), which could hinder search engine discoverability.

No. You can run one-off diagnostics for free, but abuse is rate-limited. Setting up continuous cron monitoring requires a verified email address to dispatch the alert reports to.

No, and this is by design! The script explicitly deletes structural tags (like script, style, meta, nav) and extracts only the visible, human-readable text on the page. This is exactly what you want for a content gap analyser, because AI bots ultimately care about reading the semantic text on the page, not the structural code wrappers.

Historical Release Log

v1.1.0 2026-08-08
Overhauled the text extraction engine to preserve spacing between HTML elements, eliminating unreadable text blobs. Removed truncation limits to allow full-page review, and introduced an automated diff-highlighting engine that explicitly marks missing content in the Rendered text view to help you quickly identify injected JS boilerplate (like cookie banners) versus critical missing content. Additionally, changed the headless browser execution from domcontentloaded to networkidle0 to ensure all client-side rendered scripts are fully loaded before capturing the rendered snapshot, and completely re-wrote the extraction logic so both the Raw and Rendered snapshots use the exact same DOMParser tree walker (decoding all HTML entities) to ensure pixel-perfect diff matching. Additionally, changed the headless browser execution from domcontentloaded to networkidle0 to ensure all client-side rendered scripts, tracking cookies, and delayed DOM injections are fully loaded before capturing the rendered snapshot, preventing false 100% gap scores.
v1.0.0 (First Launch) July 2026
Initial release of the CSR Content Gap Analyser. Identifies Client-Side Rendering (CSR) bottlenecks by comparing raw HTML lengths to Browserless headless rendering execution. Features include a side-by-side agent vs human visual diff and comprehensive content visibility scoring.