Pages render as thin, empty HTML before JavaScript runs
If this finding appears in a report, sampled pages returned limited content in their initial HTML response. A client-rendered application may add the content after JavaScript runs. Response size alone does not establish what a browser renders or whether a page can be indexed.
Why this matters
Google can render JavaScript, although blocked resources or rendering failures can prevent it from seeing content. Other consumers have different capabilities. Useful initial HTML can reduce dependence on rendering, but its absence is not a universal loss of SEO credit or proof of ineligibility for AI citations.
How to fix it
Compare the initial response with the rendered page on representative URLs. Check meaningful text, links, status codes, resource access and JavaScript errors. Use Search Console URL Inspection to review Google's rendered result and indexing evidence. If important content is missing for the intended consumer, consider server rendering or static generation, then verify the deployed routes. Do not infer a build failure or promise a ranking increase from HTML size alone.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit