All posts
publishing cadence

How Often Should You Blog? Cadence for a Solo SaaS

How often should you blog as a one-person SaaS? Cadence matters less than finishing a cluster. Pick a pace by stage and review time, not by AI output.

By

TL;DR For a one-person SaaS, how often you blog matters far less than whether you finish a topic cluster. Set your cadence by how many drafts you can properly review each week, not by how many an AI tool can generate, and measure "how many posts before traffic" per cluster instead of across the whole blog.

Picture two founders, both launching on brand-new domains in the same week.

The first one wires an AI writer to the CMS and ships a post every day. Thirty days later there are 30 posts on 30 different topics: pricing, onboarding, remote work, a listicle on productivity apps. The second ships two posts a week. After a month there are eight, and they all answer questions around one problem the product solves, each linking to the others and to a central guide.

Asked which blog is "doing more content marketing," most people pick the first. But if I had to bet on which one shows clicks in Search Console first, I'd pick the second. The reason why is the whole answer to the question in the title.

How often should you blog? The question is the wrong unit

Most answers to "how often should you blog" (or its cousin, "how often should you post a blog") give you a frequency: once a week, three times a week, daily. Some attach a statistic about blogs that post X times a month getting Y percent more traffic. I'm not going to repeat those numbers, because they are correlations from sites that already have authority, audiences, and teams. They tell you nothing about a DR-0 blog run by one person between support tickets.

Google doesn't publish a preferred posting frequency either. What its guidance on creating helpful content does publish is a list of warning signs, and two of them read like a description of the daily-post founder:

  • "Are you producing lots of content on many different topics in hopes that some of it might perform well in search results?"
  • "Are you writing to a particular word count because you've heard or read that Google has a preferred word count? (No, we don't.)"

Swap "word count" for "posting frequency" and the logic is the same. A target that exists because you heard Google likes it is a target that serves the algorithm in your head, not the reader.

So here's the reframe. The unit that matters for a small site is not posts per week. It's clusters finished. A cluster is a pillar page plus the five to ten supporting posts that answer the related questions around it, all interlinked. I covered the structure in the practical guide to pillar content and clusters. Your cadence is just the speed at which you complete those clusters.

Why finishing a cluster beats any posting schedule

When a low-authority site publishes one isolated post on a topic, Google has almost nothing to judge it by: no links, no history, no related pages on the same site. When the same post sits inside a finished cluster, it has neighbors. Each one links to the others with descriptive anchors, and together they show the site covers the topic end to end rather than poking at it once.

That's why I think the common question "how many blog posts to get traffic" has no useful sitewide answer. Fifty scattered posts can produce less than eight focused ones. The better question is how many posts per cluster before traffic, and the honest answer is: enough to cover the questions a searcher actually has on that topic. For most SaaS niches I plan, that lands around six to ten posts, but it's set by the topic, not by a quota. A narrow integration topic might be complete at four. A broad workflow topic might need twelve.

The practical consequence for content velocity: half-finished clusters are the most expensive thing on your blog. Three clusters at 30 percent done means you did the work of one full cluster and got the benefit of none. If you remember one rule from this post, make it this: don't open cluster two until cluster one is complete.

Daily AI publishing is the scaled-content trap

The fastest way to blow up your cadence is to let generation speed set it. An AI tool can draft ten posts before lunch. That doesn't mean you should publish ten posts before lunch.

Google's spam policies define scaled content abuse as "when many pages are generated for the primary purpose of manipulating search rankings and not helping users." The first example listed is "using generative AI tools or other similar tools to generate many pages without adding value for users." Note what the policy targets: not AI, not volume by itself, but volume without added value. I break down how that plays out for small sites in how Google's scaled content policy treats low-quality AI content.

For a solo founder, "adding value" mostly means things only you can add: a screenshot of your actual product, a number from your own data, a judgment call about when the advice doesn't apply, a correction where the model confidently got something wrong. Every one of those takes human time. Which brings us to the real constraint.

Your real limit is review time, not writing time

When people ask "how often should I post on my blog," they usually estimate writing time. With AI drafting, writing time is close to zero. The bottleneck has moved to review: checking facts, verifying every source link, adding your own experience, fixing the voice, setting internal links, and deciding whether the post should exist at all.

Here's the first-principles way to set a sustainable pace. No study needed, just your calendar:

  1. Time your next three reviews honestly, from opening the draft to hitting publish. Include fact-checking and link-checking.
  2. Decide how many hours per week content gets, after product, support, and sales take their share.
  3. Divide hours by review time. That's your ceiling. Set your cadence a notch below it so a bad week doesn't break the streak.

If a careful review takes you two hours and content gets five hours a week, your ceiling is two posts a week. Publishing a third means one of them didn't get reviewed. Not "got reviewed quickly," but didn't get reviewed. That unreviewed post is exactly the kind of page the scaled-content policy is describing.

How you structure those review hours, from brief approval to the publish checklist, is its own topic. I wrote it up separately as a content creation workflow for a solo SaaS. This post only answers how many to push through it.

A cadence decision by stage and capacity

With the cluster as the unit and review time as the ceiling, here's how I'd choose a pace at each stage of a new site. Treat the cadences as starting points, not targets. Your review-time math overrides them.

StageWhat you're trying to doStarting cadenceCluster rule
Months 0 to 3, new domainGet the first cluster finished and indexed2 to 3 posts a week if review time allows, otherwise 1One cluster only, in winnability order
Months 3 to 6, first impressionsFill gaps the first cluster revealed, start cluster two1 to 2 new posts a week, plus updatesClose cluster one before opening two
Month 6 onward, some tractionExpand into adjacent clusters, maintain winners1 to 2 new posts a weekNew cluster only when the last is complete
Any stage, under 3 hours a week for contentStay consistent without cutting review1 post every 1 to 2 weeksSmaller clusters, still finished

A few notes on reading that table.

Front-loading early helps, if you can review it. In the first months the goal is to give Google a complete topic to crawl, so finishing cluster one quickly is worth a temporary push. But only if every post gets a full review. A finished cluster at one post a week beats an unreviewed one at one post a day.

Low capacity doesn't disqualify you. One post every two weeks still finishes an eight-post cluster in about four months. Slow and complete beats fast and scattered.

Cadence and timelines are linked, but not the same thing. How long until those posts show impressions and clicks is covered stage by stage in how long SEO takes to work for a new SaaS. Publishing faster can shorten the first stage, discovery, but it can't make Google settle positions on a topic you haven't finished covering.

What about posting more for SEO specifically?

People searching "how often should you blog for SEO" often expect a magic frequency that signals freshness. There isn't one I can source. Google's helpful content guidance explicitly flags "adding a lot of new content or removing a lot of older content primarily because you believe it will help your search rankings overall by somehow making your site seem 'fresh.'" Frequency as a ranking tactic is the thing it warns against. Frequency as a byproduct of finishing useful clusters is fine.

How often should you update your blog posts?

Updating is part of cadence too, and it gets more important as the blog grows. The same Google guidance asks: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" So bumping dates on a schedule is out.

My rule is to update when there's a reason, not on a timer:

  • A post's impressions or clicks have been sliding for weeks. That's content decay, and it's worth catching early.
  • A fact, a screenshot, or a pricing detail is now wrong.
  • Search Console shows the post getting impressions for a related query it doesn't answer yet.
  • You've published a newer post in the same cluster that the older one should link to.

From month three onward, I'd reserve roughly one review slot in four for updates instead of new posts. That keeps finished clusters finished. If you need a way to pick which posts to refresh first, the guide to refreshing outdated content covers prioritization.

How many blog posts before traffic? Ask it per cluster

Back to the question founders actually care about. "How many blog posts before traffic" gets asked in founder forums constantly, and the answers I see there run anywhere from twenty to a hundred. None of those numbers can be right for you, because they ignore what the posts were about and whether anyone could win the queries they targeted.

Here's the version I trust. Pick one cluster where the queries are specific enough that a new site can realistically rank. Publish the pillar and the supporting posts in order of winnability, easiest first. Watch Search Console per page, not sitewide. If the finished cluster earns impressions but few clicks, the issue is titles or intent, not cadence. If it earns nothing at all after Google has indexed every page, the issue is the cluster's winnability, and publishing more posts at any speed won't fix it.

That's also why I'd push back on picking a frequency first and topics second. The order is: choose winnable topics, group them into clusters, measure your review capacity, then let cadence fall out of those three. Most founders do it in reverse.

The answer, in one line

So, how often should you blog? As often as you can fully review, aimed at finishing one cluster before starting the next. For most one-person SaaS teams that's one to three posts a week, and sometimes less. The number matters much less than the order.

The hard part isn't the publishing schedule. It's knowing which cluster to finish first and in what order to write it so a low-authority site can actually win it. That planning step is what I'm building Boomranq for: you describe the product, and it turns that into a 30-day calendar organized by cluster and ordered by what your site can win first, so the cadence you choose goes into work that compounds.

Want this planned for your site?

Boomranq turns your product into a sequenced 30-day calendar built around what your site can actually rank for. Join the waitlist for early access.

No spam · One email when we launch · Unsubscribe anytime