How freshness works
Why you can trust what you see
Three rules keep every page honest.
From published to confirmed, in three steps
It ends on its own
Every special has an end date the owner sets, capped at eight weeks out. When that date passes, the special leaves the site by itself.
One tap confirms it
We ask twice, at most: once when a special has run four weeks without a confirmation, and once seven days before it ends. One button on one page, no form. Nothing weekly.
What diners see
The date the owner last confirmed it, never the end date. Green up to four weeks old, amber after that.
The rules in full
Every special on Weekly Eats shows the date the owner last confirmed it. That is the whole promise of this site, so it is worth being precise about what it means and what it does not.
A confirmation date is a fact about the past. It cannot be improved by picking a distant end date: the end date is when the special stops being shown, and no end date moves the confirmation date. Confirming moves the end date, four weeks out from the day it is confirmed, and nothing moves it the other way. Only the confirmation date appears on the page, and it appears as a date rather than as "this week", so a page nobody has touched cannot keep claiming to be current.
Nothing here is left over from months ago. A special with no confirmation and a passed end date is gone, not quietly aged. Where the last confirmation is more than four weeks old, the chip turns amber and shows that date anyway, rather than the site pretending the gap is not there.
How quickly a change reaches you
Pages are held briefly at the network edge so they load fast. When an owner publishes, edits or withdraws a special, the change reaches every visitor within a few minutes, and a withdrawn special leaves the site on its own without anyone needing to refresh. Every page carries the version of the data it was built from, so the claim can be checked rather than taken on trust.