5 Ways to Decide What Not to Write

In 1997, Apple was selling printers, cameras, a dozen variations of the Macintosh, and the Newton PDA. Steve Jobs came back, looked at the product grid, and killed 70% of it. Four products survived. The company nearly tripled its stock price within two years.

I think about that grid every time I open a content backlog. Knowing how to decide what not to write saves more production hours than any writing system, any AI tool, any editorial calendar. If you’re having too many content ideas and not enough time to write them, the backlog itself is the liability.

Here are the 5 kill tests I run on every topic before a brief gets written: (1) Is anyone actually searching for this? (2) Does it belong in my content cluster? (3) Can I cover it with genuine depth? (4) Does it move the business forward? (5) Has someone already answered it better than I can?

A topic that fails any single test gets killed or reframed. That discipline is how I stop writing content that doesn’t rank. Once the weak ideas are gone, the rebuild gets easier. I’ve written a guide on 7 ways to find topics your customers search for that picks up where these kill tests leave off.

Test 1: Is Anyone Actually Searching for This?

The question I ask first: “Is there evidence that my audience is actively searching for this, or asking it in some form?”

If the honest answer is no, the topic dies here. Deciding what content to create starts with evidence of demand rather than the strength of the idea. I’ve had plenty of ideas I found fascinating that nobody was looking for. Writing them would have served my curiosity and nobody else.

The distinction matters. Internal interest, where the writer finds the topic timely or intellectually appealing, can produce good content. External pull, where the audience is already asking the question in search queries, support threads, community forums, or sales calls, has a built-in readership. Both can work. Only one comes with an audience on day one.

Search volume alone is a flawed signal, though. A topic with measurable demand dominated by sites carrying thousands of backlinks and years of domain authority is a dead end for a small or newer site. The real question is whether demand is accessible, meaning realistic to rank for given your site’s current authority.

Pass/fail: if I can point to a search query, a customer question from a call or support thread, or a community post asking exactly this, the topic passes. If the only evidence is that I thought of it, it fails.

Test 2: Does This Topic Belong in Your Content Cluster?

The question: “Does this topic strengthen the subject-matter cluster I’m building, or does it pull in a different direction?”

A yes to the second half is a kill signal. A topic can clear Test 1 easily, genuine demand exists, and still fail here because the site has no business writing about it.

Topical authority is the degree to which a site’s content cluster signals domain expertise to search engines and AI answer systems. Publishing a piece that sits outside that cluster weakens the signal for every other piece on the site. How topical authority affects what you should write about is worth understanding before building any content calendar, and I’ve written a deeper breakdown of topical authority SEO for anyone who wants the full picture.

This is the test most idea backlogs skip entirely. A topic about social media trends might genuinely interest a B2B SaaS founder’s audience, but if the site’s cluster is built around product-led growth and organic search, that piece dilutes the pattern instead of reinforcing it.

Pass/fail: if a stranger read this piece alongside your last 5 posts, would they conclude you’re a credible expert in a coherent subject area? If the new topic breaks that pattern, it fails.

Test 3: Can You Cover It With Genuine Depth?

The question: “Do I have enough first-hand experience, expertise, or access to information to produce something genuinely useful, or will the result be a surface-level overview?”

A thin overview is a kill signal. Google’s helpful content guidance asks for first-hand experience and demonstrable depth. A well-produced thin post is still thin. Production quality, good formatting, clean design, sharp headlines, none of it substitutes for knowledge density.

I’ve made this mistake. I’ve forced a weak angle onto a topic because the keyword looked promising, and the result was a post that said nothing a reader couldn’t find in 30 seconds on any other site. That kind of content dilutes topical authority rather than building it. Some topics genuinely lack a differentiable angle for a given brand at a given moment, and the honest move is to admit that.

Depth here has nothing to do with word count. A 600-word post built from a real methodology or a specific, earned perspective carries more weight than a 3,000-word overview assembled from other people’s frameworks.

Pass/fail: can I write 1 paragraph on this topic that contains something a reader couldn’t find on the first page of search results right now? If yes, it passes. If the honest answer is no, it fails.

Test 4: Does Writing This Move the Business Forward?

The question: “Does this topic serve a specific business goal, an organic growth target, a conversion path, or a defined audience need, or am I publishing for publishing’s sake?”

No clear answer is a kill signal. Content prioritization means choosing topics that move something measurable: Search and AI visibility for a keyword the business needs to own, a conversion path for a product or service, or a trust signal for a specific audience segment.

A topic that generates traffic from an audience who will never buy, never share, and never return is a traffic vanity metric. Raw visitor numbers feel productive. They look good in a dashboard. They move nothing. What matters is engagement quality over raw traffic.

This test is especially important for founder-led businesses and lean marketing teams where every published piece represents a meaningful time cost. A post that serves no goal consumes the same hours as one that does. The question isn’t whether the topic is interesting. It’s whether writing it earns back the day it costs.

Pass/fail: name the specific goal this topic serves and the specific audience segment it moves. If neither has a clear answer, the topic fails.

Test 5: Has Someone Already Answered This Better Than You Can?

The question: “Does a piece already exist that answers this question so completely that my version would offer no meaningful improvement for the reader or for a search engine?”

A yes is a kill signal. This is the test most people skip, and it’s the most practically important one for small sites and founder-led businesses who can’t out-resource larger competitors. The question is whether you can out-think them instead.

Content topic selection at its most honest means asking whether the topic is already settled. Even low-volume niche topics can be covered so thoroughly by existing content that a new piece adds nothing to the conversation.

Whether to write about a topic someone else has already covered well comes down to one question: what would my version add that a reader couldn’t get from what already ranks? A different format alone isn’t enough. A slightly different angle that doesn’t genuinely change the reader’s understanding isn’t enough. The addition has to be real, visible, and worth a reader’s time.

I run this test in under 2 minutes. I search the target question, read the top 2 results, and ask myself what my piece would add that those pieces lack. If I can’t answer immediately, the topic fails.

Pass/fail: search the target question right now and read the top 2 results. If you can’t immediately identify what your piece would add that those pieces lack, kill or reframe the topic before the brief gets written.

What to Do With the Topics That Survive

The skill here is the kill. Most content backlogs are too long because nothing ever leaves them. Running these tests regularly keeps the list short and every item on it worth starting.

A topic that clears all 5 tests is worth writing. Choosing content topics from a filtered list rather than a raw backlog means every hour spent writing is spent on something with a genuine chance of performing.

A content prioritization framework for small teams does 1 thing well: it removes topics that were never going to earn their time. The 5 tests in this article function as that framework, applied in order, before a brief is written.

If you’re ready to build a content operation around topics that are worth writing, with the research, drafting, and quality checks handled for you, Start free trial.

Frequently Asked Questions

How do you know if a blog topic is worth writing?

Run it through the 5 kill tests in order: demand, topical fit, depth, business goal, and competitive quality bar. A topic that clears every test has a genuine chance of ranking and earning its production time. A topic that fails any single test should be killed or reframed before you start writing. The tests take under 2 minutes per topic.

When should you skip a content topic entirely?

Skip it when it fails at least 1 of the 5 kill tests and has no obvious reframe that fixes the failure. Killing a topic is a sign the idea doesn’t fit this site, this audience, or this moment. It’s a discipline that saves days of wasted production, and the strongest content calendars are built from what survives the filter.

Should you write about a topic someone else has already covered?

Only if you can identify something your version adds that the existing content genuinely lacks. A different format or a marginally different angle doesn’t count. The addition has to be real and reader-visible: a specific methodology, a first-hand example, a perspective earned through doing the work. If the top-ranking pieces already answer the question completely, reframe or drop it.