17 min read · Technical SEO · Last updated July 2026
Quick answer: Google Search Console is your direct communication channel with Google’s crawler. The five reports that matter most for technical SEO: Index Coverage (what Google has and hasn’t indexed), URL Inspection (why a specific page isn’t ranking), Core Web Vitals (your real-user CWV status), Sitemaps (whether your sitemap is being processed), and the Performance report (queries and clicks for diagnosis).
Introduction
Most SEOs treat Google Search Console as a ranking dashboard. They check clicks, impressions, and average position. Those metrics matter — but they’re downstream of the technical health reports that actually tell you what’s broken.
A page stuck at position 15 is often there because Google is indexing a canonical variant instead of the target page. A page with zero impressions might be blocked by robots.txt or stuck in a crawl queue. A page that was ranking drops because Core Web Vitals degraded from a new plugin install. GSC surfaces all of these — if you know where to look and what the status codes actually mean.
This guide goes through every technical GSC report, explains each status, and gives you a decision framework for what to fix first.
What you’ll learn:
– How to read the Index Coverage report and act on each status type
– How URL Inspection reveals crawl, index, and canonical decisions for any page
– What the Core Web Vitals report shows vs. lab tools — and why they differ
– How to use Sitemaps to diagnose indexation pipeline problems
– How to use the Performance report for technical diagnosis (not just traffic tracking)
– What Enhancements reports cover and which structured data issues matter
Table of Contents
- Account Setup and Verification
- Index Coverage Report
- URL Inspection Tool
- Performance Report for Technical Diagnosis
- Core Web Vitals Report
- Sitemaps Report
- Enhancements Reports
- GSC API for Scale
- Frequently Asked Questions
- Conclusion
Account Setup and Verification
Before you can use GSC, you need to verify ownership. GSC offers five verification methods:
| Method | How | Best for |
|---|---|---|
| HTML file upload | Upload a file to root directory | Server access available |
| HTML meta tag | Add <meta name="google-site-verification"> to <head> |
CMS with head tag control |
| DNS TXT record | Add TXT record in domain registrar | Domain-level verification (recommended) |
| Google Analytics | Link existing GA4 property | Already have GA4 installed |
| Google Tag Manager | Link existing GTM container | Already have GTM installed |
Recommendation: DNS TXT record verification. It survives theme changes, plugin updates, and CMS migrations — the meta tag approach breaks whenever someone edits the site’s <head> template.
Property types:
– Domain property (recommended): example.com — covers all subdomains (www.example.com, blog.example.com) and both HTTP and HTTPS. Requires DNS verification.
– URL prefix property: https://www.example.com — covers only that exact protocol and subdomain combination.
If you have both www and non-www versions, a Domain property covers both. If you’re only set up with URL prefix properties, create separate properties for http://example.com, https://example.com, http://www.example.com, and https://www.example.com — then set a preferred domain.
Index Coverage Report
The Index Coverage report (now labeled “Pages” in the updated GSC interface) is your primary technical SEO diagnostic tool. It shows how Google has classified every URL it’s encountered from your site.
The four top-level buckets:
Error: Pages Google found but couldn’t index due to a technical problem.
Valid with warning: Pages indexed but with issues that may affect ranking.
Valid: Pages successfully indexed.
Excluded: Pages Google chose not to index (various reasons).
Index Coverage Status Explainer
Click any status to understand what it means and what to do about it.
Action workflow for Index Coverage:
- Check Error count first. Any errors need immediate attention.
- Check “Submitted URL not selected as canonical” — high counts indicate systematic canonical problems.
- Check “Crawled — currently not indexed” — these are pages Google visited but rejected. Understand why.
- Check “Discovered — currently not indexed” — high counts (relative to your page count) indicate crawl budget problems.
- Monitor trends — a sudden spike in any category is the most important signal.
URL Inspection Tool
The URL Inspection tool is your microscope for individual pages. Enter any URL to see exactly how Google has crawled, indexed, and evaluated it.
What URL Inspection tells you:
Coverage status: Is this URL indexed? What’s its exact status (from the coverage report)?
Last crawl date: When did Googlebot last visit this page? If it was 60+ days ago for an important page, crawl frequency is too low.
Crawl as Google: You can see the rendered HTML as Googlebot sees it. This is critical for JavaScript-heavy sites — it shows whether your dynamic content is actually rendering for the crawler.
Mobile usability: Does this specific URL have mobile issues?
Rich results: Does this page have valid structured data? Are rich results eligible?
Page fetch: You can trigger a live fetch to see the current state of the page and compare it to what’s in the index.
Request indexing: After fixing issues, you can ask Google to re-crawl and re-index a URL. This doesn’t guarantee immediate indexing but often accelerates it for important pages. Use this after:
– Fixing a canonical issue on an important page
– Publishing a high-priority new page
– Updating key content (price changes, service updates)
Reading the Coverage section:
– “URL is on Google” → indexed, good
– “URL is not on Google” → follow up with the specific reason given
– “Indexed, not submitted in sitemap” → your sitemap is incomplete; add this URL
– Google’s canonical: vs. User-declared canonical: — if these differ, Google is overriding your canonical tag. Investigate why.
Performance Report for Technical Diagnosis
The Performance report is usually treated as a traffic/ranking report. But it’s also a technical diagnostic tool.
Using Performance for technical diagnosis:
Filter by “Pages” with zero impressions: Pages that have been indexed (appear in Index Coverage as Valid) but show zero impressions over 90 days are likely being bypassed by Google’s index for quality reasons, or they’re indexed but never surface for any query.
Compare device performance: filter Mobile vs. Desktop. If mobile CTR is significantly lower than desktop for the same queries, your mobile experience has problems. If mobile impressions are much lower than desktop, your mobile pages may have indexation issues.
Page-level CTR analysis: sort by Impressions descending. Find pages with high impressions but low CTR (under 2%). These pages are ranking but users aren’t clicking — a title/meta description problem, not a technical problem. But find pages with CTR that dropped suddenly: often caused by a change to how the page appears in SERPs (rich result lost, title changed, position dropped due to technical issue).
Query-level diagnostics: filter Queries by a specific branded query (your company name). If branded queries show very low impressions, Google may have an indexation issue with your homepage.
Core Web Vitals Report
The Core Web Vitals report in GSC shows real-user performance data (CrUX data) aggregated from Chrome users. This is the actual data Google uses for its CWV ranking signal — not your PageSpeed lab score.
Two key differences from PageSpeed Insights:
-
Field data vs. lab data: GSC CWV shows what real users experienced, across their actual devices and connection speeds. PageSpeed shows a simulated test from a single controlled environment.
-
75th percentile threshold: a URL passes CWV only if 75% of real-user sessions meet the threshold for all three metrics. You could have 80% of users with excellent LCP and still fail if the worst 25% are slow.
Reading the CWV report:
The report groups URLs into “Good URLs,” “URLs needing improvement,” and “Poor URLs” for both mobile and desktop. Click into any category to see which specific pages are affected and which metric is failing.
A common misdiagnosis: Your PageSpeed score shows 85 (Good) but GSC shows many URLs as “Needs improvement” in the field. This means real users — on their slower devices, with their installed extensions and variable connections — are experiencing worse performance than your lab test simulates. The fix lies in real-world performance factors like third-party scripts, variable server response, and non-cached repeat visits.
What to do with CWV data:
1. Identify which metric is failing most (LCP, INP, or CLS)
2. Filter by URL to find patterns (are all product pages failing? all blog posts?)
3. Use URL Inspection on a sample of failing URLs to check for issues specific to those page templates
4. Fix at the template level — if all product pages fail, fix the product page template, not individual products
Sitemaps Report
The Sitemaps report shows every sitemap you’ve submitted, the number of URLs it contains, and how many Google has indexed.
Critical metrics to watch:
Submitted vs. Indexed gap: if you submit 5,000 URLs and Google has indexed 2,000, there’s a 60% indexation gap. Investigate using Coverage report filtered to sitemap URLs.
Processing errors: the Sitemaps report shows if Google encountered parsing errors in your sitemap (malformed XML, invalid URLs, inaccessible sitemap URL). Fix these immediately — a broken sitemap means Google isn’t receiving your URL inventory.
Sitemap best practices that affect technical SEO:
- Only include 200-status, canonical URLs in your sitemap. Redirects, 404s, noindex pages, and canonical variants pollute your sitemap.
- Use sitemap index files for large sites — a sitemap index can reference up to 50,000 sitemaps, each containing up to 50,000 URLs.
- Update sitemaps automatically when content changes. Static sitemaps that aren’t updated mean new pages take longer to be discovered.
- Include
<lastmod>dates in your sitemap — accurate lastmod dates help Google prioritize crawling updated content.
Sitemap URL to submit: https://yoursite.com/sitemap.xml — also add this to your robots.txt with Sitemap: https://yoursite.com/sitemap.xml for additional discovery.
Enhancements Reports
Enhancements reports appear in GSC when Google detects structured data markup on your site. Each report type corresponds to a schema type: Breadcrumbs, FAQPage, Product, SiteLinks Searchbox, etc.
Reports you’re likely to see:
Breadcrumbs: Validates BreadcrumbList schema. Issues here mean your breadcrumb rich results are failing. Common error: missing item property or invalid URLs in the breadcrumb path.
FAQPage: Validates FAQ schema. Google has restricted FAQ rich results to authoritative health and government sites since mid-2023 for standard websites. Don’t prioritize this unless you’re in those sectors.
Product: Validates Product schema. Critical for ecommerce — issues here prevent your products from showing price, availability, and rating in SERPs. Common errors: missing offers property, invalid price format, missing availability value.
Review Snippet: Validates aggregateRating schema. Google is strict — reviews must be visible on the page and the schema must accurately reflect them. Inflated ratings or schema without visible reviews trigger manual quality action.
Sitelinks Searchbox: Validates Searchbox schema. Shows a search box in your Knowledge Panel SERP result. Only relevant for large sites.
How to use Enhancements reports:
For each report, the interface shows “Valid,” “Valid with warning,” and “Error” counts. Click into Errors to see the specific issue and which URLs are affected. Use the Rich Results Test (search.google.com/test/rich-results) to validate your schema on individual pages before re-submitting.
GSC Technical Audit Workflow
A structured monthly GSC review process. Check each item and track your progress.
0 / 0
GSC API for Scale
For sites with hundreds of pages, manual GSC review isn’t scalable. The Search Console API (via Google’s official REST API or the searchconsole Python library) lets you automate data extraction and monitoring.
Common automated workflows:
Weekly coverage monitoring: Pull index coverage data via API, alert if Error count increases by more than X% week-over-week.
Performance anomaly detection: Pull daily clicks/impressions data, flag pages where 7-day clicks dropped more than 30% vs. prior 7 days.
Crawl date monitoring: Use URL Inspection API to check last_crawl_time for a sample of important pages. Alert if any priority pages haven’t been crawled in 30+ days.
The GSC API has a 200-request-per-day quota per property with a batch endpoint that supports up to 50 inspections per call. For large sites, this allows daily monitoring of 10,000 URLs (50 per batch × 200 batches).
Frequently Asked Questions
Why are some of my indexed pages showing in “Excluded” as well?
Pages can appear in multiple Coverage categories. A page indexed at the canonical URL may also generate canonicalized variants that appear in “Alternate page with proper canonical tag” — those are correctly excluded, not the indexed version. Always check which specific URL is indexed using URL Inspection.
How long does it take for GSC data to update after I fix an issue?
GSC data lags by 2–3 days for Performance data and up to 7 days for Coverage data. After fixing a technical issue, wait 7–14 days before evaluating whether the Coverage status has changed. Use URL Inspection → Fetch as Google for a real-time check of individual pages.
Should I request indexing for every new page?
No — use “Request Indexing” selectively for high-priority pages (homepage, new service pages, high-value product pages). Google’s crawlers naturally discover new pages through your sitemap and internal links. Spam-requesting indexing for hundreds of low-value pages doesn’t help and wastes GSC’s rate limits.
What does it mean when my mobile CWV fails but my desktop CWV passes?
Mobile users experience different performance characteristics: slower devices (less CPU for JS execution), variable connection speeds, smaller bandwidth. Your mobile Core Web Vitals are the primary ranking signal (Google uses mobile-first indexing). Mobile failure while desktop passes is common and indicates optimization is needed specifically for mobile — lighter JavaScript, better image sizing, fewer third-party scripts.
Why does GSC show fewer indexed pages than my total page count?
Several reasons: some pages are intentionally noindexed, some are canonicalized to other pages, some are excluded due to thin content, and some are in the crawl queue but not yet indexed. Use the Coverage report to understand which bucket your missing pages fall into.
How do I interpret “Valid with warning: Indexed, though blocked by robots.txt”?
This means Googlebot ignored your robots.txt disallow (because it found the page linked from other indexed pages) and indexed it anyway. This is unusual behavior from Google — typically it respects robots.txt. It means you should either: remove the disallow (if you want the page indexed) or add a noindex tag (which Google respects more reliably than robots.txt for preventing indexation).
Conclusion
Google Search Console is the most direct diagnostic tool available to SEOs. It tells you exactly what Google has done with your pages, which pages it’s chosen not to index and why, how real users are experiencing your Core Web Vitals, and whether your structured data is eligible for rich results.
The SEOs who use GSC effectively treat it as a health monitor, not a vanity metric dashboard. They check it weekly for error spikes, monthly for coverage trends and CWV status, and immediately after any site change that could affect crawlability.
Set up a domain property, submit your sitemap, bookmark the Index Coverage and Core Web Vitals sections, and build a monthly review cadence. The data GSC provides is the same data Google uses to make ranking decisions — there’s no better source.
Let Ignited Nepal Handle This
→ Request a Free Technical SEO Audit
Written by the Ignited Nepal SEO team. We build organic search systems for businesses across Nepal, Australia, UAE, USA, UK, and beyond. ignitednepal.com