Account

What new tool do you want?

Web & SEO

Redirect & Canonical Checker

Trace every redirect a URL goes through — 301, 302, 307, 308 — with timing, then check the final page's canonical tag, meta refresh and robots directives.

How to use

  1. 1Enter a URL (try the http:// or non-www version).
  2. 2See each hop with its status code and time.
  3. 3Check the canonical and robots tags of the final page.

Frequently asked questions

301 or 302?

Use 301 (or 308) for permanent moves so search engines transfer ranking to the new URL; 302/307 are for temporary changes.

Why are redirect chains bad?

Each hop adds a round trip for users and wastes crawl budget. Point old URLs straight at the final destination.

What's a canonical tag?

It tells search engines which URL is the main version of a page when several URLs show the same content.

Why the status code of each hop matters more than just 'does it redirect'

A 301 tells search engines a move is permanent and to transfer ranking signals to the new URL, while a 302 or 307 signals a temporary change that shouldn't pass that same ranking weight — so a site migration accidentally implemented with 302s instead of 301s can genuinely lose search visibility at the old URLs without ever showing an error, since the redirect still works perfectly fine for human visitors. This tool reports the exact code at each hop specifically because 'it redirects' and 'it redirects with the right status code' are different outcomes with different SEO consequences.

Worked example: Redirect & Canonical Checker

Checking an old http:// URL that's been migrated to https:// might reveal a chain: http://example.com/page → 301 → https://example.com/page → 301 → https://www.example.com/page — two hops where one would do, since the http-to-https redirect and the non-www-to-www redirect could be combined into a single direct 301 straight to the final URL. Each extra hop adds a measurable round-trip delay (visible in the per-hop timing this tool reports) and wastes a fraction of a search engine's crawl budget on that URL, which is exactly the problem the FAQ flags as the reason redirect chains are worth fixing.

Why checking the canonical tag at the end of the chain matters as much as the chain itself

A clean, single-hop 301 redirect can still undermine itself if the final destination page's canonical tag points somewhere else entirely — conflicting signals like that (redirect says 'this is the real URL' while the canonical tag says 'no, that one is') confuse search engines about which URL should actually rank. Checking both the redirect chain and the landing page's canonical, meta refresh and robots directives together is what catches this kind of self-contradicting setup that checking the redirect alone would miss.

Meta refresh is a different mechanism from an HTTP redirect entirely

A meta refresh tag (<meta http-equiv="refresh" content="0;url=...">) lives inside the page's HTML and fires after the browser has already downloaded and started parsing that page, rather than at the HTTP response level before any content loads — which means a server can return a 200 OK status (telling a crawler the page loaded successfully) while a meta refresh quietly sends the visitor somewhere else a moment later. Search engines generally treat an immediate meta refresh similarly to a redirect, but a delayed one (several seconds, historically used for 'this page has moved, redirecting you in 5 seconds' notices) can be treated with more suspicion, since it was also a technique associated with older, low-quality redirect schemes.

A robots directive at the final URL can quietly undo a correct redirect

Even a technically perfect single-hop 301 pointing at the right destination accomplishes nothing for search visibility if that destination page itself carries a noindex robots meta tag or is blocked in robots.txt — the redirect successfully tells search engines to transfer ranking signal to a page that then declines to be indexed at all. This is a surprisingly common migration mistake: a staging or placeholder noindex tag gets left on the new production page, and the redirect chain can look flawless in every other respect while the end result is the page dropping out of search entirely.

Related tools

More: Web & SEO