How to Read Google Search Console (Without Guessing)

Learning how to read Google Search Console comes down to answering three questions: what is working, what is broken, and what should I do next. Everything else in that dashboard is decoration until you can answer those.

Most site owners open Search Console, see a squiggly line and a wall of numbers, and close it again. Here is how to actually read it, including the one number almost everyone misreads.

What position actually means

Position is your average ranking for a query. The number only matters when you translate it into pages, because that is how people experience it.

• 1 to 3. You are winning. Protect this.
• 4 to 10. Page one. Real traffic lives here, and small gains are worth more than anywhere else on the list.
• 11 to 20. Page two. Google thinks you are relevant, humans never see you.
• 21 to 50. Indexed and related, but without the authority to compete yet.
• 50 plus. Barely in the game. Not worth optimizing until the page earns some relevance.

Moving from 14 to 8 changes your traffic. Moving from 40 to 30 changes nothing. That single distinction decides where your effort goes.

Impressions and clicks: the diagnostic pair

An impression means your listing appeared. A click means somebody chose you. Read them together and they tell you exactly what is wrong.

• High impressions, few clicks, position 11 or worse. Normal. You are ranking too low to be seen. This is a position problem, not a writing problem.
• High impressions, few clicks, position 1 to 10. This is the one worth acting on. You rank, and people are choosing someone else. Rewrite the title and meta description.
• Impressions climbing, position flat. Google is testing you on more searches. Good news, and usually the first sign of movement to come.
• Impressions falling across many queries. The real warning sign. Check indexing and recent site changes before blaming an algorithm.

Page two is where your traffic is hiding

If you do one thing after reading this, do this one.

Sort your queries by impressions, then look for anything sitting between position 11 and 20. Those are pages Google already considers relevant. They need a nudge, not a rebuild. Add internal links pointing at them from your stronger pages, expand the section that answers that specific query, and make sure the phrase appears in the title.

The same logic applies to high impression queries sitting at position 25 to 40. Hundreds of impressions means proven demand. The page just lacks authority, and internal links are the cheapest authority you own.

How to read a traffic drop without panicking

Run these four checks in order before you form a theory.

1. Are you comparing the same length of time? A 28 day period against a 31 day period invents a drop that never happened.
2. One page or the whole site? One page is that page’s problem. Sitewide points at indexing, a site change, or an update.
3. Did impressions fall too, or only clicks? Only clicks means the search results page changed around you, or your title is losing the click. Both falling means you lost visibility.
4. What changed on the site? Redesigns, moved URLs, a plugin update. The boring answer is usually the answer.

Algorithm updates are the last explanation to reach for, not the first.

Separate brand queries or the numbers will lie to you

Searches for your business name are not SEO wins. Those people already knew you existed.

Filter them out and look at what is left. Non brand queries are the actual scoreboard, and they are the only ones that represent new customers finding you. Averaged together, brand queries flatter everything and hide the trend that matters.

How to read Google Search Console with Claude

You can paste your data straight into Claude and ask what it means. Export the queries table, or just copy the rows on screen, and ask for the three things: what is working, what is broken, what to do next.

Two things make this dramatically better. First, tell Claude the context: what the site sells, which pages you care about, what you changed recently. Second, keep a running log. A snapshot of one month tells you very little. Six months of snapshots tells you whether any of this is working, and lets you connect a ranking jump back to the work that caused it.

That log is exactly why we built Compass, a small set of skills that decode your Search Console data, read your keyword research, and keep the monthly history in a file you own. No connections, no logins, you paste and it thinks.

What to do every month

1. Pull the last 28 days of queries and compare to the previous 28.
2. Write down your top ten queries with positions. Keep the list.
3. Pick every query between position 11 and 20. That is your work list.
4. Check any page one query with a low click rate. Rewrite those titles.
5. Note what you actually changed on the site this month, so next month’s numbers mean something.

Five steps, twenty minutes, once a month. That is the whole discipline, and it beats reading the dashboard daily and doing nothing.

For the full method, including how Google documents the performance report, the official help pages are worth a skim once. Then stop reading and go work your page two list.

Frequently asked questions

What is a good average position in Search Console?

Anything in the top ten is page one and worth protecting. Between 11 and 20 means you are close but invisible, which is the best opportunity on your site. Above 30 usually means the page needs more authority before optimization will help.

Why do I have impressions but no clicks?

If your position is 11 or worse, you are simply too far down to be seen and the fix is ranking higher. If you are in the top ten with a low click rate, your title and meta description are losing the click to competitors, and rewriting them is the fastest win available.

How often should I check Search Console?

Once a month is enough for most sites. Data lags by two to three days and daily numbers bounce around for reasons that have nothing to do with your work. Checking daily creates anxiety, not insight.

Can Claude read my Search Console data directly?

Not through a live connection. You paste the data in, as an export or copied rows, and Claude interprets it. In practice that is all you need, and it keeps your account access private.

What is the difference between Search Console and Google Analytics?

Search Console shows what happens in Google search before someone reaches your site: what they searched, where you ranked, whether they clicked. Analytics shows what happens after they arrive. For SEO decisions, Search Console is the one that matters.