Search Engine Optimisation 27 July 2026 4 min read

Google Search Console for Beginners: What Each Report Tells You

Google Search Console is free, it connects directly to Google's own data, and most small business owners never look at it. That's a genuine shame, because it shows you exactly how Google sees your site, which pages are being found, which ones are being ignored, and where things are going quietly wrong. You don't need to be technical to get value from it. You just need to know which report does what.

On this page
  1. Start Here: The Performance Report
  2. URL Inspection: What Google Actually Sees
  3. Coverage: Which Pages Google Has (and Hasn’t) Indexed
  4. Core Web Vitals: Speed From Google’s Point of View
  5. Sitemaps: Telling Google Where to Look
  6. One Thing People Consistently Get Wrong
Share:

Start Here: The Performance Report

This is the one most people open first, and for good reason. The Performance report shows how your site appears in Google Search over time. Four numbers sit at the top, total clicks, total impressions, average click-through rate, and average position.

Clicks are the people who actually visited your site from a search result. Impressions are how many times your pages appeared in results, whether anyone clicked or not. A page can rack up thousands of impressions and almost no clicks, which usually means it’s ranking but the title or description isn’t convincing enough to earn the tap.

Scroll down and you’ll see the queries people searched before finding your site. This is genuinely useful. You’ll often spot searches you never consciously targeted, which can shape what you write about next. You can also switch the view to ‘Pages’ to see which specific pages are doing the heavy lifting.

URL Inspection: What Google Actually Sees

Paste any URL from your site into the search bar at the top and hit Enter. Search Console fetches Google’s most recent cached version of that page and tells you whether it’s been indexed, when it was last crawled, and whether anything blocked it.

This is the first thing worth checking when a page isn’t showing up in search results. Nine times out of ten, the answer is either a noindex tag left on by accident, a crawling block in the site’s robots.txt file, or a canonical tag pointing Google at a different page entirely. URL Inspection surfaces all of that in one place without you needing to dig through code.

Coverage: Which Pages Google Has (and Hasn’t) Indexed

The Coverage report, now folded into the broader ‘Indexing’ section in the current interface, lists every URL Google has tried to process. Pages fall into four buckets, error, valid with warnings, valid, and excluded.

The errors are the urgent ones. A ‘submitted URL not found’ means you’ve asked Google to index a page that returns a 404. A ‘server error’ means Google couldn’t reach the page at all when it tried to crawl it. Neither of those pages will rank.

The excluded list is worth a look too. Pages marked ‘crawled but not indexed’ sit in a grey zone where Google visited the page but decided not to include it. That happens often because the content is too thin or too similar to something else on the site. It’s a signal worth acting on rather than ignoring.

Core Web Vitals: Speed From Google’s Point of View

The Core Web Vitals report shows how real visitors experience your pages on both mobile and desktop. It groups URLs into three buckets, good, needs improvement, and poor. The scores come from real Chrome users visiting your site, not a lab test, so they reflect actual conditions.

A common source of ‘poor’ scores is Largest Contentful Paint, which measures how long it takes the main content of a page to appear. Heavy images, slow server response times, and render-blocking scripts all push that number up.

If you want to dig into what’s causing the drag, Google’s own PageSpeed Insights tool runs against any URL and breaks down exactly what’s holding it back. For a plain-English explanation of what these metrics actually measure, the PageSpeed by Google breakdown on this site covers each one without the jargon.

Sitemaps: Telling Google Where to Look

A sitemap is a file that lists every page you want Google to know about. Submitting one through Search Console doesn’t guarantee indexing, but it does make sure Google isn’t missing pages simply because nothing links to them. Most WordPress sites generate a sitemap automatically.

Once you’ve submitted it, the Sitemaps report shows how many URLs were submitted and how many Google actually discovered. A large gap between those two numbers usually points to a coverage problem worth investigating.

One Thing People Consistently Get Wrong

Search Console shows historical data, not live data. There’s typically a delay of a few days before fresh information appears in the reports. So if you fix a technical error and open the console the next morning expecting the red bar to have disappeared, it probably won’t have.

That’s not a fault. It’s just how the system works, and patience genuinely matters here. Getting the console connected properly is the first step. If you haven’t done that yet, the setup guide for small business sites walks through the verification process from scratch.

Share:

Ready to take the next step?

Get in touch today and find out how we can help.

Get In Touch
Privacy Overview

Yorkshire Design uses cookies so that we can provide you with the best user experience possible.

Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.