<?xml version="1.0" encoding="UTF-8"?>
<!-- GENERATED by scripts/generate-apex-sitemap.mjs. DO NOT HAND-EDIT.
     Regenerate: SS_APEX=shuttlestats.app node scripts/generate-apex-sitemap.mjs

     THIS IS AN INDEX, not a url list. /sitemap.xml is the conventional
     discovery path and many crawlers fetch it directly without reading
     robots.txt first, so it must lead to EVERYTHING we publish, not just
     the apex's own pages. The club corpus is the product; it lives in
     clubs-sitemap.xml and is reached from here.

     The corpus is REFERENCED, never inlined. An apex url entry for a
     register URL would be a duplicate rather than a listing while landing's
     path="*" catch-all answers platform-only paths with the marketing
     homepage. A sitemapindex names the child DOCUMENT, whose
     own url entries are minted against the register's origin by
     api/lib/clubs-sitemap.mjs, so that hazard does not reach it.

     Every url here carries the apex of the STAGE THIS WAS BUILT FOR, from
     SS_APEX. A dev document naming .app hosts is a cross-host submission
     from a noindexed surface. scripts/__tests__/apex-sitemap.guard.test.ts
     pins these bytes for prod and drives both stages. -->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://shuttlestats.app/pages-sitemap.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://shuttlestats.app/clubs-sitemap.xml</loc>
  </sitemap>
</sitemapindex>
