DEV Community

Daniel Pertu
Daniel Pertu

Posted on

Our sitemap tells Google 32 pages changed on 14 September, and the edge cache says the HTML was built on 18 October

Notifio is a desktop rental-listing monitor, and its website is 38 pages. notifio.app/sitemap.xml lists all 38 of them, and it is one of the better files in the repository: ten of those URLs are typed out, and the other 28 are derived from the same arrays that render the pages.

const alertPages: MetadataRoute.Sitemap = ALERT_SITES.map((site) => ({
  url: `${APP_URL}/alerts/${site.slug}`,
  lastModified: new Date("2026-09-14"),
  changeFrequency: "monthly",
  priority: 0.8,
}));
Enter fullscreen mode Exit fullscreen mode

ALERT_SITES is the array the hub grid, the route's static params and the footer column all read, so adding a site cannot half-add it: the page and its sitemap entry come from the same edit. That is the part I am happy with.

Now look at the second line.

Four dates, all typed by a person

Every lastModified in that file is a new Date("...") with a string literal in it. Across 38 URLs there are exactly four distinct values:

2026-09-14   32 URLs
2026-10-18    4 URLs   /, /pricing, /terms, /privacy
2026-10-03    1 URL    /about
2026-07-21    1 URL    /help
Enter fullscreen mode Exit fullscreen mode

You can read them off the live file:

curl -s https://notifio.app/sitemap.xml | grep -o '<lastmod>[^T]*' | sort | uniq -c
Enter fullscreen mode Exit fullscreen mode

The ones I can check, I checked, by asking git when each page's source last changed:

route       sitemap says   git says
/            2026-10-18    2026-10-18   ✓
/pricing     2026-10-18    2026-10-18   ✓
/about       2026-10-03    2026-10-03   ✓
/terms       2026-10-18    2026-10-18   ✓
/privacy     2026-10-18    2026-10-18   ✓
/download    2026-09-14    2026-09-14   ✓
/alerts      2026-09-14    2026-09-14   ✓
/compare     2026-09-14    2026-09-14   ✓
/guides      2026-09-14    2026-09-14   ✓
/help        2026-07-21    2026-09-14   ✗
Enter fullscreen mode Exit fullscreen mode

Nine out of ten. Whoever typed these was being careful. And then there is /help, which advertises 21 July.

21 July is the date two components on that page were written, FaqAccordion.tsx and ContactForm.tsx. But help/page.tsx and help/faq-data.ts, which hold every word the page actually says, were last edited on 14 September, in a commit called "Remove em dashes from visible copy". So the sitemap entry is 55 days behind its own copy, and as of today it is 115 days behind.

That is the failure mode of a hand-typed date in a file somebody edits for a different reason. The URL list in that same file cannot go stale, because it is computed. The dates sitting next to it went stale the first time a page was edited by someone who was not thinking about the sitemap, which is every time a page is edited.

The 32 that claim 14 September

The other 32 URLs are the 28 generated ones, fifteen per-site alert pages, five comparison pages and eight long-form articles, plus /download, /alerts, /compare and /guides. They all claim 14 September, which is the day the catalogue files behind them were last changed, so by the standard above they are correct.

Except the content of a page is not only its catalogue entry. Every one of those 38 pages renders inside app/layout.tsx, which last changed on 18 October, and includes components/Footer.tsx, which last changed on 3 October. Both of those edits changed bytes in all 38 documents. One of them swapped the fonts the pages load, which changed the <link rel=preload> set in every head on the site.

So a crawler reading the sitemap is told that /alerts/kamernet last changed on 14 September, about a document whose markup demonstrably changed twice after that.

The cache header that settles it

You do not have to take git's word for when these documents were produced. The pages are statically rendered and served from Vercel's edge cache, and a cached response tells you its own age:

curl -sI https://notifio.app/alerts/kamernet | grep -E '^(age|x-vercel-cache|cache-control)'
Enter fullscreen mode Exit fullscreen mode
age: 2198726
cache-control: public, max-age=0, must-revalidate
x-vercel-cache: HIT
Enter fullscreen mode Exit fullscreen mode

2,198,726 seconds is 25.4 days. I ran that across all 38 pages:

  • 35 pages came back x-vercel-cache: HIT with an age between 2,198,726 and 2,227,669 seconds, which is 25.4 to 25.8 days, so every one of them was generated in a window a few hours wide around 18 October.
  • 3 pages came back age: 0, because they are the three that refuse to be cached at all: /, /pricing and /download. The first two carry a per-visitor price and the third hands out a signed download link, which is a thing I wrote up separately in Three of our 38 pages tell every cache not to store them.

The spread inside those 35 is itself interesting: 29,000 seconds between the oldest and the newest means the cache was not filled in one sweep, it was filled page by page as traffic arrived after the deploy.

So there are three different answers to "when did this page change", all of them available to anyone with curl:

source answer for /alerts/kamernet
lastmod in the sitemap 14 September
git, for the catalogue entry 14 September
git, for the layout it renders in 18 October
the age header on the served HTML 18 October

What I am going to do about it, and what I am not

The honest engineering answer is that lastModified should not be a literal. Two options, both cheap:

  1. Read it from git. git log -1 --format=%cI -- <file> per page at build time, with the layout's own date folded in as a floor, since an edit to the layout changes every page.
  2. Read it from the build. new Date(process.env.VERCEL_GIT_COMMIT_SHA ? buildTime : Date.now()) is one line and is never wrong about the document, though it is also never informative: every page would claim the deploy date, including the 30 that genuinely did not change.

Option 2 is the one that tempts you and the one to avoid. A sitemap where all 38 dates jump on every deploy is a sitemap whose lastmod carries no information, and Google is explicit that it only uses lastmod if it finds it to be consistently accurate. "Accurate" there means it correlates with real content changes, and a date that moves when nothing changed fails that test just as badly as a date that sits still when something did.

Option 1 is the right shape, and the floor rule is the part worth stating out loud: a page's effective last-modified is the latest of its own content, its layout, and the components it renders. That is exactly the calculation nobody performs when they are typing a date string into an array.

Meanwhile the thing that actually gets pages recrawled here is not the sitemap at all, it is an IndexNow ping fired by hand after a deploy, which has its own set of ways to lie to you: A 200 from IndexNow does not mean it read your key.

And one date in that file is going to stay hand-typed for now, with a note next to it. The comparison pages at notifio.app/compare quote five competitors' prices, each read from the company's own pricing page, and the file that holds them has this at the top:

export const PRICES_CHECKED = "September 2026";
Enter fullscreen mode Exit fullscreen mode

That string is rendered on the page next to the figures, because a quoted subscription price is the single most likely thing on this site to go stale. It is two months old. Unlike a lastmod, that one is a promise to the reader rather than a hint to a crawler, which means the fix is not a derived timestamp. It is going back and re-reading five pricing pages.

Top comments (0)