GSC knowledge base
GSC enhancements tutorials and troubleshooting guide
Check visible content and structured data, and understand the applicable conditions for products, videos, and AMP. Choose a tutorial by specific issue, and check operations, limitations, and verification results item by item.
Start with an eligible page and its visible content
What to prepare
Collect the affected URL, the exact enhancement type and error, and the markup rendered to crawlers. Valid JSON alone does not establish eligibility.
| Your situation | First action | Read next |
|---|---|---|
| Structured data has an error | Match required fields to visible facts, test the corrected markup and keep screenshots or test results. | Rich results: valid markup does not equal guaranteed display |
| Product information is incomplete | Check the actual product, variant, offer and availability; do not invent ratings or prices to pass a test. | Product snippets and merchant listings: first distinguish page eligibility |
| An AMP-specific error appears | Confirm that an AMP version actually exists and inspect its canonical relationship before editing. | AMP report: only troubleshoot existing AMP pages |
When to stop and verify
Markup describes the real page, tests have no relevant blocking error, and the page remains accessible. Correct markup does not guarantee a rich result.
Choose another Search Console problem · Check the official requirements
Enhancements
Check visible content and structured data, and understand the applicable conditions for products, videos, and AMP.
Rich results: valid markup does not equal guaranteed display
Treat rich-result readiness as several checks: suitable content, truthful fields, valid implementation, indexable delivery and observed display. A successful validator covers only part of that chain. Add supported markup for the real page task, never fabricated reviews or invisible answers.
Steps · error branches · checklistProduct snippets and merchant listings: first distinguish page eligibility
Choose product markup for the page's actual purchase or editorial task, then reconcile the same item across visible content, structured data and any Merchant Center source. Product-snippet validity, merchant-listing eligibility and feed approval are separate states; none proves exposure or sales.
Steps · error branches · checklistAMP report: only troubleshoot existing AMP pages
Investigate AMP only if your site actually maintains AMP URLs. Decide whether to keep and repair them or retire them through a planned migration. A missing AMP report is not a reason to create AMP pages, and a valid AMP document does not guarantee ranking or search distribution.
Steps · error branches · checklistCheck guide coverage and product capabilities separately
SEO operations adds bounded technical checks, saved index-version reads, laboratory records and human content review. Native Google security, Discover, News and enhancement reports still require their own tools. A guide explains a method; it does not establish every report is connected.
View real product capabilities