Search Console: The Complete Guide

Google Search Console is the free service that shows you how Google actually sees your site: which pages are indexed, which queries bring clicks, and which errors are quietly holding you back. If you own a website and you are not looking at it, you are optimizing in the dark. This guide walks through what it is, how to set it up, and how to read every core report.

What Google Search Console actually is

Search Console is a dashboard that connects your website to Google's index. According to Google Search Central, it "provides information on how Google crawls, indexes, and serves websites," which lets owners monitor and improve their Search performance. It is not the same thing as Google Analytics: Analytics tells you what people do once they land on your site, while Search Console tells you what happens before the click, in Google's results.

Three ideas are worth separating up front. Crawling is Google discovering and fetching your URLs. Indexing is Google storing and understanding those pages so they are eligible to appear. Serving (or ranking) is Google deciding which stored pages to show for a given query. Search Console gives you visibility into all three stages, which is why it is the natural hub for any serious search program. If you are new to the wider discipline, pair this guide with our complete SEO guide so the terminology lines up.

Why it matters for every site owner

You cannot fix what you cannot see. Without Search Console you have no reliable way to know whether Google has indexed your new blog post, whether a template change accidentally blocked a whole section, or which keywords are one position away from page one. The tool surfaces problems that never show up in a normal browser visit, because your pages look fine to you while returning errors to Googlebot.

• It flags indexing problems before they cost you months of traffic.
• It shows the exact search queries you rank for, including ones you never targeted.
• It reports Core Web Vitals and mobile usability issues that affect experience.
• It is the official channel Google uses to warn you about manual actions and security issues.

Setting up and verifying your property

Go to the Search Console site, sign in with a Google account, and add a property. You will be offered two property types, and the choice matters.

1. Domain property. Covers every subdomain (www and non-www) and both http and https under one roof. Verification is done through a DNS TXT record with your domain registrar. This is the recommended option because it captures all your traffic in one place.
2. URL-prefix property. Covers only the exact prefix you enter, for example the https version of one subdomain. It is quicker to verify (HTML file upload, HTML meta tag, Google Analytics, or Google Tag Manager) but gives a partial picture.

After verification, do not expect instant data. Search Console starts collecting from the moment you verify and typically shows a couple of days of lag. Give it a week before you judge trends.

The Performance report

Performance is where most people live. It records four metrics for the queries and pages that appeared in Google results: clicks, impressions, average click-through rate (CTR), and average position. An impression is counted when your result is shown; a click is when someone taps through; CTR is clicks divided by impressions; position is your average ranking for that row.

Use the filters and comparison view deliberately. Compare the last 28 days to the previous 28 to spot movement. Filter by page to see which queries a single article ranks for. The most actionable pattern to hunt for is high impressions with low CTR at a decent position: that usually means your title and meta description are not compelling enough, and rewriting them is a fast win that needs no new content.

• High impressions, low CTR, position 3 to 10: rewrite the title tag and meta description.
• Rising impressions, position 8 to 20: the page is gaining trust; add depth and internal links to push it up.
• Sudden clicks drop with steady impressions: check whether a competitor won a rich result or your snippet changed.

URL Inspection and the Pages report

The URL Inspection tool answers one question for a single URL: is this page indexed, and if not, why? Paste any URL from your verified property and Search Console reports its coverage state, the last crawl date, the canonical Google selected, and whether the page is mobile friendly. When you publish or heavily update a page, use the "Request indexing" button to nudge Google to recrawl sooner. This does not guarantee a ranking, only a faster look.

The Pages report (previously called Coverage) is the site-wide version. It groups your URLs into indexed and not-indexed buckets and lists the reason for each exclusion, such as "Crawled, currently not indexed," "Discovered, currently not indexed," "Duplicate without user-selected canonical," or "Not found (404)." Do not panic at a large not-indexed number, because it usually includes intentional exclusions like redirects and canonicalised duplicates. Focus on reasons that represent real content you want ranked. The "Not found (404)" bucket matters because, as Google Search Central explains, a URL returning 404 is dropped from the index and crawled less over time. If you see many 404s, our guide to 404 pages and how to fix them walks through the cleanup.

Sitemaps, Core Web Vitals, and the other reports

Submitting an XML sitemap under the Sitemaps report gives Google a clean list of the URLs you consider important. It does not force indexing, but it speeds discovery, especially for new or deep pages. Submit the sitemap URL once and check back for its "Success" status and the count of discovered URLs.

The Core Web Vitals report groups your URLs by real-world loading, interactivity, and visual-stability scores drawn from field data. Poor scores can dent rankings and definitely dent experience, so treat them as a prioritised to-do list; our Core Web Vitals technical guide explains each metric and its fix. Other reports worth a periodic glance include Enhancements (rich result eligibility for structured data), Manual Actions, Security Issues, Links (your top linked pages and linking sites), and the Removals tool for temporarily hiding a URL.

Beyond Google: Bing and the wider toolkit

Search Console only reports on Google. Bing, which also powers many other search surfaces, has its own free equivalent, and you can import your Google verification into it in a few clicks. If you care about coverage outside Google, set up Bing's search console too. For a deeper walkthrough of the Google product specifically for organic optimisation, see our companion piece on using Search Console for SEO. Treat these tools as complementary: each engine only tells you about itself.

Frequently asked questions

Is Google Search Console free?

Yes. Search Console is a completely free product from Google. There is no paid tier and no usage limit for a normal site. You only need a Google account and the ability to prove you own the property.

What is the difference between Search Console and Google Analytics?

Search Console reports on what happens in Google Search before the click: impressions, queries, rankings, and indexing health. Google Analytics reports on what visitors do after they arrive, such as sessions, engagement, and conversions. They answer different questions and are best used together.

How long does it take to see data after verifying?

Data begins collecting from the moment you verify, but it typically lags by two to three days and is not backfilled for the period before verification. Wait about a week before drawing conclusions from trends.

Does Search Console improve my rankings?

Not directly. It is a diagnostic and monitoring tool, not a ranking lever. It improves rankings only indirectly, by showing you the errors, opportunities, and queries you then act on.

Why are my pages showing as "Discovered, currently not indexed"?

That status means Google knows the URL exists but has chosen not to crawl or index it yet, often due to perceived low value, thin content, crawl-budget limits, or duplication. Strengthen the page, add internal links to it, and make sure it is in your sitemap.

Should I use a domain property or a URL-prefix property?

Use a domain property when you can edit DNS, because it consolidates www, non-www, http, and https into one view. Use a URL-prefix property only when DNS verification is not possible or you deliberately want to isolate a single subdomain or protocol.