← Back to blog

Strategy · November 8, 2026 · 8 min read

How Many Blog Posts Before You See Traffic?

The count is the wrong unit: a narrow topic takes 8 to 12 posts to cover, a broad niche 60. Here is how to tell the volume is working before any traffic shows up.

By FluxWriter

How many blog posts before you get traffic has an answer, but it is not a post count. It is a share of a topic: cover a narrow subject properly and that is usually 8 to 12 posts, while a broad commercial niche can absorb 60 and still leave you thin. The figure people quote, normally 20 or 30, averages those two situations and describes neither. This explains what covering a topic means, the two signals that show the volume is working before traffic arrives, and how to price the commitment.

A post count is a proxy for topic coverage

Nobody ranks because they reached 24 posts. The number matters for what it implies. A site with 30 posts on one subject has usually answered most of what a buyer asks about it. A site with six has answered the obvious questions and stopped. The count stands in for coverage, and when the coverage is scattered, no traffic follows. That is why the same number works for one site and fails for another.

There is a test that beats any published benchmark. Write down every question a customer asks you between first contact and paying. Most businesses land between 20 and 40. Now mark the ones you already have a page for. The gap is your real backlog, and it is derived from your buyers rather than from someone else's industry.

Coverage has a depth axis as well as a breadth one. Answering "what does it cost" in 400 vague words produces a page, not coverage. Assume a question is covered only when the person who lands on that page has no reason to go back to the results, because they got the number, the caveat and the next step in one place.

Eight to twelve posts covers a narrow topic, sixty barely covers a broad one

Take a narrow niche to mean one service, one buyer, one geography. Mobile dog grooming in Leeds. Invoice factoring for haulage firms. Eight to twelve posts answers most of what that buyer types: what it costs, how it compares with the obvious alternative, what goes wrong, how to choose a provider, what the process looks like. Past twelve you repeat yourself, and the next post is worth less than an afternoon spent improving one you already published.

Broad niches differ in kind rather than degree. "Project management software", "skincare" and "accounting" each hold dozens of sub-topics with their own buyers and their own entrenched competitors. Sixty posts across a field that size buys roughly five sub-topics at twelve posts each, which is real coverage in five places. Spread the same sixty evenly across twenty sub-topics and you have three apiece, which is coverage nowhere.

The move in a broad niche is therefore to treat it as a narrow one. Pick the sub-topic where you actually close deals, cover it to twelve, confirm it is moving, then start the next. Sixty is the eventual total, not the opening commitment. Framing it that way is what makes it affordable, because you get a readable result after twelve posts rather than after sixty.

Impressions move before clicks do

The first thing that changes is impressions. A page sitting at position 40 for a four-word query still records impressions in Search Console, and a rising impression count on long-tail queries you never targeted is the earliest evidence that a group of pages is being read as a group. That often shows up within a couple of months of a cluster going live on an established site, and later on a domain with no history.

The second signal is any page arriving in the top 30. Position 22 pays close to nothing in clicks. It still matters, because the distance from 22 to 8 is ordinary work: a better page, a few internal links, one more section answering what the current top result skipped. The distance from 90 to 8 is not. Telling those two apart early is what stops owners abandoning a campaign two months before it would have paid.

What is not a signal in the first eight weeks is total sessions. Neither is one post ranking alone, which usually means you found a query nobody contested. Watch the impression curve across the whole cluster instead, and check whether the queries drifting in are ones a buyer would type.

Cost per topic covered is the number to budget against

Per-post pricing hides the decision you are making. Nobody buys one post. You are buying coverage of a topic, so the unit that matters is what a covered topic costs at a pace you can hold. The figures below are illustrative round numbers rather than quotes, and assume four posts a month.

Read down the right two columns and the strategy question answers itself. At a writer's rate, covering a broad niche is a five-figure commitment before a single visitor arrives, which is why owners who price it that way stop before the cluster is finished. At a tooling rate the same commitment is a few thousand, and the constraint becomes editing time and subject knowledge, which is a better problem because you can solve it yourself.

The trap in the cheap column is assuming those posts are automatically interchangeable with the expensive ones. A page earns its position by answering the question with your real prices, your real process and a number a competitor cannot publish. Whether that came from a writer or a draft you edited for 20 minutes matters less than whether the specifics are in it.

Thirty posts across thirty topics buys less than ten across one

The most common way to publish 30 posts and get nothing is to publish 30 good posts about 30 unrelated things. Each competes alone, with no supporting page nearby, no relevant internal links, and nothing to suggest the site knows the subject in depth. That is the default outcome when posts are picked from a keyword tool sorted by volume.

Clustering fixes it cheaply. Ten posts on one subject link to each other, share an obvious hub page, and cover the follow-up questions the first page raises. That structure is also how you get value from low-volume queries, which is where most small-site traffic comes from in the first year: a single post rarely ranks for more than a handful, while ten posts covering adjacent ground pick up dozens.

If you have already published widely and got nothing, the fix is usually not more posts. It is picking the two or three existing posts closest to your buyer and building eight around each.

Your starting position moves the timeline more than volume does

Two sites publishing the same 12 posts on the same schedule can see results months apart. A five-year-old domain with existing traffic tends to move first, because pages get crawled quickly and there is something for a new cluster to connect to. A domain registered last month has to earn that first, and the honest planning assumption there is six to twelve months to a meaningful result rather than three.

Competition does the same thing. Twelve posts is enough where the current results are thin, outdated or written by people with no operational experience. It is not enough where the first page is held by well-resourced sites that have covered the topic for years. Read this before committing: search your five most commercial questions and look at what ranks. If every result is a substantial page from a known name, raise the count or pick a narrower angle.

Nothing here guarantees a position. Volume is the part you control and coverage is how you spend it well, but the result still depends on what you publish against.

FAQ

How long before the posts turn into traffic?

For an established site covering a narrow topic, plan on a first meaningful lift somewhere between three and six months after the cluster is complete, not after the first post. A new domain should assume longer, often six to twelve months. Treat these as planning assumptions rather than forecasts, because the ranges move with competition and with what else is on the site.

Is it better to publish twelve posts at once or one a week?

One a week is easier to sustain and gives you feedback while you can still act on it, which matters more than any indexing advantage either way. Publishing all twelve at once is fine if they are written and genuinely finished. The case to avoid is a burst of twelve followed by six months of silence, because the cluster never gets its second pass.

Do the posts keep working, or do I have to publish forever?

A covered topic keeps earning for a long time with light maintenance, and the pace can drop once the cluster is complete. What it does need is updating: prices, screenshots, anything with a year in it. Most owners find the maintenance load on a finished cluster is roughly one post a month, spent on revisions rather than new pages.

The Practical Takeaway

Stop pricing posts and start pricing topics. This week, write out the questions your buyers ask, group them into clusters, and pick the cluster closest to a sale. Count the questions in it: that count is your target, not 20 or 30. Then work out what covering it costs at a rate you can hold for the months the table implies. The first action is to open Search Console, sort your pages by impressions, and see whether anything you published already sits in the top 30 for a query at the centre of that cluster.

Once a cluster is finished, FluxWriter's refresh detector, which runs on every plan, re-scores each post it published against what currently ranks and flags the ones that slip, which is one way to choose where that monthly revision goes.

← All posts