SEO Blog Topic Selection: Stop Guessing, Start Ranking With Search Console Data

Your Search Console account already knows which blog topics you should write next. You're just not looking at it the right way.

Most founders doing their own SEO topic research open a new tab, search a competitor's blog, and reverse-engineer what they wrote six months ago. That's not topic research. That's copying someone else's guess with a delay built in.

The better workflow takes about five minutes. Here's exactly how it works.

The Topic Research Problem Nobody Talks About

Founders at $1M-$10M ARR who handle their own marketing consistently report the same pattern: 4-6 hours to produce one blog post, including topic selection, and the post gets somewhere between 4 and 40 organic visitors a month.

The topic selection is where most of those hours go. You check Ahrefs. You look at what G2 and Capterra categories are trending. You scan competitors' sitemaps. You open a spreadsheet and start a keyword research rabbit hole that somehow takes three hours and produces a list of topics that feel right but have no real connection to where your site already has authority.

All of that ignores the one data source that knows your specific domain better than any third-party tool: Google Search Console, which has been tracking exactly what queries are surfacing your URLs since the day you connected it.

The signal is there. It just requires you to look at the right columns.

What "Striking Distance" Actually Means

A striking-distance keyword is any query where your site currently ranks between position 8 and position 20. You're on page 1 or the top of page 2. Google already considers you relevant for the topic. You're close.

Here's why these keywords are the most valuable place to invest new content. The CTR curve for organic search is steep. Position 1 captures roughly 27% of clicks on a given query. Position 4 captures around 8%. Position 11 (top of page 2) captures less than 1%.

Moving a keyword from position 11 to position 4 doesn't sound dramatic. It roughly multiplies your clicks on that term by 8x, without acquiring a single new backlink, without changing your domain authority, and without waiting for a brand-new post to accumulate any signal. You're pushing on a door that's already open.

The catch: you can only see these opportunities if you filter your Search Console data correctly. The default dashboard does not show you this.

How Most Founders Are Reading Their Search Console Data Wrong

Open Search Console and navigate to Search results. By default you'll see your top-performing queries by total clicks. These are your winners. They're not your opportunities.

The opportunity filter is: queries where your average position is between 8 and 20, with at least 50 impressions in the last 28 days. Export that filtered list. That's your striking-distance keyword set.

What you're looking for inside that list:

First, queries where your average position is 8-12. These are one solid, well-structured post away from a top-5 result. You probably have some thin content or an off-topic page accidentally ranking for these terms.

Second, queries with high impressions but near-zero clicks. These are intent gaps. Google is surfacing your domain for these searches, but the page that's ranking doesn't satisfy the query intent. Someone searching "how to reduce SaaS churn" and landing on your pricing page is going to bounce. The fix is a post that directly answers the query.

Third, rising queries. Impressions growing week-over-week for a term you're not yet writing about is the clearest early signal in SEO. It means Google is testing your domain on that topic and you haven't given it a good answer yet.

Most founders look at this data once a quarter, if at all. Checking it weekly changes the picture entirely.

The Five-Minute Topic Selection Workflow

You don't need a complex scoring model. You need four data points, all available in Search Console:

Current position. Anything between 8 and 15 is your target zone. Position 16-20 is worth writing about if the intent match is very strong.

Impression volume. 50+ impressions per month is your minimum threshold for a B2B SaaS blog at this ARR stage. Below 50, you're in long-tail territory where the traffic ceiling is too low to justify the investment.

Trend direction. Is the query's impression count growing or declining over the last 90 days? Rising terms compound. Declining terms may reflect a seasonal dip or a genuine demand shift, and they need a closer look before you commit.

Intent match. Does your site have a page that properly addresses the query? If not, you have an intent gap. If yes but it's a low-quality or off-topic page, you have a position gap. The fix for each is different: an intent gap requires a new post; a position gap sometimes requires updating an existing one.

Score your filtered list against these four dimensions. The highest-scoring topic is almost always the one with a clear intent gap and growing impressions, sitting around position 10-14. Not the sexiest-sounding topic. The one with the clearest path.

The whole filter-and-score process takes about five minutes once you've done it twice.

Intent Gaps vs. Position Gaps: Two Different Problems

These are easy to conflate. They require different fixes.

A position gap means you have a page that reasonably addresses the query, but it sits too low to attract clicks. Common causes: thin content under 800 words, lack of internal links pointing to that page, or a page that covers the topic obliquely instead of directly. The fix is usually a rewrite or a structural upgrade of the existing page.

An intent gap means Google is matching queries to your domain but you have no page that actually satisfies the intent. The queries driving impressions but zero clicks in your Search Console report are almost always intent gaps. Fixing an intent gap means creating a new post that directly and completely answers the query, with the right heading structure and enough depth to satisfy both the reader and the algorithm.

For early-stage SaaS blogs, intent gaps typically produce faster results than position-gap fixes. Writing a new post that precisely matches a query you're already surfacing for can jump from position 15 to position 5 within 4-8 weeks of indexing, because the domain relevance signal already exists. You're not asking Google to trust a new topic; you're giving it a better answer to a question it already thinks you're qualified to address.

This distinction is also important for planning. If your striking-distance list is dominated by intent gaps, you need net-new posts. If it's mostly position gaps, you need an audit and rewrite cycle. Both are valid; they're just different calendars.

How MorBizAI Closes the Loop Between Data and Draft

The problem with the workflow described above isn't that it's complicated. The problem is that there's a gap between "I identified the topic in Search Console" and "I have a published post." That gap usually takes 4-6 hours and involves five different browser tabs.

MorBizAI connects those two ends directly.

The platform pulls your Search Console data on a weekly cadence and runs it through a scoring layer that surfaces striking-distance keywords, intent gaps, declining queries you should stop investing in, and rising terms you should write about now. You don't need to build the filter in Search Console or export a spreadsheet. The scored list shows up in your dashboard.

When you pick a topic from that list, the platform drafts a 1,400-1,800 word SEO post in 60-90 seconds using Claude, matched to your brand voice fingerprint. The draft goes into an inline editor for your review. You approve, request changes, or publish directly to WordPress via the REST API. No copy-paste.

It also dedupes every new draft against your last 14 days of canonical posts, so you don't accidentally create two posts competing for the same keyword. Keyword cannibalization is an easy mistake when you're publishing consistently; deduplication makes it structurally impossible.

The result: topic selection goes from a 4-6 hour research session with uncertain outputs to a five-minute data-backed decision followed by a 60-90 second draft. The signal was always in your Search Console. The gap was the workflow connecting it to a published post.

If your Notion is full of blog ideas that have no connection to your actual search data, that's the workflow you're missing. The ideas aren't the problem. The disconnect between the data and the draft is.