Google Search Console Setup: A Practical Guide

Most B2B sites are sitting on a free dataset that tells you exactly which search queries bring buyers to your pages, and almost nobody reads it. The data lives in Google Search Console. It shows the keywords you already rank for, the pages Google has indexed, the errors blocking you, and how your speed and structured data look from Google's side.

Setting it up takes about fifteen minutes. Reading it well is what separates a site that guesses from one that knows where its next deal is coming from. This guide walks through verification, the first three things to do after you connect, and the handful of reports worth checking every month.

We will keep it concrete. Placeholder values are written as YOUR_VALUE_HERE so you can swap them in without confusion.

What Search Console actually gives you

Search Console is Google's direct line to your site. Unlike GA4, which tracks what visitors do once they land, Search Console shows what happens in the search results before the click: which queries you appear for, your average position, how many people see you (impressions), and how many click through.

Four things make it worth the setup time:

The Performance report, your real keyword data, pulled from Google itself rather than a third-party estimate.
The Pages (indexing) report, which tells you whether Google has actually added your pages to its index.
The URL Inspection tool, which lets you ask Google about a single page and request indexing on the spot.
Coverage of technical health: Core Web Vitals, structured data, and sitemap status.

No paid SEO tool replaces this. Ahrefs and Semrush estimate; Search Console reports the truth from the source.

Step 1: Choose a property type and verify it

Before you see any data, you have to prove you own the site. Google calls this verification, and your first decision is which kind of property to create.

A Domain property covers every version of your site at once: http and https, www and non-www, and all subdomains (blog.YOUR_DOMAIN.com, app.YOUR_DOMAIN.com). It is verified through DNS, and for most businesses it is the right choice because nothing gets missed.

A URL-prefix property covers only one exact address, for example https://www.YOUR_DOMAIN.com/. It offers more verification methods and is handy when you want to track a single subdomain or section in isolation.

If you are unsure, create the Domain property. You can always add URL-prefix properties later for granular reporting.

Verifying a Domain property (DNS)

In Search Console, click Add property, choose Domain, and enter YOUR_DOMAIN.com (no https, no www).
Google gives you a TXT record that looks like google-site-verification=YOUR_VERIFICATION_STRING.
Log in to your domain registrar or DNS host (Cloudflare, GoDaddy, Namecheap, Route 53), add a new TXT record at the root (@), and paste the value.
Save, wait for DNS to propagate (often minutes, sometimes a few hours), then click Verify.

If verification fails on the first try, give it an hour and retry. DNS changes are not instant.

Verifying a URL-prefix property

For a URL-prefix property you have more options. The cleanest for most teams:

HTML tag: paste a meta tag into the <head> of your homepage.
Google Analytics: if GA4 is already running with the same Google account and admin access, Search Console can verify through it. Setting up GA4 first makes this almost frictionless, and our guide on GA4 setup for B2B covers that side.
Google Tag Manager: verify through an existing GTM container.
HTML file upload: upload a file Google provides to your root directory.

Pick whichever matches access you already have. There is no SEO advantage to one method over another; they all just prove ownership.

Step 2: Submit your sitemap

Once verified, point Google at your sitemap so it can find your pages efficiently. Most platforms (WordPress with Yoast or Rank Math, Webflow, Shopify, HubSpot CMS) generate one automatically, usually at https://www.YOUR_DOMAIN.com/sitemap.xml or /sitemap_index.xml.

Open it in a browser first to confirm it loads and lists real URLs. Then in Search Console go to Indexing > Sitemaps, enter the path, and submit. Within a day or two the status should read "Success" with a count of discovered URLs.

A submitted sitemap does not force indexing. It helps Google discover pages faster and signals which URLs you consider canonical. If your sitemap lists 80 pages but Search Console later shows only 50 indexed, that gap is a clue worth chasing in the Pages report.

While you are here, confirm your robots.txt file is not blocking anything important. A single stray Disallow: line can hide whole sections from Google, and it is one of the most common technical mistakes we find during audits.

Step 3: Read the Performance report

This is where the value lives. The Performance report shows four metrics over your chosen date range:

Clicks: visits from Google search.
Impressions: how often you appeared in results.
CTR: clicks divided by impressions.
Average position: your mean ranking for the queries shown.

Toggle all four on, then explore the tabs: Queries, Pages, Countries, Devices, and Search Appearance.

Here is a simple read that pays off fast. Open the Queries tab, sort by impressions, and look for queries where you get thousands of impressions but a position around 8 to 20. Those are pages Google already considers relevant, sitting just below the spots that earn clicks. A focused improvement to one of those pages, better title, fuller answer, stronger internal links, often moves it onto page one faster than writing something new from scratch.

How to read Performance data (illustrative numbers)
Query	Impressions	Avg. position	What to do
b2b lead generation	12,400	11.2	High potential. Improve the page, win page one.
marketing analytics setup	3,100	4.8	Close to the top. Tighten the title and CTR.
what is cpl	900	2.1	Already strong. Leave it, monitor.

The numbers above are illustrative, but the pattern is real: your fastest wins usually hide in queries ranking just off page one.

Step 4: Check indexing in the Pages report

Under Indexing > Pages, Search Console splits your URLs into "Indexed" and "Not indexed", with reasons for the latter. Common reasons and what they mean:

Crawled, currently not indexed: Google saw the page and chose not to index it, often a quality or thin-content signal. Worth reviewing the content.
Discovered, currently not indexed: Google knows the URL exists but has not crawled it yet. Usually a crawl-budget or freshness issue; common on large or new sites.
Excluded by 'noindex' tag: intentional or accidental. If an important page shows here, check your CMS settings.
Duplicate, Google chose different canonical: Google picked another URL as the primary version. Check your canonical tags.

For a single page you want indexed now, use the URL Inspection tool at the top of Search Console. Paste the URL, and if it is eligible, click Request indexing. This is the right move after publishing something new or fixing a page, though Google treats it as a request, not a command, so do not spam it.

Indexing problems are where Search Console connects to the rest of your technical work. If whole sections are missing, the cause usually lives in your crawl setup, site architecture, or page templates, the territory covered in our walkthrough of technical SEO.

Step 5: Watch Core Web Vitals and Experience

The Core Web Vitals report (under Experience on many accounts) groups your URLs into Good, Needs improvement, and Poor, based on real Chrome user data for loading (LCP), interactivity (INP), and visual stability (CLS). Slow pages cost you both rankings and conversions, and the fix is rarely a single setting. If this report shows red, our guide to page speed and SEO breaks down where the time usually goes.

One note on accuracy: Search Console reports field data from real visitors, so it can lag a deploy by up to 28 days. If you just shipped a speed fix, give it a few weeks before judging the result here.

Turning the data into leads

Setup is the easy part. The habit that compounds is a monthly fifteen-minute review:

Open Performance, set the date range to the last 3 months, and note your top movers, up and down.
Find three queries ranking in positions 8 to 20 and assign each to a page improvement.
Check the Pages report for any new "Not indexed" spikes.
Glance at Core Web Vitals for new "Poor" URLs.

For a B2B site, the queries that matter are not always the highest-volume ones. A query like "YOUR_SERVICE pricing" or "YOUR_SERVICE for manufacturers" may bring 40 visits a month and close a five-figure deal. Filter for those buying-intent terms and treat the pages behind them as priorities. That same logic, ranking the keywords by the money behind them, drives how we approach search intent across a whole site.

Common setup mistakes

A few that quietly cost teams data:

Verifying only the www version while traffic also lands on non-www (or vice versa). The Domain property avoids this.
Forgetting to submit the sitemap, then wondering why new pages take weeks to appear.
Treating "Request indexing" as a ranking button. It speeds discovery, nothing more.
Adding the property and never logging back in. Search Console rewards the people who read it.

FAQ

Is Google Search Console free?

Yes, completely. There is no paid tier and no usage limit that a normal business will hit. The only cost is the time to set it up and read it.

How long until I see data after verifying?

Performance data starts appearing within two to three days of verification, and Search Console holds up to 16 months of history once it begins collecting. The first day or two can look empty, which is normal.

Do I need Search Console if I already have GA4?

Yes, they answer different questions. GA4 tracks behavior after the click: sessions, conversions, and revenue. Search Console shows what happens in search before the click, including the exact queries and your ranking position. Connect both for the full picture; Search Console handles the search half, GA4 the behavior half.

What is the difference between a Domain and URL-prefix property?

A Domain property covers every protocol and subdomain of your site through DNS verification, so nothing is missed. A URL-prefix property covers one exact address and offers more verification methods. Most businesses should start with a Domain property.

Why are some of my pages "not indexed"?

The most common reasons are thin or duplicate content ("Crawled, currently not indexed"), a page Google has not gotten to yet ("Discovered, currently not indexed"), or an accidental noindex tag. The Pages report lists the exact reason for each URL, which tells you where to look.

Can I use Search Console for multiple websites?

Yes. One Google account can hold hundreds of properties, and you can grant team members access with Owner, Full, or Restricted permissions. Agencies manage every client this way.

The short version

If you do nothing else this week, do this: verify a Domain property, submit your sitemap, and bookmark the Performance report. That alone puts you ahead of most competitors who never look at their own search data.

A quick checklist before you close the tab:

Domain property verified through DNS.
Sitemap submitted and showing "Success".
robots.txt not blocking key sections.
Performance report bookmarked, monthly review on the calendar.
Core Web Vitals checked for "Poor" URLs.

The data is free and it is yours. The harder part is acting on it consistently, month after month, while still running the business. If you would rather have someone turn these reports into a ranking and lead-generation plan, get a 30-minute review of your Search Console data with the Lead The Way team. We will show you the three pages most likely to move and what to do with them.