2 sitemap URLs redirect or fail

Short answer

These URLs are in the sitemap but did not load directly: they redirect, return an error, refuse the request with 401, 403, 429 or 503, or time out. A sitemap should list only final URLs that answer 200. Replace redirected URLs with their targets and remove pages that are gone.

crawl.sitemap_not_ok · Priority: P1–P3, by crawler type

What it means

A sitemap should list only final URLs that answer 200. Replace redirected URLs with their targets and remove broken ones.

Why it matters for AI search

Search engines use the sitemap as the list of URLs you want crawled and indexed. Redirects and errors in it waste crawl requests and make the sitemap a less reliable signal; Google's documentation asks for the canonical URLs you want to appear in search.

Pages that refused the audit may work for people and still be listed here, so compare them with the finding on pages that refused the crawl. The rest usually come from a sitemap built from old data, one that uses http:// or the wrong host, or a static file that nobody updated after pages moved.

How to fix it

  1. Look at the status and final URL of each entry in the finding.
  2. For redirects, list the final URL instead, with the same protocol, host and trailing slash as the site. A sitemap generated from live pages by the CMS or framework avoids most of these.
  3. For 404 and 410, remove the URL from the sitemap. For 5xx errors, fix the page or leave it out until it works.
  4. For 401, 403, 429, 503 and timeouts, first check whether the page loads in a browser; if it does, the cause is a firewall or rate limit.
  5. Run the site audit again from your account to confirm the result.

Example

<url>
  <loc>https://example.com/pricing/</loc>
</url>

How to confirm the fix

After the change, press "Check again" on the report: it lists what was fixed and how the score changed.

Check my page →

All findings and how the score works