<?xml version="1.0" encoding="UTF-8"?>
<!--
  Every address this site answers.

  Four, and the three policies are the reason it is worth having a file at all:
  they are real pages with real content that nothing links to prominently, so a
  crawler is unlikely to find them by following links from the homepage.

  No <lastmod>. The honest date for a policy is in `legal/content.ts`, the
  honest date for the homepage is whenever its copy last changed, and neither is
  derivable at build time from anything that is currently tracked. A lastmod
  that is wrong is worse than none — a crawler that catches a sitemap claiming
  freshness it cannot back up stops trusting the dates on all of them.

  No <priority> or <changefreq> either. Google has said for years that it
  ignores both, and a file full of numbers nobody reads is a file nobody
  maintains.

  The domain is written out rather than templated. A sitemap's <loc> must be
  absolute and must match the host it is served from, so this file is the one
  place the canonical domain is stated twice — the other is `siteOrigin.ts`,
  and `tests/site-crawlability.test.ts` fails if they disagree.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://veyso.io/</loc>
  </url>
  <url>
    <loc>https://veyso.io/privacy</loc>
  </url>
  <url>
    <loc>https://veyso.io/terms</loc>
  </url>
  <url>
    <loc>https://veyso.io/cookies</loc>
  </url>
</urlset>
