Generating sitemap.xml When Friendly URLs Use the .html Suffix

Sites that use a global .html friendly URL suffix often run into a strange SEO side effect: generated sitemap pages try to behave like normal HTML resources instead of real XML endpoints.

The donor case described exactly that problem. A sitemap resource was intended to become something like /sitemap.xml, but the routing layer kept turning it into an HTML-style page such as /sitemap1.html.

Why this happens

When friendly URL suffixes are applied globally, the parser treats the sitemap page like any other resource alias unless you explicitly carve out an exception.

A safer strategy

• Keep the human-facing HTML sitemap and the XML sitemap as two separate endpoints.
• Do not rely on the default alias-to-suffix behavior for machine-readable outputs.
• Add an explicit routing exception or dedicated handling for the XML resource.

That approach is usually cleaner than forcing a parser hack in the middle of the core request flow. The principle is simple: SEO endpoints such as sitemap.xml, feeds, or other machine-readable resources should be treated as special outputs, not just another friendly URL page.

This post still matters because it documents a real Evolution SEO edge case that still appears whenever teams mix classic suffix-based routing with modern search-engine requirements.