The site can finally say what changed
Thirty-six URLs, twenty-eight of which told a crawler nothing about when they last moved. All forty-two now carry a real date, there are three RSS feeds, and this page exists again — with a version number the tool pages report.
This entry is about the site rather than the model, and it starts with an embarrassing measurement.
Between 2026-09-02 and 09-08 this site shipped two tool pages, rebuilt the free lane, fixed a checkout that had been refusing real money, and re-ran the generator against three endpoints nobody had tested. A crawler saw none of it. Not because the pages did not change — they did, and the site knew exactly when — but because the one field a crawler reads when deciding whether to come back was blank.
Every URL now carries a real revision date
The site already derived a publication and revision date for every page from the git history of the files that page's content comes from. Those dates were printed in the byline at the foot of each page and in its structured data.
They were not in the sitemap. Of 36 submitted URLs, 28 carried no lastmod
at all, and the 8 that did carried their publication date — which never moves,
so a rewritten article and an untouched one looked identical.
Now, with this page and its five entries added, the sitemap offers 42 URLs and:
- all 42 carry a
lastmodderived from git, spread across seven distinct days rather than bunched on the one afternoon the files were committed, - posts publish the later of their git history and an author's own
updated_at, which is the difference between the file moved and somebody re-checked the facts, - and a page with no traceable date still publishes none, because a guessed date is worse than no date.
Three feeds
Everything, the blog, and this changelog. Three rather than one because somebody following the product and somebody following the writing are not the same reader, and mixing them is how both unsubscribe.
This page exists again, and it earns its URL this time
/updates was deleted on 2026-09-04, for a good reason: it was publishing the
site template's own release notes — version bumps and screenshots of somebody
else's admin panel — on a domain whose every other page spends words
establishing that it is an independent third party. Removing those left an
indexable page with nothing on it, which was not better.
It comes back under three rules:
- Entries have their own addresses. A single scrolling page is the right shape for catching up and the wrong one for citing: the two entries above that are original measurement could not be linked to on their own.
- Every entry contains something you can check — a number, a path, or a page you can open. Anything that cannot be checked does not get an entry; it waits and gets merged into the next one.
- It is written on the day of the deploy, not reconstructed on a Monday
from
git log.
The tools report which version they are running
Tool pages now state the release they are on and link to the entry that describes it. Until today the structured data for this application named the app, its category and its price and stopped — no version, no release notes, no modification date. Those three fields are how software says it is still alive, and an undated application with no version reads exactly like one abandoned two years ago.
The version is derived from the newest entry on this page, so it cannot drift
from what shipped. 2026.09.4 is this one.