Posting frequency is the number of new posts a blog publishes each week or month, and on our own site it made no visible difference to clicks. The question that matters more is how many of those posts each deserve to rank for something. Between 27 July and 26 September 2026 we published 149 blog posts, and through 29 September they earned 15 clicks from Google Search between them. This piece is for content leads, solo marketers and founders who have to pick a publishing number and defend it. It covers what Google says about frequency, what our record shows and what it cannot show, the weekly ceiling we set afterwards, and a way to work out your own number.
The short version
- Google's guide to people-first content asks whether you are adding a lot of new content to make your site seem "fresh", and answers its own question: "(No, it won't)".
- From 27 July to 26 September 2026 we published 149 posts on this site, an average of 16.6 a week. Through 29 September they earned 15 clicks between them, and 139 of the 149 earned none.
- On 30 September 2026 we capped ourselves at three published posts a week. It works as a ceiling, not a quota: the first four-week plan under it filled 11 of the 12 to 13 slots it allowed.
- To set your own number, start with your existing posts: how many took a click in the last 90 days, how many only appeared in search, and how many did neither.
Does publishing more often help SEO?
Not by itself. Google's own guidance treats producing lots of content in the hope that some of it ranks as a warning sign, not a lever. Its page on creating helpful, reliable, people-first content lists questions where a yes is "a warning sign that you should reevaluate how you're creating content". One of them reads: "Are you producing lots of content on many different topics in hopes that some of it might perform well in search results?"
Another asks whether you are adding a lot of new content "primarily because you believe it will help your search rankings overall by somehow making your site seem 'fresh?'" The page answers in brackets: "(No, it won't)".
The pages ranking for this query give a range anyway. All six we read on 2 October 2026 put their main recommendation somewhere between one and four posts a week, usually with a caveat that it depends.
Three of the six repeat the same traffic multiplier for companies that publish heavily, and two of those credit it to HubSpot. The text of HubSpot's own guide to blogging frequency, dated "Updated: 05/22/25", does not contain that figure. What it recommends now is "6-8 posts a month" for a blog less than a year old and "2-4 posts a month" for niches that need heavy research.
Surveys that find more output alongside more traffic are describing a correlation, and a simple mechanism could produce it on its own. More pages means more chances for one of them to rank. That only pays when the extra pages are ones that can rank. Frequency multiplies whatever a single page is worth, so if that value is close to zero, the total stays close to zero too.
What did 149 posts in nine weeks actually earn?
Fifteen clicks. Here is the record week by week, with posts counted by publish date in our CMS and search figures for every URL under /blog/ as Search Console reported them.
| Week starting | Posts published (measured, CMS) | Blog clicks (measured, Search Console) | Blog impressions (measured, Search Console) | Average position (computed) |
|---|---|---|---|---|
| 27 Jul | 36 | 2 | 6,521 | 62.8 |
| 3 Aug | 11 | 0 | 6,521 | 70.6 |
| 10 Aug | 18 | 3 | 5,363 | 63.6 |
| 17 Aug | 18 | 2 | 10,283 | 66.6 |
| 24 Aug | 21 | 5 | 10,954 | 65.4 |
| 31 Aug | 11 | 3 | 7,701 | 74.1 |
| 7 Sep | 17 | 1 | 6,001 | 75.4 |
| 14 Sep | 13 | 0 | 2,941 | 66.4 |
| 21 Sep | 4 | 1 | 1,470 | 39.0 |
| Total, 27 Jul to 29 Sep | 149 | 17 | 58,139 | 67.0 (Search Console's own figure) |
Weekly positions are impression-weighted averages we computed from Search Console's daily rows. The search data runs to 29 September 2026, the latest date Search Console returned when we pulled it on 2 October. The totals also include 28 and 29 September, which add 384 impressions and no clicks, so the weekly rows sum to 384 fewer impressions than the total. The 17 blog clicks include 2 on category pages, which leaves 15 on posts.
Weekly output ranged from 4 posts to 36, a ninefold spread. Weekly clicks stayed between 0 and 5 the entire time. The best click week, with 5, was also the second-busiest publishing week, with 21 posts.
So the table supports neither "more posts, more clicks" nor "more posts, fewer clicks". Across these nine weeks, clicks did not move with the rate in either direction.
Per post, the picture is the same. Across the window, 144 of the 149 posts appeared in search at least once, 10 earned a click, and those 10 took all 15 post clicks between them. The other 139 earned nothing.
Search Console measured the clicks and impressions. The per-post counts are ours, computed by joining its page-level rows to the list of slugs in our CMS. Our CMS's own word counter puts the 149 posts at roughly 400,000 words.
Was it the volume, or what the posts were about?
Mostly what they were about, in our reading. An average position of 67.0 means a typical blog impression sat around page seven of the results, and our click column shows what that position was worth.
The last 28 days of the record make the contrast plain. From 2 to 29 September the whole domain took 15 clicks. Two went to blog posts, out of 15,746 blog impressions.
The other 13 came from 298 impressions on the rest of the site, and 11 of those 13 landed on pages averaging position 5.1 or better, led by a free tool page at position 1.7 and the homepage at 4.3. In those four weeks, clicks followed position far more closely than page count.
What this record cannot tell you:
- Cause: topics, domain authority (Ahrefs DR 22 when we measured it on 30 September 2026) and post age all changed together, so the table cannot isolate any one of them, volume included, as the reason clicks stayed low.
- A penalty, either way: we did not run a manual-actions check, so we make no claim that one applied or that none did.
- The long run: nine weeks is early. Our guide to how long SEO usually takes to show results explains why a young post's numbers are a weak verdict.
- Your site: this is one domain over one stretch of time, and it describes only us.
One pattern inside the window is easy to misread. Site-wide daily impressions ran between about 1,200 and 2,100 in the last week of August, dropped to roughly 700 to 1,100 a day in the first half of September, fell again from about 15 to 17 September, and sat at about 160 to 330 a day from 22 September. Over the same stretch, the daily average position moved from 72 to 76 in the first half of September to between 21.6 and 31.4 from 25 to 29 September.
The September 2026 spam update began on 24 September, after both drops had started. The better average does not by itself mean pages climbed: when impressions down on page nine disappear, the average improves even if no page moves up. We do not know why the impressions fell.
Can publishing too many blog posts hurt your site?
The rate is not what Google's policy names. Pages that add nothing, produced in bulk, are. Google's spam policies define it in these words: "Scaled content abuse is when many pages are generated for the primary purpose of manipulating search rankings and not helping users. This abusive practice is typically focused on creating large amounts of unoriginal content that provides little to no value to users, no matter how it's created."
The first example on that list is "Using generative AI tools or other similar tools to generate many pages without adding value for users". When Google announced the policy in March 2024, it said it applies "no matter whether content is produced through automation, human efforts, or some combination of human and automated processes." The definition contains no number. It tests purpose and value, so a weekly post count cannot tell you on its own which side of it you are on.
The spam policies page also says Google detects violations through automated systems and, as needed, human review that can result in a manual action. Google's Search Status Dashboard entry dates the September 2026 spam update to 24 September at 16:15 UTC and says "The rollout may take up to two weeks to complete." It showed no end date when we checked on 2 October. Our explainer on what the September 2026 spam update is and how to read it covers the rollout itself.
Our own exposure: the record had the shape the definition describes. Many pages, published fast, and, judging by an average position of 67.0, mostly on questions that larger sites already own. We are not claiming we were penalized, and we are not claiming we were not. What we can say is that the risk sat in the pattern, and the pattern was not earning clicks.
Why did we cap ourselves at three posts a week?
Because the record showed the rate buying nothing while carrying risk, and a ceiling makes every slot argue for itself. On 30 September 2026 we set a limit of three published posts a week, against the 16.6 we had averaged. Two rules changed with it:
- Winnable topics only: before anything is written, a topic needs a measured keyword difficulty of 0 to 10, or a written case for going slightly above it, and at least two results on the live first page that we can name as beatable.
- Something only we can say: every post carries a mechanism we built, a number we measured, or a decision we made and the reason for it. In this post, that is the table above and this section.
We deleted nothing. All 149 posts are still published. The decision changed what we write next, not what we already had.
Why three rather than two or four is a judgment, and it is mine. I have no data showing three beats either, and nine weeks of one site could not show it. Three is my estimate of how many topics a week we can research properly against a query we can actually win, while still giving each one something no ranking page has. If that estimate proves wrong, the number moves.
The ceiling has already behaved like a ceiling. The first four-week plan written under it had room for 12 or 13 posts and filled 11, because the twelfth candidate did not clear the scoring bar. An empty slot means the rule is working.
How do you work out the right number for your site?
Start from what your existing posts are doing, not from a benchmark. Five steps:
- Measure your library first: in Search Console, set the date range to the last 90 days, open the Pages tab, and sort your posts into three groups: took at least one click, appeared without a click, and absent from the report entirely (check that last group against your full list of posts). The unclicked share is the most important input you have. Once Search Console is connected, GrowthHasten's Content section files every page under one of five statuses, unclicked among them.
- Count qualified topics: a topic qualifies when you can name results on page one you could realistically beat, and you have something to add that the ranking pages lack. Our guide to deciding which topics to publish covers how to choose and order them.
- Count your capacity: how many posts a week your team can research properly, and how many live posts it can keep accurate afterwards. Each post you add is another page whose facts, links and examples someone has to check later.
- Take the smaller count: your weekly number is the lower of steps 2 and 3, and step 1 decides how much of it goes to new posts at all (the table below).
- Re-check monthly: judge the number on clicks and on average position for the queries you targeted. Impressions alone can rise or fall for reasons that say little about your choices, as our September figures show.
| If your library looks like this | Do this | Why |
|---|---|---|
| Most posts unclicked after 90 days | Stop adding more of the same kind of post, and change topic selection before touching the rate | More of the same multiplies a result that is already near zero |
| Several posts sitting at positions 5 to 20 | Improve those before writing new ones | They are already on or near page one, and a new post starts with no position at all |
| More qualified topics than you can research | Raise the rate only as far as you can research and maintain | The limit is capacity, not ideas |
| Spare capacity, few qualified topics | Put the spare hours into researching topics, not drafting | An unqualified topic fills a slot and nothing else |
| New site with nothing indexed yet | Start with a handful of posts on queries you can win | You learn which topics work before committing to a rate |
What should you do with the posts that already earn nothing?
Not a mass deletion. The same Google question quoted earlier covers removal too: "removing a lot of older content primarily because you believe it will help your search rankings" gets the same "(No, it won't)" as adding it.
Work through them by type instead. Refresh the posts that are close to page one, consolidate posts that compete for the same query, and leave the rest alone until an audit gives you a reason to act. Our guide to auditing the posts you already have sets out how to make each call.
Before your next planning meeting, open Search Console, pull the most recent 90 days, and tally every post with zero clicks. Set next week's publishing number with that count in front of you. If most of your posts earn nothing, more posts of the same kind are unlikely to fix that, and you will know it before the next batch is written.
Find Out What to Publish Next
GrowthHasten is free SEO and content software. Connect Search Console and its Content section lists every page with its word count beside its clicks, sorts them by status, unclicked included, and groups each topic as covered, partial or missing against the pages you already have. An account takes a minute and costs nothing.
Plan Your Next PostFrequently Asked Questions
How many blog posts per week do you need to rank?
No weekly count makes a post rank on its own, since each post is judged against the specific query it targets. On our own site, 149 posts published over nine weeks in 2026 earned 15 clicks through 29 September, and only 10 of them earned any click. What decides it, in our reading, is whether each post targets a query you can realistically win and adds something the current results lack. Get that right for one post before adding a second.
How many blog posts does it take to get traffic?
On our site, the count showed no visible effect: weekly clicks stayed between 0 and 5 whether we published 4 posts that week or 36. Of 149 posts we published between July and September 2026, 10 earned at least one click from Google in that period and 139 earned none. Measure which of your existing posts already get clicks before deciding how many more to write.
How many blog posts per month is good for SEO?
A good monthly number is whatever your qualified topics and your capacity support, which may be fewer than benchmark articles suggest. Count the topics where you can name a beatable result on page one and add something new, then count what your team can research and keep current. The smaller figure is your monthly ceiling. We cap ourselves at three posts a week, roughly 12 to 13 a month, because that is our capacity, not a target for anyone else.
Does Google reward websites that publish often?
Not for frequency itself, according to Google's own guidance. Its page on people-first content asks whether you are adding a lot of new content to make your site seem fresh, and answers: "(No, it won't)". Publishing often helps only to the extent that each new page is useful enough to rank on its merits. Publishing many pages that add little value, mainly to rank, is what Google's spam policies call scaled content abuse.
How many blog posts should you have before launching a blog?
The Google Search Central guidance we read for this article sets no minimum number of posts for a new blog. Our own blog's first week, starting 27 July 2026, carried 36 posts, and the blog took 2 clicks that week. A handful of posts on specific queries you can realistically win, each with a clear reason to exist beside what already ranks, is the start we would choose now, and it leaves time to learn which topics work before writing more.
Tags

Anshuman Sinha
AI SEO Specialist, GrowthHasten
Anshuman Sinha is an AI SEO Specialist and Computer Science Engineer with over three years of experience in SEO and five years in web development. He specializes in Technical SEO, AI Search Optimization (AEO and GEO), SaaS SEO, and building high-performance websites with modern technologies.
View profile


