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.
- 01Inspect title, description, Open Graph and Twitter fields
- 02Find duplicated or templated values
- 03Check rendered metadata on dynamic routes
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.
- 01Write page-specific titles and summaries
- 02Use a stable social image and absolute canonical URL
- 03Keep metadata generation aligned with page status
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.
- 01Fetch the production HTML
- 02Validate social previews and search snippets
- 03Test not-found and filtered pages
Common pitfall
A shortcut to avoid
Filling every tag with keywords creates duplication without making a page more relevant or trustworthy.
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.