<?xml version="1.0" encoding="UTF-8"?>
<!--
  Six URLs. This file used to say "three URLs, because there are three" and
  explain that the app has no router, so the whole game lives at "/" and listing
  invented paths would point crawlers at soft 404s. That reasoning still holds
  for the GAME — there is still no router, and "/" is still the entire app.

  What changed on 2026-09-13 is that there is now something to read as well as
  something to play. The three content pages below are real static files in
  public/, exactly like the two legal pages, served extensionless by Cloudflare
  Pages (ADR-0008, ADR-0013). They are not invented paths and they are not soft
  404s: they are the answer to the measurement that prompted them, which was that
  the live apex served NINE crawlable body words to every AI crawler while the
  sites winning these questions served 793-7,760.

  Every URL here is the APEX (mazepawn.com, no www), matching rel="canonical" in
  index.html. Both have to agree: a sitemap listing one host while the canonical
  names another is a duplicate-content signal rather than the fix for one.
  seo.test.ts fails if they drift.

  Every URL here is also EXTENSIONLESS, and the files behind them are still
  .html. Pages strips the extension and 308s the .html form; advertising the
  redirecting form is what ADR-0013 was written to stop.

  The 301 that actually enforces the apex is a Cloudflare zone Redirect Rule,
  not a file here — Pages _redirects cannot express a domain-level redirect.

  WHERE THE lastmod DATES COME FROM, because guessing produced a wrong one.
  For every page except "/" it is the "last updated" line PRINTED IN THE PAGE,
  and seo.test.ts now fails if the two disagree — for the content pages as well
  as the legal ones. That drift is not hypothetical: the privacy policy was
  revised twice on 2026-09-07 (analytics, then error monitoring) while this file
  still said 2026-09-03, telling a crawler not to bother re-reading the page we
  had just rewritten, days before submitting the site to Search Console.

  /terms went the other way and was too NEW: it said 2026-09-03 because the file
  was touched that day, but the only edit was href="/privacy.html" ->
  href="/privacy". The terms themselves last changed on the 2nd, which is what
  the page says and what belongs here.

  "/" has no printed date and so has no cross-check. Update it by hand when
  index.html changes in a way a reader would notice — as it did on 2026-09-13,
  when the noscript block stopped being nine words.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://mazepawn.com/</loc>
    <lastmod>2026-09-13</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://mazepawn.com/how-to-play</loc>
    <lastmod>2026-09-13</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://mazepawn.com/faq</loc>
    <lastmod>2026-09-13</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>https://mazepawn.com/strategy</loc>
    <lastmod>2026-09-13</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
  <url>
    <loc>https://mazepawn.com/privacy</loc>
    <lastmod>2026-09-07</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://mazepawn.com/terms</loc>
    <lastmod>2026-09-07</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>
