What happens to a page nobody maintains

A site that keeps adding pages ends up with some nobody looks after: a design concept from a review, a copy kept for comparison, a page whose subject moved elsewhere. Left alone they keep answering searches with layouts and wording nobody checks. Our rule, adopted November 5, 2026:

• A page is maintained when its own code changed in the last 90 days, or when it reads data a scheduled job refreshes. Those figures carry their own dates, and the ingestion ledger lists every run that failed.
• A page is unmaintained when it is a design concept or a frozen copy, whatever its age, or when it reads no data and its own code is more than 90 days old.
• An unmaintained page gets a dated archive notice at its top that names the page to use instead, is marked noindex, and is left out of the sitemap. Nothing is deleted under this rule; a deletion is a separate decision and goes in the changelog.

The list below covers all 281 page routes on the site, read from our git history on November 6, 2026. A route with a bracket is a family of pages, such as one page per ticker. "Own code" is the route's own files; a shared component changing does not count as someone looking after the page. A check fails when a route is added without rerunning the inventory, or when an archived page loses its notice, its noindex or its place outside the sitemap.

Archived pages (14)

Each carries the notice below at its top. They were already noindexed and outside the sitemap; what they lacked was a date and a pointer to the page that replaced them.

Unmaintained, waiting for a notice (0)

None on November 6, 2026: every static page's own code changed within 90 days, and the check fails the day one does not and has no notice.