Xt4b

Cadence

How many posts a month a blog actually needs.

The question is usually asked the wrong way round. What matters first is how many queries your site does not answer yet — the count follows from that, and so does the cadence that keeps up with it. Here is the shape that tends to hold.

Start with your domain See how a plan works

Coverage before frequencyOne cluster at a timeA date per post, not a quota

The short answer.

Stated as a recommendation rather than a benchmark — no public dataset says a specific number of posts ranks, and any page that claims one is selling something.

Pick a cadence you can hold for a year

As many posts a month as you have queries worth answering, published on days you will still be publishing in month nine. A blog at twice a month for a year beats ten posts in one enthusiastic fortnight and then nothing — not because search engines punish the gap, but because half a cluster does not rank and a habit that breaks does not come back.

What that looks like by site size.

The input is how much the site has left to cover, which is the number the free scan reports: the queries your pages do not currently answer.

A site with under ~50 pages
Two to four a month, all inside one cluster. At this size the site is not competing on volume, it is proving it covers a subject. Eight scattered posts a month will lose to four that interlink and answer the same question from four angles.
A site with 50–500 pages
Four to eight a month, spread across the clusters that already earn impressions. The sitemap usually shows which ones: if a cluster has one page ranking at position 12, that cluster is the cheap win, not a new topic.
A site whose archive is the asset
Publish at whatever the maintenance allows, and spend the rest of the month repairing. Past a few hundred URLs the faster return is usually in the pages that already exist, not the next one.
A publisher or a network of sites
Volume is the model, and the daily question is legitimate. That is a different job from a business blog, and it is the case where a batch generator genuinely fits better than a calendar.

Why coverage beats frequency.

Four posts that answer the same question from four angles outrank eight that answer nothing in particular. Frequency is what you do with the answer, not the answer.

The unit is a cluster, not a post

A search box rewards a page that is the best answer to one query, and it trusts a site that covers the surrounding queries too. Both of those are properties of a set of posts, which is why publishing four posts in one cluster beats publishing four in four subjects — even though the monthly count is identical.

The count follows from the gaps

Once the cluster is chosen, the number of posts is whatever the cluster actually needs. Some need three; a real buying-decision cluster needs twenty. Deciding the cadence first and the subject second is how blogs end up with fifty posts and no cluster that anyone would call authoritative.

Why the calendar matters more than the count.

A count is an intention. A date is a commitment — and the difference between the two is the entire output of a blog.

Publishing days, per site
Xt4b takes weekdays per site, then dates the plan's posts across them. The queue then holds those dates: a post that is ready early waits, and one that is late does not push the rest back.
Approval, if you want it
With approval on, a post waits for your review instead of publishing on its date. That is the control that makes a weekly cadence survivable for a team of one — nothing goes out unreviewed, and nothing slips because a review did not happen.
The count is not the price
A site publishing weekly and a site publishing daily pay the same 20€ per site and language: the cadence is a setting, not a meter. That is deliberate — it puts the decision about how many posts a month back where it belongs, on what the site needs.

The questions behind the question.

Including the two that usually decide it.

Is publishing every day worth it?

Only if you have a queue of queries worth answering and someone — or something — reviewing what goes out. A daily cadence with nothing behind it produces pages that cannot be interlinked, and thin pages cost more to fix later than they earned. If the pipeline can carry the dates and the plan is deep, then yes: the cadence is free once the queue exists.

Does publishing more often rank you faster?

Not by itself. Frequency affects how quickly a site's coverage of a subject becomes visible to search engines and how often they come back to look, and it gives you internal links to point at the pages that matter. Neither of those is a ranking factor you can buy with one extra post a week. Coverage of the queries someone actually types is what moves.

What happens if I miss a month?

Less than the internet suggests. There is no penalty for a quiet month; what a gap costs is the compounding — the cluster you were building stays half-built, and the habit is what stops most blogs. A calendar that holds its dates is doing most of its work before anyone writes anything.

How many posts do I need in each language?

A language is its own editorial line, not a translation queue, so it needs its own answer to this question. A site selling in three markets is three plans, each with the cadence its own market's search demand justifies — which is why two languages at four posts a month is eight posts, not four posted twice.

Nothing here is a promise of rankings, traffic or revenue — those are not guaranteed, and no cadence changes that. What is guaranteed is what gets published and the date it goes out.

Related.

The same question asked for a different language, and the two pages that pick it up from here.

More on content

One number to start from

See how many queries your site is missing.

The free scan reads your homepage and sitemap and lists the queries your pages do not answer yet, with the first entries of the plan it would build. That list is the honest answer to how many posts you need.

Automate my blog

20€ / site / language / month3 days free, no card