<?xml version="1.0" encoding="UTF-8"?>
<!--
  Evenzr — sitemap

  ONE static entry, deliberately.

  This file used to list /#evz-discover, /#evz-upcoming and /#pricing as
  separate <url> entries. A fragment identifier is not part of what a crawler
  requests — the server never sees it — so all three resolved to exactly the
  same document as /, and Google discards fragment-only URLs rather than
  indexing them. They were not four pages competing with each other; they were
  one page listed four times, which spends the sitemap's signal saying nothing.

  Individual event pages are created by organisers at runtime and live behind
  /register/{ownerUid}/{eventId}; a build-time file cannot know them, and
  hardcoding a sample would publish one organiser's event to every crawler
  forever. They are reachable by crawl from the discover map and are explicitly
  allowed in robots.txt.

  If the site grows real indexable routes — a company page, docs, per-section
  pages at their own paths rather than fragments — each belongs here. If
  event-level indexing becomes a priority, the right build is a Cloud Function
  serving a dynamic sitemap from the events collection, not an ever-staler list
  checked into the repo.

  The host here, the canonical in index.html, the og:url, the Sitemap line in
  robots.txt and SITE.website in src/dpdp.js must all agree on
  https://www.evenzr.com — scripts/verify-seo.js asserts it. Mixed hosts split
  the same page's signals between two URLs Google treats as rivals.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.evenzr.com/</loc>
    <lastmod>2026-10-23</lastmod>
    <changefreq>daily</changefreq>
    <priority>1.0</priority>
  </url>
</urlset>
