Content velocity vs quality: how many posts per month actually works

TL;DR: There is no single right number. New sites with no authority need higher volume (8-15+ posts a month) to build a footprint fast, because each post is a bet with a low individual win rate. Established sites with real authority get more from fewer, deeper posts: Ahrefs cut its own publishing cadence and grew organic traffic, and multiple companies have grown traffic by deleting content, not adding it. Match your cadence to your site’s authority stage, not to a universal benchmark.

---

Table of contents

• The question everyone asks wrong
• What the volume data actually shows
• What the quality-first data actually shows
• The real variable: site age and authority, not calendar discipline
• A 12-month case study in publishing less
• Why AI content changes the volume math
• The crawl budget ceiling nobody plans for
• A cadence framework by site stage
• Signals that tell you to slow down
• Signals that tell you to speed up
• How to set your own cadence in one week
• Frequently asked questions
• Key takeaways

The question everyone asks wrong

“How many blog posts per month should I publish” has no single correct answer, and every article that gives you one number without asking about your site’s age and authority is guessing. The honest answer is a range that depends on where your site sits today: a brand-new domain with zero backlinks needs a different cadence than a ten-year-old site with established authority, because the two are solving different problems. A new site needs enough published pages to give Google something to rank; an authoritative site already has that, and its bottleneck is usually depth and freshness on what it already has, not volume.

Two bodies of evidence get cited in this debate, and they look contradictory until you notice they describe different site stages. One body of evidence says more posts per month drives more traffic. The other says cutting posts per month drives more traffic. Both are true, for different sites. This article walks through both data sets, shows you where the split happens, and gives you a cadence framework based on site age instead of a single number.

What the volume data actually shows

Research from HubSpot covering more than 13,500 companies, summarized by Marketing Insider Group, found that companies with 10 or fewer employees publishing 11 or more posts a month got roughly 3x the traffic of companies publishing once a month, and roughly 2x the traffic of companies publishing 2-5 times a month. The pattern held across company sizes: businesses with 11-25 employees and 200+ employees both saw about 3.5x the traffic at 11+ posts a month versus fewer, and 26-200 employee companies saw roughly 2x.

The lead-generation split by business model is sharper. B2C companies publishing 11 or more posts a month got more than 4x the leads of companies publishing 4-5 posts a month. B2B companies publishing 11+ posts a month got 1.75x the leads of companies publishing 6-10 times a month, and 3.75x the leads of companies publishing 3 or fewer times a month. Read that carefully: it is not “more is always better” in a straight line. It is a step function, where crossing a volume threshold correlates with a jump, and staying below it does not.

Ahrefs’ own June 2025 research on AI-assisted content publishing found something adjacent: websites using AI content posted a median year-over-year traffic growth rate of 29.08% between January 2024 and January 2025, versus 24.21% for sites that did not use AI content, a roughly 5-percentage-point gap. Ahrefs attributes most of that gap to publishing volume, not to AI content ranking better per-page than human content. The two groups rated their own content strategy effectiveness almost identically, 6.4 out of 10 for AI users versus 6.3 for non-AI users. Volume moved the traffic number. It did not move the perceived quality number.

That distinction matters because it is where the “just publish more” argument usually stops being examined. Ross Hudgens, CEO of Siege Media, put it directly in that same Ahrefs research: “This data gap is telling. Is significantly more content production actually doing that much more for these companies? It may feel good, but it’s barely creating more performance.” A 5-point growth gap from a large increase in publishing volume is a real but modest return, not a multiplier.

What the quality-first data actually shows

The counter-evidence comes from sites that already had volume and cut it. Search Engine Land’s July 2026 review of content pruning case studies, by Kelsey Jones, documents QuickBooks deleting more than 2,000 pieces of content from its resource center and seeing a 20% traffic increase and more than 70% more lead signups within weeks. Userpilot deleted roughly 25% of its content and hit its highest-trafficked month yet immediately after. These are not slow-burn results measured in quarters; both companies saw the lift within weeks of cutting content, which points to a crawl-efficiency or content-cannibalization mechanism, not a quality-perception mechanism that would take months to show up in rankings.

The older, frequently cited version of this pattern is Ahrefs’ own blog, which cut from roughly four posts a week down to about two and reported an 89% increase in Google traffic over three months, per a 2016 case study by David McSweeney. That data point is a decade old and should be read as illustrative rather than current, but the mechanism it describes, redirecting writer hours from many thin posts into fewer well-researched ones targeting real search volume, matches what QuickBooks and Userpilot did nearly a decade later with content pruning instead of a frequency cut.

Google’s own guidance backs the mechanism, not the volume number. The Search Central crawl budget documentation states that crawl budget is a function of crawl capacity limit and crawl demand, and that sites with an excessive number of low-value URLs may not get fully crawled. A large site with 2,000 thin pages is competing for its own crawl budget against its best 200 pages. Deleting the 2,000 pages does not just remove clutter, it reallocates the crawl budget those 2,000 pages were consuming toward the pages that convert.

The real variable: site age and authority, not calendar discipline

Put the two data sets side by side and the split is not “volume works” versus “quality works.” It is site maturity. The HubSpot volume data skews toward smaller companies building a footprint from close to zero, where each additional post is a new indexed page targeting a new keyword with almost no existing internal competition. The pruning case studies are companies that had already accumulated years of publishing, much of it thin or overlapping, competing against itself for crawl budget and internal link equity.

flowchart TD
    A["What stage is your site in?"] --> B{"Domain age and\npublished post count"}
    B -->|"Under 12 months,\nunder 50 posts"| C["Volume phase:\n8-15+ posts/month\nBuild coverage fast"]
    B -->|"1-3 years,\n50-300 posts"| D{"Are old posts\ndecaying or thin?"}
    D -->|"Yes"| E["Refresh + prune phase:\n4-8 new posts/month\n+ audit backlog"]
    D -->|"No"| F["Steady growth phase:\n6-10 posts/month\nDepth over count"]
    B -->|"3+ years,\n300+ posts"| G{"Traffic flat or\ndeclining despite\nnew posts?"}
    G -->|"Yes"| H["Pruning phase:\nCut 20-30% of thin pages\nPause new volume"]
    G -->|"No"| I["Maintenance phase:\n2-4 posts/month\nRefresh cadence"]

If you are still in the first 90 days of a new site, this split matters even more, because early publishing decisions set the pattern the site carries for years. New sites cannot prune their way to visibility, because there is nothing to prune. A domain with 15 posts and no backlinks does not have a crawl-budget problem or a cannibalization problem; it has a coverage problem, and the fix for a coverage problem is publishing more pages that target real keywords, not fewer. This is the case where the HubSpot volume numbers apply directly: an 11-post-a-month cadence gives Google 11 new targeting opportunities a month, and at low post counts the marginal value of the twelfth post is still close to the marginal value of the first.

Mature sites hit the opposite problem. Once you have 300+ published posts, a meaningful share of them are competing with each other for the same queries, decaying past their traffic peak, or targeting keywords too far from anything that converts. Adding a 301st post does not fix that; it adds another page to the pile the crawler has to sort through. This is where the QuickBooks and Userpilot results apply: cutting the pile made the good pages easier to find, both for the crawler and for internal links. A content pruning process with a clear decision matrix per page class is what turns “cut the pile” from a vague instinct into a repeatable process, and the content refresh vs new content decision framework tells you which of those existing pages are worth rewriting instead of deleting outright.

A 12-month case study in publishing less

A 12-month publishing experiment by inblog founder Han Jang, tracked from April 2025 through April 2026, isolates the volume-versus-traffic relationship on a single site instead of averaging across many companies. The blog published 9 posts in April 2025 and pulled 505 organic visits that month. By September 2025, publishing dropped to just 3 posts, and organic visits rose to 979, nearly double, with no new content driving the increase. From November 2025 through February 2026, the blog published zero new posts for four straight months, and daily total visits still climbed from 92 to 119, a 29% increase driven entirely by older content continuing to rank.

The mechanism is timing, not magic: content published today does not peak on the day it goes live. It typically takes 3 to 6 months to reach its traffic ceiling as Google finishes evaluating it, other pages link to it, and it accumulates the signals that push it up the rankings. A site that published 9 posts in April was still seeing those posts mature in July, August, and September, which is why traffic kept climbing even as new publishing slowed. Judging a month’s publishing volume by that same month’s traffic mismeasures the relationship entirely; you are always looking at the compounding effect of posts from 3 to 6 months earlier, not this month’s output.

This is the same decay curve behind why traffic drops even without an announced Google update: pages age past their ranking peak on a schedule that has nothing to do with your publishing calendar. That single-site data point does not contradict the HubSpot company-level averages, it explains the mechanism behind them. Companies publishing 11+ posts a month for a year are not getting 11x the value from month 12’s posts; they are riding a compounding curve where months 1 through 11’s output is still maturing while month 12’s output is just starting its own 3-to-6-month ramp. Slow the cadence and the curve does not collapse, it just stops adding new posts to the pipeline while the existing pipeline keeps paying off. That is precisely what let the inblog site grow traffic across a four-month publishing freeze.

Why AI content changes the volume math

AI-assisted writing removes the labor constraint that used to cap volume, which is exactly why the quality question got sharper, not weaker. When writing a post took a human writer 6-10 hours, a company physically could not publish 30 posts a month without hiring, and that labor cost acted as an informal quality filter: nobody spent 8 hours writing a post that would not earn its keep. Word-count-controlled AI generation removes that constraint, which is also why running the ROI math on AI-generated content before you scale volume matters more than it did when labor cost was doing the filtering for you. A team can now hit 30, 50, or 100 posts a month without the labor cost that used to force triage.

That is a genuine capability gain for the new-site, coverage-building phase described above, where the limiting factor really was writer-hours against a long list of keywords worth targeting. It becomes a liability in the mature-site phase, where the limiting factor was never writer-hours, it was crawl budget and internal competition. Vrid.ai builds AI article generation with word-count control specifically for that first phase: hitting a defined target length across a keyword list fast enough to build coverage on a new site, without the per-post labor cost that used to be the natural brake on volume. The same capability applied to a mature site with a pruning problem just produces more pages competing for the same crawl budget the existing 300 posts are already fighting over. The tool does not know which phase your site is in; you have to.

Google’s guidance draws the line for AI-generated volume specifically. The Search Central helpful content documentation states the policy is about how content was produced with the intent to manipulate rankings, not about the production method itself, meaning AI-written content is not penalized for being AI-written, but content produced primarily to generate ranking signals rather than to help a reader still qualifies as the kind of content the system is built to demote, regardless of who or what wrote it.

The crawl budget ceiling nobody plans for

Every article on this topic mentions “quality over quantity” as a principle. Almost none quantify the actual ceiling where quantity stops paying off, because that ceiling is not a fixed number, it is a function of your site’s existing authority and crawl allowance. Google’s crawl budget guidance is explicit that the ceiling is set by crawl capacity limit (how much the crawler is willing to request without straining your server) and crawl demand (how much Google wants to keep your indexed pages fresh, which rises with a site’s perceived importance).

Building topical authority is really a way of raising that crawl demand ceiling on purpose, cluster by cluster, instead of hoping volume alone does it. A new site with low authority has a low crawl demand ceiling regardless of how fast it publishes, because Google has not yet decided the site is worth crawling aggressively. Publishing 20 posts a month on a brand-new domain does not mean Google indexes all 20 promptly; some sit in the crawl queue for weeks. A high-authority site earns a higher crawl demand ceiling, which is exactly the resource that gets wasted when a large share of that site’s URLs are thin, duplicate, or decaying, which is the mechanism behind the QuickBooks and Userpilot pruning results above. The practical read: volume has a much higher ceiling on a low-authority new site than intuition suggests, because there is so much unused crawl and indexing headroom to fill, and a much lower ceiling on a high-authority mature site than intuition suggests, because that site’s crawl budget is already spoken for by its backlog.

A cadence framework by site stage

Site stage	Posts/month	Primary constraint	What “more” costs you if ignored
✓ New domain, 0-50 total posts	8-15+	Writer-hours / research time	Nothing; coverage gap is the bigger risk
✓ Growing, 1-3 years, 50-300 posts	6-10	Internal cannibalization	New posts compete with your own recent ones
✗ Mature, 3+ years, 300+ posts, flat traffic	2-4 + active pruning	Crawl budget, decayed backlog	Adding volume buries your best pages deeper
✗ Any stage, thin/rushed content	0 (pause and fix quality first)	Content that fails E-E-A-T signals	Volume amplifies a quality problem, does not fix it
✓ Any stage, strong quality baseline, real keyword gaps identified	Match to identified gaps, not a fixed number	Keyword research depth	Publishing on schedule instead of on opportunity wastes slots

Read the table by row, not by column. The “right” answer for your site is whichever row your current post count, site age, and traffic trend actually put you in today, not the row you wish you were in. A three-year-old site with 320 posts and flat traffic that keeps publishing 15 posts a month because “more content is always good” is applying the new-site playbook to a mature-site problem, and the QuickBooks and Userpilot results say that is actively working against it.

Signals that tell you to slow down

Traffic per post published is falling even as total post count rises, which usually means new content is cannibalizing rankings your older content already held rather than capturing new ones. Check Google Search Console for two or more URLs ranking for the same query cluster; that is the direct symptom, not a proxy for it. If you track this alongside the SEO KPIs that still matter once clicks alone stop telling the full story, cannibalization shows up as flat or falling share of answer even while raw post count climbs.

Your average time-to-index has stretched past what it used to be. If posts indexed within days a year ago and now take weeks, your crawl demand has not kept pace with your publishing volume, which is the crawl budget ceiling described above showing up in practice rather than in theory.

A meaningful share of your last 12 months of posts have under 10 organic clicks in Search Console. That is not proof those posts are worthless individually, but at scale it is the same pattern QuickBooks and Userpilot found before they pruned: a long tail of pages that costs crawl budget and internal link equity without returning traffic.

Signals that tell you to speed up

Your site is under 50 total published posts and under a year old. At this stage, the coverage gap is almost always the bigger risk than the cannibalization risk, and the HubSpot volume data applies most directly here. A programmatic SEO approach can close that gap faster on templated page types, provided each generated page still clears the thin-content bar Google’s helpful content guidance sets.

You have keyword research showing 20+ unaddressed, real-search-volume topics your competitors already rank for and you do not. An identified gap with demonstrated demand is a different decision than publishing on a fixed calendar; it is filling a specific hole, which is closer to what actually drove the HubSpot volume numbers than raw calendar discipline was.

Your existing published content is performing well (rising organic clicks, stable rankings, low decay), which means you are not diagnosing a quality problem, only a coverage one, and adding volume on top of a working base is the lower-risk move.

How to set your own cadence in one week

Pull your full list of published URLs from Search Console with clicks and impressions over the trailing 12 months, sorted ascending by clicks. If more than 25% of your posts have single-digit organic clicks, you are closer to the pruning end of the framework than the volume end, regardless of your site’s age.

Check your average days-to-index on the last 20 posts you published, using the URL Inspection tool’s “last crawled” date against your publish date. Under a week suggests you have crawl headroom to publish more. Multiple weeks suggests you are already straining your crawl budget and adding volume will make indexing slower for everyone, not just the new posts.

Run a query-overlap check across your last 100 posts: pull top query for each URL in Search Console and look for duplicates. Any query claimed by 2+ of your own URLs is internal competition you created, and it is a stronger signal to stop adding volume than any calendar-based rule.

Match whatever cadence you land on to your actual research pipeline, not the reverse. A 12-post-a-month target with 4 posts’ worth of real keyword research behind it produces 8 posts written to fill a slot rather than to answer a query, which is the exact failure mode Google’s helpful content guidance targets. Weigh your production cost against output before committing to a number; the real cost of SEO content across agency, freelance, and AI production bands makes the trade-off concrete instead of theoretical.

Frequently asked questions

Is there a universal ideal number of blog posts per month?

No. The data splits by site maturity: new, low-authority sites benefit from higher volume (8-15+ posts/month per HubSpot’s 13,500-company dataset), while mature sites with hundreds of posts often gain more from cutting volume and pruning, as QuickBooks and Userpilot both demonstrated. Match cadence to your site’s stage, not a fixed benchmark.

Does publishing more blog posts always increase traffic?

Not linearly, and not indefinitely. HubSpot’s data shows a step-function jump at 11+ posts a month for smaller companies, but Search Engine Land’s 2026 review documents mature sites gaining traffic by deleting thousands of posts. Volume helps most when you are building coverage from near-zero; it hurts once your own posts start competing with each other.

How long does it take a new blog post to reach peak traffic?

Typically 3 to 6 months, based on tracked SEO industry patterns and confirmed by a 12-month single-site publishing study where traffic kept rising for months after publishing paused. Judging a post’s performance in its first few weeks measures noise, not its real ceiling.

Can a site grow traffic while publishing zero new content?

Yes, for a period. The same 12-month study recorded a 29% increase in daily visits during a four-month stretch with zero new posts, because older posts were still maturing through their normal 3-to-6-month ranking ramp. This does not mean publishing stops mattering forever; it means the traffic you see this month reflects posts from months ago, not this month’s output.

Does AI-generated content need to be published less often than human-written content?

The production method is not the deciding factor; Google’s helpful content guidance states policy targets content produced to manipulate rankings, regardless of who or what wrote it. AI content lets a small team hit a coverage target faster, which is genuinely useful for a new site and genuinely risky for a mature one already fighting crawl-budget and cannibalization problems.

What is crawl budget and how does it limit publishing volume?

Crawl budget is Google’s combination of crawl capacity limit (what your server can handle) and crawl demand (how much Google wants to keep your pages fresh), per Google’s Search Central documentation. Sites with a large number of low-value URLs may not get fully crawled, meaning some new posts can sit unindexed for weeks on a site that has accumulated too much thin content.

Why did QuickBooks gain traffic by deleting 2,000 pieces of content?

QuickBooks removed more than 2,000 pages from its resource center and saw a 20% traffic increase and over 70% more lead signups within weeks, according to Search Engine Land’s July 2026 case study review. Removing thin, overlapping, or decayed pages frees crawl budget and internal link equity for the pages that were already converting.

Is 2 blog posts a week too few for SEO?

Not on its own; it depends entirely on your site’s stage and what those two posts target. A mature site with 300+ existing posts and a clean keyword map can do more with 2 well-researched posts a week than a new domain publishing 2 posts a week and calling it coverage. Volume is a means to a coverage goal, not the goal itself.

Is 20+ posts a month too many?

For a new site building coverage from a real keyword list, no; that pace matches the volume end of the HubSpot data. For a mature site with existing cannibalization or decay problems, that pace almost certainly makes the underlying problem worse by adding more URLs competing for the same crawl budget the backlog already strains.

How do I know if my content is cannibalizing itself?

In Google Search Console, check whether more than one of your URLs ranks for the same target query over a trailing 90-day window. If they do, both pages are splitting the ranking signal that a single, stronger page would otherwise concentrate, and neither ranks as high as the combined content could.

Should a brand-new site start with high volume or high quality?

Both, not one or the other; the choice was never actually between them. A new site needs volume because it has coverage gaps, but each of those posts still needs to answer the query it targets or it wastes the crawl allowance a new domain is already short on. Volume without quality on a new site produces pages that get indexed slowly and rank nowhere.

What is content decay and how does it relate to publishing cadence?

Content decay is the gradual traffic loss a previously-ranking page experiences as competitors publish fresher or more thorough content, or as the topic’s underlying facts shift. Industry guidance generally recommends waiting at least six months before diagnosing decay on a given URL, since younger content has not had time to establish a stable ranking to decay from.

Does posting daily actually work for most businesses?

It works for some; HubSpot’s 2025 State of Blogging Report found 22% of blog-maintaining businesses publish daily, but the same report notes publishing value has taken priority over publishing frequency industry-wide, and posts in the 1,500-2,000 word range with strong internal linking perform best. Daily cadence without research depth behind each post trades reach for quality, which the data above says loses on a mature site.

How much does site age matter versus post count?

Both matter, and they usually move together, but post count is the more direct proxy for the crawl-budget and cannibalization risk described above. A 6-year-old site with only 40 posts behaves like a young site for cadence purposes; a 1-year-old site that published 400 posts through aggressive AI-assisted volume behaves like a mature site with pruning risk despite its age.

Can I mix a pruning strategy with continued new publishing?

Yes, and for most 1-3 year old sites this is the realistic path: keep a modest new-post cadence (6-10/month) targeting genuinely uncovered keywords while running a parallel audit to prune or consolidate low-performing older posts. The two are not mutually exclusive; the mistake is running high-volume new publishing without ever auditing the backlog it is adding to.

What role does internal linking play in this decision?

Internal linking is part of why volume without a plan backfires. Every new post needs to link to and receive links from relevant existing posts to signal relevance and pass authority; a rushed post with no internal linking plan sits isolated, contributing to the crawl-budget drag described in Google’s guidance without returning the internal-link value that makes volume worthwhile in the first place.

How do I set a realistic publishing cadence for a solo founder or small team?

Base it on your actual research capacity, not an aspirational number. If you can properly research and outline 4 topics a week, a cadence of 4 posts a week using AI article generation with word-count control to handle drafting can hit that pace without the labor cost forcing you to cut research corners; if your research pipeline only supports 1 topic a week, publishing faster than that just produces posts built on thinner research.

Does this framework apply the same way to e-commerce, SaaS, and local business sites?

The mechanism (crawl budget, decay, cannibalization, coverage gaps) is the same across site types, but the thresholds shift. E-commerce sites with large product catalogs hit crawl-budget ceilings faster because catalog pages already consume significant crawl allowance; SaaS and local sites with smaller page counts have more headroom before volume becomes a liability.

What is the single biggest mistake companies make with this decision?

Treating cadence as a fixed calendar commitment instead of a variable tied to site stage. A cadence set once, at launch, and never revisited as the site accumulates 100, then 300, then 500 posts is the direct cause of the crawl-budget and cannibalization problems that QuickBooks and Userpilot both had to fix by cutting content years later.

How do I know if I have already crossed from a volume problem into a pruning problem?

Check three signals together: the share of your indexed pages that received zero clicks in the last 90 days in Search Console, whether your average position on existing pages is drifting down as you publish more, and whether new posts take longer to get indexed than they did six months ago. If two of the three are true, additional volume is costing you more than it earns.

Key takeaways

• New, low-authority sites (under 50 posts, under a year old) get real traffic gains from higher volume, 8-15+ posts a month, because coverage is the binding constraint.
• Mature sites (300+ posts, multiple years old) more often get traffic gains from cutting volume and pruning thin or decayed pages, as QuickBooks’ 20% traffic increase and Userpilot’s highest-trafficked month after deletion both show.
• Traffic from a given month’s posts reflects publishing decisions from 3 to 6 months earlier, not that month’s output; a 12-month study recorded 29% traffic growth during a four-month publishing freeze, purely from older content maturing.
• Crawl budget, not motivation or writer supply, is the real ceiling: Google’s own documentation ties it to crawl capacity and crawl demand, both of which scale with site authority.
• AI-assisted, word-count-controlled generation removes the labor constraint that used to force triage, which helps coverage-building new sites and hurts mature sites that already have a pruning problem, so match the tool to your site’s actual stage before you match it to a target post count.

Set your cadence from the framework above, then check it against your own Search Console data using the B2B SaaS AI-search playbook and SEO content schedule for the workflow steps that turn a cadence decision into a published, indexed post.