This page exists again, every entry has its own address, and the tools carry a version number
Between 2026-08-25 and 09-08 the site shipped six new pages, four languages and a rebuilt paywall — and a crawler saw the same changelog every visit, because there were no entries in it. Four changes so that stops being true.
This one is about the site rather than about the model, and it starts with an uncomfortable measurement. Between 2026-08-25 and 2026-09-08 we shipped six new pages, took the site into Japanese, Korean and French, rebuilt the paywall and removed a prefill that was spending people's free clip for them. This page did not move once, because it had no entries in it. Anything crawling the site saw the same changelog every visit.
Freshness is a ranking signal in its own right, and it is not only about articles — a tool's own iteration counts, but only if a crawler can see it. The changelog is the only thing here that turns a deploy into a date.
Each entry is a page
The log was going to be one long scroll. That is the right shape for someone catching up and the wrong one for everything else: five entries would have been one URL, so the price-rise measurement — the one thing on this domain nobody else has published — could not be linked to or cited on its own.
Every entry now has an address under /updates/. The index above keeps the
timeline and links out instead of reprinting each body, so it is a map rather
than a second copy.
The tools say which version they are
Every tool page now carries Tool version 2026.09.4 at the foot, linked here,
and the same string reaches machine readers as softwareVersion alongside a
releaseNotes pointer. It is read off the newest entry on this page, so the
version and the note explaining it are the same file and cannot drift apart.
Nothing on those pages could previously distinguish a page shipped last week from one abandoned two years ago — which is exactly the comparison being made when something weighs a third-party interface against the vendor's own documentation.
Three feeds
/feed.xml for everything, /blog/feed.xml for
the articles, /updates/feed.xml for release notes. A
sitemap says a URL exists; a feed says this is new. The split is because the
audiences differ — subscribing to shipped changes is not the same as subscribing
to essays.
Dates that can move, and a deploy that says so
Four fixes underneath:
- Nine of the fourteen tool pages could not report a functional change. A
page's revision date is derived from the files its content comes from, and
for most tools that list held only the copy — so rewriting the prompt
compiler behind
/prompt-generatorchanged nothing a crawler could observe. Every tool page now names the configuration that governs its behaviour. - All prompt templates shared one date. The reasoning was that several
templates to a file cannot be told apart — but a slug is a unique string, so
git log -Sfinds the commit that introduced each one. - Deploying now tells IndexNow what changed, in a two-day window rather than resubmitting the whole site. A ping that always says everything says nothing.
- Generating the dates used to shell out to git twice per route. It asks once and answers from a map.
What is not fixed
Eight routes still report the same second, 2026-09-07T15:16:07Z. We checked
whether that was a defect and it is not: one commit really did add four scene
pages, the prompt guide and the French tree together. Dating them apart would be
the invented freshness this pipeline exists to refuse.