Google Search Console: The Complete Guide

Google Search Console is a free tool, built and maintained by Google, that shows you exactly how Google sees your website — what search queries bring people to your pages, whether pages are indexed correctly, and what technical problems Google has actually found. Unlike third-party rank trackers, this data comes straight from Google, which makes it the most reliable source available for understanding your organic search performance. It requires no budget and takes about fifteen minutes to set up properly.

Step 1: Add and verify your property

Go to search.google.com/search-console and sign in with a Google account your business controls long-term. You'll be asked to choose a property type.

Domain property (recommended if you can)

Covers your entire domain — all subdomains and both http/https versions — under one unified view. Verification requires adding a TXT record to your domain's DNS settings, which typically means logging into wherever you registered your domain (GoDaddy, Namecheap, your hosting provider) or asking whoever manages your DNS to add it for you.

URL-prefix property (easier to verify)

Covers just the specific URL you enter, such as https://www.yoursite.com. Offers several simpler verification options: uploading an HTML file to your site, adding a meta tag to your homepage, or, if you've already connected Google Analytics or Google Tag Manager, verifying through that existing connection with one click.

Step 2: Submit your sitemap

A sitemap is a file listing every important page on your site, and submitting it helps Google discover your pages faster and more completely than relying on crawling alone.

1. Find your sitemap URL — most platforms generate one automatically at a predictable address like yoursite.com/sitemap.xml. WordPress SEO plugins, Shopify, and Squarespace all generate one without extra setup.
2. If your platform doesn't generate one automatically, our XML Sitemap Generator tool builds a valid one from a list of your URLs.
3. In Search Console, go to Sitemaps (left sidebar), paste in just the path (e.g. sitemap.xml) and click Submit.
4. Check back in a day or two — the status should update from "Pending" to "Success," along with a count of discovered URLs.

Step 3: Understand the Performance report

This is the report you'll return to most often. It shows total clicks, total impressions, average click-through rate, and average position — for your site overall, and broken down by individual query, page, country, and device.

• Clicks — actual visits to your site from Google Search results.
• Impressions — how many times your site appeared in search results, whether or not anyone clicked.
• CTR (click-through rate) — clicks divided by impressions. A page with high impressions but low CTR often has a title or meta description that isn't compelling enough to earn the click, even though it's ranking.
• Average position — your average ranking position across all the queries a page showed up for, which can be misleading in isolation since it blends high-volume and obscure queries together.

The Queries tab under Performance is worth checking regularly — it shows the actual search terms bringing traffic to your site, including ones you may never have deliberately targeted. It's a genuinely useful, free source of keyword research drawn from your own real search visibility.

Step 4: Understand the Pages (Coverage) report

Found under Indexing > Pages, this report shows which of your pages are indexed and, critically, why any pages aren't. Common statuses worth knowing:

• Indexed — the page is in Google's index and eligible to appear in search results.
• Crawled - currently not indexed — Google visited the page but chose not to index it, often due to thin content or close similarity to another page.
• Discovered - currently not indexed — Google knows the page exists but hasn't crawled it yet, sometimes a sign of limited crawl priority.
• Excluded by noindex tag — the page is intentionally blocked from indexing, which is fine if deliberate and a real problem if accidental.
• Page with redirect or Not found (404) — expected for old URLs that have been redirected or removed, but worth reviewing if they show up on pages you didn't intend to remove.

Step 5: Check Core Web Vitals and mobile usability

Under Experience, Search Console reports on Core Web Vitals — Google's measurements of loading speed, interactivity, and visual stability, based on real user data from Chrome — grouped into "Good," "Needs improvement," and "Poor" for both mobile and desktop. This is a genuinely useful early warning system, since a slow or unstable page can quietly work against you even when everything else about your SEO is solid.

Step 6: Set up email alerts and check Manual Actions

Under Settings, make sure email notifications are turned on — Search Console will alert you to critical issues (a spike in errors, a manual action, a security issue) without requiring you to log in and check manually. Also check Security & Manual Actions periodically; a manual action here means Google has identified a specific policy violation on your site and applied a targeted penalty, which is different from, and rarer than, an ordinary ranking fluctuation.

Once Search Console is set up, connecting it to Google Analytics 4 under GA4's Admin > Product Links gives you query-level search data alongside on-site behavior data in one place. For a deeper walkthrough of reading the Performance report specifically, see how to read a Search Console performance report.