<?xml version="1.0" encoding="UTF-8"?>
<!--
  A sitemap INDEX, not a list of pages — one URL covering both the marketing
  pages and all of the documentation.

  SUBMIT THE -index URL, NOT THIS ONE.  https://data-conductor.com/sitemap-index.xml

  Cloudflare intercepts the literal path /sitemap.xml on this zone and answers
  it with 404.html, while the GCS origin serves the very same object with a 200
  (verified both ways: storage.googleapis.com/data-conductor.com/sitemap.xml is
  fine). /sitemap-index.xml passes through untouched. That intercept is also
  why /sitemap.xml appeared to be "missing" before any sitemap existed.

  This file is kept and deployed anyway: it costs 832 bytes, it is what
  crawlers probe by convention, and it starts working the moment somebody finds
  and removes the Cloudflare rule — look under Rules (Redirect / Transform /
  WAF) and Workers routes for anything matching /sitemap.xml.

  robots.txt cannot carry the usual `Sitemap:` line here either: the live one is
  synthesised by Cloudflare (content-signal comments, no directives) and is not
  served from this bucket.
-->
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://data-conductor.com/sitemap-pages.xml</loc>
    <lastmod>2026-09-17</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://data-conductor.com/docs/sitemap.xml</loc>
    <lastmod>2026-09-17</lastmod>
  </sitemap>
</sitemapindex>
