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.
- 01Inventory JSON-LD types and properties
- 02Compare markup to visible page facts
- 03Check stable identifiers and URLs
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.
- 01Use the most specific supported type
- 02Reuse consistent organization and website IDs
- 03Generate markup from the same source as visible content
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.
- 01Run schema and rich-result validators
- 02Inspect production HTML
- 03Monitor Search Console enhancement reports
Common pitfall
A shortcut to avoid
Adding unsupported or invisible claims may produce warnings and can undermine trust without earning a search feature.
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.