The Content Consistency Trap: When Weekly Publishing Costs More

The trap in one paragraph

A weekly schedule is easy to plan, easy to report and easy to defend. The trap is that the schedule starts choosing topics. Week 14 needs a post, the good ideas were used in weeks 1 to 10, so week 14 gets "five tips" on something nobody asked about. The post costs as much to produce as a good one, earns almost nothing, and still counts towards "consistency". Over a year, those weeks quietly multiply the real cost of the posts that actually work; in the worked example below, a quarter of the posts do a job, so each useful one carries the cost of four.

AI makes the trap worse, not better, because it removes the friction that used to force a pause. When a post takes twenty minutes to generate, there is always time to fill the slot.

Measure cost per useful piece

Cost per piece is the number most teams track. The number that matters is cost per useful piece: total content spend divided by the pieces that did a job. Decide "useful" with three tests, and count a piece if it passes any one:

1. • Demand: it earns search impressions or visits for the question it was written to answer.
2. • Sales use: sales or customer success send it to prospects or customers.
3. • Conversion: it is a meaningful step before enquiries, sign-ups or purchases.

Worked example (illustrative)

Illustrative example with round, hypothetical figures; not a client. Assumptions: every piece, whatever the schedule, costs the same to produce, including writing, editing and publishing time; "useful" is judged with the three tests above after six months.

Model A: weekly, calendar-led. 52 posts at £300 each = £15,600. After six months, 13 pass at least one test. Cost per useful piece = £15,600 ÷ 13 = £1,200.

Model B: fortnightly, demand-led. 26 posts, each from a real question with a fuller brief, at £450 each (more research and editing time) = £11,700. After six months, 16 pass. Cost per useful piece = £11,700 ÷ 16 = £731.

Model B spends £3,900 less and produces three more useful pieces. The numbers are invented; the mechanism is not. Your own figures will differ, which is why the next step is to calculate them.

Cadence models compared

Criterion	Fixed weekly	Demand-led	Campaign bursts
How topics are chosen	Calendar slot needs filling	Queue of real questions, published when ready	Grouped around a launch, season or cluster
Risk	Low-demand filler; reviewer fatigue	Gaps when the queue is empty	Long quiet periods between bursts
Planning effort	Low	Medium: requires a maintained question queue	High before each burst
Best for	Newsletters and series where readers expect a fixed day	Search content and sales enablement	Launches, seasonal demand, building one topic cluster

What consistency should mean

Consistency still matters, but not as output frequency. Three kinds are worth protecting:

• • Consistent quality: every piece passes the same brief and review standard.
• • Consistent rhythm of inputs: a fixed weekly slot to capture questions from sales and support, so the queue never runs dry.
• • Consistent promises to subscribers: if a newsletter says "every Tuesday", keep it. That is a reader expectation, which is different from a search content target.

Google's guidance on people-first content asks whether content is created for an existing or intended audience who would find it useful if they came to you directly. A post written to fill a slot usually fails that test, and Google's scaled content abuse policy targets producing many pages without adding value for users, however they are made.

Setting your cadence

Work it out from two numbers:

1. • Demand: how many genuinely distinct questions does your queue gain per month from sales, support and search data? That is the ceiling for useful search content.
2. • Review capacity: how many pieces a month can the person who owns quality genuinely read, check and approve? That is the ceiling for anything published.

Your cadence is the lower of the two. If the queue gains six questions a month and review can handle eight, publish about six. If you want more, grow the queue (better capture from sales calls) or grow review capacity; do not grow the calendar. The related article on the content production bottleneck covers how to widen either constraint.

Doing the audit

Export last year's posts. For each, mark the three tests. Total your content spend including internal time. Divide. If your cost per useful piece is more than about twice your cost per piece, more than half your output is not doing a job, and the calendar is probably choosing your topics.

FAQ

Does Google reward sites that publish frequently?

Google's public guidance focuses on whether content is helpful and people-first, not on publishing frequency. A site that publishes less often but answers real questions well is aligned with that guidance.

What if our marketing plan promises a weekly post to the board?

Offer a better commitment: a fixed number of pieces that pass the demand, sales-use or conversion tests each quarter, with cost per useful piece reported. It is a harder target and a more honest one.

Should we delete posts that fail all three tests?

Review them first. Merge those that overlap a useful page into it and redirect, update any that answer a real question badly, and leave harmless ones alone. Deleting in bulk without checking links and traffic can lose value.

Is social media different?

Partly. Social feeds tend to favour regular presence more than search does, so a fixed rhythm can make sense there. The same test still applies: a post that says nothing useful is a cost, not consistency.