<?xml version="1.0" encoding="UTF-8"?>
<!--
  Ragnity — sitemap. A declared inventory of what exists, not a ranking factor.

  For six pages Google would find everything without help; the real reasons this
  file is here are that Search Console needs it to report on indexing at all,
  and that it states plainly which URLs we consider ours.

  ONLY THE TWO HOME PAGES ARE LISTED, and since 2026-09-24 that is the whole
  file. `/de/match/` and `/en/match/` were here from 2026-08-25 — the indexable
  landing surface of a printed QR code — until the two pages were deleted and
  forwarded to `/meet` (see public/_redirects and docs/STATE.md). A sitemap
  entry for a URL that now answers 302 is a contradiction a crawler has to
  resolve, so the entries went in the same commit as the pages.

  Note what that costs, because it is a real consequence and not a tidy-up: the
  event pages WERE indexed, and `/meet` is `noindex, follow`. The content does
  not move to a new address in Google's eyes — it leaves the index. That is the
  intended outcome for a business card, which is meant to be reachable rather
  than found, but it is a deliberate removal rather than a migration.

  `/de/meet/` AND `/en/meet/` ARE DELIBERATELY ABSENT, and they stayed absent
  when they stopped being placeholders (Stefanie, 2026-09-14). They are the
  target of a printed QR code and are meant to be REACHABLE, not FOUND: whoever
  lands there is holding a business card, and whoever searches for Ragnity
  should get the home page. They keep `noindex, follow`, so the rule below
  covers them for the same reason it covers the legal pages.

  The four legal pages carry `noindex, follow` on purpose, and listing a page
  you have asked not to be indexed is a contradiction a crawler has to resolve —
  so they stay out. Change the noindex and this file changes with it.

  Each <url> repeats the FULL set of alternates including itself, which is what
  the protocol asks for and what the pages' own hreflang tags already say. The
  two must agree; if one is edited the other is edited in the same commit.

  No <priority>, no <changefreq>. Google has said for years it ignores both, and
  a number nobody reads is a number that goes stale without anyone noticing.
  <lastmod> is real and must be updated when a page's content changes.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:xhtml="http://www.w3.org/1999/xhtml">

  <url>
    <loc>https://ragnity.ai/de/</loc>
    <lastmod>2026-09-24</lastmod>
    <xhtml:link rel="alternate" hreflang="de" href="https://ragnity.ai/de/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://ragnity.ai/en/"/>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://ragnity.ai/"/>
  </url>

  <url>
    <loc>https://ragnity.ai/en/</loc>
    <lastmod>2026-09-24</lastmod>
    <xhtml:link rel="alternate" hreflang="de" href="https://ragnity.ai/de/"/>
    <xhtml:link rel="alternate" hreflang="en" href="https://ragnity.ai/en/"/>
    <xhtml:link rel="alternate" hreflang="x-default" href="https://ragnity.ai/"/>
  </url>

</urlset>
