The redirect checker follows a URL one hop at a time and shows the HTTP status code of every step until it reaches the final page. It tells you whether a redirect is permanent (301, 308) or temporary (302, 307), how long the chain is, and whether the final page works or returns an error.
Key takeaways
- One direct 301 from the old URL to the final URL is the ideal redirect.
- Chains of two or more hops waste crawl time and slow users down; fix them at the source.
- Use 301 for permanent moves so search engines transfer the old page's signals to the new one.
How to check a URL
- Paste the URL you want to test, for example an old page, an http:// version or a short link.
- Press Check URL.
- Read the summary, then the list of hops: each line shows the status code and the address at that step.
The tool follows up to six hops and stops if it detects a longer chain.
Status codes you will see
| Code | Meaning | SEO impact |
|---|---|---|
| 200 | OK | Page works |
| 301 / 308 | Moved permanently | Signals move to the new URL |
| 302 / 307 | Moved temporarily | Old URL may stay indexed |
| 404 | Not found | Page drops from the index |
| 410 | Gone | Removed faster than 404 |
| 5xx | Server error | Crawling slows; urgent fix |
Redirects and link equity
Backlinks are votes, and a redirect is how you keep those votes when a URL changes. A permanent redirect to the closest matching page passes most of the value, often called link juice. Redirecting many old pages to the home page does not: Google treats irrelevant redirects like soft 404s. Map every old URL to the most relevant new one during a migration, then check a sample of them here. Our technical SEO team runs this mapping on every site migration we manage.
Fixing chains and loops
Chains build up over years: http to https, then non-www to www, then an old slug to a new one. Each hop adds delay for users, and crawlers may stop following after several hops. Update the first rule so it points straight to the final URL, and update internal links to point to the final URL directly, so no redirect is needed at all. A loop, where A goes to B and B back to A, makes the page unreachable and must be fixed immediately in your redirect plugin or server rules.
When to merge pages with a redirect
Redirects are also a content tool. If two articles target the same query and split traffic, a classic case of keyword cannibalization, merge the best parts into one page and 301 the weaker URL to it. The same applies to thin pages that will never rank on their own. Combining them builds one stronger page with all the backlinks and history. Check the merged page afterwards with the on-page SEO checker and the keyword density checker.
A post-migration checklist
- Test the http, https, www and non-www versions of your home page; all should end on one URL in a single hop.
- Test your top 20 pages by traffic and backlinks from the old structure.
- Check that redirected URLs are removed from the sitemap and from hreflang tags.
- Watch Search Console for 404 spikes in the weeks after launch.
- Keep redirects in place for at least a year; for pages with strong backlinks, keep them permanently.
Server rules or a plugin?
On WordPress, a redirect plugin or the redirections module in Rank Math is the easiest way to manage individual URLs, and it logs 404 errors so you can find new broken links. Site-wide rules, such as forcing https or removing www, belong in the server configuration or your host panel, because they run before WordPress loads and are faster. Whichever you choose, keep one place of truth; rules split across a plugin, .htaccess and a CDN are the usual cause of chains and loops.
Need more than a free tool?
Our team runs full audits, fixes and growth plans for sites in 10 languages.Frequently asked questions
What is the difference between 301 and 302?
Do redirects lose SEO value?
Why does the tool show code 0?
Should I redirect deleted pages?
Can it check JavaScript or meta refresh redirects?
How we built this tool: the checks and thresholds follow Google Search Central documentation, Schema.org and the IETF/W3C standards, and we tune them against what we see on client sites every month. We keep no record of the text or URLs you enter: generators and calculators run in your browser, while checkers fetch the page through our server and cache the result for a few minutes only to speed up repeat checks. Questions or a bug? Tell us.