<?xml version="1.0" encoding="UTF-8"?>
<!--
  myhelloassist.com's OWN sitemap. Deployed to S3 key `sitemap-app.xml` and
  served at /sitemap.xml on this domain only, by the myhelloassist-router
  CloudFront function. helloassist.us keeps the shared sitemap.xml untouched.

  Why this file exists: both domains share one S3 bucket, so /sitemap.xml on
  myhelloassist.com used to serve the helloassist.us sitemap — four URLs, none
  of them on this domain. Anyone following standard discovery (a crawler, or a
  reputation vendor reviewing a categorization request) was sent straight to a
  different hostname, which reads as a domain with no content of its own.

  ONLY public, indexable paths belong here. The myhelloassist-noindex function
  allowlists the same set; a path listed here but not allowlisted there would be
  advertised to crawlers and then served "X-Robots-Tag: noindex", which is worse
  than omitting it. Keep the two lists in step.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://myhelloassist.com/</loc>
    <lastmod>2026-09-22</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://myhelloassist.com/guide</loc>
    <lastmod>2026-09-22</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>https://myhelloassist.com/privacy</loc>
    <lastmod>2026-06-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.2</priority>
  </url>
  <url>
    <loc>https://myhelloassist.com/terms</loc>
    <lastmod>2026-06-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.2</priority>
  </url>
  <url>
    <loc>https://myhelloassist.com/sms-terms</loc>
    <lastmod>2026-06-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.2</priority>
  </url>
</urlset>
