Google Search Console is the only place Google tells you, in its own words, how it crawls, indexes, and ranks your site. These 24 guides turn that data into a working routine: reading the Performance report without fooling yourself, understanding the Generative-AI report that tracks your visibility in AI Overviews and AI Mode, fixing every indexing status that quietly costs traffic, and mastering the power layer — regex filters, the URL Inspection tool, the API, bulk export to BigQuery, and Looker Studio dashboards. Every guide is written from daily GSC workflows: what each report actually measures, where it misleads, and what to do next.
- 24In-depth guides
- Jul 17, 2026Last updated
- 7 minAvg. read time
- FreeNo paywall, ever
Featured guides
Every Search Console article
No articles match — try another term or pick a different topic chip.
Google Search Console: The Complete Guide
Google Search Console (GSC) is Google’s free reporting surface for site owners: it shows how Google crawls, indexes, and ranks your pages, and since June 2026 it also reports your visibility inside generative-AI features like AI Overviews and AI Mode. It is first-party data — not estimates from a third-party tool — which makes it the single most trustworthy source you have about your own search performance.
This pillar is the working manual for it. The 24 guides below each take one report or workflow and go deep; this page gives you the map — what lives where, which numbers to trust, and the order in which to look at things.
Quick Navigation
- What is Google Search Console?
- Setup and Verification
- The Reports That Matter
- Fixing Indexing Statuses
- Power Features
- GSC for AI Search
- Common Misconceptions
- Getting Started
- Frequently Asked Questions
- All 24 Articles
What is Google Search Console?
Search Console is not an analytics tool — it measures Google’s side of the relationship, not your visitors. GA4 tells you what people did on your site; GSC tells you what Google did with your pages: which ones it crawled, which it indexed, which queries triggered them, and where they were positioned. The two datasets disagree constantly, and that is expected — they count different things at different points in the journey, a distinction the GSC vs GA4 guide settles for good.
Three capabilities make it irreplaceable. First, indexing truth: the Page indexing report is the only authoritative list of what Google has and has not indexed, with a stated reason for every exclusion. Second, query data: the Performance report shows the actual search terms that surfaced your pages — data no third-party tool can fully reconstruct. Third, direct communication: manual actions, security issues, and enhancement validations flow through GSC and nowhere else.
Setup and Verification
Verify a Domain property if you can (DNS record) — it aggregates every protocol and subdomain in one property, so you never wonder whether www and non-www are split. URL-prefix properties are fine when DNS access is impossible, but they only see the exact prefix you register. After verification, submit your XML sitemap under Sitemaps: it accelerates discovery and gives the sitemap a visible processing status you can read in the Sitemaps report. That is the whole setup — everything else in GSC is reading, not configuring.
The Reports That Matter
Performance
Clicks, impressions, CTR, and average position for Search, Discover, and News — filterable by query, page, country, device, and search appearance. It is also where most self-deception happens: averages hide bimodal positions, CTR moves with SERP features rather than your title, and 16 months of history disappears if you never export. The full Performance report guide covers the metrics honestly; regex filters turn it into an analysis tool, a brand/non-brand split is where every trend read should start, and the content-decay workflow uses it to catch slipping pages early.
Generative-AI performance
Launched June 3, 2026: dedicated reports for impressions inside AI Overviews, AI Mode, and generative features in Discover. Impressions only for now — no clicks, no queries — but it is the first time Google has shown site owners their AI-surface visibility directly, and it arrived with a control to opt your content out of those features. The Generative-AI report guide explains what it measures, its rollout limits, and what to actually do with it — and the GSC-for-AI-Overviews workflow shows how to read it against the main report.
Page indexing
Every URL Google knows about, split into indexed and not-indexed, with a named reason for each exclusion. Some reasons are healthy (redirects, deliberate noindex), some are quality verdicts in disguise. The Page indexing report guide maps every status to an action — or to deliberate inaction.
Experience and enhancements
Core Web Vitals (field data from real Chrome users), HTTPS, and structured-data enhancement reports live here — including the Video indexing and Merchant listings reports for sites that use video or sell products. They are slower-moving and mostly confirm work you do elsewhere — the CWV data pairs with our technical SEO checklist, and the enhancement reports validate the markup covered in the structured data guide.
Fixing Indexing Statuses
Several exclusion statuses cause most of the anxiety, and they mean very different things. Crawled — currently not indexed: Google fetched the page and chose not to index it — usually a quality or demand verdict, and the hardest one to fix honestly. Discovered — currently not indexed: Google knows the URL but has not crawled it yet — a crawl-scheduling signal that points at internal linking and site quality. Duplicate without user-selected canonical: you never declared which of several similar pages wins, so Google picked for you. Then there are the statuses that are usually just bookkeeping — Page with redirect, soft 404s, blocked by robots.txt, excluded by noindex, and indexed though not in sitemap — where the status-by-status guide separates the alarms from the noise.
The common thread: indexing exclusions are rarely fixed by resubmitting. They are fixed by improving the page, its crawlability, its internal links, or by accepting that Google is right and the page should not be indexed.
Power Features
The URL Inspection tool is the microscope: index status, the Google-selected canonical, last crawl date, rendered HTML, and a live test for any URL in your property. Regex filters unlock the Performance report with brand/non-brand splits, question queries, and long-tail isolation. Beyond the UI, the Search Console API and the bulk data export to BigQuery remove the 1,000-row limit for larger sites, the Looker Studio dashboard turns that data into shareable reports, and the Crawl stats report shows exactly how Googlebot is treating your server.
GSC for AI Search
Search Console is becoming the measurement layer for AI visibility in Google surfaces. The Generative-AI report shows where your pages appear inside AI Overviews and AI Mode; the opt-out control makes AI participation an explicit choice; and crawler access — GPTBot, Google-Extended, and friends — remains a robots.txt decision covered in our robots.txt guide. For the strategy side — how to be the source AI answers cite — start with the GEO & AEO pillar and the complete GEO/AEO guide, and audit your AI-crawler access in seconds with the free AI Crawler Access Auditor.
Common Misconceptions
Myth 1: “Submitting a sitemap makes Google index everything.” Sitemaps aid discovery; indexing is earned. A URL in a sitemap with thin content still lands in Crawled — currently not indexed.
Myth 2: “Average position is my rank.” It is an average across every query and impression, including position 60 one-offs. Filter to a single query before trusting it.
Myth 3: “Request indexing fixes exclusions.” It re-queues a crawl; it does not overturn a quality decision. If the page was excluded for quality, it returns to the same status.
Myth 4: “GSC shows all my queries.” Low-volume and privacy-filtered queries are omitted, and the UI caps rows at 1,000 — the visible query list is a sample, not a census, which is exactly why the API and bulk export exist.
Myth 5: “Not indexed means penalized.” Most exclusions are routine canonicalization and crawl scheduling. Penalties are manual actions, and they have their own report.
Getting Started
If your traffic dropped: start in the Performance report, compare the drop window against the prior period, and split brand from non-brand with a regex filter before concluding anything.
If pages are not ranking at all: check the Page indexing report first, then inspect the specific URL with the URL Inspection tool — indexing problems masquerade as ranking problems constantly.
If you care about AI visibility: open the Generative-AI report, note your baseline, and pair it with the strategy work in GEO & AEO. Need an expert pass instead? Our services cover exactly this.
Frequently Asked Questions
Is Google Search Console free?
Yes — every report, including the Generative-AI performance report, is free for verified site owners. There is no paid tier; the only cost is the discipline to read it regularly.
How often does GSC data update?
Performance data typically lags by about a day and can take 2–3 days to finalize; indexing statuses refresh on Google’s crawl schedule, not yours. Judge trends weekly, not hourly.
Why do GSC and GA4 numbers disagree?
They measure different events: GSC counts clicks on Google’s side; GA4 counts sessions that successfully loaded your tracking. Ad blockers, redirects, and consent banners all widen the gap. Both are right about what they measure — the full comparison is here.
Should I use the URL removal tool for excluded pages?
No — removals are for urgent takedowns, not indexing hygiene. Pages excluded as duplicates or low-value simply stay excluded; removing them adds a temporary block on top and solves nothing.
Explore This Cluster: The Complete Search Console Resource
The 24 guides below cover the daily-workflow reports, every indexing status that matters, the enhancement reports, and the power features most sites never touch. Start with the one matching your current problem.
| Article | What it covers |
|---|---|
| GSC Performance Report Explained | What clicks, impressions, CTR, and position actually count, and analysis workflows that do not fool you. |
| GSC Generative-AI Performance Report: What It Shows | The June 2026 report for AI Overviews, AI Mode, and Discover AI — metrics, limits, and the opt-out control. |
| How to Use GSC for AI Overviews Visibility | Reading the AI report against the main report to infer which queries trigger your Overviews. |
| Brand vs Non-Brand Analysis in Search Console | Splitting brand from non-brand with regex so real trends stop hiding. |
| GSC vs GA4: Which Data to Trust for SEO | Why the two never match and which tool answers which SEO question. |
| Finding Declining Content With GSC (Content Decay) | Catching decaying pages with the period comparison, then refresh, consolidate, or retire. |
| Page Indexing Report Explained | Every indexing status decoded — which exclusions are healthy and which need action. |
| Crawled — Currently Not Indexed: How to Fix It | Why Google fetches pages and declines to index them, and the honest fixes. |
| Discovered — Currently Not Indexed: How to Fix It | Why Google delays crawling known URLs and how to get the queue moving. |
| Duplicate Without User-Selected Canonical: How to Fix It | How Google picks canonicals when you do not, and how to take the choice back. |
| Page With Redirect in Search Console | Why it is usually healthy, and the redirect chains and wrong targets that are not. |
| Soft 404 Errors: Causes and Fixes | Why 200-status pages get flagged as empty, and how to match responses to reality. |
| Blocked by robots.txt (Submitted URL) | Resolving the sitemap-vs-robots.txt contradiction without breaking other pages. |
| Excluded by ‘noindex’ Tag: When It’s a Problem | Telling a deliberate noindex from an accidental one that is costing you traffic. |
| Indexed, Though Not in Sitemap | Using the status to find sitemap gaps and unwanted indexed URLs. |
| Sitemaps Report: Statuses and Errors | Whether Google can read your sitemap, the errors that stop it, and discovered vs indexed. |
| URL Inspection Tool: Full Walkthrough | Index status, live tests, rendered HTML, and the diagnostics most people miss. |
| GSC Regex Filters: Patterns That Actually Work | A copy-paste RE2 pattern library for brand splits, questions, and URL segments. |
| Google Search Console API: Beginner-to-Pro Guide | Past the 1,000-row cap — auth, first queries, quotas, and the workflows worth building. |
| GSC Bulk Data Export to BigQuery | Streaming complete, unsampled data into BigQuery daily — setup and when it is worth it. |
| GSC + Looker Studio: SEO Reporting Dashboard | Automated, shareable dashboards — connectors, reports, and sampling limits. |
| Crawl Stats Report: Reading Googlebot Behavior | Crawl volume, response codes, and host status — and when any of it matters. |
| Video Indexing Report Explained | Which videos Google indexed, why some were not, and how to fix them. |
| Merchant Listings Report Explained | Product structured data for rich results — the errors that block eligibility and their fixes. |
Search Console — Frequently Asked Questions
What is the Generative-AI performance report in Search Console?
A set of reports Google launched on June 3, 2026 showing impressions your pages earn inside generative-AI features — AI Overviews, AI Mode, and Discover AI. It currently reports impressions and pages only, with data starting May 18, 2026, and includes a control to block your content from those features. Full breakdown here.
How do I fix “Crawled — currently not indexed”?
Treat it as a quality verdict, not a bug: consolidate thin or overlapping pages, strengthen internal links from pages Google already values, and make the page answer a query real people search for. Resubmitting without changes almost never works. The full fix process is here.
Which Search Console report should I check first each week?
Performance (compare the last 7 days against the prior 7 with a brand/non-brand split), then Page indexing for any new exclusion spike, then the Generative-AI report for your AI-surface baseline. Fifteen minutes covers all three once the routine exists.
How do I get past the 1,000-row limit in Search Console?
Use the Search Console API (up to 25,000 rows per request) or the bulk data export to BigQuery (complete, unsampled data daily). Both surface the long-tail the interface hides, and both feed Looker Studio dashboards.
Does Search Console data match what AI tools see?
No single tool sees everything. GSC covers Google surfaces only — for ChatGPT, Perplexity, and Claude visibility you need direct testing, covered in our AI citation study method and the free AI Citation Tracker.
Keep exploring
Related pillars: Technical SEO — the fixes GSC tells you to make · GEO & AEO — the strategy behind AI-surface visibility · SEO Fundamentals — the groundwork.
Put it into practice: free tools · audit templates · analysis prompts · glossary.
Want an expert to read your Search Console? Get in touch.
Never miss a breakdown. One email when something genuinely changes in AI search or SEO — plus new guides and free templates. Subscribe to the newsletter →