Separate generation from publication
One system can generate several files without mixing every hostname into an unexplained list. Partition by domain, language or a content family that helps the team. Understandable partitions make investigation and ownership changes easier.
Establish control explicitly
Cross-site submission has ownership conditions documented by the search provider. Verify the current procedure before relocating a sitemap to another hostname. A link between domains, or a shared agency, does not itself establish the required permission.
Exclude test hostnames
Central generation can accidentally mix public, retired and staging sites. Validate allowed hosts and final destinations explicitly. Save exceptions in a report rather than silently discarding them, so the responsible team can correct the underlying records.
Plan domain departures
When a domain leaves the group, revoke appropriate access and remove its URLs from shared generation. Check what each hostname actually serves. Organisational control and technical behaviour should remain intelligible to the next maintainer.
- Partition
- Verify control
- Validate hosts
- Plan removals
Worked example
Control sheet: domain / public file / permitted hosts / owner / last check date. A staging URL discovered in a production list stops publication until its source is corrected.
Check before moving on
These checkboxes are not saved.
Sources & method
Sources reviewed on 1 October 2026. Worked calculations use explicitly hypothetical inputs.
Topic provenance: La déclaration croisée des Sitemaps, une fausse bonne idée ? (2008-02-28). Search Engine Feng Shui. Byline retained in the consulted version: François Houste.
This guide is newly written in 2026. It does not reproduce the earlier text and is not attributed to its historical author.