GSC knowledge base
GSC page experience tutorials and troubleshooting guide
From real user metrics to experiment diagnosis, verify that performance changes haven't broken the business. Choose a tutorial by specific issue, and check operations, limitations, and verification results item by item.
Separate user experience from indexing access
What to prepare
Use the affected mobile or desktop URL group and note whether real-user data exists. A lab score is a diagnostic sample, not the field report.
| Your situation | First action | Read next |
|---|---|---|
| The field report shows slow loading or interaction | Inspect representative pages for LCP, INP and CLS, make a bounded change and verify the affected interaction. | Core Web Vitals: separate field data and lab scores |
| There is not enough real-user data | Use reproducible lab tests to diagnose the page, while keeping field status marked unavailable. | Core Web Vitals: separate field data and lab scores |
| The page fails to load or returns 5xx | Restore the correct HTTP response before tuning visual performance. | 404, Soft 404, and 5xx: handle by business destination |
When to stop and verify
The changed page still works on mobile and desktop; the problematic interaction is tested. Field metrics need later real-user observation, so a faster lab run is not a validation receipt.
Choose another Search Console problem · Check the official requirements
Page experience
From real user metrics to lab diagnostics, verify that performance changes have not broken the business.
Check 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