<?xml version="1.0" encoding="UTF-8"?>
<!--
  lastmod is maintained by hand. Only /privacy and /terms carry their own "Last
  updated" line on the page, and tests/pages.test.ts cross-checks lastmod against
  it for just those two; / and /support have no such line, so their lastmod must
  be bumped by hand whenever those pages change, with nothing to catch a miss.
  It is not derived from file mtime: the build copies src/static into
  dist/static, which restamps every file with the copy time, so a mtime-derived
  sitemap would tell crawlers all four pages changed on every deploy.

  A RESTYLE IS NOT A CHANGE TO /privacy OR /terms. Their lastmod is pinned to
  the "Last updated" line those pages declare, which is a statement about the
  policy, not the markup — so presentation-only work (e.g. the 2026-08-11
  header/footer port) deliberately leaves both dates alone. Bumping them would
  tell a reader the terms they agreed to had changed when they had not. /support
  carries no such line and is bumped normally.

  changefreq and priority are omitted deliberately — Google ignores both.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://pricehound.co.uk/</loc>
    <lastmod>2026-09-01</lastmod>
  </url>
  <url>
    <loc>https://pricehound.co.uk/privacy</loc>
    <lastmod>2026-09-13</lastmod>
  </url>
  <url>
    <loc>https://pricehound.co.uk/terms</loc>
    <lastmod>2026-07-13</lastmod>
  </url>
  <url>
    <loc>https://pricehound.co.uk/support</loc>
    <lastmod>2026-08-11</lastmod>
  </url>
</urlset>
