TYPO3 Core

The same problem concerns the canonical field.

Example:
We have a client (SingleNode) with the languages DE and EN. For an EN page we now specify a canonical.

Result:
The page is still output in the sitemap.xml because of the DE canonical_link = '' query.

Background:
Using the query in getPages() in PagesXmlSitemapDataProvider we get all DE pages. Via generateItems the overlays are fetched and all filter methods (canonical, doktype and more) are ignored.

Possible solution v13:
- We first fetch all pages of the default language and filter the result afterwards
- Remove TypoScript Condition for the canonical field
- Introduce a new constant for canonical fields (excldueCanonicalPages = 1 / Default on)
- Introduce PSR-14 events (separate issue) to change pages results

Workaround:

Use a custom provider via TypoScript

config {
    xmlSitemap {
      sitemaps {
        pages {
          provider = TYPO3\CMS\Seo\XmlSitemap\PagesXmlSitemapDataProvider
        }
      }
    }
  }

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80535