A URL redirect sends visitors and search engines from one address to another. This guide covers how to check if a URL redirects, how to test 301 vs 302 redirects, how to trace redirect chains, and how to fix the most common redirect problems.
A URL redirect is an instruction that sends anyone requesting one web address to a different one. When a browser requests a URL that has a redirect, the server responds with an HTTP status code in the 3xx range — most commonly 301 or 302 — along with the destination URL in aLocationheader. The browser then loads the destination URL automatically.
Redirects serve several purposes: preserving traffic and rankings when pages move, consolidating duplicate content, sending users from HTTP to HTTPS, and redirecting old domains to new ones after a rebrand. Each redirect type sends a different signal to search engines about whether the move is permanent or temporary.
The fastest way to check if a URL redirects is to use a redirect checker tool:
If the URL returns a 200 OK directly, it does not redirect. If it returns 301, 302, 307, or 308, it redirects to the URL shown in the destination column.
You can also check redirects using the browser developer tools: open DevTools (F12), go to the Network tab, enable Preserve log, and load the URL. Every hop in the redirect chain appears as a separate network request with its status code.
The status code tells you whether a redirect is permanent or temporary:
The most common mistake: using 302 when you should use 301. This happens when a developer sets up a temporary redirect and forgets to change it. Search engines will not pass ranking signals through a 302, so any backlinks pointing to the old URL are not helping your new URL rank. Check your redirects and switch any permanent ones from 302 to 301.
Check your redirect type: Paste any URL into the redirect checker and the status code column shows you exactly whether it is a 301, 302, 307, or 308.
A redirect chain occurs when a URL redirects to a second URL, which then redirects to a third, and so on. For example:
http://example.com → https://example.com → https://www.example.com → https://www.example.com/home
Each hop in this chain adds latency — typically 50 to 300 milliseconds per hop. Four hops means your page starts loading a full second later than it could. It also dilutes link equity at each step.
How to find and fix redirect chains:
Google will follow up to 10 redirect hops, but chains longer than 3 hops can cause crawling issues and noticeable page speed problems. Keep redirect chains to a single hop wherever possible.
When you have hundreds or thousands of URLs to check — after a site migration, domain consolidation, or CMS change — checking them one at a time is not practical. Use a bulk redirect checker:
After a site migration: export all your old URLs, paste them into the bulk checker, and confirm every one resolves with a 301 to the correct destination. Any returning 404 means a redirect is missing.
Some servers serve different redirects based on who is making the request. A page might redirect desktop users to one URL, mobile users to another, and Googlebot to a third. This practice — called cloaking when done deceptively — can cause significant SEO problems if Googlebot sees different content than real users.
To check what a specific bot or browser sees:
If Googlebot sees a different redirect destination than a regular browser, that is a red flag. Google's quality guidelines require that the experience for Googlebot matches the experience for real users.
URL A redirects to URL B, and URL B redirects back to URL A. The browser gives up after a set number of attempts and shows an error like "Too many redirects" or ERR_TOO_MANY_REDIRECTS.
Fix: Check your server configuration, .htaccess file, or CMS redirect rules for conflicting entries. Use the redirect checker — a loop shows as repeated URLs in the chain view before the tool stops.
The most common redirect mistake. A developer sets up a redirect quickly using 302 and never changes it. Search engines keep the original URL indexed and do not pass ranking signals.
Fix: Change the redirect type to 301 in your server config, .htaccess, or CMS. In Apache: Redirect 301 /old-page https://example.com/new-page. In Nginx: return 301 /new-page;
The URL goes through both HTTP and HTTPS hops before reaching the final destination, for example: http → http/www → https/www → final page. The HTTP hops are unnecessary and add latency.
Fix: Update your redirect rules so HTTP always goes directly to the HTTPS final destination in a single hop. Enable HSTS so browsers skip HTTP entirely for returning visitors.
When a page is deleted or moved, redirecting to the homepage rather than the closest equivalent page is a "soft 404" in Google's eyes. Google treats it as a 404 and does not pass ranking signals.
Fix: Map each deleted or moved URL to its closest equivalent page and redirect there. Use the bulk redirect checker to verify every redirect lands on a relevant destination, not the homepage.
For quick checks without a tool, Chrome DevTools shows redirect chains in the Network panel:
Location header that shows the destinationThe limitation of DevTools is that it only shows how your browser sees the redirect — not how Googlebot or other bots see it. For bot-specific redirect checking, use the user agent selector in the redirect checker.
Go to RedirectChecker.com, paste your URL, and click Check Redirects. It is completely free with no signup required. You see the full redirect chain, every status code, latency on each hop, and the final destination URL.
No. A correctly configured 301 redirect does not hurt SEO. Google has confirmed that 301 redirects pass full PageRank to the destination URL. What hurts SEO is redirect chains (multiple hops), using 302 when you should use 301, and redirecting to irrelevant pages.
Googlebot will follow a new redirect the next time it crawls the original URL. For important pages, this typically happens within a few days to a few weeks depending on your site's crawl frequency. You can speed this up by submitting the original URL in Google Search Console and requesting indexing.
Google will follow up to 10 redirect hops per URL before stopping. In practice, chains longer than 3 hops cause crawling issues and page speed problems. Keep chains to a single hop.
Use the bulk redirect checker. Paste up to 15,000 URLs — one per line — and the tool checks them all in parallel. Filter by status code, expand any row to see the full chain, and export to CSV.
Check any URL redirect right now
Free, no signup. Paste a URL and see every redirect hop, status code, and final destination.