<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
    <sitemap>
        <loc>https://traderise.co/sitemap-static.xml</loc>
    </sitemap>
    <sitemap>
        <loc>https://traderise.co/sitemap-articles.xml</loc>
        <lastmod>2026-09-26</lastmod>
    </sitemap>
    <sitemap>
        <loc>https://traderise.co/sitemap-news.xml</loc>
        <lastmod>2026-09-26</lastmod>
    </sitemap>
    <!-- THE FIFTH SITEMAP, AND WHY IT IS LISTED HERE THOUGH IT IS NOT OURS.

         `/sitemap-carousels.xml` is written by the FRONTEND build into
         `dist/` (`scripts/prerender.mjs`) and served as a static file —
         nginx's sitemap regex deliberately excludes it so it falls through
         (`nginx.conf`: "DO NOT BROADEN THIS REGEX"). That is about who
         SERVES it, and it was being read as though it were about who
         ANNOUNCES it: until 2026-09-20 the file existed, was declared only as
         a second `Sitemap:` line in `robots.txt`, and was absent from this
         index. Measured that day: the index listed 3 children and the
         carousels file's 6 URLs had their own weaker discovery path and no
         row in Search Console's sitemap report — so nothing said whether they
         were being read at all.

         A sitemap index is a list of URLs. It does not care which server
         answers them, and this one is on the same host. No `lastmod`: this
         service does not build that file and has no honest date for it. -->
    <sitemap>
        <loc>https://traderise.co/sitemap-carousels.xml</loc>
    </sitemap>
</sitemapindex>
