Why consistency beats bursts in search visibility

Almost every company blog we inherit has the same shape. A dense cluster of posts in the first two months, a thinner cluster three months later, then eighteen months of silence broken by a single press release. The graph looks like a heartbeat that stopped.

The instinct behind that shape is reasonable: batch the work, do it properly, move on. It just happens to be the one publishing pattern that reliably produces nothing.

Rhythm is what the rest of the system is built on

The compounding argument gets made badly. People say search engines "reward consistency", which sounds like a rule in a rulebook. It is not. Nothing in Google's documentation promises a bonus for publishing on Tuesdays.

What actually happens is quieter and more mechanical. A site that publishes steadily gets crawled more often, so new pages are discovered faster. A steady archive accumulates internal links, so authority spreads instead of pooling on a homepage. Topics get covered in sequence rather than in one undifferentiated dump, which means each post can be about one thing and link to the others.

None of that is a reward. It is just what happens when a system has a pulse.

There is a second-order effect that matters more than any of it. A live archive changes how the people around it behave. Someone who knows a post goes out every fortnight starts noticing subjects during the week. A sales team that sees its own objections turned into posts starts forwarding the good ones. A dormant blog generates none of that, because nobody sends material to a channel that has not published since spring.

A burst produces one good week and one bad year

Consider the arithmetic of the heroic push. Twelve posts written in three weeks by a team that also has a day job. The posts go live, traffic ticks up, someone screenshots the graph for a board deck.

Then nothing for eleven months. The twelve posts age together, so they all go stale together. Nothing links to them, because nothing came after. The one person who understood the plan changes jobs. When somebody finally revisits it, the archive reads as a fossil layer — clearly the output of a project that ended.

Two posts a month for a year is the same twenty-four posts. It behaves completely differently, because each one arrives into an archive that is still alive.

The real reason bursts happen

Bursts are not a strategy. They are what a good intention looks like after it collides with a quarter.

The work of publishing is not writing. Writing is maybe a third of it. The rest is deciding what the post is about, remembering that the decision was made, chasing an approval, checking it renders, and doing that again next week when three more urgent things have appeared. The writing scales fine. The remembering does not.

This is why "we'll do it in-house" so often means "we did it for a while". Nobody quits because writing is hard. They quit because the calendar has no owner and the reminder is a Slack message from four weeks ago.

What a machine changes, precisely

An engine does not get busy, sick, bored, or promoted. That is the whole of it — and it is enough, because the failure mode being solved is not a skill problem.

Be careful about what this does and does not fix. It does not make you interesting; the subjects still have to come from something your company actually knows. It does not make forty posts a month a good idea. What it removes is the specific gap between deciding to publish regularly and still publishing regularly in month nine, which is where essentially every company blog dies.

The honest version of the pitch is not "we write better than your team". It is "we still show up in November".

What to do with this

If you are choosing between four posts a month and a quarterly deep-dive, take the four — not because volume wins, but because a rhythm gives every other part of the system something to attach to.

And if your archive already looks like a stopped heartbeat, the fix is not another burst. Pick a cadence you would still be embarrassed to miss in six months, make one person or one system accountable for it, and let the compounding do the boring work.