Technical SEO redirect audit

Follow every hop. Find every detour.

Trace server-side redirects, classify permanent and temporary hops, detect loops and uncover chains that waste crawl time or send users to the wrong destination.

Server-side checkingUp to 8 hopsSSRF protected
LIVE
This tool performs a real server-side request.

It checks only public HTTP and HTTPS URLs, follows redirects one hop at a time, and blocks local or private network destinations.

Check a redirect path

Use the exact URL users or search engines currently visit.

NOTE
A clean redirect path is zero or one deliberate hop.

Two or more redirects add latency and create extra failure points. Prefer a direct 301 or 308 for permanent URL moves, and update internal links to the final destination.

Technical SEO Redirect Audit

Follow every redirect hop and find the detours between an old URL and its real destination.

The Redirect Chain Checker traces server-side redirects one hop at a time, identifies permanent and temporary redirects, detects loops, measures the path to the final response and confirms whether the destination matches the URL you expected.

Quick Answer: What is a redirect chain?

A redirect chain occurs when one URL redirects to another URL that redirects again before reaching the final destination. For example, URL A → URL B → URL C. The redirect may still work, but unnecessary intermediate hops add latency, create more failure points and make crawling less efficient.

Redirects are a normal part of website maintenance.

They are used when pages move, domains change, URLs are consolidated, HTTP becomes HTTPS or an obsolete address needs to send visitors somewhere more appropriate.

The problem begins when years of redesigns, migrations, CMS changes and redirect plugins create several intermediate destinations.

Instead of checking only whether the old URL eventually loads, this tool shows the complete path.

What the live checker reports

  • Starting URL
  • Every server-side redirect hop
  • HTTP status at each hop
  • 301 redirects
  • 302 redirects
  • 307 / 308 behavior
  • Redirect loops
  • Final response status
  • Final destination
  • Total redirect count
  • Server-side elapsed time
  • Expected destination match
Real server-side checking: the live tool requests public HTTP and HTTPS URLs directly and follows redirects one hop at a time. Local and private-network destinations are blocked for security.
Redirect Path Quality

A clean redirect normally goes directly to the intended destination.

Old URL /old-service/
→
301 Permanent move
→
Final URL /new-service/
Old URL HTTP version
→
301 HTTPS
→
301 www
→
301 New slug
→
200 Final page

Both paths may eventually work. The second path is still unnecessarily complicated.

Where possible, redirect the original URL directly to the final current destination.

Google Redirect Guidance

Googlebot can follow redirect chains—but Google still recommends keeping them short.

How many redirect hops can Google follow?

Google currently says Googlebot can follow up to 10 hops in a redirect chain. However, Google recommends redirecting directly to the final destination. When that is not possible, Google advises keeping chains low—ideally no more than three redirects and fewer than five.

“Google can follow it” is not the same as “this is a good implementation.”

Additional hops add latency for users, create additional server requests and increase the number of places where a redirect can fail.

How to Use the Checker

Audit one redirect path in six steps.

01

Enter the original URL

Use the exact URL that users, backlinks or search engines currently request.

02

Add the expected destination

When you know where the old URL should end, enter that final URL for destination verification.

03

Run the redirect check

The tool follows the response headers one hop at a time until it reaches a final response or detects a problem.

04

Review every status

Check whether each intermediate hop is permanent, temporary, broken or looping.

05

Check the destination

Confirm that the final URL is relevant, returns the intended status and matches your expected destination.

06

Shorten the path

Where appropriate, replace multi-hop rules and outdated internal links with direct references to the final URL.

Redirect Status Codes

Permanent and temporary redirects communicate different intentions.

Status Meaning Typical SEO use
301 Moved Permanently Permanent URL migration or consolidation.
308 Permanent Redirect Permanent server-side move.
302 Found / Temporary Temporary redirection where the original URL is expected to remain the primary address.
307 Temporary Redirect Temporary server-side redirection.
200 Successful Response Common final destination for a normal live page.
404 / 410 Missing / Gone May indicate a broken redirect destination if the page was expected to exist.
Permanent Redirects

Use 301 or 308 when a URL has permanently moved.

Does Google treat both 301 and 308 as permanent?

Yes. Google currently lists both HTTP 301 and 308 as permanent redirects. Permanent redirects are used as signals that the destination should become the canonical representative of the moved content.

MOVE

Changed URL

A page moves permanently from an outdated path to a new URL.

MERGE

Content Consolidation

Several overlapping pages are merged into one stronger destination.

DOMAIN

Domain Migration

Old-domain URLs permanently redirect to mapped equivalent URLs on the new domain.

Temporary Redirects

Use temporary redirects when you genuinely expect the original URL to return.

How does Google treat 302 and 307 redirects?

Google currently classifies HTTP 302 and 307 as temporary redirects. Googlebot follows them, but Google does not use the temporary redirect itself as a signal that the destination should replace the source URL as canonical.

Reasonable temporary use

  • Short-term maintenance
  • Temporary service unavailability
  • Short-lived campaign routing
  • Temporary location changes

Potential mistake

  • Permanent migration using 302 forever
  • Deleted page permanently routed with a temporary code
  • Domain move implemented as temporary redirects
  • Permanent consolidation with unclear signals
Redirect Loops

A redirect loop has no reachable final destination.

URL A 301
→
URL B 301
→
URL A Again

A loop is not merely an inefficient redirect chain.

The user or crawler never reaches the intended content because the redirect path repeatedly returns to an earlier URL.

RULE

Conflicting Rules

Two rewrite rules can accidentally redirect each URL back toward the other.

HTTPS

Protocol Conflicts

HTTP, HTTPS, www and non-www rules can conflict when configured in multiple systems.

CMS

Plugin Conflicts

CMS plugins, CDN rules and server configuration can each redirect the same URL differently.

Redirect Latency

Every additional hop requires another request before the destination can load.

REQ

Extra Requests

Each redirect requires the client to request another URL before receiving the final page.

TIME

Added Delay

DNS, TLS, server response and network latency can compound across several hops.

FAIL

More Failure Points

Every intermediate URL becomes another place where configuration can break.

The tool reports server-side elapsed time. Treat that value as diagnostic context, not a substitute for a complete page-performance test.
Redirect Chains & Crawling

Long redirect chains make crawling less efficient.

Do redirects use crawl resources?

Yes. Google must request the redirected URLs to reach the final destination. Google's crawling guidance specifically warns that long redirect chains can negatively affect crawl efficiency.

One deliberate redirect

Old URL → final URL

Straightforward for users and crawlers.

Repeated historical migrations

URL 2019 → URL 2021 → URL 2024 → URL 2026

Usually worth consolidating into a direct redirect.

Internal Link Cleanup

Do not make your own site intentionally link through redirects.

Should internal links point to the redirected URL or the final URL?

In most cases, update internal links to point directly to the current final URL. The redirect should remain available for old external links, bookmarks and historical addresses—not as the normal internal navigation path.

NAV

Navigation

Update menus so they link directly to current URLs.

BODY

Contextual Links

Replace old article and service links with direct final destinations.

CTA

Buttons & CTAs

Make sure conversion paths do not pass through unnecessary redirects.

Keep the redirect for historical traffic. Update your own links for current traffic.

That reduces server work and removes unnecessary hops for regular site navigation.

Redirects & Canonicalization

Permanent redirects are one of Google's canonicalization signals.

Does a 301 tell Google which URL should become canonical?

A permanent redirect is a strong signal that the destination should represent the moved content. However, Google evaluates multiple canonicalization signals, including redirects, canonical annotations, sitemap URLs and other evidence.

301

Redirect

Signals that users and crawlers should move from the old address to the new destination.

CAN

Canonical

The final page should normally use canonical signals consistent with the intended preferred URL.

MAP

Sitemap

Current XML sitemaps should generally list preferred final URLs rather than redirecting source URLs.

Align your signals. Redirecting URL A to URL B while canonicalizing URL B back to URL A creates unnecessary ambiguity.
Redirects & Link Signals

A normal permanent redirect is not supposed to destroy PageRank.

Do 301 redirects lose PageRank?

Google's current site-migration documentation says that 301 and other permanent redirects do not cause a loss of PageRank. That does not mean every redirected page will preserve identical rankings, because migrations can also change content, relevance, internal linking, architecture and other signals.

“No PageRank loss” does not mean “no ranking change.”

Google still needs to crawl and process the redirect, understand the destination and update its indexing and canonicalization systems.

Destination Relevance

A technically valid redirect can still send users to the wrong page.

Useful redirect

Old “Austin Gravel Delivery” URL → new consolidated “Austin Sand & Gravel Delivery” page.

The destination still satisfies substantially the same user need.

Poor redirect

Deleted service page → generic homepage.

The user may reach a technically successful page that does not replace the requested content.

Avoid mass-redirecting unrelated URLs to the homepage.

Google warns that redirecting many old URLs to one irrelevant destination can confuse users and may be treated as a soft 404.

Final Destination QA

A redirect chain is only as healthy as its final response.

200

Expected Success

A normal migrated content page commonly ends at a successful 200 response.

404

Broken Destination

The redirect works technically but sends visitors to a page that no longer exists.

500

Server Failure

A redirect may end at a destination experiencing a server-side error.

Always review the final status. “Redirect found” is not enough evidence that the migration works correctly.
Expected Final URL

The destination can return 200 and still be the wrong URL.

Why does the tool let you enter an expected final URL?

It lets you test business intent as well as HTTP behavior. If an old product page is supposed to end at Product B but actually ends at a category page, a simple “200 OK” test would miss the routing mistake.

Expected destination matched

The redirect path ended at the URL you intended.

Destination mismatch

The chain resolved, but the final URL differs from the expected target and deserves review.

Protocol & Hostname Chains

HTTP, HTTPS, www and non-www rules commonly create avoidable extra hops.

Longer implementation

HTTP non-www
↓
HTTPS non-www
↓
HTTPS www
↓
Final page

Cleaner implementation

Every unwanted protocol/hostname variation
↓
Preferred final HTTPS hostname and path

Review server, CDN and CMS rules together. One layer may enforce HTTPS while another separately enforces www, accidentally creating multiple redirects.
Site Migration Redirects

Redirect mapping is one of the most important parts of a URL migration.

MAP

Map Old to New

Build a deliberate mapping from each important old URL to its relevant replacement.

301

Use Permanent Redirects

For permanent URL changes, server-side 301 or 308 redirects are Google's preferred approach.

TEST

Test the Mapping

Verify individual high-value URLs and crawl larger sets when the migration affects many pages.

Do not build chains into the migration.

If an old URL has already moved several times, point it directly to the current final destination where practical.

Redirect Retention

Do not remove permanent migration redirects too quickly.

How long should permanent redirects stay in place?

Google's current site-move guidance recommends keeping migration redirects for as long as possible and generally for at least one year. From the user's perspective, keeping useful redirects indefinitely can make sense when old links and bookmarks may continue to exist.

Keeping the redirect does not mean keeping outdated internal links. Update your own navigation and links to the final destination while preserving redirects for historical URLs.
Other Redirect Methods

Server-side redirects are usually the clearest choice for URL moves.

Method Google interpretation Recommendation
301 / 308 server redirect Permanent Preferred for permanent moves
302 / 307 server redirect Temporary Use for genuine temporary moves
Instant meta refresh Interpreted as permanent Fallback
Delayed meta refresh Interpreted as temporary Fallback
JavaScript redirect Can be processed after rendering Use when better methods are unavailable

JavaScript redirects add rendering dependency.

Google says JavaScript redirects may be missed if rendering fails, which is why server-side redirects are preferred when technically possible.

Redirects & XML Sitemaps

Your current sitemap should normally contain the URLs you want indexed—not redirect sources.

Current sitemap

  • Final canonical URLs
  • Current HTTPS URLs
  • Current preferred hostname
  • URLs returning intended indexable content

Review or remove

  • Old redirecting URLs
  • HTTP versions
  • Deprecated slugs
  • Old migration destinations
Redirects & AI Crawlers

Direct destination paths are easier to consume across different crawlers.

Do redirect chains matter only for Google?

No. Redirects are HTTP behavior that can affect browsers, search engines, AI crawlers, social crawlers and other automated clients. Different user agents may have different hop limits and implementation details, so eliminating unnecessary chains improves portability.

Do not design redirect architecture around the maximum number of hops one crawler can tolerate.

Design the shortest reliable path to the correct destination.

Common Redirect Chain Causes

Where do long chains usually come from?

01

Repeated URL Changes

A page receives a new slug every few years without updating the original redirect.

02

HTTP → HTTPS

Protocol enforcement creates a separate hop before another redirect rule runs.

03

www Changes

Hostname normalization happens separately from protocol or path redirects.

04

Trailing Slashes

One system adds a slash while another later changes the slug.

05

CMS Plugins

Several redirect systems each manage part of the same URL history.

06

CDN Rules

Edge-level redirects can stack on top of web-server and application redirects.

07

Domain Migrations

An old domain redirects through another historical domain before reaching the current one.

08

Deleted Content

An obsolete URL is redirected to another page that is later redirected again.

09

Case / Parameter Rules

URL normalization can introduce intermediate redirects before the intended content path is reached.

Fix Redirect Chains

How do you shorten a redirect chain?

01

Identify the final URL

Confirm the current canonical destination before editing any rule.

02

Map every historical source

List the old URLs that should now point directly to that destination.

03

Replace chained rules

Point old URLs directly to the final destination where technically and editorially appropriate.

04

Update internal links

Stop sending normal site navigation through the historical redirect.

05

Update sitemap URLs

List current preferred URLs rather than redirected source URLs.

06

Retest

Run the checker again to confirm the old URL now reaches the intended destination directly.

Common Redirect Mistakes

What should a redirect audit catch?

01

Multi-Hop Chains

Old URLs pass through several historical destinations before reaching the current page.

02

Redirect Loops

The path returns to a previous URL and never reaches content.

03

Wrong Final URL

The chain ends successfully but at an irrelevant page.

04

Temporary Code for Permanent Move

A permanent migration remains on a 302 or 307 implementation.

05

Broken Destination

The final URL returns an error.

06

Homepage Dumping

Large sets of unrelated old pages redirect to the homepage instead of relevant replacements.

07

Redirecting Internal Links

The site continues linking to obsolete URLs even though their final destinations are known.

08

Redirect URLs in Sitemaps

The XML sitemap continues submitting historical source URLs.

09

Conflicting Canonicals

The final page's canonical signal points somewhere inconsistent with the redirect destination.

Redirect Best Practices

How to keep redirect architecture clean over time.

Redirect directly

Point historical URLs to the current final destination rather than the next URL in an old migration sequence.

Use the right status

Use permanent redirects for permanent moves and temporary redirects for genuinely temporary routing.

Preserve relevance

Redirect to the closest useful replacement rather than a generic page merely because it returns 200.

Update internal links

Keep historical redirects for external traffic, not routine internal navigation.

Align canonical signals

Redirect destinations, canonicals and sitemap URLs should support the same preferred URL.

Retest after migrations

Recheck important legacy URLs whenever domains, slugs, CMS platforms or routing systems change.

Keep permanent redirects long enough

Preserve migration redirects while Google and users may still depend on old addresses.

Audit high-value backlinks

Prioritize old URLs receiving external links or significant referral traffic when cleaning complex redirect paths.

Know the Limitations

What the Redirect Chain Checker can — and cannot — tell you.

The checker can help you

  • Make a real server-side URL request
  • Trace redirect hops
  • Identify HTTP redirect codes
  • Detect long chains
  • Detect loops
  • Find the final URL
  • Check the final HTTP status
  • Compare an expected destination
  • Measure server-side elapsed time
  • Copy the final URL
  • Download CSV
  • Download an audit report

The checker cannot prove

  • Google has processed the redirect
  • Google selected the final URL as canonical
  • Ranking signals have fully transferred
  • Search rankings will remain unchanged
  • The destination satisfies search intent
  • The redirect exists in every geographic region
  • Every crawler follows the same hop limit
  • Client-side JavaScript redirect behavior
  • Complete sitewide redirect health from one URL

The tool proves the HTTP path it observed—not Google's final indexing decision.

Use Search Console, crawl data, canonicals and index evidence when you need to understand how a migration has been processed by Google.

Frequently Asked Questions

Redirect chains, 301s, 302s and SEO explained.

Direct answers to common questions about redirect hops, loops, migrations, PageRank, canonicals, crawl efficiency and internal links.

What is a redirect?

A redirect sends a request from one URL to another URL, telling users and crawlers that the content is available at a different address.

What is a redirect chain?

It is a sequence where one URL redirects to another redirecting URL before the final destination is reached.

What is a redirect loop?

A redirect loop occurs when the path repeatedly returns to a previous URL so no final destination can be reached.

Are redirect chains bad for SEO?

Redirects are normal, but long unnecessary chains add latency and make crawling less efficient. Google explicitly recommends redirecting to the final destination directly where possible.

How many redirect hops can Googlebot follow?

Google's current site-migration documentation says Googlebot can follow up to 10 redirect hops.

How many redirect hops should I use?

Prefer zero or one deliberate redirect. Google recommends keeping unavoidable chains low, ideally no more than three and fewer than five.

What is a 301 redirect?

HTTP 301 means a resource has moved permanently to another location.

What is a 308 redirect?

HTTP 308 is also a permanent redirect. Google lists both 301 and 308 as permanent server-side redirect types.

What is a 302 redirect?

HTTP 302 is a temporary redirect used when the original URL is expected to remain the primary address.

What is a 307 redirect?

HTTP 307 is another temporary redirect status.

Should I use 301 or 302 for a permanent page move?

Use a permanent server-side redirect such as 301 or 308 when the URL has genuinely moved permanently.

Do 301 redirects lose PageRank?

Google's current site-migration documentation says 301 and other permanent redirects do not cause a loss in PageRank.

Does that mean rankings can never change after a redirect?

No. Rankings can change during migrations because Google needs to recrawl and reprocess URLs and because other factors such as content, relevance and internal linking may also change.

Should internal links point through a redirect?

Usually not. Update your own internal links to point directly to the current final URL.

Should redirected URLs remain in my sitemap?

Your current sitemap should generally contain the preferred final URLs you want search engines to discover and index.

Can a redirect affect canonicalization?

Yes. Google lists redirects among the signals it uses when determining canonical URLs.

Should the final page canonicalize to itself?

For a normal preferred destination, a self-referencing canonical is often a useful consistency signal. The important point is that canonical signals should not contradict the redirect destination.

Can I redirect every deleted URL to the homepage?

No. Google warns against redirecting many unrelated old URLs to one irrelevant destination because this can confuse users and may be treated as a soft 404.

What should I do when there is no replacement page?

If there is no useful equivalent destination, allowing an appropriate 404 or 410 response may be more accurate than redirecting the URL somewhere irrelevant.

What is a soft 404?

It describes a situation where a URL behaves like missing or irrelevant content even though the server returns a successful response or redirects somewhere that does not genuinely replace the requested resource.

How long should I keep migration redirects?

Google currently recommends keeping them for as long as possible and generally for at least one year.

Can I keep permanent redirects forever?

Yes, when old URLs may continue receiving bookmarks, links or user traffic. Google specifically notes that indefinite redirects can make sense from the user's perspective.

Why should I update old backlinks if a redirect works?

Updating important external links can remove unnecessary requests and ensure users reach the current destination directly. Prioritize links that send significant traffic when outreach is practical.

Can HTTPS redirects create chains?

Yes. Separate HTTP-to-HTTPS, hostname and path rules can accidentally stack into several hops.

Can WordPress plugins create redirect chains?

Yes. Redirect plugins, SEO plugins, server rules, hosting redirects and CDN rules can all interact and produce chains or loops.

Can Cloudflare or another CDN create redirect chains?

Yes. Edge-level redirect rules can stack with origin-server and CMS redirects.

Are JavaScript redirects okay for Google?

Google can process JavaScript redirects, but recommends server-side redirects when possible because JavaScript redirects depend on successful rendering.

Does Google understand meta refresh redirects?

Yes. Google currently interprets instant meta refresh as permanent and delayed meta refresh as temporary, although server-side redirects are preferred when possible.

Why does final status matter?

A chain may successfully redirect through several URLs but still end at a 404, 500 or another unexpected response.

Why does expected final URL matter?

It confirms that the path reaches the destination you intended rather than merely reaching any successful page.

Can redirect chains slow users down?

Yes. Each hop requires another request before the final page can be retrieved.

Can redirect chains affect crawling?

Yes. Google specifically warns that long redirect chains have a negative effect on crawl efficiency.

Does the tool check live redirects?

Yes. The live AnswerEnginee checker performs real server-side HTTP requests rather than relying on pasted redirect data.

How many hops does the AnswerEnginee tool follow?

The current live checker follows up to eight redirect hops.

Can I test private or local network URLs?

No. The tool restricts checks to public HTTP and HTTPS destinations and blocks private or local-network targets for security.

Can this checker tell me whether Google indexed the final URL?

No. It checks the redirect path and HTTP responses. Use Search Console or separate index evidence when you need Google's indexing status.

Can a clean redirect guarantee rankings are preserved?

No. Correct redirects are important migration signals, but rankings depend on many additional content, technical and competitive factors.

Related Technical SEO Tools

Continue from redirect tracing to canonical, indexing and sitemap validation.

Google Indexability & Index Evidence Checker → Check whether the final destination is technically indexable and separate eligibility from actual Google index evidence. AI Citation URL & Canonical Auditor → Review canonical, preferred URL and redirect evidence when multiple URL variants are being cited or consolidated. Sitemap Freshness & AI Discovery Auditor → Check whether current sitemap URLs align with the destinations your redirect architecture now prefers.
Shorten the Path

A redirect should move the request forward. It should not send users and crawlers on a historical tour of your URL structure.

Use the Redirect Chain Checker to trace every HTTP hop, detect loops, distinguish permanent and temporary redirects, verify the final destination and identify chains that should be replaced with a cleaner direct path.

Scroll to Top