<?xml version="1.0" encoding="UTF-8"?>
<!-- Hand written on purpose: this site is a handful of pages and a
     generator would be one more thing to keep running. Add a page here
     when you add a page.

     THE EXCLUSION LEDGER, COMPLETE. `VG-B-875`. This list was audited on
     2026-08-24 against every .html file in web/ and it was already correct;
     what it lacked was a reason for each absence, so the question kept being
     reopened and the honest answer kept having to be re-derived. It is now
     written down once. The rule: a page belongs here if and only if it is
     crawlable AND carries no `noindex`. All four that qualify are listed.

     404.html        -- noindex. An error document in a sitemap asks Google to
                        index a page whose entire job is to say the URL is
                        wrong, and Search Console flags exactly that.
     affiliate.html  -- noindex. A sitemap that advertises a page the page
                        itself refuses is a contradiction. It is also the
                        right side to keep for now, because the /affiliate/*
                        Worker routes are not deployed, so search traffic
                        would land on a form that cannot submit. When that
                        deploy lands, drop the noindex and add the entry
                        TOGETHER, in one commit.
     partners.html   -- noindex, and it is a meta-refresh stub whose canonical
                        points at affiliate.html. Listing a URL that
                        canonicalises to a different URL is the "alternate
                        page with proper canonical tag" report, by hand.
     referral.html   -- noindex AND Disallow. Opened from a link somebody was
                        given, never from a search.
     share.html      -- noindex AND Disallow. Same reason: a half loaded
                        snapshot of one stranger's trip is a poor result.
     googlea083837e59031db3.html
                     -- not a page. It is the Search Console verification
                        token and its whole content is its own name.

     NOTE ON THE THREE THAT ARE noindex WITHOUT A Disallow. That combination
     is deliberate and it is not an oversight in robots.txt: a Disallow stops
     the fetch, and a crawler that never fetches the page never reads the
     `noindex` on it, so the URL can still surface from inbound links. To keep
     a page OUT, let it be crawled and let it say no. robots.txt says the same
     thing from its side. `web/../app/tests/website-meta.test.ts` holds this. -->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://vagort.app/</loc>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://vagort.app/support.html</loc>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>https://vagort.app/privacy.html</loc>
    <changefreq>yearly</changefreq>
    <priority>0.4</priority>
  </url>
  <url>
    <loc>https://vagort.app/terms.html</loc>
    <changefreq>yearly</changefreq>
    <priority>0.4</priority>
  </url>
</urlset>
