Skip to content
Free tool · Technical SEO

Redirect Checker

Trace every redirect a URL makes: the status code, where it points, and how long each hop takes.

No sign-up. We read the live page for you. Nothing is stored.

For example:

Start with http:// to see whether it redirects to https://. We follow up to 10 hops.

In the output

What you get

  • Every hop, in order, with its status code
  • Where each redirect points
  • Whether http:// reaches https://
  • Loops, dead ends and long chains flagged
  • Every response between the URL you enter and the page it ends on, with its status code and the Location header it sent.
  • Whether each redirect is permanent (301, 308) or temporary (302, 303, 307), which is how search engines decide whether to move the old URL’s signals.
  • Whether http:// redirects to https://, and whether any hop passes through an unencrypted URL on the way.
  • Loops, broken redirects and chains longer than ten hops, which stop crawlers before they reach a page.
Three steps

How to use the Redirect Checker

1

Enter the URL to test

Start with http:// or the bare domain to test the redirects people actually hit. Old links and typed addresses rarely use your final URL.

2

Read the chain top to bottom

Each hop shows its status and where it points. The last row is the page a visitor lands on.

3

Collapse it to one hop

Point the first redirect straight at the final URL, and update internal links so they skip redirects entirely.

Why it matters

Why redirect chains are worth checking

Each hop costs a round trip.

A visitor waits for every redirect before the page starts loading. On a slow connection, three hops add a noticeable delay to the first view.

Temporary says the move is not final.

A 302 or 307 tells search engines the old URL will come back, so they may keep showing it. A permanent move should be a 301 or 308.

Chains grow without anyone deciding.

Every migration adds a hop: http to https, bare domain to www, old path to new. Nobody removes the earlier ones, so the chain lengthens with each change.

Crawlers stop following.

Googlebot follows up to ten redirect hops and then gives up. Well before that, each hop spends crawl attention that could have gone to a real page.

After you run it

What to do with the result

A redirect chain is invisible from inside the site: every page loads, so nothing looks broken. The cost shows up as slower first visits and search engines crawling redirects instead of pages. Fixing one URL takes minutes; the harder job is finding every internal link that still points at an old address. Site Audit crawls the site and flags redirect chains and links to redirected URLs, so you can fix them at the source.

Site Audit

Frequently asked questions

A 301 says the page has moved permanently, so search engines move the old URL’s signals to the new one and show the new URL in results. A 302 says the move is temporary, so they may keep showing the old URL. 308 and 307 are the same pair with one difference: the browser must repeat the original request method, which matters for forms and APIs rather than ordinary pages.

See where you actually stand.

A free tool checks one thing once. Veritas watches all of it, continuously, across every engine that decides whether you get cited.

GOOGLE · CHATGPT · PERPLEXITY · GEMINI · AI OVERVIEWS