<?xml version="1.0" encoding="UTF-8"?>
<!--
  The indexable route of the public site. Everything else is per-visitor and
  already disallowed in robots.txt: the booking flow, the guest manage links
  (which carry an appointment capability token) and the admin panel.

  /aviso-de-privacidad was listed here too, while the one document every
  route is served from names https://munecos.com.mx/ as its canonical: the
  sitemap asked for the notice to be indexed and the page itself said it was
  the home page. It stays crawlable through its links; it is simply no longer
  advertised as a page of its own until it can carry its own canonical, which
  needs a per-route document (audit 2026-10-23, live-blackbox-03).

  robots.txt has advertised this file since the site went live; until #135 the
  address answered 200 with the app shell, because nginx falls every unmatched
  path back to index.html for client-side routing. That reads as an invalid
  sitemap in Search Console rather than a missing one. nginx/app.conf now
  serves this path from disk or answers a real 404.

  `lastmod` is deliberately absent: nothing regenerates this file, and a date
  that stops being true is worse than no date at all.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://munecos.com.mx/</loc>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
</urlset>
