Google Search Console is Google’s free tool that shows how your site appears in Google Search: which queries bring clicks, which pages are indexed, what broke, and whether Google has flagged a penalty or a hack. This Google Search Console guide covers setup first (property type and verification), then every main report and the one question each report answers.
I open Search Console before any other tool when I audit a site. Paid tools estimate. Search Console reports what Google itself recorded, which is why I trust it over any third-party traffic graph when the two disagree about what happened to a client’s rankings last month.
The trick for beginners is not learning every screen. It’s knowing which report to open for the problem you have right now. So I’ve built this guide around questions, and each section points to a deeper post where I go step by step.
The Condition Map: What Changes How You Use Search Console
Four things decide where you should start:
- Whether you control your DNS. If you do, a Domain property is the better choice. If you can only edit pages, you’ll use a URL-prefix property.
- Whether your problem is traffic or indexing. Traffic questions live in Performance. Indexing questions live in Page indexing and URL Inspection.
- Whether you sell products. Stores get extra Shopping and merchant reports that blogs never see.
- How big the site is. Crawl stats and crawl budget only matter once you reach many thousands of URLs.
Keep those four in mind. They decide which branch of this guide you actually need.
How Do You Set Up Google Search Console?
Setup takes three steps. Add a property, verify you own it, then submit a sitemap. The first step is where most people make a choice they regret later, usually because they picked a URL-prefix property for the wrong version of the site and then wondered for months why half their traffic seemed to be missing.
Domain Property vs URL-Prefix Property
A Domain property covers everything under your domain. Google’s help page says it includes all subdomains (www, m and so on) and every protocol, so http and https are counted together.
A URL-prefix property covers only URLs that start with the exact prefix you type. https://example.com/ won’t include http://example.com/ or https://shop.example.com/. That’s useful when you want to isolate one folder, and annoying when you forget the www version exists.
My default is simple. If you can add a DNS record, create a Domain property. Then add URL-prefix properties later only for folders you want to report on alone, like /blog/. If you can’t touch DNS, start with a URL-prefix property that matches your live canonical version exactly, including https and www.
Search Console allows up to 1,000 properties per account. Adding both types costs nothing.
Which Verification Method Should You Use?
Google’s ownership verification help page lists the options. Domain properties accept only DNS verification. URL-prefix properties accept DNS, an HTML file upload, an HTML meta tag, a Google Analytics tracking code or a Google Tag Manager container.
| Your situation | Property | Verification I’d use |
|---|---|---|
| You can log in to your domain registrar or Cloudflare | Domain | DNS TXT record |
| WordPress with an SEO plugin, no DNS access | URL-prefix | HTML meta tag via the plugin |
| GA4 or Tag Manager already installed by you | URL-prefix | Google Analytics or Tag Manager |
| Static site you deploy yourself | URL-prefix | HTML file upload |
One warning from that same page: verification lasts only as long as Google can still find the token. Don’t delete the DNS record or the meta tag after it works. I’ve seen theme switches quietly strip the meta tag and lock owners out of their own data.
Google also says it takes a few days for data to start showing up. Don’t panic on day one.
Submit Your Sitemap
The last setup step is the Sitemaps report. Paste your sitemap URL, submit, and check that the status reads Success. I cover the exact URLs for WordPress, Shopify and Wix, plus the “Couldn’t fetch” error, in how to submit a sitemap to Google Search Console.
Google Search Console Guide Map: Which Report Answers Which Question?
Here’s the map I wish someone had handed me years ago. Find your question in the left column and open that report.
| Your question | Report to open | Deep guide |
|---|---|---|
| Which searches bring me clicks? | Performance (Search results) | Performance report |
| Do I show up in AI Overviews or AI Mode? | Generative AI performance | This guide, below |
| Why isn’t this page on Google? | URL Inspection | How to index pages |
| How many pages are indexed, and why are others not? | Page indexing | Status posts linked below |
| Did Google read my sitemap? | Sitemaps | Submit a sitemap |
| Is my site fast enough for real users? | Core Web Vitals | Core Web Vitals |
| Who links to me, and how do I link internally? | Links | Backlink audit |
| Am I penalized or hacked? | Manual actions, Security issues | Check for a Google penalty |
| Can Google read my robots.txt? | robots.txt report (Settings) | Robots.txt guide |
| Is Googlebot crawling too little or hitting errors? | Crawl stats (Settings) | Crawl budget |
| Are my products eligible for Shopping results? | Shopping and merchant listings | This guide, below |
Bookmark this table. The rest of the guide explains each row, in roughly the order I’d work through them on a site I’ve never seen before, starting with traffic and ending with the settings most people never open.
The Performance Report: Where the Traffic Questions Live
The Performance report shows four numbers for Google Search: clicks, impressions, average CTR and average position. You can slice them by query, page, country, device, search appearance and date, and it keeps 16 months of history.
I open it most. It’s also the easiest to misread. Average position is an average across every impression, so one page ranking 3rd for one query and 40th for another can show a meaningless 21. I explain the metrics, filters and the reasons totals don’t add up in my Google Search Console performance report walkthrough.
Once you’re comfortable there, four follow-up jobs use the same data:
- Filtering many queries at once: the custom regex filter. Copy-paste patterns are in Google Search Console regex.
- Pages that get seen but not clicked: my guide to high impressions, low clicks covers titles, snippets and intent mismatch.
- Quick wins in positions 8 to 20: see how to identify low-hanging keywords.
- New topic ideas from real queries: how to use Google Search Console for keyword research.
The Generative AI Performance Report
This one is new. It changes how I report on AI search. According to Google’s Generative AI performance report help page, it counts how many times links to your site were shown in AI Overviews and AI Mode. Google’s launch post adds a separate Discover view for generative AI features there, and says the reports rolled out to all websites worldwide as of August 31, 2026.
Two limits matter. It shows impressions only, no clicks, and you get pages, countries, dates and devices, but no queries. Clicks from those AI features still sit inside the normal Web results of the Performance report.
My take? Use it as a visibility check, not a traffic report. If a page earns AI impressions but its clicks in Performance keep falling, that’s a page worth rewriting so the click is worth making.
Branch 1: When Your Problem Is Indexing
Zero impressions means trouble upstream. Google either hasn’t crawled the page yet, has crawled it and decided it isn’t worth a spot in the index, or has picked a different URL as the main version and folded your page into that one.
Page Indexing Report
This report splits your known URLs into Indexed and Not indexed, with a reason for each excluded group. Don’t chase zero. Redirects, noindexed tag pages and duplicates are supposed to sit in the “Not indexed” pile, and trying to force them into the index usually makes the site worse rather than better.
What I care about is whether a page I want indexed is sitting in the wrong bucket. The four statuses that confuse people most each have their own guide:
- Discovered, currently not indexed: Google knows the URL but hasn’t crawled it yet.
- Crawled, currently not indexed: Google fetched it and chose not to index it, often a quality or duplication call.
- Alternate page with proper canonical tag: usually fine, it means the canonical worked.
- Soft 404: the page returns 200 but looks empty or missing to Google.
URL Inspection Tool
Paste any URL from your property into the search bar at the top. You’ll see whether it’s indexed, which canonical Google picked, when it was last crawled and whether it’s mobile-crawled. The live test fetches the page right now and shows the rendered HTML, which I use to check JavaScript-heavy pages.
Request Indexing lives here too. It helps for new or updated pages, but it isn’t a ranking boost and it has a daily cap. The full routine is in how to index pages in Google Search Console.
If a page shows “URL is not on Google” and the live test passes, then request indexing and add internal links to it. If the live test fails, fix the error it shows first. Requesting indexing on a broken page just wastes a slot.
Branch 2: When Your Problem Is Experience or Trust
Sometimes pages are indexed and still slide. Then I check two things: how real users experience the site, and whether Google has taken any action against it.
Core Web Vitals
This report groups your URLs as Good, Needs improvement or Poor for LCP, INP and CLS, split by mobile and desktop. It uses field data from the Chrome UX Report, so low-traffic sites may see “not enough data.” My Core Web Vitals guide explains the thresholds and what each metric measures.
Links
The Links report lists top linking sites, top linked pages, top anchor text and your internal link counts. I use the internal links table more than the external one. A key page with only two internal links tells me exactly what to fix next. For reviewing external links, follow my backlink audit process.
Manual Actions and Security Issues
These two reports should say “No issues detected.” If Manual actions shows anything, a human reviewer at Google found a spam policy violation, and affected pages can drop or disappear. Security issues covers hacked content, malware and deceptive pages.
Both are urgent. Drop everything. I explain the difference between a manual action and an algorithmic drop in how to check for a Google penalty.
What Hides Under Settings?
Two useful reports hide under Settings. Beginners rarely find them.
The robots.txt report shows the robots.txt files Google found for your top hosts, when it last fetched them and any parsing errors. If you’ve ever blocked a whole folder by accident, this is where it shows up. My robots.txt guide covers the syntax.
Crawl stats shows Googlebot’s requests over 90 days, broken down by response code, file type and purpose. For most small sites it’s trivia. For large stores with faceted navigation, it explains why new pages wait weeks. Read crawl budget before you start tuning anything.
Settings is also where you manage users and permissions, associations with Google Analytics, and the Change of address tool for domain moves.
Edge Cases
- You run an online store: Search Console shows Shopping reports for eligible stores, including a Shopping tab listings section and the Merchant listings and Product snippets reports. They flag structured data problems that stop products showing in Shopping experiences. If the reports are missing, your product markup may not be detected yet, and my product schema markup post walks through it.
- You want dashboards: Search Console’s charts are basic. Looker Studio, renamed Data Studio in April 2026, connects to Search Console for free. Setup and templates are in Google Search Console Looker Studio.
- Your numbers don’t match Google Analytics: they measure different things. Search Console counts clicks from Google Search, while Analytics counts sessions on your site from every source. I break down the gaps in Google Search Console vs Google Analytics.
- You followed an old tutorial: some screens it mentions no longer exist (next section).
Which Search Console Tools Were Retired?
Old tutorials still send people hunting for screens that no longer exist, which is a common trap when you follow a tutorial written before 2023 and can’t work out where the button went. These are the three that come up most:
| Retired tool | When | What to use now |
|---|---|---|
| Mobile Usability report and Mobile-Friendly Test | December 2023 | Lighthouse in Chrome, plus the Core Web Vitals report |
| URL Parameters tool | 2022 | Canonical tags, clean internal links and robots.txt rules |
| International Targeting report | 2022 | hreflang annotations, which Google still supports |
Country targeting through Search Console is no longer supported at all. If your international setup depended on it, hreflang and a clear URL structure are what’s left.
Decision Matrix
| If you see this | And this | Then open |
|---|---|---|
| Traffic dropped | Impressions dropped too | Performance by page, then Page indexing |
| Traffic dropped | Impressions steady | Performance by query, then CTR fixes |
| New page has no impressions | Inspection says not indexed | URL Inspection live test |
| Many pages “not indexed” | They’re pages you want ranked | Page indexing reason, then the status guide |
| Sudden total drop | Any message in the inbox | Manual actions and Security issues |
| Products missing from Shopping | Store uses product markup | Shopping and merchant listings reports |
When Should You Get Help?
Most Search Console work is reading, not fixing. You can do it. Bring in a technical SEO specialist when a manual action appears, when a migration shows thousands of URLs falling out of the index, or when Crawl stats shows server errors you can’t explain.
That’s the kind of work our complete SEO service covers, with Search Console as the starting point. If you’d like a second pair of eyes first, request a free SEO audit.
Frequently Asked Questions
Is Google Search Console Free?
Yes. Search Console costs nothing, and so does every report in it. You only need a Google account and proof that you own or manage the site.
How Long Does It Take for Data to Appear?
Google says data takes a few days to start accruing after you add a property. The Performance report then keeps 16 months of history, so set it up early even on a brand new site.
Should I Use a Domain Property or a URL-Prefix Property?
Use a Domain property if you can add a DNS record, since it covers every subdomain and both http and https. Use URL-prefix when you can’t edit DNS or want to isolate one folder.
How Often Should I Check Search Console?
I glance at the Overview and inbox weekly and do a deeper Performance and Page indexing pass monthly. Check immediately after a redesign, migration or big content change.
Does Search Console Show AI Overview Clicks?
Not separately. The Generative AI performance reports show impressions only, for AI Overviews and AI Mode in Search plus a separate Discover view. Clicks from those features are counted inside the regular Web search results in the Performance report.
Last updated: October 2026 by Mizanur Rahman
