How to see which blog posts get traffic from Google with Search Console

You see which blog posts get traffic from Google in Search Console's Performance report, which records every click Google search sends to each page on your site. Open the report, choose Search results, and set a date range such as the last three months. Then add a page filter for the part of the address all your posts share, such as "URLs containing /blog/", and open the Pages tab. Sort by clicks, and the posts at the top are the ones Google sends readers to. Click any post and switch to the Queries tab to see the searches that brought those readers.

Search Console gives you four numbers for each post:

• Clicks are the visits Google search sent to the post.
• Impressions count how often the post appeared in someone's search results, whether or not they clicked.
• Click-through rate is clicks divided by impressions.
• Average position is where the post usually ranked when it appeared, averaged across all of those impressions.

The built-in routes stop at the table. The report shows up to 1,000 rows in its interface, and you can export them to Google Sheets or a CSV file, or connect Search Console to Looker Studio for a dashboard. All of these show you numbers. None of them tell you what the numbers mean for each post or what to do next, and that reading is the slow part of the job.

That's where the real value is. A post with 400 clicks is doing its job. A post with 20,000 impressions and 60 clicks has a title that isn't winning the click. A post ranking at position 12 for a search with real demand is one good refresh away from page one. A post with no impressions at all may not be in Google's index. A good result sorts your posts into those groups and names the searches behind each one, so you know which posts to leave alone and which to work on.

Kite does that reading for you. It pulls the data from Search Console, decides what each post needs, and can make the changes on your site.

Start by asking Kite which posts Google sends readers to, in the Kite web app or in Slack:

"Which of our blog posts get the most traffic from Google, and which ones should we work on next?"

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. From that research, it already knows your site, your products, and the searches your buyers make, so it can tell a post that brings in likely customers from one that draws readers who will never buy.

You'll need to connect the Google account that has access to your Search Console property through OAuth. Reading your performance data doesn't change anything in Search Console, so Kite pulls the numbers and reports back without asking first. If you'd like the report on a regular schedule, such as the first Monday of every month, say so in your request.

Kite starts by confirming which Search Console property holds your blog's traffic. It lists the verified properties on your connected Google account and checks your permission on each one. A domain property covers every subdomain and both http and https, while a URL-prefix property covers only the address it names. That difference matters when a blog lives at blog.yoursite.com rather than yoursite.com/blog, so Kite picks the property that actually includes your posts.

Next, Kite works out which pages count as blog posts. When your posts share a path, such as /blog/ or /articles/, it filters the search data to that path. When they don't, it reads your blog's index page and your sitemaps to build the list of post addresses, and it leaves out category pages, tag pages, and author pages so they don't crowd the results.

Kite chooses a date range that treats every post fairly. Search Console data runs two to three days behind, so Kite ends the range on the last day with finished data. It usually reads the last three months, which is long enough to smooth out a slow week and short enough to reflect how posts rank now. Search Console keeps about sixteen months of history, so Kite can also compare the same months a year earlier when your traffic is seasonal.

A post published three weeks ago can't be judged against one that has had a year to rank. Kite notes when each post went live and reads newer posts against their own short history rather than ranking them at the bottom.

Kite queries your search performance by page and reads the clicks, impressions, click-through rate, and average position for every blog post in the range. The Search Console connection returns thousands of rows at a time, so a large blog gets read in full rather than cut off at the first 1,000 posts.

Kite reads web search results by default, since that's where most blog readers come from. Google Discover, the feed of articles on phones and in the Google app, is reported separately in Search Console, and Kite adds it when your posts appear there.

Kite then queries by page and query together, which shows the exact searches behind each post's clicks. This is often the most useful part of the job, because the searches that send readers to a post are frequently different from the keyword it was written for. A post written for "email marketing tips" might earn most of its clicks from "welcome email examples", and that tells you what the post should lead with.

Kite also reads the share of each post's clicks that come from your brand name. A post that only gets clicks from people searching your company's name isn't finding new readers, so Kite counts it separately from a post that wins searches for the topic itself. Search Console hides very rare searches to protect searchers' privacy, so a post's listed searches can add up to fewer clicks than its total, and Kite reports the total from the page figures.

Kite sorts every post into a group based on what its numbers show, because each group calls for different work:

• Posts that earn steady clicks. These are your proven posts. Kite checks that they still lead toward a signup or a product page, since a post that draws readers and sends none of them anywhere is the next thing to improve.
• Posts with many impressions and few clicks. Google shows these posts often, but searchers skip them. Kite compares the title and description with the searches the post appears for, and it checks whether Google now shows an AI Overview for those searches, which can answer the question on the results page.
• Posts just off page one. These rank around positions 8 to 20 for searches with real demand. Kite checks the monthly search volume for those searches with its built-in search data, and it reads the pages that rank above you to see what they cover that your post doesn't.
• Posts with no impressions. A post missing from the results hasn't necessarily left Google, because Search Console lists only pages that appeared at least once. Kite inspects each of these addresses in Search Console to confirm whether Google has indexed it, and it checks your sitemaps for errors.

Average position is an average across every impression, so Kite treats it as a direction rather than an exact rank. It weighs each post's numbers against how much traffic the post normally gets, so a small post that dipped by chance doesn't get flagged as a problem.

When the work is done, Kite answers in the conversation where you asked, starting with the posts that bring the most readers from Google and the searches behind each. In the Kite web app, the answer comes with a table you can sort. When the blog is large enough that a chat reply would be cramped, Kite also publishes a report with charts and tables at a shared link.

After the ranking, Kite lists the groups and the fix it recommends for each post: a new title and description, a refresh with current information, a section that answers a search the post already appears for, or an indexing fix and a resubmitted sitemap. On a site Kite hosts, or through a supported CMS connection such as Webflow, Kite can make these changes itself. It asks for your approval before it publishes, and it records which posts it changed so that the next report shows whether each fix worked.

When Kite finishes, you know which posts Google sends readers to, why, and what to do with the rest.