How Many Blog Posts a Week Does SEO Actually Need?

How Many Blog Posts a Week Does SEO Actually Need?

Ask ten SEOs how many posts a week you need, and you'll get ten different numbers — all of them guesses, because none of them know your domain age, your competitors, or how many old posts are quietly rotting on page two. For most small and midsize sites, one to three new articles a week beats five written on a hunch, as long as each one is tied to a search you're actually losing. Posts per week isn't the number that matters. The ratio is: new pages against real gaps, and how much of that weekly budget goes to refreshing what you've already published instead of piling on more.

Here's how to set your own number instead of copying someone else's.

A new domain needs volume first, an older one needs refresh first

Under roughly 30 to 40 indexed pages, volume comes first. Google needs enough signal to figure out what your site is actually about, and that means building a baseline library fast — two to four new articles a week until you clear that threshold. Each one should answer a specific question your buyers type into the search box, not a broad topic you think sounds impressive.

Infographic comparing a new domain's need for volume against an older domain's need for refresh.

Past that baseline, the math flips. Once a domain has 100-plus published pages, the real value is usually sitting in posts that already earned some ranking and are now sliding, not in a fresh batch of new ones. Cut new output to one or two a week at that point. Put the rest of your time into rewriting what's already indexed — that's the part most publishing schedules skip, and it's the difference between a blog that compounds and one that just gets longer.

Three posts tied to real gaps beat ten written on a hunch

Volume without a target creates its own problem. Two articles chasing the same search term split the ranking signal between them, and often neither ranks well. Before you scale up your weekly count, check your existing titles against your content plan, and get familiar with how pages end up competing with each other — otherwise five new posts might just land in the same trap.

A gap-driven post — built from a search you're stuck on page two for, or a question an AI answer engine skipped you on — does more in a single week than three posts written because the calendar had a slot open. No running list of real gaps? Build that first. Worry about cadence after.

Refresh on a schedule, not when you happen to remember

Most teams update old posts reactively — someone notices, almost by accident, that a post fell off page one. By then it's already lost most of its traffic. Better rule: any page that drops more than five positions in 60 days, or falls out of the top 20 for its main term, gets rewritten that same week. Not queued for a quarterly audit that may or may not happen.

A person reviewing a content publishing schedule alongside a ranking dashboard on a laptop.

Treat refresh as its own weekly line item, with its own count, separate from new articles. A site with 150 published posts and no refresh cadence is bleeding rankings every month, even while the publishing calendar looks full. New volume covers new ground. Refresh protects ground you already won.

Comparing raw counts across companies tells you almost nothing

So another company publishes ten articles a week and you manage two — so what? That number tells you nothing without knowing their domain age, their competitive set, or how many of those ten are refreshes dressed up as new posts. What's worth copying is a ratio: new pages against open gaps, refresh against total catalog size. Not a headline count pulled from someone else's dashboard.

The more common failure isn't publishing too little. It's bursting — fifteen posts in month one, then nothing for three months, on repeat. Search engines read steady output as a sign of an active, maintained site. Burst-and-abandon reads the opposite way, and the thin posts rushed out during the sprint tend to age out of relevance before they ever get the chance to rank.

Where SearchAgent fits

Recalculating this ratio by hand every week gets old fast. SearchAgent's plans are built around it directly: Starter publishes up to 100 articles a month with no refresh included, Pro adds four refreshes a week alongside 200 articles, and Scale runs ten refreshes a week against 300 articles, with your own strategist reviewing the split monthly. The full breakdown is on pricing, or compare the approach against hiring out the work on our agency comparison page.

Chart comparing Starter, Pro, and Scale plans by article volume and refresh count.

Questions people ask next

How many articles should I publish per week?
One to three for most established sites. Two to four only while a new domain is still building its baseline library of indexed pages. Past that, more volume without more gap-matching rarely moves the needle — it just creates cannibalization.

How often should I update old blog content for SEO?
Watch for pages that dropped more than five positions in 60 days, or fell out of the top 20 for their main term — rewrite those the same week you spot them. Make refresh a standing weekly task, not an occasional cleanup project.

Is it better to publish in bursts or steadily?
Steadily, every time. A burst of posts followed by silence looks like an abandoned project to readers and crawlers alike, and the thin posts rushed out during that sprint usually lose relevance before they ever get a chance to rank.

More articles

All articles