No Redirects in Sitemap
Checks that sitemap URLs return 200 directly, not via 301 or 302 redirects.
What this check measures
We fetch each sitemap URL with HEAD requests and check the final status. URLs that redirect waste crawl budget and suggest stale or incorrect sitemap entries.
Why it matters
Every redirect in the sitemap costs two requests (original + target) vs. one. Google's crawl budget is finite; redirects mean fewer unique pages get crawled per session. Also signals a poorly maintained sitemap.
How our audit detects it
HEAD request each sitemap URL. Flag responses with 301, 302, 307, 308 status and record the final URL.
Typical findings
- error_outlineOld http:// URLs in sitemap that redirect to https://.
- error_outlineNon-www URLs listed but redirect to www (or vice versa).
- error_outlineLegacy URL slugs still in sitemap after a rename.
How to fix
Always list the final canonical URL in the sitemap. When you move a URL, update the sitemap at the same time you add the redirect.
Copy-paste fix prompt for your stack
Lovable · Cursor · Bolt · v0 · Replit · Windsurf · Claude Code · Base44
Frequently asked questions
Does Google still follow the redirect?expand_more
Want this checked on your site?
Pantra runs the full audit (SEO, Security, GEO, Performance, Schema, Technical, Images) in 10 seconds and generates stack-specific fix prompts.
Scan my siteRelated checks
Meta Title
Checks that every page has a unique, keyword-rich <title> tag between 10-60 characters.
SEOMeta Description
Checks that every page has a unique meta description between 50-160 characters.
SEOH1 Tag
Checks that every page has exactly one H1 tag containing the primary keyword.
SEOHeading Hierarchy
Checks heading order — H1 → H2 → H3 without skipping levels.