Publishing cadence for SaaS: full-batch over weekly drip
Written by Olayinka Olayokun·Published ·Updated ·Verified
Publishing cadence for topical authority is the discipline of shipping a pillar plus all of its clusters as a single batch over 2–4 weeks, so search engines see a complete sub-topic land at once rather than partial coverage trickling in.
Summary and key takeaways
A SaaS sub-topic ships as 4–7 URLs inside a 2–4 week window — pillar plus every cluster underneath it. Invoicemonk's first complete sub-topic batch (a pillar + 5 clusters in 19 days) ranked the pillar in the top 20 by day 41; the previous strategy of one post a month had produced zero rankings in five months. Completeness, not consistency, is what moves Google.
- •The unit of release is the sub-topic (4–7 URLs), not the article.
- •Ship sub-topics in 2–4 week windows — anything stretching past 6 weeks signals 'blog' rather than 'source'.
- •Sequence sub-topics by commercial proximity to the conversion page, not by what's most interesting to write.
- •Push re-crawl with Search Console URL Inspection within 48 hours of every new URL going live.
- •Link the new batch from the highest-traffic existing page for at least 30 days post-launch.
In plain English ·Publishing cadence for SaaS topical authority means shipping each sub-topic as a complete batch — pillar plus all clusters — inside 2–4 weeks, then pushing re-crawl via Search Console URL Inspection. One-post-a-week consistency ranks like a blog; full-batch completeness ranks like a source.
How this compares
| Cadence | Output over 6 months | Signal to Google | Typical outcome |
|---|---|---|---|
| One post a week, mixed topics | 26 disconnected posts | Looks like a blog | Ranks like a blog — long tail only, rarely the head term |
| One post a week, single topic | 26 posts, no pillars | Looks like a tag page | Some long-tail rankings, head term elusive |
| Full-batch sub-topics (this playbook) | 3–5 complete sub-topics, ~25 pages | Looks like a source | Pillar enters top 20 by day 60, top 10 by day 90–120 |
Part of the Topical Authority for SaaS (Without 100 Articles) guide
Publishing cadence for topical authority is the discipline of shipping a pillar plus all of its clusters as a single batch over 2–4 weeks, so search engines see a complete sub-topic land at once rather than partial coverage trickling in.
Google rewards completeness more than dribble. Shipping a pillar plus four clusters in three weeks teaches Google you're a source on that sub-topic; shipping one post a month for five months looks like a blog and ranks like one. The cadence question is not 'how often should I publish' but 'how do I sequence releases so each one teaches search engines something complete'.
What this chapter covers: full-batch publishing, sub-topic order, re-crawl push, no off-map publishing, visible internal links from existing pages.
Ship sub-topics, not posts
The unit of release is the sub-topic, not the article. A release contains the pillar page plus every cluster underneath it — typically 4–7 URLs going live inside a 2–4 week window.
The unit of release is the sub-topic, not the article. A release contains the pillar page plus every cluster underneath it — typically 4–7 URLs going live inside a 2–4 week window.
If the team can only realistically ship one post a week, plan a 5-week sub-topic release. If the team can ship two posts a week, plan a 3-week release. What you should not do is publish one cluster, wait a month, publish another cluster, and then publish the pillar three months later. The sub-graph isn't complete until the whole batch is live.
Sequence by commercial proximity
Pick the sub-topic closest to the conversion page first. For SERPNAUT that is technical SEO and topical authority — they map directly to the audit offer. The most interesting sub-topic to write about is rarely the most commercial one; pick the commercial one anyway.
Pick the sub-topic closest to the conversion page first. For SERPNAUT that is technical SEO and topical authority — they map directly to the audit offer. The most interesting sub-topic to write about is rarely the most commercial one; pick the commercial one anyway.
Move to adjacent sub-topics second. By the time the third sub-topic ships, the first two are starting to rank and the new sub-topic inherits internal-link equity from them. Sequencing matters because each batch becomes a launching pad for the next.
Push re-crawl after every batch
Don't wait for Google to discover new URLs on its own. After each batch ships, open Search Console URL Inspection, submit the pillar, submit each cluster. This typically gets the batch indexed in days rather than weeks.
Don't wait for Google to discover new URLs on its own. After each batch ships, open Search Console URL Inspection, submit the pillar, submit each cluster. This typically gets the batch indexed in days rather than weeks.
Link to the new batch from the home page or the highest-traffic existing page for at least 30 days. The fastest re-crawl signal Google reads is a new link from a page Googlebot already visits often.
What 'finished' looks like
A sub-topic batch is finished when the pillar is live, every cluster is live, every cluster links up to the pillar with the right anchor, every cluster links across to two siblings, and the batch is linked from the highest-traffic existing page on the site.
A sub-topic batch is finished when the pillar is live, every cluster is live, every cluster links up to the pillar with the right anchor, every cluster links across to two siblings, and the batch is linked from the highest-traffic existing page on the site. Anything short of that is half-shipped — it earns half the authority signal.
Resist the urge to ship a pillar before its clusters are written. Pillars without clusters are orphan pages and rank accordingly.
The checklist for this chapter
- ✓Each release contains a full pillar plus every cluster underneath it
- ✓Release window is 2–4 weeks per sub-topic, not 6+ months
- ✓Sub-topics sequenced by commercial proximity to the conversion page, not interest
- ✓URL Inspection submitted in Search Console for every new URL within 48 hours
- ✓Each batch linked from the highest-traffic existing page for at least 30 days
- ✓Nothing published that doesn't fill a node on the drawn map
- ✓Previous batch's link graph audited before the next batch ships
Where this chapter sits in the guide
the topical map and the pillar/cluster page structure — cadence is about the order things ship, not what they are. Read the pillar and cluster strategy for saas topical authority chapter →
Search Console position movement on the pillar's head term and the clusters' long-tail queries. Read the how to measure topical authority in search console chapter →
a content calendar — a calendar schedules dates; cadence describes the structural shape each release has to satisfy.
internal linking from the existing high-traffic pages so the new batch is crawled and indexed in days, not weeks. Read the related guide →
Quick answers about publishing cadence for saas topical authority
- Isn't consistent weekly publishing the standard SEO advice?
- It's the standard advice for content marketing, where consistency builds an audience. It underperforms for topical authority, which compounds on completeness. For a SaaS site without backlinks, shipping a 5-cluster sub-topic in 3 weeks routinely outranks shipping the same 5 articles spaced one a month — and the gap widens for the head term.#
- How many articles should ship in one batch?
- Match the natural shape of the sub-topic, usually 4–7 URLs (one pillar + 3–6 clusters). Force-fitting every sub-topic to the same count produces filler. If a sub-topic legitimately has only 3 clusters, ship 4 URLs and move on — padding to 7 dilutes the batch.#
- Which sub-topic should I publish first?
- The one whose head term sits closest to the page that converts. For SERPNAUT, technical SEO and topical authority ship before keyword research because they map directly to the audit offer. The most interesting sub-topic to write about is rarely the most commercial one — pick the commercial one anyway.#
- How often should a SaaS company publish blog posts?
- There is no fixed weekly cadence. Ship a complete sub-topic every 4–8 weeks (depending on capacity), with the batch concentrated into a 2–4 week burst inside that window. Five sub-topics per year — roughly 25 finished pages — is enough to earn topical authority for most B2B SaaS niches.#
Questions about publishing cadence for saas topical authority
- It is, and it underperforms for topical authority. Consistency matters for content marketing; completeness matters for topical signals. They optimise for different things — and for a SaaS site without backlinks, the latter is what unlocks rankings.
- Google recommends submitting new URLs via URL Inspection for faster discovery. Google Search Console — URL Inspection
- Google's quality guidance emphasises comprehensive topic coverage over publishing frequency. Google Search Central — Helpful content
This chapter is one node in the founder-led playbook. To see which nodes your specific URLs are bleeding traffic from, get a founder-grade SEO audit of your URLs. Same six disciplines, applied to the pages you actually own.
Olayinka Olayokun
Founder, SERPNAUT and Invoicemonk
Written by Olayinka Olayokun. I run SERPNAUT, a founder-led SEO service for B2B SaaS, and Invoicemonk, the SaaS I grew from zero to 300+ organic visits and a paying customer in 28 days using the same playbook. Everything below is what worked on my own URLs and on the audits I've shipped since.
More chapters in this guide
Publishing cadence is the discipline that turns a drawn map and a finished page structure into actual ranked URLs. The next cluster covers what to measure once a batch is live — the GSC leading indicators that tell you whether the sub-topic is on track to rank, weeks before the rankings themselves arrive.
See the full guide at topical authority for saas (without 100 articles). The commercial bridge above is the canonical path from this chapter to your URLs.