What it is
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. Server HTML and client DOM diverge after hydration.
Why does hydration mismatch (server ≠ client dom) matter for AI search?
Google may index the pre- or post-hydration state inconsistently; content can be lost or doubled.
How do you fix it?
Ensure consistent SSR/CSR output.
How do you 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.
Which ranking and citation factors does it touch?
A clean, stable hydration keeps the indexed HTML and the user experience aligned. Mismatches risk content being replaced or lost.
What is the impact?
Medium-high. Inferred.
What is the evidence?
Indexed content is the rendered HTML; keep SSR/CSR consistent. Google Search Central, Understand JavaScript SEO Basics
Sources
Frequently asked questions about hydration mismatch (server ≠ client dom)
What does "Hydration mismatch (server ≠ client DOM)" mean?
Server HTML and client DOM diverge after hydration.
How do you fix hydration mismatch (server ≠ client DOM)?
Ensure consistent SSR/CSR output.