Google Search Console is free, it is official, and it contains data that no third-party SEO tool can replicate — because it comes directly from Google. It is the first tool I recommend to any small business owner starting out — and I cover exactly what to do with it in SEO training for small business owners. It tells you what queries Google is showing your site for, which pages are indexed and which are not, where your structured data is broken, and how your Core Web Vitals scores look to real users. I have been using it for over a decade and it is still the first place I go when diagnosing a ranking problem, investigating an indexation issue, or evaluating a site’s overall search health. Most site owners either have not set it up or use it only to glance at the traffic graph.

Setting Up GSC Correctly

Verification sounds basic but it is often done wrong. You should verify all meaningful variants of your domain: the www and non-www versions, and both HTTP and HTTPS — four properties total. Add them as separate properties or use domain-level verification (which covers all variants under a single property). The preferred verification method is DNS TXT record verification because it survives theme changes, platform migrations, and plugin updates without breaking. HTML file and meta tag verification breaks whenever the page they are on is significantly modified.

Inside my SEO training, I run through GSC setup in the first technical session because I have seen people spend months interpreting partial data, missing half their search traffic because they only verified the https://www version and their site redirects from a non-www base domain.

The Performance Report: Reading It Productively

The Performance report shows clicks, impressions, average position, and click-through rate for the queries your site is receiving. The default date range is 3 months — change it to 16 months to see meaningful trends. The four most useful analyses you can run in this report:

  • High impressions, low CTR: Google is placing your site in results for these queries but users are not clicking. This typically indicates your title tag and meta description need to be rewritten for better relevance and appeal — or that a rich result (schema markup) could improve your listing’s visual appearance in the SERP.
  • Good average position (top 10), unexpectedly low clicks: You rank on page one but conversion to clicks is below what position should generate. Your listing may be missing structured data enhancements, or a competitor’s listing has richer SERP features that attract attention away from yours.
  • Queries you did not intentionally target: These are content expansion signals. If Google is organically ranking you for something adjacent to your primary topic, a dedicated page on that adjacent topic will often rank quickly given your existing domain context.
  • Position tracking over time: Compare the same date ranges year over year to identify whether changes in rankings correlate with algorithm updates, site changes, or content updates you made.

The Index Coverage Report

This report is where you find out which pages Google has indexed, which it attempted to index but could not, and which it decided not to index. The distinction between categories matters significantly:

  • Excluded — noindex tag: Correct for pages you intentionally excluded. A serious problem if it includes pages you expected to be indexed.
  • Crawled — currently not indexed: Google visited the page and decided not to include it in the index. This is nearly always a content quality signal — thin content, near-duplicate of another indexed page, or content that does not provide distinct value.
  • Discovered — currently not crawled: Google found a URL reference to the page but has not visited it yet. On large sites, this indicates crawl budget constraints and typically means your most important pages need stronger internal link signals.
  • 404 and redirect errors: Broken internal links and failed redirects that waste crawl budget and potentially lose link equity pointing to those URLs.

The Salterra team starts every technical audit with this report. The pattern of errors across these categories tells you more about a site’s indexation health than any other single data source, and it directs the rest of the audit toward the issues most likely to be causing ranking underperformance.

The URL Inspection Tool

When you need to understand exactly how Google sees a specific page — what it indexed, when it last crawled it, which canonical it selected, whether it can access all required resources — URL Inspection is your tool. It renders the page as Googlebot would render it, showing you the actual HTML the crawler processes after JavaScript execution. This is the correct tool for debugging schema implementation problems: it tells you whether Google found your structured data, whether it parsed it correctly, and whether it contains errors — without requiring you to wait for the next scheduled crawl cycle.

Use URL Inspection any time you update a page and want to signal to Google that a fresh crawl is warranted. The ‘Request Indexing’ function tells Google to prioritize the page in its next crawl queue, though it does not guarantee an immediate re-crawl.

Core Web Vitals in Search Console

The Core Web Vitals report shows your site’s LCP, INP, and CLS scores as measured from real Chrome users over the previous 28 days, grouped by issue type and broken down by specific URLs. This is the field data that Google uses as a ranking signal — distinct from the lab data in PageSpeed Insights or Lighthouse. The two data sources will often disagree, and when they do, field data in Search Console is the more relevant number for ranking purposes.

I cover this report and how to prioritize the fixes it surfaces in detail in my Core Web Vitals training resource.

Sitemaps and Crawl Efficiency

Submit your XML sitemap through GSC’s Sitemaps section and monitor it for submission errors. GSC reports how many URLs were submitted versus how many were indexed — a significant gap between those two numbers is diagnostic. It typically means either the sitemap includes URLs that should not be there (noindexed pages, redirects, thin content pages), or the content on those submitted pages has quality issues that caused Google to decline to index them.

A well-maintained sitemap contains only the pages you actually want indexed. Pruning tag archives, author pages, paginated archive pages, and other auto-generated thin content from your sitemap is one of the cleaner signals you can send about your site’s content quality intentions. This comes up consistently in Phoenix SEO training sessions when we audit participant sites live.

Making GSC Part of a Regular Workflow

Google Search Console is not a tool you set up once and check annually. It should be part of a monthly review workflow: check the Performance report for CTR anomalies, review Coverage for new indexation errors, glance at Core Web Vitals for new ‘Poor’ URL groupings, and verify that submitted sitemaps are processing without errors. If you are Phoenix-area based and want to learn this in a structured setting, SEO classes in Phoenix covers the available formats.

For participants in the SEO University cohort, we spend a dedicated session on GSC interpretation because reading the data accurately is a learnable skill that takes practice to develop. It is also central to everything else I teach — GSC is the ground truth that validates or challenges everything else you think you know about how your site is performing in search. My SEO training covers it as a core tool from the first session onward.