<?xml version="1.0" encoding="UTF-8"?>
<!--
    Two entries, and that is not an oversight either way. The landing page and
    the privacy policy are the only routes that are content; the editor and the
    account pages render an application, and a share link is unlisted by design
    and is excluded in robots.txt as well as by an X-Robots-Tag header. A sitemap
    listing routes that should never be indexed would be arguing with itself.

    /privacy is here on purpose rather than tolerated. A policy somebody has to
    be told about before they can find it is doing half its job, and a consent
    bar that links to a page search engines were told to skip reads as an
    attempt not to be read.

    https://aiuml.itsmepotato.com is substituted at startup from Site:PublicUrl — see
    Infrastructure/SiteMetadata.cs. A sitemap must carry absolute locations, so
    this file is served through that substitution rather than as a static file.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://aiuml.itsmepotato.com/</loc>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://aiuml.itsmepotato.com/privacy</loc>
    <changefreq>monthly</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>
