TYPO3 Core

Description:
I am experiencing an unexpected behavior with the sitemap functionality in my setup. When I append /sitemap.xml to any URL within my domain, the system serves a sitemap file. This occurs not only at the expected location (mydomain.de/sitemap.xml) but also at paths such as:

• mydomain.de/anotherURL/sitemap.xml
• mydomain.de/anotherPath/to/anotherURL/sitemap.xml

These are not redirects (e.g., mydomain.de/anotherURL/sitemap.xml → mydomain.de/sitemap.xml); the system appears to generate and serve a file for these nested paths as if they were real files.

Expected Behavior:
I expected the sitemap to only be accessible at mydomain.de/sitemap.xml.

Environment:
This issue occurs in both version 12 and 13.

Question:
Am I misconfiguring something, or is this behavior unintended?

Configuration (site config):

routeEnhancers:
  PageTypeSuffix:
    type: PageType
    map:
      sitemap.xml: 1533906435

Thank you for your assistance!

While performing a search using Indexed Search for specific terms, we noticed that for each search term (or URL), there is an additional result appearing in the search results in the form of mydomain.de/term/sitemap.xml.

This does not appear to be an issue related to TYPO3 itself but rather a configuration problem within Indexed Search. It seems the sitemap URLs are being indexed and included in the search results, which is likely unintended behavior.

Thank you; indeed this scenario would benefit from only having a single sitemap result (still a single result would show up for you which is probably still unintended).

I'm leaving this open as Benni has some ideas about this kind of routing.

I found a solution. Adding the line

seo_sitemap.config.index_enable = 0

in your setup.typoscript effectively prevents the sitemap.xml from being indexed.