How to use Google Search Console

Updated 2026-08-07

Set up a property, verify it, and learn the four reports that matter. A practical starting order for Search Console, with the traps that mislead beginners.

Search Console is free, it is the only place your actual Google search data exists, and it presents that data in a way almost designed to be misread. This is the order worth learning it in.

1. Add and verify a property

Two property types, and the choice matters more than it looks. A domain property (sc-domain:example.com) covers every subdomain and both protocols but can only be verified by DNS. A URL-prefix property covers one exact prefix and accepts five verification methods: HTML file, meta tag, DNS record, Google Analytics, or Tag Manager.

If you have DNS access, use a domain property. It is the complete picture and it survives migrations. Full comparison in domain vs URL-prefix.

Then submit a sitemap once — see submitting a sitemap — and stop touching it.

2. Wait

Verification is instant; data is not. Search Console starts collecting from the day you verify and does not backfill. A new property shows nothing useful for a few days, and performance data always runs about two days behind regardless. That right-edge dip on every chart is the reporting lag, not a problem.

3. Learn the performance report properly

This is 90% of the value, and where the misreadings live. Four metrics, and average position is switched off by default — tick it.

• Impressions — times a link to you appeared in results. Includes page 2 and beyond.
• Clicks — times someone clicked through to you.
• CTR — clicks ÷ impressions. Deep-ranking terms drag it down for reasons unrelated to your titles.
• Average position — an impression-weighted mean, not your rank. It moves when your query mix moves even if nothing has changed in the rankings.

Exact definitions in clicks, impressions and CTR, and the position trap in what average position actually means.

Then use the tabs. Queries is what people searched, Pages is what they landed on, and Countries / Devices narrow a problem fast. Set the range to three months; anything shorter is too noisy to act on.

4. Check indexing when something is missing

The Pages report says which URLs are indexed and why the rest are not. Use URL Inspection for one specific page — see the URL Inspection tool. The two statuses that confuse everyone are covered in crawled vs discovered, currently not indexed.

The three things to actually do with it

1. Find queries in positions 11–20 with real impressions. The highest-leverage list in the account, because you already rank — see striking distance keywords.
2. Find pages ranking well with poor CTR. A ranking you already have that the title is underselling. How to judge CTR.
3. Diagnose drops in a fixed order. Reporting artefacts first, panic last — the checklist.

Four things nobody tells beginners. Your query rows will never sum to your totals, because rare queries are withheld for privacy (why). Search Console clicks will never match Analytics sessions (why). Only 16 months of history exists, so export if you want more. And Search Console cannot change your rankings — it is a measurement tool, not a lever.