Blog Sections Open
Removing the .html Suffix from sitemap.xml in Evolution CMS
If your sitemap ends up as <code>sitemap.xml.html</code>, fix the route and suffix behavior directly instead of relying on search engines to guess the intended file.
A sitemap should have one stable URL. When friendly URL suffix rules produce sitemap.xml.html instead of sitemap.xml, some crawlers will follow the redirect, but others may treat it as a quality problem.
Why This Happens
- The global friendly URL suffix is applied to a resource that already represents an XML endpoint.
- A strict URL plugin reinforces the generated suffix.
- The sitemap is treated as a normal page instead of a special endpoint.
What to Fix
- Make sure the sitemap resource has the intended alias and content type.
- Exclude the sitemap from suffix logic if necessary.
- Keep the canonical crawlable URL at
sitemap.xml, not a redirected variant.
Search engines are usually tolerant, but sitemap endpoints are one of the places where URL precision matters. A clean XML URL is worth fixing properly.
Avoid Clearing the Entire Site Cache When Saving a Resource
Evolution CMS clears cache broadly by default, so if you need narrower invalidation you have to plan it deliberately instead of expecting per-resource cache out of the box.
Why a Facebook Like Box URL May Fail Even When the Account Exists
A small but useful reminder that some third-party widgets require a Facebook Page URL, not just any profile or group URL.