Redirect best practices for crawlers
Good redirects keep crawlers and link equity flowing to the right destination. The essentials: use 301 or 308 for permanent moves and 302 or 307 only for genuinely temporary ones, redirect each old URL directly to its final target in a single hop, map to the closest equivalent page rather than dumping everything on the homepage, and avoid loops. These choices preserve indexing signals and conserve crawl budget.
Pick the right status code
Match the code to intent. Use 301 (Moved Permanently) or 308 (Permanent Redirect) when a URL has moved for good — crawlers consolidate signals onto the target and update the indexed URL. Use 302 (Found) or 307 (Temporary Redirect) only when the move is genuinely temporary and the original URL should remain canonical.
The difference between 301/302 and 308/307 is method handling: 307 and 308 require the request method to be preserved, while 301 and 302 historically allowed a method change. For simple GET page moves either pair works; choose permanence (3 vs 30x semantics) deliberately.
- Permanent move: 301 or 308 (signals consolidate onto the target)
- Temporary move: 302 or 307 (original URL stays canonical)
- 307/308 preserve the request method; 301/302 historically may not
Keep chains short and targets relevant
Redirect each old URL directly to its final destination. A chain (A to B to C) wastes crawl budget, slows users, and risks losing signals at each hop; collapse it so A points straight to C. Never create a loop, where redirects cycle back on themselves and strand both crawlers and users.
Map each old URL to its closest equivalent. Redirecting many retired URLs to the homepage is treated by Google as a soft 404 — the destination is not a real replacement for the requested content. If there is no equivalent, returning 404 or 410 is often more honest than an irrelevant redirect.
Migration hygiene
During a site move, prepare a complete old-to-new URL map, implement single-hop redirects, update internal links to point at the new URLs directly (so crawlers do not rely on the redirect), and keep redirects in place long enough for crawlers to process them — months, not days.
Update sitemaps and canonical tags to the new URLs, and monitor Search Console and logs for redirect errors and chains afterward. Done well, redirects make a migration nearly invisible to rankings; done poorly, they are a common cause of post-migration traffic loss.
How it appears in analytics and logs
Redirect quality determines whether crawlers consolidate a moved URL onto its target. Wrong codes, long chains, loops, or redirecting to irrelevant pages waste crawl budget and can lose the indexing signals you meant to preserve.
Diagnostic use case
Plan a migration or URL change so redirects pass signals correctly — right status code, one hop, equivalent targets — without creating chains, loops, or soft-404 patterns.
What WebmasterID can help detect
WebmasterID records the redirect status codes crawlers receive server-side, helping you spot chains, loops, or unexpected temporary redirects affecting how crawlers reach your canonical URLs.
Common mistakes
- Using 302 temporary redirects for moves that are actually permanent.
- Leaving redirect chains (A→B→C) instead of pointing A straight to C.
- Redirecting many retired URLs to the homepage, which Google treats as soft 404.
- Not updating internal links, leaving crawlers reliant on redirects.
Privacy and accuracy notes
Redirect behaviour concerns how crawlers traverse URLs, not visitor identity. WebmasterID records crawler fetches and their statuses without attaching them to any person.
Frequently asked questions
- Should I redirect a removed page or return 404?
- Redirect only if there is a genuinely equivalent page to send users and crawlers to. If there is no equivalent, return 404 or 410 — redirecting to an unrelated page or the homepage is treated as a soft 404.
Related pages
- Redirect chains and loops
A redirect chain is a sequence of hops (A to B to C) before reaching the final URL; a redirect loop never resolves. Chains waste crawl budget, slow signal consolidation, and can stop crawlers following beyond a hop limit. The fix is to point each source straight at the final destination.
- Infinite redirect loops
An infinite redirect loop occurs when URL A redirects to B which redirects back to A (directly or through a cycle), so the request never reaches a final response. Browsers and crawlers stop after a few hops and report an error. Loops make pages completely unreachable, blocking both users and indexing.
- HTTP 308 vs 301 for SEO
301 and 308 both signal a permanent move and let search engines consolidate signals onto the new URL. The difference is method handling: 301 has historically been treated loosely, while 308 strictly preserves the request method and body. For ordinary GET page moves either works; 308 is safer when the method must not change.
- Website observability
See the redirect status codes crawlers receive, and spot chains, server-side.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.