'We need to publish more' is the most common reaction to flat traffic, and often the worst one. Here's why volume without value backfires, and what to do instead.
Traffic flat? Publish more. It sounds logical, feels productive, and is easy to put in a plan. It also fails more often than it works.
TL;DR: Content volume is not a growth strategy. More pages that overlap, repeat each other, or barely answer a query can compete with your own content and weaken your site's overall quality signals. Producing many pages mainly to rank is exactly what Google's spam policies call scaled content abuse. A better path is to improve what you already have: update, consolidate, and prune, then publish new pages only where there's a genuine gap you can fill better than anyone else.
In the early days of blogging, more indexed pages meant more chances to rank for more phrases, and that did work for a while. It's also easy to measure: pieces published per week is a number you can put in a report. Quality is harder to put in a column, so volume wins by default.
AI has made it trivial to publish a hundred pages a week. That's precisely why it's a poor differentiator now: if anyone can do it, doing it earns you nothing. What's scarce is originality, a point we make in why your content isn't ranking and in our guide to AI content at scale.
If the answer to all of these is no, the page probably isn't helping.
Does publishing frequency matter at all? Consistency helps you build a body of useful work, but a fixed number of posts per week isn't a ranking factor.
Should I delete old content? Only after checking whether it has value. Improving or consolidating is usually better than deleting, and when you remove pages, redirect where appropriate.
How many pages does a site need? As many as it takes to genuinely cover your topics, and no more.
Is a content hub strategy still valid? Yes, when each page serves a distinct purpose and links to related pages. Quantity alone isn't the goal.
Last updated: October 12, 2026. Evaluate content decisions against your own Search Console and analytics data.