What is Google Search Console?

Google Search Console is Google’s free reporting tool for site owners. It shows how Google crawls, indexes and ranks a site: which queries it appears for, how many impressions and clicks each page gets, which URLs are indexed and which were excluded and why, and whether the site has problems with mobile usability, Core Web Vitals, security or manual penalties. It is the only source of search performance data that comes from Google itself rather than from a third party’s estimate.

Search Console does not change anything on a site. It reports, and it accepts a few requests: submit a sitemap, ask for a URL to be crawled, confirm that a problem has been fixed. Everything it tells you still has to be acted on in the site’s code and content, which is why it is the first tab we open in any SEO audit and the last one we check after a launch.

What Search Console reports

• Performance. Clicks, impressions, average position and click-through rate for every query and page, filterable by country, device, date and search type (web, image, video, news, and Discover where it applies). Sixteen months of history.
• Page indexing. Every URL Google knows about, grouped as indexed or not indexed, with the reason for each exclusion: noindex tag, redirect, canonical pointing elsewhere, crawled but not indexed, discovered but not crawled, soft 404, server error.
• URL Inspection. The status of one specific URL: whether it is indexed, which canonical Google chose, when it was last crawled, what the page looked like when it was rendered, and a live test with the option to request indexing.
• Experience. Core Web Vitals from real Chrome users, HTTPS coverage, and historically mobile usability.
• Enhancements. Structured data Google found on the site (FAQ, product, breadcrumb, review and others), with errors and warnings per type.
• Links. The pages on other sites that link to yours, which pages they point at, and the site’s own internal link counts.
• Security and manual actions. Hacked-site warnings and penalties applied by a human reviewer. Empty is the correct state.
• Sitemaps and removals. Submitted XML sitemaps with their discovered URL counts, and a tool for temporarily hiding a URL from results.

Setting it up correctly

Most Search Console mistakes happen at setup. The property type is the first one.

• A domain property (verified through DNS) covers every protocol and subdomain: http, https, www, non-www and anything else under the domain. This is the one to use.
• A URL-prefix property covers one exact prefix, such as https://www.example.com/. Sites that only have this type often have a second, forgotten property for the http or non-www version, with the data split between them.

Verification can be done through a DNS record, an HTML file, a meta tag, Google Analytics or Google Tag Manager. DNS is the most durable, because theme changes and plugin updates cannot remove it. After verification, submit the sitemap, confirm that the indexing report shows the right number of pages, and add any other people who need access as users rather than sharing a login. Businesses with more than one web property can manage them from one account, which our note on Search Console platform properties covers.

Reading the performance report without fooling yourself

The performance report is where most of the misreadings happen, because the four headline numbers interact.

• Impressions count appearances, not views. A result at position 48 on page 5 counts as an impression if the page was requested, even though no person scrolled to it. Rank-tracking tools that fetch 100 results generate impressions at deep positions, and on small sites they can be a large share of the total. Impressions at positions 1 to 10, and mobile impressions, are the better proxies for human exposure.
• Average position is an average. A page ranking 3 for one query and 60 for another shows as 31. Look at position per query, not per page.
• Brand queries inflate everything. Searches for your own name produce high positions and high click-through rates. Filter them out to see how the site performs for people who do not already know you.
• Sitelinks are counted per URL. When Google shows your homepage with six sitelinks, each linked page records an impression at a high position with no click. Service pages showing position 4 with zero clicks are usually this, not a problem.
• Anonymized queries are hidden. A share of queries, often large on smaller sites, is withheld for privacy and appears only in the totals. The queries you can see are a sample.
• Data lags and is sampled in exports. The last two or three days are incomplete, and an export caps at 1,000 rows per table unless you use the API or Looker Studio.

The indexing report is the diagnostic tool

The page indexing report answers the question that precedes all ranking questions: is the page in Google at all? Its reasons are specific and most have a clear fix. A page excluded by a noindex tag was either deliberately kept out or launched with a staging setting still on. “Alternate page with proper canonical tag” is normal for paginated and filtered URLs. “Crawled, currently not indexed” means Google saw the page and decided it was not worth keeping, which is a content and indexability question rather than a technical one. “Discovered, currently not indexed” means Google has not fetched it yet, which on a small site usually means it needs stronger internal links and a sitemap entry, and a request through URL Inspection.

The report keeps history, so a URL that was fixed weeks ago can still show its old status until Google recrawls it. The Validate Fix button prompts a recrawl and tracks the result, and is worth pressing after every redirect or template change.

Search Console and Google Analytics

The two tools measure different things and disagree on purpose. Search Console counts clicks on Google results; Google Analytics 4 counts sessions that started on the site, which excludes clicks that bounced before the tag loaded and includes visits from every source. Clicks in Search Console will usually run higher than organic sessions in GA4, and the queries are only available in Search Console because Google does not pass them to analytics. Linking the two accounts puts a Search Console report inside GA4, which is convenient, but the source of truth for query data stays in Search Console.

What to check, and how often

• After a launch, migration or redesign: the indexing report for noindex or redirect surprises, the sitemap’s discovered count, and URL Inspection on the five most important pages. Same day.
• Weekly: nothing, unless a campaign is running. Daily fluctuation is noise.
• Monthly: performance compared to the previous period, filtered to non-brand queries; the indexing report’s not-indexed count; any new manual action or security issue.
• Quarterly: a full export of queries and pages, which is the basis of the content decisions we make. Pages ranking 4 to 15 with impressions and no clicks are the fastest wins on any site, because a better title and description can change the click-through rate without changing the ranking.

Search Console on WordPress

WordPress sites generate URLs that Search Console will surface and that should usually be kept out of the index: attachment pages, tag and author archives, paginated comment URLs, feed URLs and the query-string variants that caching and tracking produce. Yoast and similar plugins handle most of this, and the indexing report is where you confirm they did. The other WordPress-specific check is the sitemap: when a custom post type is added or a page is converted to an archive, the sitemap has to include it, and a cached copy of the old sitemap at the edge can keep serving stale URLs to Google after the site itself is correct. Always check the sitemap at the exact URL Google requests, not the one the plugin says it generated.

Why it matters more than a rank tracker

Rank-tracking tools estimate; Search Console records. The tracker tells you where a page ranked when the tool checked, from the tool’s location, on the tool’s device. Search Console tells you what real searchers saw and clicked, across every query including the ones no tool tracks. Both have a place: the tracker for watching specific competitive terms week to week, Search Console for understanding what the site actually earns. Decisions about which pages to improve, which titles to rewrite and which content to build should come from the second.

Reading Search Console properly is part of every technical SEO engagement and every audit we run. If your site has impressions and no clicks, or pages Google refuses to index, book a discovery call and we will go through the report with you.