The page describes something that has ended. Lower stakes than a stale event, and still a page whose usefulness expired. Expired pages are worth keeping when they carry history, and worth removing when they only carry a promise that is no longer true. indexgap does not decide which — it reports the date it found and leaves the judgement to you, because the same expired page can be an archive on one site and a broken promise on another.
The finding reads:
info stale-closed the date … has passed and the page is already closed to indexing — that is correctDecide what the page has become: an archive or a promise it can no longer keep. Mark an archive with its end date in the text itself, and take the promise out of the index.
Collapsed when it fires template-wide. If it appears on 90% or more of the pages — or of one language version — of a site with at least 20 pages, it is a property of the template and is reported once, with the count, instead of once per page.
pipx install indexgap
cd your-project
indexgap init
indexgap checkThen indexgap brief turns
every finding on this page into a work order in indexgap-briefs/,
with the thresholds the result has to satisfy and the command to check it.