Scan at scalePages whose content only appears after JavaScript
Pages whose content only appears after JavaScript
A per-URL report: one row per page that matches, over the pages a crawl reached.
What this report returns
Many AI agents and crawlers read the raw HTML response and never execute JavaScript. On these pages the meaningful content only exists after client-side JS runs: the primary container is empty in the static HTML, the raw response is near-empty, or only navigation chrome is server-rendered, so no-JS agents see a shell instead of the content.
How to fix it. Server-render or prerender the primary content (SSR/SSG or a prerender service) so the HTTP response itself carries it; the flagged column names which pattern each page shows.
The columns it shows
Every defect this technology can carry is a column in the grid, worst first, so nothing is hidden behind a filter you have to know to apply.
- Server-Rendered Content Valid
ssrValid - SSR Findings
ssrFindings - SSR Static Text Chars
ssrStaticTextChars - SSR Rendered Text Chars
ssrRenderedTextChars - SSR Static Share Percent
ssrStaticSharePercent - SSR Primary Content Empty
ssrPrimaryContentEmpty - SSR Content Only After JS
ssrContentOnlyAfterJs - SSR Boilerplate Only
ssrBoilerplateOnly - SSR Low Static Share
ssrLowStaticShare
About Server-side rendering
Whether the content exists before JavaScript runs. Most agents never run it.
Read how Server-side rendering is checked, including the specification it is validated against and a worked correct and broken example.
Running it
This report ships in the Lumar agent-readiness container and appears on any project it is linked to, on every crawl. See the whole set, or check a single URL with the scanner on this site, which runs the same code with no account.