<?xml version="1.0" encoding="UTF-8"?>
<!--
  forefitter.com — sitemap INDEX.

  The suite is one origin made of four separately-deployed bays, so each bay
  publishes its own sitemap and this index ties them together. A sitemap may
  only list URLs at or below its own path, which is exactly how the bays are
  laid out, so the scoping works out.

    /sitemap-pages.xml        the hub itself
    /shafts/sitemap.xml       generated by the Shaft Lab — 70 URLs
    /golf-balls/sitemap.xml   generated by the Ball Lab (Next)
    /coaches/sitemap.xml      generated by the Coach Lab (Next) — ~1,240 URLs
    /courses/sitemap.xml      generated by the Course Lab (Next) — ~16,800 URLs

  The Course Lab's course pages used to be left out of its sitemap, on the
  grounds that enumerating tens of thousands of on-demand IDs would cost an
  upstream sweep per build and go stale immediately. The cost was real; the
  conclusion was wrong. Nothing links to a course page from server-rendered
  HTML — the finder's map is client-side — so with no sitemap entry either,
  every one of those pages was unreachable by a crawler. They are now
  enumerated weekly into a baked index (course-finder/scripts/harvest-courses.mjs,
  ~199 requests), and that bay's sitemap is prerendered from it.

  Referenced from /robots.txt. Submit THIS url to Search Console, not the
  individual sitemaps.
-->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://forefitter.com/sitemap-pages.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://forefitter.com/shafts/sitemap.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://forefitter.com/golf-balls/sitemap.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://forefitter.com/coaches/sitemap.xml</loc>
  </sitemap>
  <sitemap>
    <loc>https://forefitter.com/courses/sitemap.xml</loc>
  </sitemap>
</sitemapindex>
