Non-200 URL in sitemap: find and remove it

What it means

A URL in your sitemap returns a non-200 status code when Googlebot fetches it. This means the page is listed as discoverable but the response isn't a normal 200 OK.

Why it matters

Non-200 responses slow crawl demand because Googlebot treats them as less valuable than healthy pages. Status codes like 302, 404, or 5xx cause the URL to be deprioritized in the crawl queue and, if persistent, eventually dropped from the index. For AI agents and crawlers, a broken status means the page content is never extracted, so it won't appear in search results or AI-generated answers.

How to fix it

1. Identify which status codes are flagged — check the crawl report for 302, 404, 410, or 5xx responses.
2. Fix the underlying issue: return 200 for valid pages, serve real 404/410 for removed content, and resolve 5xx server errors.
3. Remove permanently deleted URLs from the sitemap (or mark them with noindex), and update the <lastmod> attribute.
4. Verify the fix by re-fetching the URL in the URL Inspection tool and confirming the status code returns 200.

When it's not a problem

A 302 redirect in the sitemap is often fine — Google follows it and uses the target URL. A 404 for a page that was recently deleted is also expected and not a real problem.

How Crawlinx detects it

We fetch each URL listed in your XML sitemap and check its status. Any that return a redirect or an error (non-200) are reported — a sitemap should list only live, final URLs.

How common is it?

896 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.

FAQ

Should a sitemap contain redirects or 404s?

No. A sitemap is a list of canonical, indexable, 200-status URLs. Redirects and errors in it erode Google's trust in the whole file.

Related guides

• XML Sitemaps: Format, Limits & Common Mistakes