Multi-sitemap discovery

Flowpane searches multiple sources:

1. robots.txt — parse all Sitemap: directives
2. Standard locations — /sitemap.xml and /sitemap_index.xml
3. Platform-informed candidate paths — bounded hints only; platform evidence does not prove that a CMS/plugin owns or manages the sitemap
4. Index expansion — child sitemaps fetched and analysed

Review the discovered sitemap set. Discovery is bounded and may not include every child of a large index; confirm your expected public files against the result.

Indexes and nested discovery

A sitemap index points to other sitemap documents. Discovery may follow available declarations and child documents within the scan’s limits; it is not a promise to enumerate every nested resource. A blocked or malformed child can leave the observation set incomplete even when the parent index is readable.

Check the discovered document list and any failed requests. Confirm that robots.txt declarations point to the intended public sitemap set, and that child URLs are reachable. Do not replace a CMS-generated index with a flat file without deciding who owns future updates. See sitemap protocol.