The four Search Console reports worth your time

Most of Search Console is not for you

Google Search Console ships with something like fifteen reports. A handful of them exist for enterprise sites with millions of URLs, a handful exist for developers debugging structured data, and a couple exist for problems your five-page business site will never have.

Four of them are worth a calendar reminder. Everything else you can open when something specific breaks.

The reason it matters is that Search Console is the only free source of first-party search data you will ever have. Every rank tracker, every SEO tool, every agency dashboard is estimating from a sample. Search Console is Google telling you what Google actually did.

Set it up as a domain property

Before any report is useful, verify the right kind of property.

Search Console offers two: URL prefix and domain. A URL-prefix property covers exactly one protocol on one subdomain. That means https://www.yourbusiness.com/ and https://yourbusiness.com/ are, as far as Search Console is concerned, two unrelated websites with two separate sets of data. If your site redirects one to the other — and it should — you can end up staring at a property that shows almost nothing while the real traffic sits in a property you never created.

A domain property covers every subdomain and both protocols in one place. It is verified with a DNS TXT record rather than an HTML file, which is the only reason anyone chooses the other option.

If you do not know where your DNS lives, that is a bigger problem than Search Console and worth fixing first.

Report one: Performance

This is the report you would build yourself if you could. It has four toggles across the top — clicks, impressions, average CTR, average position — and a table beneath it that can be pivoted by query, page, country, and device.

The query table is the whole point. It is the list of things people typed into Google that caused Google to show one of your pages. Not what you hoped to rank for. What you rank for.

Two habits get almost all the value out of it:

Read the queries you did not plan for. Nearly every small business site ranks for something nobody sat down and targeted — a brand name spelled wrong, a product question, a neighbourhood you mentioned once in an About page. Those are free signals about the language your customers actually use, and they cost nothing to act on. This is the same vocabulary gap that makes "drain unclogging" outrank "residential drainage services".

Filter to positions 8 through 20. Set the position filter, sort by impressions, and read the top twenty rows. Those queries are ones Google already associates with your site but does not rank you well enough to win the click. Moving a query from position 11 to position 6 is a much shorter piece of work than creating relevance from nothing, because the relevance already exists.

One caution: the Performance report is a 16-month rolling window, and it reports on a two-to-three-day lag. Reading it daily produces noise. Reading it monthly produces trend.

Report two: Page Indexing

The Page Indexing report splits your URLs into indexed and not-indexed, and gives a reason for each exclusion. Most of the reasons are benign — redirects, canonicalised duplicates, pages you deliberately blocked. Two are worth attention.

"Discovered – currently not indexed" means Google knows the URL exists but has not fetched it yet. On a small site this is usually a crawl-budget non-issue that resolves itself; if it persists across dozens of URLs, the common cause is that nothing on your site links to them, so Google has no reason to prioritise the fetch.

"Crawled – currently not indexed" is the one people misread. Google fetched the page, looked at it, and decided not to index it. Google's own documentation is direct about this: requesting indexing again will not change the outcome. It is not a bug report. It is a quality verdict.

When we see it, the cause is almost always one of three things:

1. The page is thin — a location page with 80 words and a phone number, a service page that is a paragraph and a stock photo.
2. The page is a near-duplicate of another page on the same site, which is exactly the failure mode that scaled location pages fall into when they are done lazily.
3. Nothing links to it internally, so it reads as an orphan.

The fix is editorial, not technical.

Report three: Core Web Vitals

The Core Web Vitals report groups your URLs into Good, Needs Improvement, and Poor, based on field data from real Chrome users rather than a lab test.

That distinction matters more than most people realise. PageSpeed Insights runs a simulated load on a simulated device. The Core Web Vitals report in Search Console reports what happened to actual visitors on actual phones on actual connections. When the two disagree, the field data is the one Google uses.

The catch is volume: the report needs enough real traffic to form a sample. A site with a few hundred visits a month will show "not enough data" indefinitely. That is not a failure — it just means you fall back to lab tools and a performance budget you enforce at build time.

If you do have data and it is red, the largest single lever on most small business sites is the hero image. Getting the LCP image right usually moves the whole report.

Report four: Sitemaps

The smallest report and the one most likely to be quietly broken.

Submit your sitemap URL once. Then check two things: that the status reads Success, and that the discovered-URL count roughly matches the number of pages you think you have.

The failure we see most often is a sitemap that was generated correctly at launch, then never regenerated — so it lists twelve pages while the site now has forty. Google is not blocked from finding the other twenty-eight, but you have removed the one signal that would have told it where to look first. The second most common failure is a sitemap listing URLs that redirect or 404, which Google will report as errors and which usually indicates a slug change that nobody propagated.

A sitemap is not a ranking factor. It is a hint about crawl priority, and on a site that publishes regularly it is a useful one.

A realistic cadence

Here is the routine we recommend to clients, offered as an operating habit rather than an industry rule:

• Monthly, 15 minutes. Open Performance, set the range to the last three months, sort the query table by impressions, and read it. Note anything in positions 8–20 that you could reasonably win. Check the Page Indexing total for a sudden drop.
• After any structural change. New pages, changed URLs, a redesign, a platform migration — check Page Indexing and Sitemaps within two weeks. This is where a botched migration announces itself.
• Quarterly. Core Web Vitals, if you have enough traffic for it to report.

That is it. Search Console rewards patience and punishes daily checking, because the underlying data is both delayed and noisy at small volumes. The month-over-month shape of the query table is the signal. Tuesday versus Wednesday is not.