Skip to content

Google Search Console

Search Console reports how a site performs in Google Search. How it differs from Analytics, which questions each answers, and why the numbers never match.

Definition

Google Search Console is a free Google service reporting how a site performs in Google Search, including which queries showed it, how it was crawled and indexed, and which pages were excluded. It measures what happens in search results, before a visit.

Illustration representing google search console

Why it matters

Search Console is the only report of your search performance that comes from Google rather than from a model of Google. Any ranking number from a third-party tool is an estimate taken from a sample of locations and devices. Search Console is a record of what actually happened.

It is also the only place that tells you why a page is not indexed, which is the question most SEO problems eventually reduce to.

How it works

The split with Analytics is clean once you see it, and Google's documentation on how Search works explains which half this tool reports on: Search Console measures the search result, Analytics measures the visit.

QuestionWhere it is answered
Which queries showed my siteSearch Console
What position did I averageSearch Console
Why is this page not indexedSearch Console
What did visitors do on the siteAnalytics
Which pages led to a conversionAnalytics
How much traffic came from searchEither, differently

Google's documentation on the performance report defines the four metrics. An impression is your listing being shown. A click is somebody following it. CTR is clicks divided by impressions. Position is the average position of your best-ranking URL for that query.

The numbers will not match Analytics, and this is expected rather than a tracking fault. Search Console counts a click at the moment it leaves the results page. Analytics counts a session after a page loads and its script runs. Anything in between, a back button, a blocked script, a slow load abandoned, is a click with no session.

Worked example

The most useful report in the whole tool is queries where you already rank between positions eleven and twenty, sorted by impressions:

what is nap consistency1,24012.4
faceted navigation seo89014.1
A ladder against a wall with figures standing on the rungs just below a marked line, one reaching over it
Queries at positions eleven to twenty are already close. Moving them up is usually a better page, not a new one.

These are terms Google already considers you relevant for. Moving from page two to page one is usually a better page rather than a new one, which makes these the cheapest wins on the site and a far better starting point than any keyword difficulty score, because the data is measured rather than modelled.

The page indexing report is the second place to look. It names pages excluded and why: crawled but not indexed, duplicate with a different canonical, blocked by robots.txt, and so on.

Common mistakes

  • Expecting the numbers to match Analytics.
    They measure different events and never will.
  • Reading average position as a rank.
    It is an average across every impression, so one appearance at position 40 in another country moves it.
  • Ignoring the sixteen month limit.
    The data expires. Export anything you want to compare year on year.
  • Only verifying one property.
    http, https, www and non-www are separate properties unless you verify the domain itself.
  • Submitting a URL and waiting.
    Requesting indexing does not override an assessment that the page is thin or duplicated.

Where to start

Verify the domain property, submit the XML sitemap, then read the page indexing report before anything else. It usually names the real problem in a sentence, which is why it is the first thing we open in an SEO audit.

Let's build

Got something to build?

Tell us what you're making. We'll tell you - honestly - if we're the right team, and how we'd do it.