How to Measure Blog Performance in Search Console After You Publish

7 min read·3 October 2026

To measure blog performance after you publish, you need four numbers from Google Search Console for each post: impressions, clicks, click-through rate (CTR) and average position. Watch how they change over weeks, not days, and compare each post against its own history rather than against your whole site. That goes for AI content too. Google doesn't report AI-written posts any differently, so you measure them the same way you'd measure anything else you publish.

The hard bit isn't finding the numbers. It's knowing which movements mean something and which are just noise. That's what this post covers.

The four Search Console metrics for blogs, in plain words

Search Console's Performance report is the screen that shows how your site does in Google Search. Google's own definitions of its four metrics are short enough to quote:

• Impressions: how often someone saw a link to your site on Google. Your post turned up in the results someone was looking at, whether or not they clicked.
• Clicks: how often someone clicked through from Google to your site.
• Click-through rate (CTR): clicks divided by impressions. If 200 people saw your post and 6 clicked, your CTR is 3%.
• Average position: roughly where your link sat on the results page, where 1 is the top.

Two details trip people up.

First, average position is an average of your best spot each time you appeared. Google gives a worked example: if one query shows your site at positions 2, 4 and 6, and another shows it at 3, 5 and 9, the average position is 2.5. One post ranking at 3 for a big query and 40 for a dozen small ones can average out to a number that describes none of them.

Second, a position is only recorded if the result actually got an impression. If your post sits on page 3 and nobody scrolls that far, its position isn't recorded for that query. So a brand-new post can show a surprisingly good average position simply because it's only being seen for a handful of small searches.

How to measure blog performance for one post

Site-wide totals hide what individual posts are doing. Here's how to look at a single post.

1. Open Performance > Search results in Search Console.
2. Use the filter bar at the top to add a Page filter, and paste the post's full URL.
3. Tick all four metric boxes above the chart so you can see impressions, clicks, CTR and position together.
4. Set the date range. The default view covers the past three months, which is fine for a post that's been live a while. For a newer post, pick a custom range starting on the day it went live.
5. Switch the chart to Weekly. Google says weekly and monthly views smooth out daily fluctuations like weekends and holidays, which matters a lot for a small blog where a single day's numbers are tiny.
6. Open the Queries tab under the chart. This shows the searches the post actually appears for, which is often not the keyword you wrote it for.

That last tab is where the useful work happens. If a post is showing up for searches you didn't expect, that's either a sign to adjust the post or an idea for a new one. We cover the second case in how to find blog topic ideas from Search Console data.

What to check, and when

The most common mistake with new posts is checking daily and reacting to every wobble. Google's advice on ranking changes is that small movements can happen at any time, including moving back up without you doing anything, and it recommends avoiding radical changes to a page that's already doing well.

A rough rhythm that suits a small blog:

Week one or two: is it being seen at all?

Look only at impressions. You're checking that Google has found the post and is showing it for something. Clicks and position this early are too thin to read. If there are no impressions at all after a couple of weeks, check the post with the URL Inspection tool before you do anything else.

Around a month: what is it being seen for?

Now read the Queries tab. Are the searches close to what the post is about? Is average position for the main query heading in the right direction week on week? A post that's appearing for the right searches at position 30 is on a very different path from one appearing for the wrong searches at position 12.

Around three months: is it earning clicks?

By now you usually have enough impressions to judge CTR. Use the date filter's Compare tab to put the latest period next to the previous one. Google's troubleshooting guide suggests exactly this, comparing the last three months to the previous period or to the same months last year.

If you've changed a post and want to see whether it helped, Google's guidance is to wait a few weeks before judging, and some changes take several months to show.

What the patterns usually mean

No single metric tells you much alone. The combinations do.

What you see

What it usually means

What to try

Impressions rising, clicks flat, position 20+

Google is testing the post but it's on page two or lower

Strengthen the section that answers the main query; add internal links to it

Impressions steady, position 4–15, low CTR

People see it but choose other results

Rewrite the title and meta description to match the query more closely

Impressions steady, clicks falling

Your snippet has become less appealing, or a rich result is taking attention

Check the live results page for the query

Impressions and clicks both falling

Lower rankings, less demand, or seasonality

Check the last 16 months and Google Trends before changing anything

Good clicks for a query you didn't target

The post answers something you didn't plan for

Add a section for it, or write a separate post

The "impressions steady, clicks falling" row comes straight from Google, which says it may mean you're not generating the best page title and snippet, or that other sites have a more appealing rich result. Google's Performance report help also names the same use for the Queries tab: finding queries with high impressions and low CTR so you can improve the title and description.

Posts sitting between positions 4 and 20 deserve most of your attention, because small improvements there are the likeliest to turn into clicks. We've written a full walkthrough on finding and fixing striking distance keywords.

For the "both falling" row, check seasonality before you panic. Google's troubleshooting guide suggests setting the date range to Last 16 months so you can see whether the same dip happened this time last year. Say you run a garden design business in Cork: a post about planting spring bulbs will lose impressions every summer, and there's nothing wrong with it.

Measuring AI content performance fairly

Search Console won't tell you whether a post was written with AI, and it doesn't need to. The metrics are the same. What changes is the question you're asking: is this way of producing posts giving you results you're happy with?

A fair way to answer it:

• Compare like with like. Put a set of AI-assisted posts next to posts you wrote yourself on similar topics, and compare them over the same number of weeks since publishing. A post live for six months will beat a post live for three weeks regardless of who wrote it.
• Judge the group, not one post. Individual posts vary a lot. One AI-assisted post that flops tells you less than ten that are showing up for the queries they were written for.
• Look at queries, not only totals. The Queries tab shows whether a post matches what people actually search. If AI-assisted posts keep appearing for vague, loosely related searches, that points to the brief or the editing, not the tool.

If you're worried AI content is at a disadvantage in Google, we've looked at that separately in do AI-generated blog posts rank on Google and what Google's guidelines actually say about AI content. The short version from those posts: Google cares whether the post is useful, and your Search Console data is the most direct evidence you'll get on that for your own site.

What Search Console can't tell you

Search Console is good at one thing: what happened between Google's results page and the click. It's worth being plain about what it leaves out.

• What happened after the click. It doesn't show whether readers stayed, rang you or filled in a form. For that you need your analytics tool.
• Every query. Some searches are hidden to protect user privacy, and Search Console also only stores the most important rows, so your Queries list won't add up to your totals. On a small blog, a fair share of your impressions can come from searches you never see.
• Your exact ranking. The figure is an average across everyone who searched. Results depend on the time, place, device and recent history of the person searching, so checking Google yourself won't match the report.
• Why something changed. It shows the movement, not the cause. That part still needs your judgement.

Blog AI has the same limits, because it reads the same Search Console data. It can flag a post whose clicks are falling or a query sitting just off page one. It can't tell you whether that post brought in a customer.

The one habit that makes this work

Measuring blog performance comes down to watching each post's own impressions, CTR and position over weeks, and acting only when a pattern holds. Your next step: open Search Console, filter the Performance report to the last post you published, switch the chart to weekly, and write down its four numbers. Check the same post again in a month and compare.

Researched and drafted with Blog AI, checked against its sources, and edited before publishing. How the checks work