Google Search Console is the most important free SEO tool available. It is the only tool that shows you exactly how Google sees your website — not an estimate, not a third-party approximation, but direct data from Google's own systems about what it crawls, what it indexes, what queries it shows your pages for, and what technical issues are preventing your pages from ranking.
This guide covers every step of setting up Search Console correctly, what each report shows, and how to build the weekly monitoring routine that turns the tool from a diagnostic tool into a proactive growth driver.
What Google Search Console shows that no other tool can
Every paid SEO tool estimates organic performance based on crawling the web and modelling search behavior. Google Search Console does not estimate. It reports.
| Data point | What it shows | Why no other tool can replicate it |
|---|---|---|
| Actual impressions | How many times your pages appeared in Google results for specific queries | Comes directly from Google's serving logs — third-party tools model this from sampled data |
| Actual clicks and CTR | How many users clicked through to your site and the click-through rate per query | Only Google knows which results were clicked by actual users |
| Actual ranking position | Your average position in results for each query and page combination | Based on real served results, not tool crawler estimates |
| Index status | Which pages Google has indexed, which are excluded, and why | Only Google's own index database holds this information |
| Core Web Vitals field data | Speed and stability metrics measured from real user sessions on your pages | Collected from Chrome users — no third party has access to this data at scale |
| AI Overview appearances | Which queries trigger AI Overviews for your pages (added 2025) | Only available through Search Console — not yet available in any third-party tool |
Step 1: Create your Search Console account and add a property
Navigate to search.google.com/search-console and sign in with the Google account that manages your website. If this is your first time, you will be prompted to add a property. You can also add a new property from the property selector dropdown at any time.
Google offers two property types, and the choice affects every report you will see:
- Domain property (recommended): Covers your entire domain, including all subdomains (www, m, blog, etc.) and both HTTP and HTTPS versions. A domain property at example.com captures all data for www.example.com, blog.example.com, and any other subdomain automatically. This is the correct choice for almost every site.
- URL-prefix property: Covers only URLs beginning with a specific prefix. Use this only if you need to track a specific subdirectory or subdomain separately from the rest of your domain — for example, a blog at example.com/blog/ that is managed by a different team.
Step 2: Verify ownership of your property
Verification proves to Google that you have authority over the domain you are adding. The process differs between property types:
Domain property verification DNS record method
Domain properties can only be verified via a DNS TXT record. Google provides a unique TXT record value that you must add to your domain's DNS settings through your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.). Log into your registrar's DNS management panel, add a new TXT record with the value Google provides, and click Verify in Search Console. DNS propagation typically takes a few minutes but can take up to 48 hours in some cases. The Search Console verification screen shows whether the record has been found.
URL-prefix property verification multiple methods
URL-prefix properties offer five verification methods. The recommended ones in order of reliability:
- HTML file upload: Download the provided HTML file and upload it to the root directory of your website. Navigate to the file in your browser to confirm it is accessible, then click Verify.
- Google Tag Manager: If GTM is installed on your site with a published container, select the GTM verification option. GTM must be in place and the container tag firing on all pages.
- Google Analytics: If GA4 is already installed and the same Google account has edit access, select the Analytics verification option. This links verification to the analytics installation.
- HTML meta tag: Add a provided meta tag to your homepage's head section. Suitable for sites where you can edit the HTML but cannot upload files or use GTM.
Step 3: Submit your XML sitemap
Submitting your sitemap tells Google where to find all your important pages. This accelerates discovery of new content and ensures Google has a complete picture of your site's URL inventory.
In Search Console, click Sitemaps in the left navigation under Indexing. Enter the path to your sitemap — typically /sitemap.xml or /sitemap_index.xml — and click Submit. Google will fetch and process the sitemap and display the status: how many URLs were submitted and how many were indexed. Check this section after every major content migration and whenever you publish a large batch of new pages. Full sitemap creation and management guidance is in the XML sitemap guide.
If your site has multiple sitemaps — a common pattern for sites with separate sitemaps for posts, pages, products, and images — submit each one individually. The Coverage report will then show the indexing status of all URLs across all submitted sitemaps.
Step 4: Link Search Console to Google Analytics
Linking Search Console to GA4 is one of the highest-value configuration steps available and takes under two minutes. Once linked, GA4 gains access to the Queries and Landing Pages reports showing which search terms drive traffic to which pages — data that is not available in GA4 without this connection.
To link: in GA4, go to Admin, then Property Settings, then Search Console links. Click Link, select your verified Search Console property, and save. Within 48 hours, a Search Console collection appears in GA4 with the Query and Landing Page reports. Alternatively, link from within Search Console itself: go to Settings, then Associations, then Google Analytics, and add your GA4 property. Full GA4 setup guidance is in the Google Analytics setup guide.
Step 5: Configure email alerts
Search Console can notify you of critical issues automatically without requiring you to log in and check. In Settings, then Email Preferences, enable notifications for: Coverage issues (when Google encounters new indexing errors), Manual actions (when Google applies a penalty to your site), and Security issues (when Google detects malware or hacking).
These alerts surface problems that often go unnoticed for weeks in sites without active monitoring. A manual action or a sudden coverage issue that is caught within hours is far less damaging than one discovered only when traffic has already declined significantly.
The key reports and how to use each one
Performance report
The Performance report is the core SEO report in Search Console. It shows clicks, impressions, CTR, and average position for every query your site appears for, every page that receives organic traffic, and every country in your audience. The 2025 update added a branded vs non-branded filter — a major addition that lets you separate brand-driven traffic (people searching for your name) from non-branded organic performance (people finding you through topical queries).
The most valuable SEO workflow in this report: filter by Queries, sort by Impressions, and look for queries with high impressions but low CTR. These are queries where your pages are appearing frequently but not getting clicked — usually a title tag or meta description problem that a short optimization can fix without any content changes. Queries between positions 5 and 15 with decent impression volume are your quickest ranking improvement opportunities: a few targeted optimizations can move them to page one.
Coverage report (now called Indexing)
The Indexing report shows which pages are indexed, which are excluded, and the reason for each exclusion. Understanding the status categories is essential for diagnosing indexing issues:
| Status | What it means | When to act |
|---|---|---|
| Valid — indexed | Page is in Google's index and eligible to rank | No action needed — monitor for unexpected drops |
| Valid with warning | Indexed but a minor issue was detected (e.g. chosen canonical differs from declared canonical) | Review the specific warning — usually fixable with a canonical tag correction |
| Excluded — noindex | Page has a noindex directive | Confirm this is intentional — accidental noindex on important pages is a common issue |
| Crawled — currently not indexed | Google crawled the page but chose not to index it | Review content quality, uniqueness, and internal links pointing to the page |
| Discovered — currently not indexed | Google knows the page exists but has not crawled it yet | Add internal links from important pages; ensure the URL is in the sitemap |
| Duplicate — Google chose different canonical | Google selected a different URL as the preferred version | Review and correct canonical tags and ensure internal links point to the canonical URL |
Core Web Vitals report
The Core Web Vitals report shows LCP, INP, and CLS performance measured from real Chrome users visiting your pages — field data, not lab estimates. It segments pages into Good, Needs Improvement, and Poor categories for both mobile and desktop. Prioritize fixing pages in the Poor category on mobile first, since Google uses mobile-first indexing. The Core Web Vitals guide covers how to diagnose and fix each metric.
Links report
The Links report shows your top linked pages (which of your pages have the most internal and external links), your top linking sites (which domains link to you most), and your top linking text (the anchor text used in links to your site). Use the external links section to identify your most authoritative pages and ensure those pages have strong internal links distributing their authority to related content. The backlink analysis guide covers how to use this data within a broader link research workflow.
URL inspection tool
The URL Inspection tool is the most powerful diagnostic in Search Console. Enter any URL on your site to see: the last date Google crawled it, whether it is indexed and under what canonical, how Google rendered the page (crucial for JavaScript sites), and any crawl issues encountered. For any page that is not performing as expected — not indexed, not ranking despite optimization — start with URL Inspection to understand exactly what Google sees when it visits that page.
In 2026, you can also use URL Inspection to request Google recrawl a specific page after updates. Click Request Indexing after an important content change to signal Google to recrawl the updated version sooner than its normal crawl schedule would.
Building a weekly Search Console review routine
Search Console's value compounds with consistent monitoring. A focused 20-minute weekly review covering the right metrics catches problems early and surfaces opportunities before competitors act on them.
- Performance report: Check week-over-week click and impression trends. Filter for non-branded queries to see underlying organic performance. Identify any queries where position has dropped by 3 or more positions.
- Indexing report: Check for new coverage errors. Any new Crawled — currently not indexed or Excluded by noindex status on pages that should be indexed is an immediate action item.
- Core Web Vitals: Check for any newly flagged Poor URLs on mobile. A page moving into the Poor category has usually been affected by a recent template or asset change.
- Manual actions: Confirm no manual actions are active. A penalty appearing here requires immediate investigation and remediation before anything else.
- Quick win scan: In Performance, filter for queries ranking between positions 5 and 15 with at least 200 monthly impressions. These are your active SEO opportunities for the week.
Common Search Console setup mistakes
| Mistake | What you miss | Fix |
|---|---|---|
| Adding URL-prefix property instead of domain property | Misses subdomains and HTTP/HTTPS variants — partial data picture | Add a domain property to capture all versions of your site in one view |
| Not submitting XML sitemap | Google discovers pages more slowly and may miss newly published content for weeks | Submit your sitemap immediately after verification and update it after major content migrations |
| Not linking to GA4 | Cannot see which organic queries drive engagement and conversions on specific pages | Link the accounts in GA4 Admin or Search Console Settings |
| Checking only when traffic drops | Misses gradual indexing decay, emerging technical issues, and ranking opportunities | Build a 20-minute weekly monitoring routine across the core reports |
| Ignoring the Coverage report | Misses accidental noindex tags, canonicalization errors, and crawl issues silently harming rankings | Review Coverage weekly and investigate any new exclusion statuses immediately |
| Not setting up email alerts | Manual actions and security issues go undetected for weeks until traffic damage is visible | Enable email notifications for Coverage, Manual Actions, and Security Issues in Settings |
Conclusion
Google Search Console is not just a setup task you complete once and reference occasionally. It is the most accurate picture of your site's relationship with Google available anywhere, and it improves as you build a routine around it. The setup steps in this guide — domain property creation, DNS verification, sitemap submission, GA4 linking, and alert configuration — take under an hour to complete and pay dividends in data quality for as long as your site exists.
Once set up, the value comes from the routine: weekly performance scans for ranking movements and quick wins, indexing report monitoring for technical issues, Core Web Vitals tracking for page experience, and the URL Inspection tool for diagnosing any page that is not performing as expected. Pair this with the Google Analytics setup guide to connect your Search Console query data to conversion tracking, and the technical SEO guide for the full infrastructure framework that Search Console monitors.
