<?xml version="1.0" encoding="UTF-8"?>
<!--
  TWO URLS, AND THAT IS THE WHOLE SITE.

  Wyzenest has no router. src/main.jsx picks between three pathnames and
  everything else a person can reach — dashboards, chores, the store, the bank,
  Zoomies — is React state behind "/", so it has no address to list. The three
  paths are "/", "/index.html" and "/privacy" (KNOWN_PATHS in
  src/components/NotFound.jsx); "/index.html" is the same document as "/" and is
  left out on purpose, because listing both would ask search engines to pick a
  canonical between two identical pages. index.html's <link rel="canonical">
  already answers that question.

  KEEP THIS IN STEP WITH KNOWN_PATHS. If a real route is ever added, it belongs
  in both files or in neither.

  "/privacy" IS DELIBERATELY ABSENT, AND IS THE ONE THING TO ADD BACK.
  src/pages/PrivacyPolicy.jsx refuses to render the policy while a bracketed
  placeholder or the DRAFT banner is still in docs/PRIVACY_POLICY.md — a guard
  that exists so a half-written policy can never be published as if it were
  real. Listing "/privacy" here today would therefore hand a crawler the refusal
  page and let it index that as the privacy policy, which is worse than having
  no sitemap entry at all.

  ADD IT BACK when the policy is published, in the same change that fills the
  last placeholder. It is the same gate that blocks migration 0054, so the two
  move together:

    <url>
      <loc>https://wyzenest.com/privacy</loc>
      <lastmod>YYYY-MM-DD</lastmod>
      <changefreq>monthly</changefreq>
      <priority>0.5</priority>
    </url>
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://wyzenest.com/</loc>
    <lastmod>2026-09-23</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
</urlset>
