You want a number. Two posts a week? Four a month? The answer is: there isn’t one.
Chasing a fixed cadence is why most content calendars produce unranked posts with no traffic gain. The real answer is a range with a reason: publish as often as you have a genuinely sequenced next move — and no more often than that. Frequency is a symptom of strategy, not an input to it. If you’re setting cadence before you’ve mapped what each post does, you’re guessing.
Why a fixed schedule is the wrong frame
Editorial calendars love round numbers. “Three posts a week” feels disciplined. But SEO doesn’t reward discipline for its own sake — it rewards pages that answer a specific query better than what’s currently ranking, linked into a structure that shows Google (and readers) how they relate to everything else on the site.
A fixed schedule treats publishing as a metronome: tick, tock, new post, regardless of whether the site needs it. The right question isn’t “is it Tuesday?” — it’s “what’s the highest-value thing this site needs right now?” Sometimes that’s a new article. Often it isn’t.
Where diminishing returns come from
Diminishing returns don’t come from posting “too often.” They come from publishing unsequenced volume — articles that don’t build on each other, don’t support a target page, and don’t close a gap in what the site already covers.
Ten posts in a month with no relationship to one another will underperform three posts deliberately ordered: a foundational piece, two supporting pieces that link into it and target adjacent queries, and internal links tying them together. The three-post site did less work and got more value, because each post had a job.
Frequency is not the lever. Sequencing is the lever.
Sequencing beats cadence
An SEO content strategy should sequence publication so earlier pages support later ones. In practice:
- Publish the foundational page first. A broad, authoritative piece on your core topic gives later, narrower posts something to link into.
- Follow with supporting pages that fill specific gaps. Each new post should target a query the foundational page doesn’t fully answer, and link back to it.
- Let internal linking compound. Every new post is a chance to strengthen an older one.
Once you think this way, “how often should I post” becomes “how often do I have a genuinely next step in the sequence” — a more useful question.
When to refresh instead of publish
Publishing isn’t your only move. It competes for priority against refreshing existing pages, building internal links, and improving search snippets — because only one is likely the highest-value move on any given day.
A three-year-old post that’s slipped from position 4 to position 11 usually needs a rewrite, not a neighbor. New posts don’t rescue decaying ones; refreshes do. If your best-performing pages are aging and your backlog of uncovered topics is thin, refreshing is the higher-value move — even if it means a week with no new posts.
Balancing publish against refresh, links, and snippets
Most manual content operations fail at this comparison: new post vs. refresh vs. internal link vs. snippet fix. Doing this daily across every page is the actual work of an editorial operation, separate from writing itself.
The discipline here is daily re-prioritization: across new articles, page refreshes, internal link work, and snippet improvements, which single move delivers the most value today? Tools like Ghost Writr run this comparison continuously — checking your site on a recurring schedule, weighing what’s worth doing next, and making the single highest-value move each pass, whether that’s a new article, a page refresh, internal links, or search snippet work. That comparison needs to happen continuously, not just at planning time.
Posting frequency across multiple sites
If you run multiple sites, cadence gets harder — because you’re not just weighting publish vs. refresh vs. link on one property, you’re weighting it across several, each with different histories and decay curves.
Without shared prioritization logic, attention flows to whichever site is loudest — the one with the most urgent-feeling backlog or the founder who asks most often — rather than where a move would actually be most valuable. Each site also decays differently: content on one property might lose ranking value quickly while another stays stable, which changes how often each needs new posts versus refreshes.
This means your posting frequency shouldn’t be set per-site in isolation. It should come from a single prioritization pass across your whole portfolio, asking: of every possible move on every site today, which one is worth doing first?
Setting your own cadence
Skip the search for a magic number. Instead:
- Map your sequence — what foundational pages exist, what gaps remain, what should link to what.
- Audit for decay — which existing posts are sliding and need a rewrite before they need a neighbor.
- Compare, don’t schedule — on any given day, ask whether a new post, a refresh, a link pass, or a snippet fix is the higher-value move.
- If you run multiple sites, prioritize across all of them together, not one calendar per site.
The frequency that falls out of that process is the right one for your site — and it will change over time, which is exactly the point.
FAQ
Is there an ideal number of blog posts per week for SEO? No. The right frequency depends on how many genuinely sequenced posts you have ready to publish and how much of your priority list is actually refresh, linking, or snippet work instead.
Does publishing more often always help rankings? No. Diminishing returns show up when volume isn’t sequenced — posts that don’t support each other or fill a real gap add little value regardless of frequency.
Should I refresh old posts or publish new ones? Whichever is the higher-value move right now. A decaying page that’s lost ranking usually benefits more from a refresh than the site benefits from an unrelated new post.
How does this change across multiple sites? You need one shared prioritization method across all your sites, not a separate calendar for each — otherwise attention goes to whichever site is loudest, not whichever move is most valuable.