<?xml version="1.0" encoding="UTF-8"?>
<!--
  MangoBook sitemap.

  Four URLs: the marketing site, and nothing else. Every one of them is a
  static HTML document with its own entry in vite.config.ts and its own rule in
  _redirects - scripts/check-static.sh checks that all three lists agree, so a
  page listed here that does not build, or that falls through to the booking
  shell, fails before it ships.

  Venue booking pages at /<venue-slug> are deliberately NOT here. They are
  resolved from the API in the browser, so a crawler fetching one receives an
  empty shell and listing them would point search engines at pages with nothing
  in them. Worse, the list would have to be generated at build time from live
  customer data, which would publish our customer roster as a side effect of a
  deploy.

  Venue pages become worth listing the day they are rendered on the server; the
  gap and the two ways out of it are written up in docs/seo.md.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://mangobook.net/</loc>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://mangobook.net/pricing</loc>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
  <!-- Policy pages are listed rather than hidden. They are low priority to a
       search engine and high value to an assistant answering "how long does
       MangoBook keep booking data" - which is a question a venue's own
       compliance officer asks before signing up. -->
  <url>
    <loc>https://mangobook.net/privacy</loc>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://mangobook.net/terms</loc>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>
