GSC data is 16 months deep and comes directly from Googlebot's crawls of your site. It's the most authoritative source for understanding what Google sees — not what third-party tools estimate. Setting it up takes five minutes; knowing which reports to check weekly takes five more.
Key Takeaways
- GSC shows Google's actual view of your site — indexed pages, crawl errors, search queries — not estimates
- Coverage report: shows which pages are indexed, which are excluded, and which have errors — the most important starting report
- Performance report: shows clicks, impressions, and average ranking position for every query your pages appear for
- URL Inspection: shows exactly how Google last crawled a specific URL — and lets you request a recrawl
- Sitemap submission accelerates indexing of new pages and flags any sitemap errors
Setting Up Google Search Console
1. Go to search.google.com/search-console and sign in with a Google account. Add a new property by entering your domain or full URL.
Domain property vs URL prefix: Domain properties (e.g. example.com) cover all variants — http, https, www, non-www, and all subdomains — in a single property. URL prefix properties only cover the exact URL variant you enter. Domain properties require DNS verification; URL prefix properties offer more verification methods including HTML file upload and meta tag.
2. Verify ownership using your preferred method. DNS TXT record is the most reliable for domain properties. For URL prefix properties, adding a <meta name="google-site-verification" content="..."> tag to your homepage or uploading an HTML verification file both work.
3. Submit your sitemap — Sitemaps → Add a new sitemap → enter the path (typically sitemap.xml). GSC will fetch it, validate it, and show how many URLs it found. Verify your sitemap is valid first using the Sitemap Validator.
The Coverage Report — Most Important Starting Point
Index → Coverage (or "Pages" in the newer GSC interface) shows the indexing status of all URLs Google has discovered on your site.
Valid — pages Google has indexed. Click to see the full list. Verify that all important pages appear here and that no pages you intended to block appear.
Valid with warnings — indexed but with a flag. Common: "Indexed, though blocked by robots.txt" means a page is indexed despite being blocked — Google learned about it from links but can't crawl it. "Submitted URL has a noindex tag" means you submitted a noindex URL in your sitemap — fix the sitemap or the noindex.
Error — pages Google tried to index but couldn't. Errors include 404s, server errors, redirect errors, and canonicals pointing to non-indexable pages.
Excluded — pages Google chose not to index. Reasons include: noindex tag (intentional), canonical pointing elsewhere (intentional), duplicate content (Google chose a different canonical than you specified — investigate), crawled but not indexed (low quality signal).
The Performance Report — What Queries You Rank For
Performance shows clicks, impressions, CTR (click-through rate), and average position for every search query that triggered your pages over the last 16 months.
The most useful starting analysis:
- High impressions, low CTR — your pages appear in search results for a query but users aren't clicking. Either the page doesn't match the query intent, or the title/description snippet isn't compelling. Rewrite the title tag and meta description for those URLs.
- Position 8–15 (second page) — these are "almost ranking" pages. A targeted content or technical improvement can push them to page 1. Filter by position (8–15) to find these.
- Brand vs non-brand queries — use the Search Type filter to separate branded queries (your company name) from non-branded. Non-branded impressions are your addressable SEO opportunity.
URL Inspection — What Google Sees for a Specific Page
Enter any URL in the inspection bar at the top to see:
- Whether it's in the index, and when Google last crawled it
- The exact canonical URL Google selected (may differ from your canonical tag if Google disagrees)
- The crawled HTML — what Googlebot actually saw (useful for diagnosing JavaScript rendering issues)
- Any structured data found and validated
- Mobile usability status
Use "Test Live URL" to re-crawl the page right now and see its current state. Use "Request Indexing" after making significant changes to tell Google to recrawl the URL sooner than its regular crawl schedule.
Core Web Vitals Report
Experience → Core Web Vitals shows LCP (Largest Contentful Paint), FID/INP (interaction delay), and CLS (Cumulative Layout Shift) measured from real Chrome users visiting your site (Chrome User Experience Report data).
Unlike PageSpeed Insights, which tests a single URL in isolation, CWV in GSC aggregates real user data — slower connections, lower-powered devices, different network conditions. A "Poor" URL in GSC means real users are experiencing slow performance, not just a lab simulation.
Click any URL in the report to see which URLs are in the "Poor" or "Needs Improvement" groups. Use the Page Speed Inspector to identify the specific technical issues causing the poor scores — render-blocking resources, missing image dimensions, oversized payloads.
The Sitemaps Report
Sitemaps → shows submitted sitemaps with the status, last read date, and number of URLs found vs URLs indexed. A significant gap between "discovered" and "indexed" suggests Google is finding pages in the sitemap but choosing not to index them — usually quality signals.
If a sitemap shows errors, use the Sitemap Validator to check every URL in the sitemap for 404s, noindex conflicts, and canonical mismatches before resubmitting.
Validate Your Sitemap Before Submitting to GSC
Free, no signup. The Sitemap Validator checks every URL in your sitemap for broken links, noindex conflicts, and canonical mismatches — so your GSC sitemap submission is clean from the start.
Try the Sitemap Validator Free →Related reading: Google Search Console Tutorial — From Setup to Action
Affiliate disclosure: Some links on this page may be affiliate links. We only mention tools we've personally used and have an honest opinion about. Affiliate revenue helps keep ByteWaveNetwork's tools free and maintained. We are not paid by any of the tools compared in this article for favorable coverage.