<?xml version="1.0" encoding="UTF-8"?>
<!--
  Pillara sitemap.xml
  ────────────────────────────────────────────────────────────────────────
  Enumerates every CURRENTLY-SHIPPED public marketing route on the apex
  domain (https://mypillara.com), derived directly from the <Route> entries
  in MarketingRoutes inside src/App.tsx. We intentionally do not include:

    • /invite/:token  — dynamic param route, not enumerable without a list
                        of issued caregiver-invite tokens. Each token is
                        scoped to a single recipient and shouldn't be
                        crawled anyway.
    • /app and /app/* — these live on app.mypillara.com (the demo sandbox),

    • beta.mypillara.com routes — beta carries
                                  <meta name="robots" content="noindex,nofollow">
                                  via NoindexBeta, so by design it stays
                                  out of every search index.

  lastmod uses today's ISO date (UTC) per the date the file was authored.
  Bump this whenever a route is added, removed, renamed, or its on-page
  copy is materially changed; crawlers use it as a "do we need to refetch"
  hint, not as a strict authority.

  Priority values are relative weights (Pillara's own pages only, not
  cross-domain). The marketing apex landing is the highest-value entry
  point; legal pages are the lowest. Google has stated it largely
  ignores <priority>, but Bing/Yandex still honour it as a hint and
  leaving the field present costs nothing.

  This file is served as static asset /sitemap.xml from the Vite public
  directory on every host (apex, demo, beta, dev preview). The
  production robots.txt points crawlers at the apex copy specifically
  (https://mypillara.com/sitemap.xml), which is the version they should
  use. The same bytes on app.mypillara.com / beta.mypillara.com are
  harmless because:
    - beta carries a noindex meta on every page, so its sitemap copy is
      never consulted by indexing crawlers in the first place.
    - the demo subdomain's pages all canonical-tag back to the apex, so
      a crawler that did fetch /sitemap.xml from app.mypillara.com would
      still resolve every entry to the canonical apex URL.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://mypillara.com/</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://mypillara.com/founders</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://mypillara.com/founders-refund-policy</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.5</priority>
  </url>
  <url>
    <loc>https://mypillara.com/brand</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.4</priority>
  </url>
  <url>
    <loc>https://mypillara.com/press</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.4</priority>
  </url>
  <url>
    <loc>https://mypillara.com/privacy</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://mypillara.com/terms</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>https://mypillara.com/delete-account</loc>
    <lastmod>2026-05-24</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.2</priority>
  </url>
</urlset>
