Free redirect checker: see where your address really ends up.
Updated
This redirect checker follows an address to the page it finally lands on, then checks that page: its status, https, canonical, noindex and any meta refresh. It also tries the address's other three versions, http and https with and without www, to see whether all four end in one place.
One thing it doesn't do: list each hop or its 301 or 302 code. Our page fetch follows redirects to the end and reports only where it lands. Free, with no signup and no email.
- Free
- No signup
- Results in about 15 seconds
What the redirect checker tests
Where the address lands and how healthy that page is. The hops in between, and their codes, aren't listed.
Where it ends up
The final address after every redirect, with the status that page returns.
All four versions
http and https, with and without www, each followed to its end.
One address or several
Whether the four versions meet on one page or split your links.
https at the end
Whether every http version moves to https.
Canonical
Whether the final page names itself as canonical, or another address.
Indexable
Whether a noindex meta tag keeps the final page out of results.
Meta refresh
A redirect written into the page's HTML, with its delay and target.
From an old address to its final page in four steps.
- 01
Enter an address
Any page, old or new, with or without https.
- 02
We follow it
To the page it finally lands on.
- 03
We try its versions
http, https, with www and without.
- 04
You get the verdict
Where each ends, and how healthy that page is.
Why redirects decide which page gets the links and rankings
A permanent redirect, a 301 or 308, tells Google the new address should replace the old one in results. A temporary one, a 302 or 307, keeps the old address in play. Google follows up to 10 hops, but every hop slows the visit, and a broken end wastes all of them.
Most redirect trouble isn't the redirect itself; it's where it lands. A page that errors, an http page, a canonical that points somewhere else or a noindex left over from staging. Those are what this check looks at.
For SEO, links and signals pile up on the final page only if every version ends there. For AEO and GEO, AI Overviews and AI assistants cite pages that can be indexed, so an address that ends on a noindex or error page drops out of answers too.
How to read your redirect report
The top shows the address you entered and the page it lands on. "No redirect" means the address answered on its own, which is normal for a live page.
Each check is about the final page. If all four versions end on one https page that answers 200, is indexable and names itself as canonical, the redirect does its job. We don't show the hops between, or their codes: a site crawler flags chains, and your browser's network panel shows each step.
A 403 at the end usually means the site turned our fetch away, and a 5xx that its server failed; neither is the redirect's fault. Open the address in a browser, or run the check again, before you change anything.
| RESULT | WHAT IT MEANS | WHAT TO DO |
|---|---|---|
| Lands on 200 | The final page works | Nothing, if it's the page you meant |
| Lands on 404 or 410 | The redirect points at a dead page | Point it at the closest live page |
| Lands on http | Visitors end on an insecure page | Redirect http to https |
| Versions split | Links and signals spread over two pages | Redirect three versions to the fourth |
| Canonical elsewhere | Google may index another address | Point the canonical at the final page |
How to fix redirect problems
Split versions:
choose https with or without www, and redirect the other three to it with a 301.
Ends on http:
install a certificate if the site has none, then send every http address to its https twin.
A dead end:
redirect to the closest live page, not the homepage. Google may treat a redirect to an unrelated page as a soft 404.
Canonical elsewhere or noindex:
point the final page's canonical at its own address, and remove a noindex left over from staging.
Send every http and www visit to one https address, on Apache (.htaccess):
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} ^www\. [NC]
RewriteRule ^ https://example.com%{REQUEST_URI} [L,R=301]When to check a redirect.
- After a migration: spot check old addresses to see that each lands on its new page, not the homepage or a 404.
- After moving to https: confirm every http version ends on https.
- When a page drops from Google: see whether it now redirects or carries noindex.
- Before you buy a domain or a link: see where it really sends visitors today.
- Short links and campaign URLs: check where a link in an email or an ad lands before it goes out.
Find every redirect chain, not just this one.
Zivooo's Site Health crawls your whole site and flags redirect chains, http pages that don't move to https, canonicals that point at a redirect and internal links that still use old addresses. Switch it on monthly. $10 a domain a month after 7 days free, no card.
- Redirect chains found across your site
- Internal links that go through a redirect
- Fixes written out for each issue
- Whether AI assistants name you
This redirect checker vs hop tracers and crawlers
Hop tracers show each step of a chain with its code, which is what you want when you debug a single redirect rule. This checker doesn't, and we'd rather say so; your browser's developer tools show the same steps for free. What this check adds is the other half: all four versions of the address followed to their end, and the final page checked for status, https, canonical and noindex. For a whole site, a crawler like Site Health finds chains on every page.
Redirects, answered.
How do I check where a URL redirects?
Enter it above. We follow it to the end and show the final address with its status, plus where the http, https and www versions end up.
Does this show every hop and its 301 or 302 code?
No. Our page fetch follows redirects to the end and reports only where it lands. To see each hop, open your browser's developer tools, go to the Network tab and load the address.
What's the difference between a 301 and a 302 redirect?
A 301 is permanent: Google moves the old address's place in results to the new one. A 302 is temporary, so the old address stays in play. A 308 works like a 301, and a 307 like a 302.
How many redirects will Google follow?
Google's crawlers follow up to 10 hops by default. Fewer is better: each hop adds a delay, and a long chain is easy to break.
Do redirects hurt SEO?
A single permanent redirect to the right page passes its signals on. Problems come from chains, redirects to unrelated pages, and versions of an address that end in different places.
Should http and www versions redirect to one address?
Yes. Pick one version, usually https with or without www, and redirect the rest to it with a 301, so links and signals count toward one page.
Is a meta refresh a redirect?
Yes, one written into the page instead of sent by the server. Google treats an instant one as permanent and a delayed one as temporary, but a server redirect is clearer for every crawler.
Check what the final page says.
- AI READINESS & TECHNICALSEOCanonical Tag CheckerSee which URL a page asks Google to index, and if that page works.Check my canonical
- AI READINESS & TECHNICALSEOAEONoindex CheckerSee if a page tells Google, Bing or AI search to stay away.Check for noindex
- AI READINESS & TECHNICALSEOSitemap CheckerValidate your XML sitemap and open a sample of the pages it lists.Check my sitemap
- AI READINESS & TECHNICALSEOAEOAI SEO CheckerAudit a page for Google first, then for AI search.Run my AI SEO audit
Send every visit to one good page.
Your keys, your costs, $10 a domain. 7 days free, no card.