Reference guide · search-console · Published 2026-08-15 · 3 min read

Search Console basics for non-search people

Search Console basics for non-search people: why the Pages and URL inspection reports exist, what the numbers mean and what to ignore.

A plain map of the Console

Search Console is the free tool that shows what Google's infrastructure sees for your site: which pages it knows about, which it indexed, and how your pages appear in search. It does not subjectively rank your site; it reports on crawl, index and surface behavior, plus the traffic that came from search.

The left menu after you open a property contains the reports that matter for a first read:

Everything else in the menu is a subset or an older family of these four.

The one idea to internalize: index, not rank

Search Console does not tell you your "page rank" with a single number. The important lifecycle is:

  1. Google discovers the URL (via links or sitemap).
  2. Google fetches it, often with JavaScript rendering.
  3. Google decides whether to add it to the index.
  4. When someone searches, the index decides where to show it.

The Console surfaces where in that pipeline each URL is (indexed, discovered not indexed, etc). The first three steps are the "indexing" half; the last is the "serving/ranking" half. Reports like Performance are the latter, and Pages plus URL inspection are the former.

The reports in one sentence each

ReportOne-sentence use
PerformanceHow often your site shows and gets clicked in Google results
PagesWhich URLs are indexed and which are not, with a reason for each
URL inspectionWhy that one URL is or is not indexed, plus a live test
SitemapsWhere your sitemap was accepted and what Google extracted from it

What beginners over-read

Three habits produce false alarms:

  1. Daily noise: single-day and two-day movement in the report is normal; compare like-for-like windows.
  2. Indexing as rank: pages report growth is not traffic growth, and many indexed pages do not receive clicks.
  3. Search Console as the only truth: it is one source, and it samples and delays. A server log or the web performance audit covers what Search Console does not (load behavior, response codes the crawler saw).

The one thing to fix first

If you are new and you can only do one thing: set up the property correctly (setup guide), submit your sitemap, then watch the Pages report for your main pages. Everything else is depth on top of that habit. When you outgrow this map, the search results unit and the search-console family on this site take it further, including the crawl stats angle.

Need a website built, fixed, optimised, migrated or replaced?

This technical resource is written by CSMBAC, a small design and development studio. If you would rather hand the problem to a professional, the website service page explains how we build enquiry-ready websites.

Explore website services