XML sitemap errors that send crawlers to the wrong list

Audit the list against the live site

Every URL in the sitemap should return 200, be indexable, and canonicalise to itself. Redirects, 404s, noindex pages, and parameter duplicates do not belong there.

Search Console will flag some of these as issues. A crawl of the sitemap file catches the rest, including URLs on the wrong host.

Generate the sitemap from the pages you mean

Build the file from the same source as the routes, not from every row in a CMS. When a guide is unpublished, it should leave the sitemap in the same change.

Split very large sites by type if one file becomes hard to reason about. A small site can stay in one file as long as the rules are strict.

• Include only canonical 200 URLs.
• Use the preferred host and protocol.
• Update the file when routes change, not on a vague timer.

Treat warnings as a publishing bug

A sitemap full of redirects means the routing layer and the content layer disagree. Fix the generator. Resubmitting the same file does not change what the URLs return.

After a clean submission, use the sitemap as a regression check: new soft 404s and accidental noindex pages show up as status mismatches.

Does a sitemap make pages rank?

No. It helps discovery and reporting. Rankings still depend on the page, the links, and whether the URL is the one you intend to index.

Should redirected URLs stay in the sitemap?

No. List the destination. A sitemap of redirects spends crawl on hops and muddies coverage reports.