Page redirected: the sitemap declares a URL that bounces

In brief

A page still declared in your sitemap started redirecting to another URL: the sitemap presents a bouncing address as canonical, which wastes crawl budget. If the redirect is intended, remove the URL from the sitemap; otherwise it is often a broken route to restore.

WarningP1 — Direct ranking

What is it?

A page still declared in your sitemap has started redirecting to another URL.

Why it hurts SEO and AI

Your sitemap tells Google "this URL is canonical, crawl it" while it bounces elsewhere: contradictory signals, crawl budget wasted on an address that no longer really exists. Two possible readings: either the redirect is intentional (migration, content merge) and the sitemap is lagging behind; or it is not, and it is often a broken route, a page deleted by mistake or a redesign that moved the URL without anyone noticing. A page that is 301-redirected AND removed from the sitemap, however, is a clean removal: Seogard does not flag it.

When it is NOT a problem

  • The redirect is intended and the URL has already been removed from the sitemap: that is a clean removal, and Seogard does not alert on it.
  • A migration in progress where the sitemap will soon be regenerated with the new URLs.
  • A 301 redirect to the equivalent page, pending the already scheduled sitemap update.
Before
<!-- sitemap.xml -->
<url><loc>https://site.com/product-a</loc></url>
<!-- but /product-a returns 301 to /product-b -->
After
<!-- sitemap.xml -->
<url><loc>https://site.com/product-b</loc></url>
<!-- /product-a removed; 301 kept -->

The sitemap should list only URLs that answer with a 200; the old one can keep redirecting, outside the sitemap.

How to fix it

  1. Confirm the redirect on the listed URL (curl -I) and note its destination.
  2. Decide: intended redirect (migration) or broken route to fix?
  3. If intended, remove the URL from the sitemap and check the redirect is a 301 to the equivalent page; otherwise, restore the original page.
  4. Regenerate the sitemap and re-crawl to clear the inconsistency.

This scan checks the HTTP status, noindex and canonical of every page

Is this issue on your site?

Does your sitemap list URLs that redirect? Enter a URL: Seogard compares your sitemap pages with the real status they return and spots the ones that bounce instead of answering. Free, no credit card.

By clicking Scan, I certify that I own this site or have permission to crawl it.

  • No credit card
  • Result in ~30 s

What you get back

The sitemap and the server tell the same story: Google focuses its crawl on real pages, and an accidental redirect no longer goes unnoticed.

Seogard catches this regression automatically — through its monitoring for your metas and canonicals.

Frequently asked questions

Why should a redirecting URL not stay in the sitemap?

The sitemap is a list of canonical URLs to index; leaving a redirecting address in it sends contradictory signals and wastes Google's crawl budget.

Is a redirect in the sitemap serious?

Not catastrophic on its own, but it is a frequent symptom of a broken route or a lagging sitemap; worth watching so pages do not disappear unnoticed.

Related rules

JavaScript redirectThe page responds 200 but its JavaScript redirects the browser elsewhere. Google only follows it after rendering (delayed, or never if rendering fails) and AI systems read the original HTML, not the destination: machines and humans see two different pages. Broken redirectA cleanly removed page (redirect + removed from the sitemap) now returns a 4xx error: its redirect broke. Link equity from backlinks pointing to the old URL is no longer passed — typically a refactor that deleted the redirect rule or its target. Broken SSRThe HTML returned by the server (SSR) is almost empty even though the page works in the browser. Google indexes an empty page.

Updated July 10, 2026