Sign in Start free

Set a Cadence You Can Actually Sustain

Bursts followed by silence are worse than a slower steady rate, because internal linking and refresh debt accumulate during the burst and nobody pays them down during the silence. The obvious answer - publish as much as budget allows - ignores that every published page creates ongoing maintenance. Cadence is a capacity decision, not an ambition.

CATEGORY
Content strategy
FORMAT
sustainable-publishing-cadence.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when you are planning publishing volume and tempted to commit to a number that assumes nothing else goes wrong.

The skill file

sustainable-publishing-cadence.md 
---
name: sustainable-publishing-cadence
description: Use when you are planning publishing volume and tempted to commit to a number that assumes nothing else goes wrong.
---

# Set a Cadence You Can Actually Sustain

Bursts followed by silence are worse than a slower steady rate, because internal linking and refresh debt accumulate during the burst and nobody pays them down during the silence. The obvious answer - publish as much as budget allows - ignores that every published page creates ongoing maintenance. Cadence is a capacity decision, not an ambition.

## What you need first

- actual finished-page throughput over the last 3 months, not planned throughput
- the number of live pages already needing periodic refresh
- who reviews and approves, and their real availability

## Method

1. Measure throughput from the last quarter using pages that actually went live, including everything that stalled in review. Planned rate is usually double the real one.
2. Reserve 30 percent of capacity for refreshes from the moment you have more than about 40 live pages, because decay starts eating your existing traffic faster than new pages add to it.
3. Set cadence at the throughput you hit in your worst month of the last three, not your best. The worst month is your true capacity; the best was borrowed time.
4. Batch by cluster rather than by date - publish a core page and its supporting pages within the same fortnight so the internal links land together and the cluster is evaluated as a whole.
5. Put a hard stop in the workflow: nothing publishes without its internal links from and to existing pages already placed. Unlinked pages are the single largest source of silent underperformance.
6. Review cadence quarterly against throughput, and only raise it after two consecutive quarters of hitting the current number.

## What this produces

A committed weekly or fortnightly publication rate with an explicit refresh reserve inside it.

## Where this goes wrong

- setting cadence from your best month, so every following month reads as failure
- publishing without placing internal links and blaming content quality when the pages do not move
- adding new pages at full speed while decay quietly removes more traffic than you are adding

---

From the QuQi skill library - https://www.quqi.io/skills/sustainable-publishing-cadence
Free to download · no account, no email

What you need first

  • actual finished-page throughput over the last 3 months, not planned throughput
  • the number of live pages already needing periodic refresh
  • who reviews and approves, and their real availability

Method

  1. 01 Measure throughput from the last quarter using pages that actually went live, including everything that stalled in review. Planned rate is usually double the real one.
  2. 02 Reserve 30 percent of capacity for refreshes from the moment you have more than about 40 live pages, because decay starts eating your existing traffic faster than new pages add to it.
  3. 03 Set cadence at the throughput you hit in your worst month of the last three, not your best. The worst month is your true capacity; the best was borrowed time.
  4. 04 Batch by cluster rather than by date - publish a core page and its supporting pages within the same fortnight so the internal links land together and the cluster is evaluated as a whole.
  5. 05 Put a hard stop in the workflow: nothing publishes without its internal links from and to existing pages already placed. Unlinked pages are the single largest source of silent underperformance.
  6. 06 Review cadence quarterly against throughput, and only raise it after two consecutive quarters of hitting the current number.

What this produces

A committed weekly or fortnightly publication rate with an explicit refresh reserve inside it.

Where this goes wrong

  • setting cadence from your best month, so every following month reads as failure
  • publishing without placing internal links and blaming content quality when the pages do not move
  • adding new pages at full speed while decay quietly removes more traffic than you are adding

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/sustainable-publishing-cadence/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When is this worth doing rather than dividing the budget by cost per page?

Once you are past roughly 40 live pages. Budget arithmetic ignores that every published page creates ongoing maintenance, so bursts followed by silence leave refresh and internal linking debt that nobody pays down during the quiet. Below that page count decay is not yet eating your traffic and a simple volume commitment is fine.

What do I need in hand before starting?

Real finished-page throughput for the last three months including everything that stalled in review, the count of live pages already needing periodic refresh, and the actual availability of whoever reviews and approves. Planned throughput is usually double the real figure, so starting from the plan sets a rate you miss every month and then read as a performance problem rather than arithmetic.

What do I end up with, and which part of it gets used?

A committed weekly or fortnightly rate with the refresh reserve inside it rather than sitting alongside it. The reserve is the part that gets used and the first thing raided when a launch slips. Around 30 percent past 40 live pages is a working starting figure rather than a rule; measure your own decay rate and move it.

What ruins this most often?

Setting cadence from your best month. That month borrowed capacity from somewhere, so every month after it reads as a shortfall and the team stops trusting the schedule. Publishing before internal links are placed costs more: unlinked pages underperform silently, the diagnosis lands on content quality, and rewriting content is the expensive answer to a linking problem.

More in Content strategy

Build a Topical Map From Real Demand

Use when you have a subject area but no defensible list of what to publish, and keyword exports...

Prioritize by Effort Against Realistic Win

Use when your content backlog is longer than your capacity and you need to decide what gets buil...

Decide Build New or Refresh Existing

Use when a target query is one you already have a page for and you are unsure whether to rewrite...

Competitor Gap Analysis Without Fooling Yourself

Use when you want to learn from competitors' content but keep producing a list of topics you hav...