Skip to content

Redirect Checker

Enter a URL to see every redirect between the address you typed and the page that finally loads: status code, Location header and response time for each hop. Test as Googlebot or a mobile browser, or check 20 URLs at once.

What the redirect checker shows

For each URL, the redirect checker requests the address without following redirects automatically, records the response, then requests the URL in theLocation header. It repeats until it gets a non-redirect response. For every hop you see:

  • Status code — 301, 302, 303, 307, 308, or the final 200/4xx/5xx.
  • Location — where that hop sends the request, resolved to an absolute URL.
  • Response headers — useful for spotting which layer (CDN, server, app) issued the redirect. For the full set of headers on each hop, including security and caching headers, use the HTTP Header Checker.
  • Verdict — direct, single redirect, redirect chain, loop, or error.

The user-agent selector matters more than it looks. Some sites redirect mobile visitors to an m-dot domain, redirect by country, or treat bots differently. Checking as Googlebot Smartphone shows what Google's mobile-first crawler actually receives.

Redirect types and how search engines treat them

TypeMeaningWhat Google does
301 Moved PermanentlyThe page has moved for goodStrong signal to index the target URL. Use for migrations and changed URLs.
308 Permanent RedirectPermanent; keeps the request method (POST stays POST)Treated the same as 301.
302 Found / 307 TemporaryTemporary moveWeak signal; Google may keep the original URL in results. Fine for genuinely temporary cases like a sale page.
Meta refreshHTML tag, not an HTTP redirectInstant refresh is treated like a permanent redirect, delayed refresh like a temporary one. Shows as 200 in this tool.
JavaScript redirectRuns after the page loadsOnly seen if Google renders the page. Use a server redirect when you can.

Redirect chains: where they come from and how to fix them

A chain is any path with more than one hop. Most chains are not planned — they build up as rules are added over the years. The classic example:

http://example.com/blog
  → 301 https://example.com/blog       (force HTTPS)
  → 301 https://www.example.com/blog   (force www)
  → 301 https://www.example.com/blog/  (add trailing slash)
  → 200

Three hops for one page. Googlebot will follow it, but each hop is another round trip for visitors on slow mobile connections, and chains get longer every time the site moves again. The fix is to send every variant straight to the final URL in one rule. On Apache:

RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

And on Nginx, a dedicated server block for the variants:

server {
  listen 80;
  server_name example.com www.example.com;
  return 301 https://www.example.com$request_uri;
}

Then update internal links, canonical tags and your XML sitemap to the final URL, so neither visitors nor crawlers hit the redirect in the first place.

Checking redirects after a site migration

  1. Export your old URLs from the old sitemap, analytics, or Search Console's Pages report.
  2. Run them in bulk, 20 at a time, with the Googlebot Smartphone user-agent.
  3. Confirm each one is a single 301 ending in a 200. Anything ending in 404 needs a redirect rule; anything with two or more hops needs its rule pointed at the final URL.
  4. Check the destinations make sense. Redirecting many old pages to the homepage is usually treated as a soft 404 — send each one to the closest matching page instead.
  5. Make sure the old URLs are crawlable. If robots.txt blocks them, Google cannot see the redirect and may keep the old URLs indexed.

Limits of this tool

  • It follows HTTP redirects only. Meta refresh and JavaScript redirects show as a 200 response.
  • It stops after 10 hops, the same limit Googlebot uses.
  • Each request times out after 5 seconds.
  • Private and internal network addresses (localhost, 10.x, 192.168.x) are blocked.
  • Bulk mode accepts 20 URLs per run.

Frequently asked questions

How do I check if a URL redirects?

Paste the URL into the checker and click Trace Redirects. If the first response is a 3xx status with a Location header, the URL redirects, and the tool follows each hop until it reaches a page that returns 200, an error, or the 10-hop limit.

How many redirects will Googlebot follow?

Google documents that Googlebot follows up to 10 redirect hops. If it still has not reached content after that, Search Console reports a redirect error for the URL. In practice you should aim for one hop: every extra hop adds a network round trip for visitors and another fetch for crawlers.

Do 301 redirects lose PageRank?

Google has stated that 3xx redirects do not lose PageRank. The practical difference between redirect types is which URL Google indexes: a 301 or 308 is a strong signal that the target should be indexed, while a 302 or 307 is a weak signal, so Google may keep showing the original URL.

What causes ERR_TOO_MANY_REDIRECTS?

Two rules sending a request back and forth. Common causes are a CDN set to connect to your server over HTTP while the server forces HTTPS (for example Cloudflare's Flexible SSL mode), conflicting www and non-www rules, and a CMS site URL that disagrees with the server's redirect rule. The checker marks the loop and shows which URLs repeat.

Why does a URL redirect in my browser but show 200 here?

The redirect is probably a meta refresh tag or JavaScript, not an HTTP redirect. This checker follows HTTP Location headers only. Search engines can process meta refresh and JavaScript redirects, but a server-side 301 is faster and more reliable.

Can I check redirects for many URLs at once?

Yes. Switch to Bulk mode and paste up to 20 URLs, one per line. Each URL is traced separately with the user-agent you choose, and results can be copied as a table.

After the redirects are clean, confirm the final URL is the one you want indexed with the Canonical Tag Checker and the Page Indexability Checker.

Related Tools

  • HTTP Header Checker — View raw HTTP response headers for every redirect hop and check security headers, caching, compression, HTTP version, CDN and X-Robots-Tag.
  • Canonical Tag Checker — Analyze canonical tags to identify missing, conflicting, invalid, cross-domain or improperly configured canonical URLs that may affect indexing and duplicate content.
  • Meta Tag Checker — Check a page's title, meta description, robots directives, canonical, viewport and hreflang tags, with a Google result preview and a fix for each issue.
  • HTML Minifier — Compress HTML, inline CSS and JavaScript to cut file size and speed up your pages, or beautify minified code back to readable form.
  • Keyword Density Checker — Analyze word frequency and keyword density for any article or URL, review 1–4 word phrases, and catch keyword stuffing.
  • Robots.txt Tester & Generator — Test URLs against a live or pasted robots.