Somewhere along the way, 'publish consistently' became 'publish frequently,' and then 'publish as much as possible.' The logic felt reasonable: more content means more entry points, more indexed pages, more chances to rank. That logic is not entirely wrong. But it's been used to justify a lot of thin content, and thin content has a cost that compounds over time.
The honest answer to how often you should publish is: as often as you can without sacrificing depth. That's not satisfying if you're looking for a number. But the specific cadence matters much less than whether each piece you publish is genuinely good enough to rank and retain its position over time.
What Frequency Actually Signals to Google
Google doesn't reward frequency directly. It rewards freshness on topics where freshness matters (news, rapidly changing industries, recurring events), and it rewards coverage depth on topics where depth matters (everything else). A site that publishes five mediocre articles a week isn't doing better than one that publishes one excellent article a week — at least not on any metric that holds up past the initial crawl.
What frequency does affect is your crawl budget and your ability to build topical authority quickly. If you're trying to cover a topic cluster comprehensively, publishing at a faster cadence gets you there sooner. But 'faster' here means weeks, not days. The idea that you need to publish daily to signal vitality to Google is not supported by how Google's systems actually work.
The Frequency Argument, Steelmanned
It's worth taking the pro-frequency case seriously instead of dismissing it, because there's real data behind it. HubSpot's analysis of blogging data across thousands of companies found that companies publishing 16 or more posts a month saw meaningfully more traffic and leads than companies publishing fewer than four times a month. That's not a small effect, and it's not nothing.
But look at what the data is actually comparing. It's comparing high-frequency publishers to low-frequency publishers in aggregate — it isn't controlling for whether the high-frequency group was also maintaining quality at that pace. A company publishing 16 mediocre posts a month is still publishing 16 more entry points into search than a company publishing one. More entry points, even mediocre ones, will often out-traffic fewer entry points in raw volume terms. That's a real effect and it's compatible with everything argued above — it's just not evidence that quality doesn't matter. It's evidence that volume has its own separate, smaller effect that stacks on top of quality rather than substituting for it.
The honest synthesis: frequency and quality aren't actually in tension for a team with the resources to do both well. They're in tension for a team using frequency as a substitute for quality because quality is harder to scale. If you have the editorial bandwidth for real frequency without sacrificing the editing pass, take it — the data supports doing both. If you don't have that bandwidth yet, quality is the one to protect.
The Case For Publishing Less
HubSpot famously tested this: reducing publishing frequency while improving article quality produced better organic traffic outcomes than maintaining a high cadence of average content. The mechanism isn't mysterious — better articles rank higher, attract more backlinks, and retain rankings longer. A single article in the top three positions for a meaningful query is worth more than ten articles ranking nowhere. The reverse works too — QuickBooks deleted over 2,000 underperforming pages and saw organic traffic rise, because a thin archive was diluting the pages worth ranking.
There's also a team reality argument. Most content teams that commit to a high-frequency schedule eventually compromise quality to hit it. The editorial review gets shorter. The sourcing gets thinner. The editing pass disappears. What looked like a sustainable five-per-week cadence turns into a content debt problem, where you're constantly publishing but the archive is slowly filling with content you wouldn't want to link to.
Publishing less forces you to make better decisions about what to write. If you can only publish twice a month, you have to justify each piece on merit — not because it fills a slot in the calendar. That constraint produces better content, almost without exception.
When High Frequency Makes Sense
There are real cases where volume matters. News sites and publications where recency is the product. Sites trying to build topical authority quickly in a competitive space where many angles need to be covered. Brands with large, capable editorial teams where quality control doesn't degrade at volume. SEO plays targeting thousands of long-tail queries where a programmatic approach makes sense.
If you're using AI to scale content, matters more at higher volumes, not less. The temptation when you can generate quickly is to generate carelessly. Resist it. AI makes it possible to publish 20 articles a week. That doesn't mean you should. Publish 20 articles a week only if you have the editorial process to make each one good — which, if you're honest, most teams don't.
The Cadence That Actually Works for Most Teams
For most content teams — especially those in the 1-10 person range — one to three well-researched, properly sourced, thoroughly edited articles per week is a sustainable cadence that produces results without destroying quality. That's enough to build topical authority over a reasonable time frame. It's enough to signal active publishing to Google. And it's enough to make each article worth making.
The single most important cadence decision isn't how often — it's whether. Teams that publish sporadically (a burst of activity followed by two months of nothing) consistently underperform teams that publish modestly but reliably. Google's freshness signals reward consistency. Readers reward it too — if they come back to your blog and the last post is three months old, they won't come back again.
The Part of the Cadence Nobody Schedules: Maintenance
Most publishing calendars have a slot for new articles and no slot for anything else. That's a mistake, because content decay — the gradual decline in traffic and rankings that even good articles experience over time — isn't an edge case. It's the default outcome for almost every article eventually. Competitors publish something better. Search intent shifts. The information in the article ages. None of that is a failure of the original piece; it's just what happens to content left alone for two years.
This changes the honest cadence math. If a team can produce three articles a week, the highest-leverage version of that schedule usually isn't three new articles. It's two new articles and one refresh of an existing piece that's showing decay — updated numbers, a new example, a fixed dead link, a rewritten intro. Refreshing a decaying article is consistently cheaper than producing a new one from scratch, and because the page already has ranking history and backlinks, the traffic recovery tends to arrive faster than a brand-new article would rank at all.
A publishing calendar that never allocates time to maintenance isn't actually optimizing for growth. It's optimizing for the appearance of output while quietly letting last year's best work erode underneath it.
Common Mistakes When Scaling Up Frequency
Hiring writers before hiring an editor. Frequency scales the volume of drafts; it doesn't scale the review capacity needed to keep them good. Teams that add three new writers with no additional editorial review end up with three times the drafts and the same quality bar applied a third as carefully to each one.
Treating AI generation speed as a reason to skip the brief. The tools make it possible to go from idea to draft in minutes, which tempts teams to skip the step where they decide what the article should actually argue. A fast draft built on a thin brief is still a thin article — it just arrived faster.
Measuring the calendar instead of the archive. A publishing schedule that's 100% on time looks like a healthy content operation from the outside. It says nothing about whether the last twenty articles are any good. Track the quality metric, not the compliance metric — the calendar was never the goal.
Measuring Whether Your Cadence Is Working
Look at your 6-month-old articles. Are they ranking? Are they still getting traffic? Are they still accurate? If the answer is mostly yes, your cadence and quality are calibrated correctly. If most of your 6-month-old articles are already stale, ranking nowhere, and would embarrass you if a prospect read them — you're publishing too fast for your quality floor.
The goal is a content archive you're proud of, not just a large one. Every article you publish either adds to or subtracts from that. Frequency is just the rate at which you're adding or subtracting.
A Realistic Weekly Split
For a two-person content team: two new articles, one refresh of a decaying page, and an hour reserved for the internal-linking pass on whatever published that week. That's a four-item week that fits inside three focused days, not five scattered ones. It's not a formula to copy exactly — team size, industry, and competitive pressure all shift the numbers — but it's a concrete example of what 'quality-protected frequency' actually looks like on a calendar, rather than an abstraction everyone nods at and nobody schedules.
The right publishing cadence is the fastest rate at which you can consistently produce content you'd be happy to see in position one.