Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Capture production console warnings
- 02Find time, randomness and browser-only branches during render
- 03Check invalid HTML nesting
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Make initial rendering deterministic
- 02Move browser-dependent work to effects or client-only boundaries
- 03Correct invalid markup
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Reload and navigate with production builds
- 02Test multiple locales, time zones and cached data
- 03Fail CI on known hydration warnings
Common pitfall
A shortcut to avoid
Suppressing hydration warnings hides evidence and should be limited to deliberate, understood differences.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.