Google Search Console Tutorial: The 4 Metrics That Actually Matter

Google Search Console is a free service that shows you how your site actually performs in Google Search: which queries bring it up, how often people see those results, and how often they click through. You do not need to sign up to appear in results, Google is explicit about that on its About Search Console page, but it is the only place Google hands you the data you need to improve: the exact queries people typed, the pages that earn them, and whether both hold up week to week.

Setup is four steps: prove you own the site, confirm Google can read your pages, submit a sitemap, and then read the Performance report. Here is the setup, the four numbers that matter, the caveats beginners trip on, and a weekly routine that turns the data into decisions.

What Google Search Console is for

Search Console is Google’s free tool for monitoring, maintaining, and troubleshooting your site’s presence in Google Search, as Google describes it. Its reports show how Google crawls, indexes, and serves your site, and they are the only place you see the queries people typed to find you. Analytics shows what visitors did after they arrived; Search Console shows why they found you at all.

Google’s own getting-started guide lists four essentials: verify that you own the site, make sure Google can find and read your pages using the Index coverage report, consider submitting a sitemap to speed up discovery, and monitor the Search performance report. Google adds that you don’t need to sign in every day; once a month, or whenever you change content, is enough for a healthy site.

How to verify your site, including on Cloudflare

Verification proves you own the site before Google hands over the data. As Google’s verification documentation puts it, a verified owner gets the highest degree of permissions because Search Console exposes sensitive information and lets you take actions that affect how your site appears.

You can add a property in one of two shapes:

• A URL-prefix property, such as https://example.com/blog, covers one protocol and path only.
• A domain property, such as example.com, covers http and https and every subdomain at once, which is why Google requires a DNS record to verify it.

For a domain property, Google gives you a unique TXT record, and you add it to your DNS provider’s records. On Cloudflare that means: copy the TXT value in the Search Console verification dialog, then in the Cloudflare dashboard go to DNS, then Records, choose Add record, the flow Cloudflare documents for managing DNS records, set the type to TXT, paste the value, and save. Back in Search Console, click Verify.

Two details keep this painless on Cloudflare. First, TXT records are never proxied: the proxy setting applies to A, AAAA, and CNAME records only, so the verification record is served straight from DNS whether or not your site is behind the orange cloud. Second, leave the record in place; Google re-checks tokens periodically, and its instructions warn that removing the record revokes the property.

Prefer not to touch DNS at all? The HTML tag method works for a URL-prefix property: paste the meta tag Google gives you into the head of your homepage, and Cloudflare serves it like any other HTML. It is the method Google recommends when you can edit the homepage source.

The four metrics, and the caveats that keep you from misreading them

Every number in the Performance report is one of these four:

Google’s definitions page spells out the counting rules in detail. The definitions sound simple; the caveats are where beginners go wrong.

An impression is “seen or potentially seen,” not “seen.” For ordinary paged results, an item counts as an impression whenever it appears in the current page, whether or not the user scrolled to it; inside carousels and infinite-scroll results, it usually has to be scrolled into view. Impressions are an upper bound on attention, which is why CTR matters more than either number alone.

Average position is the topmost result, and it only counts what was seen. If your site appears at positions 2, 4, and 6 for one query, position is recorded as 2. It is averaged across all queries that recorded an impression, and a result on page 3 that nobody scrolled to records no position. It applies to Google Search results only, not Discover or News.

CTR is meaningless on small samples. A 50% CTR on four impressions is a rounding error, not a signal. Google’s performance report documentation also warns that results are specific to the time, place, device, and search history of each person, so you may not reproduce the report by typing the same query into an incognito window. Judge CTR only where impressions run to a few hundred per month or more.

Chart totals and table totals can disagree. The chart aggregates by property: two of your pages in one set of results count as one impression. Grouped by Pages, the table counts each URL separately, so CTR and position look higher at the property level. Use the chart for trends and the table for decisions about one page.

This is the mental model behind all four metrics: an estimated CTR for a given rank, multiplied by how many people search, produces the traffic a page can expect. The spreadsheet above is one person’s real estimate of that math, assuming a 7.22% CTR for position 3. Search Console shows you only the results, never the formula, but the shape matters: position matters, and it matters most at the top.

The reports to look at weekly

Open the Performance report, which shows clicks, impressions, CTR, and average position for the past three months by default, and run the same short pass every week:

1. Queries tab, sorted by clicks. Skim the top 20. Note any new query and any top query whose clicks are sliding week over week.
2. Pages tab, sorted by clicks. See which pages earn the traffic, then look for pages with high impressions and near-zero CTR. Those are title and description rewrite targets.
3. If you published or changed a page this week, confirm it is indexed with the URL Inspection tool, and check the Page indexing report for errors.

Do the pass on Monday for the completed previous week, not today. The newest Performance data is preliminary, still being collected and subject to change, and Google flags it with a dotted line on the chart, as its About the data page explains. Reading complete days keeps you out of that noise.

Prefer to watch it? Google’s own Search Console Training series covers exactly this ground: Daniel Waisberg walks through the performance report, showing where to find queries, countries, devices, and search-appearance breakdowns, in about eight minutes.

Signal versus noise: how to tell what actually changed

Beginners check Search Console like a weather app and panic at every dip. The skill that separates the two is knowing which movement is signal.

Noise is: a one-day spike or dip (weekends, a surge of traffic from one link, a briefly trending query), preliminary data that changes the next day, CTR swings on a handful of impressions, and seasonal drops that happen every year.

Signal is: a query or page moving in the same direction for three or four consecutive weeks, impressions growing for a specific query while its position holds steady, a CTR that improves in the two to three weeks after you changed a title or description, and a position that moves from the bottom of page one to the top half for a query that matters to you.

Three rules make the distinction practical. Compare like with like: this month against last month, or one four-week window against the previous one, never a single day against another. Only judge a change you actually made, and give it two to three weeks of data. And treat direction as the truth, not level: a site with 50 impressions a day learns nothing from day-to-day numbers, but learns a lot from which queries are slowly gaining ground.

The loop you can automate

Every useful thing you can do with Search Console is a loop: read the data, decide one change, apply it, wait, then read the data again to see whether the change worked. Drop what lost, double down on what won. That loop is the entire job of a working SEO routine, and it is the only part that actually moves traffic.

It is also exactly what an AI SEO agent does, which is why SEOEdgeAI is built around it. The product connects to a Cloudflare site in about two seconds, reads its Search Console results on a weekly schedule, rewrites titles and descriptions for underperforming pages, publishes new articles aimed at queries that are gaining ground, and keeps or drops each change based on the next week’s data. The measure-and-adjust cycle never stops, and you stay in control, as the how-it-works page explains.

If you want to understand the difference between an agent that runs this loop and a dashboard that merely reports on it, our article on what an AI SEO agent actually does explains the read-plan-apply-measure cycle in detail. For most site owners, the honest summary is this: Search Console contains everything you need to grow, and almost nobody has time to read it every week. That is a problem worth automating.