XML and Markdown Sitemaps

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats. Include concise robots/XML-sitemap discovery comments and llms.txt navigation sentences pointing to actual Markdown answers; preserve the native protocols and verify delivery as described in the local contract.

Lane outputs: sitemap-inventory.md; sitemap-dispositions.md; markdown-coverage.md (combine small related steps with stable section links). Own reconciliation of CMS/routes, XML, internal discovery and every inventory URL disposition. Produce sitemap.md, topic maps and exact canonical-to-.md mappings for the entire eligible scope. Preserve XML protocol and truthful lastmod; keep excluded sensitive URLs in private records.

Purpose

Compare sitemap files with the URLs a site actually intends to expose, then produce safe inventory, generation, or cleanup recommendations. A sitemap is a discovery hint; it neither forces crawling nor guarantees indexation.

Read references/sitemap-inventory-protocol.md before creating or changing a sitemap.

Input gate

Require the current sitemap/index files, expected canonical/indexable URL inventory, preferred host/protocol, robots/sitemap discovery context, relevant locale rules, and source of truth for update time. Do not generate a sitemap from an unfiltered crawler export or an unverified CMS list.