A big gap between the text in the raw HTML and the text after rendering tells me the page leans heavily on JavaScript for its content. The larger the gap, the more I am exposed to render failures. Most text appears only after rendering (high hydration dependency).
Why does large raw-vs-rendered text gap matter for AI search?
The more content depends on rendering, the more exposure to render failures, timeouts, and partial indexing.
How do you fix it?
Reduce client-side dependence for primary content; SSR the core.
How do you find it on your site?
- Capture the raw HTML with curl and the rendered HTML from URL Inspection or a headless browser.
- Compare the visible text length of each.
- Flag pages where most of the text only appears after rendering.
- Move the important text into the server-rendered HTML.
Which ranking and citation factors does it touch?
The smaller the raw-to-rendered gap, the more reliably your content reaches the index. A large gap is a fragility I try to design out.
What is the impact?
Medium-high. Inferred from rendering pipeline.
What is the evidence?
Rendered HTML is what gets indexed; minimise render dependence for core content. Google Search Central, Understand JavaScript SEO Basics; Google Search Central, In-Depth Guide to How Google Search Works
Sources
Frequently asked questions about large raw-vs-rendered text gap
What does "Large raw-vs-rendered text gap" mean?
Most text appears only after rendering (high hydration dependency).
How do you fix large raw-vs-rendered text gap?
Reduce client-side dependence for primary content; SSR the core.