Re-dating a drip without hiding what's already live

Every essay carries a publish date. The public list hides anything dated in the future, so a stack of finished essays with tomorrow's, and next week's, dates simply reveals itself one morning at a time. No cron to publish, no button to press — the calendar does it. The only rule I hold on top is one essay per distinct day, so the list reads as a steady cadence instead of a burst followed by silence.

Here is the part that bites. If hiding future dates is how a queued essay stays hidden until its day, then moving an already-published, already-indexed page to a future date does the same thing to it — it disappears from the list and, to a crawler, becomes a page that used to be there and now is not.

So re-spacing a clump of same-day posts is not a free operation. Push a live page into next week to tidy the calendar and you have quietly de-indexed it for a week. The tidy list is not worth a week of a real page being gone.

I hit this for real with a run of ten essays that had all landed on the same day — a whole series stamped with one date. The lazy fix is to spread all ten across the next ten days and call it tidy. But most of those pages were already live and crawled; sending them forward would have pulled real, indexed pages out of the index to buy a prettier list. The right fix was narrower: keep one on the original day, move the rest only into empty days that had already passed, and let just the still-unseen tail take future slots.

The rule that keeps it honest: fill empty past days freely, because a page dated last Tuesday is still live today; but only ever move something into the future if it was never public in the first place — a genuinely new or still-queued piece. Never send a live page forward to make room.

It is the same discipline as keeping a sitemap honest: the schedule you advertise should match what you actually want found, with no page caught contradicting itself.