Core Sitemap or Plugin Sitemap
If Sitemap and Robots are from different plugins, their inclusion rules must fit together. Not just manually edit the visible XML file.
Using robots.txt and the delivered XML file, determine the active sitemap producer. WordPress Core and SEO plugins can select different content and taxonomies. Exclusions belong in this source and not in a downloaded XML copy.
Where to check the setting in WordPress
Go to /wp-sitemap.xml if the core sitemap is used. With an SEO plugin, you determine its sitemap index via robots.txt instead. Check whether the affected content is published and contained in the selected content type or taxonomy.
Example of this specific finding
Illustrative control case: An internal search page with conscious noindex is recorded by the sitemap generator. Sitemap selection and indexing intent do not match.
Sitemap: https://example.org/suche/?q=rad
HTML: <meta name="robots" content="noindex">
Entscheidung: interne Suche bleibt ausgeschlossen → nicht in die Sitemap aufnehmen.follow-up audit in WordPress
Review a published paper, a draft and a relevant taxonomy. After a change, retrieve the sitemap index and the affected partial sitemap without logged in session.
If consciously excluded, permanently remove the URL from the generator selection. If noindex is accidental, correct the page default and retrieve both outputs.
Derogations and scope
Remove Noindex not only to pass the sitemap check. For user functions, the exclusion may be correct.
Related: WordPress with classic or block theme. SEO plugins and page builders are different; there is no universal menu path for all installations.
Classify the general error
Definition, system-independent causes and further correction examples: Align sitemap selection with the intention to publish