<?xml version="1.0" encoding="UTF-8"?>
<!--
  sitemap.xml for moonstaff.ai

  Four URLs since the 2026-10-22 redesign (lean site): the homepage, which is the
  Custom AI Department's page, /lead-growth, security and accessibility.

  The two standing rules, unchanged:

  1. NEVER list a #fragment as a separate <url>. Fragments are not crawlable
     URLs; Google discards them and an inflated sitemap of anchors is a known
     way to look spammy for zero gain.

  2. <lastmod> must be a real date on which the page CONTENT changed. Scripting
     it to today's date on every deploy is the most common sitemap mistake;
     Google learns the signal is noise and stops weighting it. Update it by
     hand, in the same commit that changes the copy.

  EVERY OFFER PAGE MUST BE LISTED, the homepage included (it carries the Custom AI
  Department). verify-dist.mjs (G3) fails the build when one is missing from this
  file or from llms.txt, so offer #3 cannot ship unlisted.

  /privacy, /terms, /card and /demo are deliberately ABSENT: each carries noindex, and
  listing a noindexed URL in a sitemap sends Search Console two contradictory
  signals. verify-dist.mjs fails the build if one is listed.

  /ai-department, /lead-growth/pricing, /lead-growth/team, /plan and /plan/<pain>
  (all retired 2026-10-22), and the older /pricing, /meet-the-team and
  /department-builds, are ABSENT because they are not final URLs: the edge answers each
  with a 301 (terraform/moonstaff-websites sites.tf, brand_site redirects), and a
  sitemap lists only the page a crawler should keep.

  /accessibility IS LISTED, and the asymmetry with /terms is deliberate. It is the one
  legal-adjacent page that should be findable: it carries the barrier-reporting route,
  and a user with a disability (or a plaintiff's firm) finding it in search BEFORE a
  complaint is the entire reason it exists. Florida was the #2 web-accessibility filing
  jurisdiction in 2025 (961 federal filings, nearly double its 2024 total of 470;
  Seyfarth Shaw), so discoverability here is risk reduction, not an SEO play.

  Priorities are relative, not absolute. The two offer pages carry the conversion
  goal; security and accessibility are supporting reassurance.
-->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://moonstaff.ai/</loc>
    <lastmod>2026-10-22</lastmod>
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://moonstaff.ai/lead-growth</loc>
    <lastmod>2026-10-22</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>https://moonstaff.ai/security</loc>
    <lastmod>2026-09-30</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <!-- Added 2026-09-16 with the page. Priority 0.5, the lowest on the site: it must be
       findable (see the note above) but it is not a page that should outrank an offer
       surface for a commercial query. -->
  <url>
    <loc>https://moonstaff.ai/accessibility</loc>
    <lastmod>2026-10-02</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.5</priority>
  </url>
  <!-- /about REMOVED 2026-08-26: the page was deleted at Eric's direction because he
       does not want his personal information published. Delisted in the same commit
       that deleted the file. A sitemap that advertises a URL returning 404 is the
       fastest way to teach Search Console the feed is unreliable. -->
</urlset>
