Quick answer: Your best blog topics are already sitting in Google Search Console — you're just not looking at them. Check the Performance report for queries where your site ranks positions 5–20 with decent impressions but low clicks; those are pages Google already thinks you're relevant for, and a focused blog post can push them onto page one. This beats guessing at topics because you're working with real demand data instead of a hunch.
Key takeaways
- Queries ranking in positions 5–20 with high impressions and low click-through rate are the highest-priority blog topics — Google already associates your site with the term.
- The Performance report in Google Search Console (Search Results view) is free and shows exactly which queries bring people to your site, filterable by page, query, country, and device.
- Pages with impressions but zero or near-zero clicks often signal a title or meta description problem, not a ranking problem — fix the pitch before writing a new post.
- Search Console data reflects only what your site already ranks for somewhere; pair it with a broader content plan like the ideas in 10 Small Business Blog Post Ideas You Can Publish This Week so you're not only chasing existing rankings.
Step 1: Get Into the Right Report
Log into Google Search Console and click Performance in the left sidebar, then make sure you're on the Search results tab, not Discover or News. This report shows every query that triggered your site in Google Search results, along with clicks, impressions, click-through rate (CTR), and average position.
Set the date range to the last 3 to 6 months. A shorter window like 7 or 28 days is too noisy for topic planning — you want patterns, not a single good or bad week.
Check the four boxes at the top of the report: Total clicks, Total impressions, Average CTR, and Average position. With all four visible, sort the query table by impressions descending. This immediately surfaces what Google shows people the most, regardless of whether they click.
Step 2: Find Your "Almost Ranking" Queries
This is the single most useful move in the whole process. Filter or sort your query list for anything sitting between position 5 and position 20 — Google's own documentation for Search Console defines average position as the topmost position at which your site appeared for that query, averaged over the date range.
A query at position 5–10 is on page one but below the fold or below competitors. A query at position 11–20 is on page two, which almost nobody scrolls to. Both groups have something in common: Google already considers your page relevant enough to show it. You don't need to convince the algorithm your site belongs in the conversation — you need to give it a stronger, more complete answer.
Here's a worked example. Say your landscaping company's Search Console data shows the query "how often should I aerate my lawn" getting 340 impressions over 3 months, sitting at an average position of 14, with only 2 clicks. That's a 0.6% CTR on a topic people are clearly searching for. A dedicated blog post that directly answers the question in the first sentence — not a paragraph buried in your services page — has a real shot at climbing toward page one.
Compare that to a query with 20 impressions at position 45. There's demand data there too, technically, but it's thin and you're starting from much further back. Prioritize accordingly.
Step 3: Separate a Ranking Problem From a Pitch Problem
Low clicks with high impressions doesn't always mean you need a new post — sometimes it means your existing title and meta description aren't earning the click. Before you write anything new, pull up the page that's already ranking for that query and look at how it appears in search.
| Signal | What it usually means | What to do |
|---|---|---|
| High impressions, position 5–20, low CTR | Page is relevant but title/meta isn't compelling or the content is thin | Rewrite the title tag, add the query's exact phrasing near the top of the page, or expand the content |
| High impressions, position 30+, low CTR | Page isn't strong enough to rank higher yet | Write a new, focused post targeting the query directly |
| Low impressions across the board | Google isn't associating you with the topic yet | Treat it as a genuinely new topic — check search volume elsewhere before investing |
| High clicks, high CTR, position 1–3 | Already working — don't touch it | Look for adjacent long-tail questions instead |
If a page is technically ranking but reads like a sales page instead of an answer, no title tag tweak will fully fix it. That's a content problem, and it's exactly what a dedicated blog post is built to solve — a page whose entire job is answering one question well, without also trying to sell something in the second paragraph.
Step 4: Mine the Query Wording Itself
The exact words in your query list are a free source of headline ideas — people type the way they think, and Search Console shows you their actual phrasing, not the polished version. Look for:
- Question-style queries ("how much does X cost," "what is the difference between X and Y") — these map directly to H2-style headings that answer engines like ChatGPT and Google AI Overviews tend to lift.
- Comparison queries ("X vs Y") — a strong sign readers are choosing between two options and want a straight answer, not a sales pitch.
- Long-tail variations of a page you already have — if "emergency plumber cost" and "how much is an emergency plumber" both show impressions, that's a signal to cover both phrasings in one comprehensive post rather than splitting them.
- Branded queries mixed with generic ones — if people search "[your business name] pricing" alongside generic "pricing" terms, that tells you which pages need the clearest, most current pricing information.
- Seasonal or recurring queries — check if certain terms spike in the same months year over year; that's a signal to have the post live and refreshed before the season starts, not during it.
Don't skip this: a query with 500 impressions and zero clicks is not a failure — it's the clearest, most literal piece of demand data Google will ever hand you for free. Treat it as a to-do item, not background noise.
Step 5: Check the Pages Report to Find Content Gaps
The Pages tab (next to Queries in the same Performance report) shows which URLs on your site are pulling in traffic — and, just as usefully, which ones aren't showing up at all. If your site has ten service pages and Search Console only shows meaningful impressions for three of them, that's a gap.
Cross-reference this with your query data. If a service page is getting almost no impressions but a related query is showing up in your query list pointing to a different, less relevant page on your site, that's a sign the wrong page is trying to rank for that term. A new blog post built specifically around that query can take over and let each page do the job it's actually suited for.
This is also where Search Console becomes a documentation problem more than a data problem. Once you're pulling weekly reports, cross-referencing query and page data, and mapping it all to a content calendar, it starts eating real hours — which is the exact gap tools built for this exist to close. Segeo, for instance, pulls Search Console data automatically as part of its topic selection, so the daily post it publishes to your site is built around what your own data says people are already almost finding you for, instead of a generic content calendar.
Step 6: Turn the List Into a Publishing Schedule
Once you've got a ranked list of queries by opportunity — high impressions, mid-pack position, low CTR — turn it into an actual schedule instead of letting it sit in a spreadsheet. A list of topics with no publishing rhythm behind it doesn't move rankings.
- Rank your query list by impressions first, then by how far the position is from page one (positions 8–15 are usually your fastest wins).
- Assign one query cluster per post — don't try to target five unrelated queries in a single article.
- Write the exact query phrasing into your H2 or opening sentence, since that's the language Google and AI answer engines already associate with your site.
- Set a realistic cadence you can sustain; we cover how frequency affects results in How Often Should a Small Business Blog Post?
- Re-check Search Console every 4–6 weeks to see which posts moved and which queries are new.
Search Console data updates on a rolling basis and Google states in its own documentation that data can take a few days to appear, so don't judge a new post's performance in the first week. Give it a full reporting cycle before deciding whether it worked.
What to Do Next
Pull your Performance report today, sort by impressions, and pull out the ten queries sitting in positions 5–20 with the lowest CTR. That list is your next ten blog posts, already validated by real search demand instead of a guess.
If keeping that process running every week sounds like more time than your business has, that's the specific problem Segeo is built around — it checks your Search Console data, picks the next topic automatically, and publishes a new post to your site every day without you touching a spreadsheet.
