<?xml version="1.0" encoding="UTF-8"?>
<!--
  Hand-maintained, and deliberately so.

  There are TWO indexable URLs on this site and no CMS, so a generated sitemap
  would be a build step producing the same three lines. It is edited by hand
  instead, which means a new public page has to be added here deliberately
  rather than appearing by accident.

  A sitemap lists URLs that should be indexed, so anything carrying a noindex
  must NOT appear here. Listing a noindexed URL sends crawlers a contradiction:
  "index this" in the sitemap, "do not index this" in the page. Google usually
  resolves it by dropping the URL, but the honest fix is to keep them apart.
  This file and the meta tags are edited as a pair.

  What is here, and why:

    /                The builder. The product, and the page most worth earning
                     clicks on. High priority is not a ranking signal, it is a
                     crawl-order hint, and this is genuinely the page that most
                     deserves crawl budget.

    /help/           The how-to. The only page here that answers a question
                     rather than being the tool. Someone searching for how to
                     make a digital wedding invitation is looking for exactly
                     what it documents, so it is indexable and linked from the
                     builder, the sign-in page and the dashboard.

  What is not here, and why:

    /privacy/, /terms/    Reachable and linked from the builder, the invitation
                          card, the 404 and now the sign-in page, which is the
                          only way anyone actually needs them. Both carry
                          `noindex, follow`. They answer no search query, so
                          listing them would trade two thin pages in the index
                          for no traffic.

    /manage/               A per-couple sign-in form behind a secret. It holds no
                          invitation content of its own, so a search result for
                          it could only ever be a login page. It carries
                          `noindex, follow`: follow, so the legal and Help links
                          in its footer still get read. Deliberately NOT
                          disallowed in robots.txt, because a Disallow stops the
                          page being fetched, and a page that is never fetched
                          never has its noindex read either.

    /invite/<slug>        A wedding. Private to the couple and their guests, and
                          dead 90 days after creation. Listing these would
                          publish a stranger's date, venue and names. Also
                          disallowed in robots.txt, because noindex only works
                          if the page is fetched first.

    /api/*                The card's own fetch. Same reason, also disallowed.

    /404.html             Served for any unmatched path, reached by no internal
                          link, and noindex.

  lastmod is the date that page's content last materially changed, not the date
  this file was touched. Bump it when the content changes; a stale lastmod on an
  unchanged page is harmless, but a fresh one on an old page is a small lie that
  crawlers notice.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://floryn.day/</loc>
    <lastmod>2026-09-27</lastmod>
    <changefreq>monthly</changefreq>
    <!-- The builder is the product and the only page that earns clicks. High
         priority is not a ranking signal, it is a crawl-order hint, and this
         is genuinely the page most worth spending crawl budget on. -->
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://floryn.day/help/</loc>
    <!-- First published 28 September 2026. -->
    <lastmod>2026-09-28</lastmod>
    <!-- The how-to changes when the product does, not on a schedule. Quarterly
         is a hint, not a promise, and a crawl a fortnight too early costs
         almost nothing. -->
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>
