<?xml version="1.0" encoding="UTF-8"?>
<!--
  The two indexable routes 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.

  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>
  <url>
    <loc>https://munecos.com.mx/aviso-de-privacidad</loc>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
</urlset>
