<?xml version="1.0" encoding="UTF-8"?>
<!--
  LEGACY ROOT INDEX — /sitemap_index.xml is the real one.

  Suheb's approved structure names the root index /sitemap_index.xml, and that is
  what robots.txt advertises and what should be submitted in Search Console. This
  file is retained only so the older /sitemap.xml URL — already crawled, and
  already submitted in GSC — keeps resolving to a valid index with the SAME three
  children rather than 404ing during and after the transition.

  Keep the child list identical to sitemap_index.xml. Two indexes disagreeing about
  what exists is worse than either one alone.

  ⚠️ SERVED FROM S3/CLOUDFRONT, NOT BY THE CONTAINER.
  This is a MASTER COPY. Editing it changes nothing until it is uploaded to S3 and
  the CloudFront cache is invalidated. Same rule as every other file in this folder;
  see s3-sitemaps/README.md.

  This path has ALWAYS been an S3 object — it is the one that caused the June 2026
  failure, when commit 19877121 edited the repo's public/sitemap.xml and production
  went on serving a stale June object for two months. As of 2026-08-26 every sitemap
  is deliberately an S3 object, so that failure mode is now handled by having no
  competing copy in the web root at all, rather than by avoiding S3.

  WHEN THIS FILE CAN BE RETIRED
  Once GSC shows /sitemap_index.xml processed cleanly and no crawler has requested
  /sitemap.xml for a reasonable window, replace this object with a 301 to
  /sitemap_index.xml. Do not simply delete it — a 404 on a submitted sitemap is an
  error in Search Console, a redirect is not.
-->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://prismlearning.academy/sitemap-main.xml</loc>
    <lastmod>2026-08-26</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://prismlearning.academy/sitemap-sat-pages.xml</loc>
    <lastmod>2026-08-26</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://prismlearning.academy/blog/sitemap.xml</loc>
  </sitemap>
</sitemapindex>
