<?xml version="1.0" encoding="UTF-8"?>
<!--
  Every page a crawler can actually read, and **only pages that exist**.
  Everything else in this product is behind a session, so listing it
  would only send Google to the login screen.

  Three absences, each deliberate, and all for one reason: a sitemap is
  a list of pages worth indexing, so an entry is a claim that there is
  something there.

  `/terms` and `/refunds` ship with `apps.legal`, on a branch that has
  not merged — today both answer with the not-found screen, and an entry
  for one is the site telling a crawler it is broken. Add them back in
  the same change that lands those routes.

  `/coaches` is a real page with an honest empty state, and being listed
  in it is opt-in: `GET /api/coaches/` currently returns `count: 0`.
  Indexing it now means Google caching "nothing here" for the one page
  that is supposed to attract coaches. It is linked from the nav and the
  footer, so it will be found regardless. Add it back once somebody is
  actually in the directory.

  Written by hand rather than generated at build time, because five URLs
  do not justify a plugin and a hand-written file cannot silently start
  listing routes that were never meant to be public.

  The one change that would make this file matter is a product decision,
  not a technical one: the 540 exercises are public-ready content sitting
  behind the login, and that — not a sitemap — is where a competitor's
  search traffic comes from.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.grooow.app/</loc>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://www.grooow.app/signup</loc>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>https://www.grooow.app/notices</loc>
    <changefreq>yearly</changefreq>
    <priority>0.2</priority>
  </url>
</urlset>
