Xt4b

Cadence

How often to publish, and what a gap really costs.

Frequency advice online tends to be either a superstition or an advert. What is actually true is narrower and more useful: consistency changes how often your site is looked at, and a gap costs you compounding rather than a penalty.

Start with your domain Start with your domain

The short answer.

One rule, and it is about what you can hold rather than what is optimal.

Pick the weekdays you can review on, then let the queue keep them

Weekly if the plan has fifty queries to spend. Twice a month if the plan is thinner or the team is one person, and twice a month is not a compromise — it is roughly a hundred pages over four years, which is a serious archive. What fails is a cadence that only exists as an intention: ten posts in March, nothing until July.

What consistency actually does.

Three mechanisms, none of them a penalty. Knowing which one you care about is the difference between a real reason and a superstition.

Recrawl, not reward
A site that keeps changing gets looked at more often, which means new pages are found and indexed sooner. That is a discovery effect, not a ranking boost: it changes how long the wait is, not how high you land.
Internal links that have something to point at
Every new post is a chance to link to the pages that should rank. A cluster only becomes authoritative when its members link to each other, and that structure accumulates at the speed you publish.
Coverage, one query at a time
The straightforward one: a post is the only thing that answers a query. Ten posts a year is ten answered questions, and no schedule makes that faster than the posts themselves.

What a quiet month costs.

Said plainly, because the honest version is more useful than a warning.

What it does not cost

Nothing is penalised. A blog that stops for a month and starts again does not lose ranking for the pause, and no page quietly expires because its author took a holiday. The retreat you will see in Search Console is the same seasonal noise you would have seen anyway.

What it does cost

Momentum, twice over. The half-built cluster stays half-built, and the restart is the expensive part: the second month of a pause is where most blogs stop for good. That is the argument for a dated queue — the dates do not depend on anyone remembering.

How to set it up so it holds.

Three settings, and the third is the one that decides whether the cadence survives a busy week.

Publishing days, per site
Weekdays, set once per site. The plan puts its posts on those days, so “when does this go out” is answered before the post exists rather than after it is written.
A queue that holds its dates
A post finished early waits for its date; one that arrives late does not shove the rest of the month down the line. The published archive therefore has even spacing, which is what the schedule was for.
Approval, on or off
On, and a post waits for your review and then publishes on its date. Off, and it publishes whether or not you looked. Keep it on for the first month; the point of the setting is that you can decide.

When to stop publishing and start repairing.

Past a few hundred URLs, the faster return is usually in the pages you already have. That is a deliberate choice, not a failure of cadence.

Publishing is the only lever most blogs use, and it is the slower one once an archive exists: a page in position 12 for a query with real demand is a cheaper win than a new post on a new subject. Two useful questions before the next post — is there a page of mine that already nearly ranks for this, and is there one that has slid? Where the answer is yes, fix it first. Xt4b does not do that audit for you; it plans, writes and publishes new posts, and the reviews below are the pages that cover the other half.

Questions behind the cadence.

The two everyone asks, and two that decide the schedule.

Is there a minimum frequency for SEO?

There is no threshold below which a site stops ranking. What frequency buys you is coverage and recrawl: more pages answering more queries, and a site that search engines check more often because it keeps changing. A site that publishes twice a month for two years is ahead of one that publishes weekly for a quarter and stops.

Does a gap in publishing hurt rankings?

Not directly — nobody is penalised for a quiet month. What a gap costs is compounding: the cluster you were building stays incomplete, the internal links you were going to add do not exist, and the habit is what usually fails next. If you have to stop, stop, and restart on the same days.

Weekly or twice a month?

Weekly, if the plan has the queries to support it — roughly fifty a year, which most sites with any gaps at all do have. Twice a month is a perfectly respectable floor for a business blog, and it is usually the honest number for a team of one. What is not respectable is a plan whose dates are further apart than the queue behind it.

Should I publish on weekends or in batches?

The date matters less than the spacing. A batch of four posts published on one afternoon is four posts the site has to discover at once, and nothing lands next month. Publishing days are a setting per site: pick the weekdays you can review on, and let the posts fall on them.

Nothing here is a promise of rankings, traffic or revenue — those are not guaranteed, and no schedule changes that. What is guaranteed is what gets published and the date it goes out.

Related.

The same question answered in other languages, and the pages that go deeper.

More on content

Dates that hold

A calendar that keeps publishing without you.

Set the weekdays once. The plan fills them, the posts land on their dates, and approval decides whether you see them first.

Automate my blog

20€ / site / language / month3 days free, no card