TapCub is live — analytics, insights and live chat, free on one platform

Free tool Redirect checker: follow every hop of a URL

Enter an address and see the whole path to the final page: each hop with its status code, where it points and how long it took. The checker explains whether each redirect is permanent or temporary, flags chains, loops, https-to-http downgrades and redirects hidden in the HTML, and can compare what Chrome, Googlebot and AI crawlers are sent.

  • Every hop, up to 5
  • Compare user-agents
  • Sent only when you click

Trace the redirects of a URL

Enter the address you want to test, usually an old URL, an http address or a campaign link. Until you click Check, the result is a sample for http://apple.com.

Checker
What is sent, and to whom. Nothing is requested when the page opens: the result below is a dated sample. When you click Check, the address goes to TapCub’s checking service check.tapcub.com, which fetches it from Cloudflare’s network with the user-agent shown and a From: tools@tapcub.com header, then returns the status codes, response headers and at most 512 KB of the page. A single check uses one request; comparing user-agents uses three or four. The service records only the host name, status and timing for rate limiting, not the path, query or page content, and stores no results. Limits: 10 requests a minute and 200 a day per IP address.

Include the scheme to test it: http:// and https:// often redirect differently.

Some sites send crawlers or phones somewhere else.

Sample result for http://apple.com/, fetched on 2026-11-17. Click Check to test it live, or enter your own address.

Path

http://apple.com/ → https://www.apple.com/ (200) · 7,036 ms

Every address in order, with the final status and the total server time.

Checks

  • OKOne permanent redirect straight to the final page. That is the ideal setup.

Hop by hop

Permanent redirects pass the strongest signal to the target; temporary ones keep the original as canonical.

#URLStatusTypeRedirects toTime
1http://apple.com/301301 Moved permanentlyhttps://www.apple.com/4,326 ms
2https://www.apple.com/200Final page—2,710 ms
The checks, tables and explanations are worked out in your browser from what the service returns. Nothing you check is saved to an account or shared.

Share these inputs: the values go after the # in the link, so they never reach a server.

Version v1.0Updated Update history

Read the result

What the status codes mean for SEO

The browser ends up on the same page either way. Search engines care which code you used.

301 and 308: permanent

The page has moved for good. Google takes a permanent redirect as a strong signal that the target should be the canonical URL, and passes the old URL’s signals to it. 308 is the same but keeps the request method, which matters for forms and APIs, not for pages.

302, 303 and 307: temporary

The original URL stays canonical. Right for short campaigns, maintenance or geo and language routing; wrong for a site move, where the old URL may keep appearing in results.

Chains and loops

Every extra hop is another round trip for the visitor. Googlebot follows up to 10 hops, other crawlers fewer. A loop never resolves: the browser shows “too many redirects”.

Redirects in the HTML

A meta refresh or a JavaScript location change is a redirect too, but only for clients that read the HTML or run the script. Use them only when you cannot change the server.

Test the exact URLs people and links use: the http and https versions, with and without www, old paths, tracking links. The www and https checker tests the four host variants in one go.

How to use it

Three steps

Nothing is requested until you click Check.

  1. 1

    Enter the starting URL

    Paste the old or short address, including http:// or https:// if you want to test a specific one.

  2. 2

    Choose who follows it

    One user-agent for a quick trace, or compare Chrome with search or AI crawlers to see whether they are routed differently.

  3. 3

    Fix what is flagged

    Replace 302s with 301s for permanent moves, collapse chains into one hop and update internal links to point at the final URL.

Method

How the checker follows redirects

Requests go from Cloudflare’s network through check.tapcub.com, one hop at a time:

  • A GET request with the chosen user-agent; any 3xx with a Location header is followed, the target address is checked again before the next request
  • At most 5 hops; going back to an address already in the chain is reported as a loop
  • The final page’s HTML (first 512 KB) is scanned for <meta http-equiv="refresh"> and inline scripts that assign location
  • Classification follows RFC 9110 §15.4; SEO meaning follows Google Search Central’s redirect documentation
Redirect status codes (RFC 9110)
CodePermanent?Method kept?Use it for
301YesNot guaranteed (POST may become GET)Moved pages, http → https, www ↔ non-www
308YesYesSame as 301 when the method matters
302NoNot guaranteedShort-term moves, A/B tests
303NoBecomes GETAfter a form post
307NoYesTemporary moves where the method matters
Meta refresh, 0 sTreated as permanent by Google—Only when the server cannot redirect
Worked example

http://apple.com in one hop

The sample on this page was fetched on 2026-11-17 as Chrome on desktop.

Redirect path for http://apple.com
#URLStatusReading
1http://apple.com/301 → https://www.apple.com/Permanent; switches to https and adds www in a single hop
2https://www.apple.com/200Final page, sends HSTS so later visits skip the http step

Compare with a chain such as http://example.com → https://example.com → https://www.example.com: two hops where one would do. Fix it by making the very first redirect point to the final https://www address.

Common mistakes

Redirect setups that cost traffic

All of them still “work” in a browser, which is why they survive for years.

302 for a permanent move

Many CMS plugins and server panels default to 302. After a migration, check the codes, not just that the page loads.

Chains after each redesign

Old → older → current. Every migration adds a hop unless you update the earlier rules to point at the final URL.

Internal links to redirects

Menus and articles that link to the old URL make every visitor and crawler take the detour. Link to the final address.

Redirecting everything to home

Sending all removed pages to the homepage is treated like a soft 404. Redirect to the closest equivalent, or return 404 / 410.

FAQ

Redirect checker questions

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

How do I check where a URL redirects?

Enter it above and click Check. You get every hop with its status code. On the command line, curl -sIL http://example.com prints the headers of each hop; the checker adds the SEO reading and can switch user-agents.

What is the difference between a 301 and a 302 redirect?

A 301 says the page moved permanently, so search engines index the new URL and move signals to it. A 302 says the move is temporary, so the old URL usually stays in the index. Both take the visitor to the same place.

Do redirects lose SEO value?

Google’s Gary Illyes said in 2016 that 30x redirects no longer lose PageRank. The risks are elsewhere: a temporary code where you meant permanent, long chains, and redirects to unrelated pages, which are treated as soft 404s.

How many redirects are too many?

Aim for one. Googlebot follows up to 10 hops before giving up, but each hop adds a round trip for visitors, and this checker stops at 5.

Why does Googlebot get a different redirect than my browser?

Some sites redirect by user-agent (mobile sites, bot rules), by country or by cookie. Use compare mode to see it. Note that our requests come from Cloudflare’s network, not Google’s IP ranges, so sites that verify crawlers by IP may treat us as a fake Googlebot.

Does it detect meta refresh and JavaScript redirects?

Yes, on the final page: it scans the HTML for a meta refresh tag and inline scripts that set location. Redirects added by external scripts or after user interaction are not detected.

Can I check many URLs at once?

This tool checks one URL at a time. For lists, use the bulk HTTP status checker.

Changelog

Update history

New features, fixes and data refreshes for this tool, newest first.

  1. · v1.0

    LaunchedFirst release.

Data this tool relies on

  • Sample fetches (github.com, apple.com, wikipedia.org, example.com, bbc.com) — checked 2026-11-17, reviewed every 6 months (next review by 2027-05-17)

Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics