<?xml version="1.0" encoding="UTF-8"?>
<!-- Corrected 27 August 2026. Three things were wrong with this file and each one
     told a search engine something the site itself contradicts.

     1. HOST. It listed ssjcmediagroup.com while every rel=canonical, every og:url,
        the JSON-LD url and robots.txt's Sitemap directive all name
        ssjcmediagroup.com. A sitemap that disagrees with the canonical it
        points at is a sitemap the crawler discards.
        STATUS 28 Aug 2026, and READ THIS BEFORE TRUSTING THE HOST BELOW.
        The apex was moved to ssjcmediagroup.com in every canonical, og:url, JSON-LD url
        and @id, robots Sitemap, llms.txt and the vCard, canonical tags first and this file
        second, in the order this note asked for. THE DOMAIN IS NOT YET ATTACHED TO THIS
        NETLIFY PROJECT.
        What was verified: ssjcmediagroup.com is registered at GoDaddy, its nameservers are
        delegated to Netlify (dns1-4.p05.nsone.net), and its A record is 54.253.94.210.
        WHAT THAT DOES NOT PROVE, and it was briefly read as proving it: that IP is Netlify's
        shared edge and it answers for every project on it. Routing is by Host header and by
        which project claims the domain. Fetched live on 28 Aug, ssjcmediagroup.com returns a
        DIFFERENT and older site, title "SSJC Media Group | AI Automation for Modern Business",
        h1 "Your Business, Automated." That is the positioning the venture CLAUDE.md bans by
        name, and it is what a prospect reaches today if Craig says the domain out loud.
        SO: matching A records are not evidence of anything. Compare the served TITLE.
        Craig attaches the domain in the Netlify dashboard, ssjc-media-group, Domain
        management, and the canonicals below become true the moment he does. Until then this
        project is correct at ssjc-media-group.netlify.app and the apex is somebody else's page.

     2. NOINDEX PAGES WERE LISTED. privacy.html carries robots noindex,follow, so
        listing it here asks a crawler to index a page the page itself refuses. It
        is out. why.html is NOT added, for the same reason and deliberately, against
        an audit note that asked for it: it carries robots "noindex, nofollow". If
        why.html is meant to be found, remove its noindex first, then list it. The
        order matters; doing it the other way round publishes a contradiction.
        404.html, thanks.html and /for/ are noindex or private and stay out.

     3. lastmod said 2026-07-30 on files edited today. -->
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://ssjcmediagroup.com/</loc>
    <lastmod>2026-08-27</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://ssjcmediagroup.com/sources.html</loc>
    <lastmod>2026-08-27</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>
</urlset>
