This document is open to every reader on every plan. Availability tells you what a plan includes; it does not decide what you may read.
EN
What it is for
The Sitemap Quality Monitor tells you whether your sitemap is honest. This page is where you manage the registrations themselves at each search engine: see what Google, Bing and Yandex have on file for your site, submit a sitemap URL, and remove a registration where the provider permits it. Three providers, three different sets of permissions, on one screen.
EN
How to use it
Connect the provider in Integrations and match a property to the project. Without a matched property there is nothing on this page to read.
Read the inventory before you submit anything. A sitemap already registered does not need registering again.
Submit the HTTPS URL of a sitemap the project hostname actually serves. A URL on another host is refused rather than sent.
To remove a registration, read the warning first, then confirm with your password and the exact confirmation phrase. That deliberate friction is the point.
EN
Reading the result
Each provider permits different things, and the page says which rather than offering the same three buttons everywhere. Google lets you list, add and remove. Bing lets you list and add. Yandex keeps the sitemaps its robot discovered separate from the ones you submitted, and only the ones you submitted can be removed - so a discovered entry with no remove control is the provider rule, not a missing feature.
EN
What it cannot tell you
Removing a registration affects the search engine only. Your XML file stays on your website and your pages stay indexed: this is not a way to remove pages from search, and reading it as one is the mistake the confirmation phrase exists to slow down. Nor does submitting cause a crawl - it tells the provider where to look when it next decides to.
EN
What it keeps
The record of every submission and removal you made through this platform, with the provider, the URL, and the outcome. What the providers hold is read live on each visit, because a cached inventory would let this page contradict the search engine it is describing.