List the public URLs you actually want discovered
List the canonical pages you actually want discovered and keep retired or non-indexable variants out of the intended inventory. An automatically generated sitemap may include preview URLs and thin archives that do not serve a useful search purpose.
A sitemap helps communicate intended URLs, but it does not guarantee crawling, indexing or rankings. Including a URL also does not fix an error response, conflicting canonical or poor page purpose. Keep the list aligned with the site’s public publishing decisions.
A worked example
A hypothetical sitemap includes live service pages alongside staging previews, redirects and internal thank-you pages. The file is syntactically valid, yet the inventory does not describe a clean set of intended public destinations. Removing inappropriate entries is different from asking a search engine to delete content.
How to apply it
- Compare sitemap entries with current canonical destinations and publication status.
- Exclude private, redirecting, retired or deliberately nonindexable destinations as appropriate to the site.
- Verify that retained URLs resolve and that changes are reflected in the published sitemap.
What the result can establish
Check submission and processing status where authorized, then monitor actual page inclusion separately. The number of submitted URLs is a discovery input, not the count of indexed or ranking pages. Keep protected staging outside the public discovery inventory.
Reference: Google: requesting recrawling.
Supporting documentation
Google: requesting recrawlingGoogle: canonicalizationGoogle: noindexGoogle: technical requirements