Step-by-Step Guide
How to Check Redirects
Trace redirect paths, detect chains and loops, and verify that your 301/302 redirects are working correctly for SEO.
Step-by-Step Instructions
Open the Redirect Checker
Navigate to SerpNap's Redirect Checker. The tool traces the full redirect path from the initial URL to the final destination.
Enter the URL to check
Paste the URL you want to trace. This can be an old URL you've redirected, a shortened link, or any URL you suspect has redirects in place.
Run the redirect trace
Click check and the tool follows every redirect hop, recording each URL and its HTTP status code (301, 302, 307, etc.) along the way.
Review the redirect chain
The results show each step in the redirect path. A direct redirect (one hop) is ideal. Chains of 2+ hops slow page load and dilute link equity.
Identify issues
Look for: redirect chains (more than one hop), redirect loops (URL redirecting back to itself), 302 temporary redirects that should be 301 permanent, and redirects landing on 404 pages.
Fix redirect issues
Shorten chains by pointing the original URL directly to the final destination. Convert 302s to 301s for permanent moves. Remove loops. Update internal links to point to the final URL, bypassing redirects entirely.
Ready to Check Redirects?
Use SerpNap's Redirect Checker — free, instant, no signup required.
Open Redirect CheckerWhy It Matters
Redirect chains slow down page loading (each hop adds latency), dilute PageRank (link equity), and waste crawl budget. Google follows up to 10 redirects but recommends keeping chains as short as possible. A single redirect from the old URL to the final URL preserves the most SEO value and provides the fastest user experience.
Pro Tips
- After a site migration, check all your old URLs to ensure they redirect to the correct new pages — not to the homepage or a 404.
- Use 301 (permanent) redirects for SEO. 302 (temporary) redirects do not pass full link equity to the destination URL.
- Update all internal links to point to final URLs, not redirected ones. Even a 301 redirect adds a small amount of latency.
- Check your redirects from both HTTP and HTTPS versions of your URLs — misconfigured HTTPS redirects are a common issue.
- Monitor redirect chains quarterly, as CMS updates and plugin changes can introduce unexpected redirects.
Frequently Asked Questions
What is a redirect chain?
A redirect chain occurs when a URL redirects to another URL, which then redirects to yet another URL (A -> B -> C). Each hop adds latency and can dilute link equity. Ideally, redirects should go directly from the source to the final destination (A -> C).
What is the difference between a 301 and 302 redirect?
A 301 is a permanent redirect — it tells search engines the page has moved permanently and to transfer ranking signals to the new URL. A 302 is temporary — search engines keep the original URL indexed. Use 301 for permanent moves and 302 only for genuinely temporary situations.
How many redirects is too many?
Google follows up to 10 redirect hops, but best practice is one hop or none. Each additional redirect adds latency (typically 50-100ms per hop) and can reduce the link equity passed to the final URL.
Do redirects hurt SEO?
A single, properly implemented 301 redirect preserves most SEO value. However, redirect chains, loops, and 302s used incorrectly can hurt rankings by diluting link equity, slowing page load, and wasting crawl budget.
Related Resources