SEO

Google Search Console

Also called GSC, Search Console

Google's free reporting tool showing which queries a site appears for, which pages are indexed, and what is blocking the rest.

Quick facts: Google Search Console

Category
SEO
Also called
GSC, Search Console
Level
Beginner
Affects
Indexing decisions, keyword reporting, technical fixes, migration checks
Where to see it
Google Search Console (Performance, Pages, Sitemaps, URL Inspection)
In this article4
  1. What Google Search Console shows
  2. Why Search Console matters
  3. Common mistakes with Search Console
  4. How to act on it

What Google Search Console shows

Search Console is Google’s own reporting on your site, given to you free once you prove you control the domain. Verification is the first step and it decides how much you see: a domain property covers every subdomain and both protocols at once, while a URL-prefix property covers only the exact address you verified. Sites verified on one version and moved to another quietly lose their history, which is why a migration checklist always starts here.

Four parts do most of the work:

  • Performance — clicks, impressions, click-through rate and average position, split by query, page, country, device and search appearance.
  • Pages — which URLs Google has indexed and, for the rest, the reason it decided not to.
  • URL Inspection — what Google has stored for one address, plus a live fetch showing how the page renders to its crawler.
  • Manual actions and security issues — the only place Google tells you a human reviewer has penalised the site.

Why Search Console matters

It is the only source of query data straight from Google. Analytics tells you what someone did after arriving; Search Console tells you what they searched for and how often the site was shown without being clicked. Those two questions cannot be answered anywhere else without guesswork, and third-party tools estimate them rather than measure them.

It is also the earliest warning system you have. Indexing problems, a botched robots file, a certificate error or a manual action surface here before traffic falls far enough to be obvious in a revenue report.

Common mistakes with Search Console

The biggest is expecting the numbers to reconcile with analytics. They count different things at different moments, so a click and a session are never the same event; the gap between Search Console and GA4 is normal, not a fault to be fixed.

The second is trusting totals. Google withholds rare queries to protect privacy, so the query rows will not add up to the page totals, and the interface caps how many rows it will draw. The third is reading average position as a ranking, when it is an impression-weighted average that moves whenever the mix of queries changes. Finally, people request indexing for URL after URL instead of removing whatever stopped Google indexing them in the first place.

How to act on it

Verify a domain property, submit a sitemap, and check the Pages report before you judge any content. If a page is not indexed, the reason given there is the job — a noindex tag, a canonical pointing elsewhere, a redirect, or a page Google looked at and considered not worth storing, which is a content problem rather than a technical SEO one.

Then use Performance properly: filter to one page, look at the queries it already earns impressions for, and improve the title, the intro and the coverage of those questions. Export regularly, because the reporting window rolls forward and the older data simply stops being available.

Do and do not

Do

  • Verify a domain property so every subdomain is covered
  • Check Pages and URL Inspection before blaming the content
  • Export query data before the reporting window rolls off

Do not

  • Read average position as a live ranking
  • Expect clicks here to match analytics sessions
  • Request indexing instead of fixing what blocked it

Questions people ask about this

Do I need Search Console if I already have Google Analytics?

Yes, because they answer different questions. Analytics starts once someone lands on the site and describes what they did. Search Console describes what happened in Google before that: the queries, how often you were shown, whether pages are indexed, and whether Google has any complaint about the site. Neither substitutes for the other.

Why do Search Console clicks not match my analytics sessions?

They measure different moments. Search Console records a click on a result; analytics records a page that loaded and a tag that ran. People leave before the page loads, block scripts, decline consent, or arrive again in the same visit. A steady gap is normal — watch the trend rather than trying to reconcile the totals.

Does requesting indexing make a page rank?

No. It asks Google to look at the page sooner, nothing more. If the page is blocked, redirected, marked noindex, duplicated by a canonical or simply judged thin, requesting indexing again changes nothing. Fix the reason shown in the Pages report or the URL Inspection result, then let Google recrawl.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.