1.4 Rendering & JavaScript ✦HighInferred
Hydration mismatch (server ≠ client DOM)
When the server HTML and the client-rendered DOM disagree, the framework can throw away and rebuild the content during hydration. That instability can leave Google with a different page than users get.
What it is
Server HTML and client DOM diverge after hydration.
Why it matters
Google may index the pre- or post-hydration state inconsistently; content can be lost or doubled.
How to fix it
Ensure consistent SSR/CSR output.
How to find it on your site
- Check the browser console for hydration warnings.
- Compare the server-rendered HTML against the DOM after hydration.
- Find the source of the mismatch, often time, randomness or user-specific data rendered on the server.
- Make the server and client output consistent.
Cross-reference to ranking and citation factors
A clean, stable hydration keeps the indexed HTML and the user experience aligned. Mismatches risk content being replaced or lost.
Impact
Medium-high. Inferred.
Evidence
Indexed content is the rendered HTML; keep SSR/CSR consistent. Google Search Central, Understand JavaScript SEO Basics