- Home
- Technical and performance
- Redirect Checker
Redirect Checker
See every hop between the address you type and the page that finally loads.
Each hop is requested individually and re-validated rather than followed automatically, so the report shows the real path rather than a summary. Redirects to private network addresses are refused as a safety measure. No usage limit.
What this tool is for
Between the address someone types and the page that appears, there is often more than one step. Each step is a full round trip to the server before a single pixel renders. Users feel it as slowness; crawlers spend budget on it; nobody sees it, because browsers hide the whole sequence.
Chains grow by accident. A rule forcing HTTPS, added in 2018. Another forcing www, added by someone else in 2021. A third normalising trailing slashes. Each one is reasonable alone; together they produce three hops where one would do — and occasionally a loop that makes the page unreachable.
This tool walks the chain one hop at a time and shows each step with its status code. It is the fastest way to answer the two questions that matter: how many hops, and does the last one land somewhere relevant.
How to read your results
The number of hops is the headline figure. One is expected. Three or more means separate rules are stacking, and they can nearly always be merged into a single rule that handles protocol and hostname together.
The status code of each hop tells you what was intended. 301 and 308 are permanent and pass signals. 302 and 307 are temporary and do not. A permanent move served as 302 keeps the old address as the canonical one — the opposite of the intent.
The final destination decides whether the redirect is worth anything. A discontinued product redirected to a closely related product retains its value. The same product redirected to the homepage is treated as a soft 404 and loses everything.
Alternating hostnames in the chain — www, then bare, then www again — always indicate contradictory rules. This pattern is a bug even when it eventually resolves, and it becomes a loop the moment one rule is edited.
The most common mistakes
Redirecting everything to the homepage during a migration. It looks tidy and it destroys the migration. Every redirected page is judged individually; a thousand pages pointing at the homepage is a thousand soft 404s. Map old to new page by page, and accept a 410 for what genuinely no longer exists.
Stacking rules instead of combining them. Protocol and hostname can be handled in a single rule. Two separate rules produce two hops on every single request, forever, for every visitor.
Using 302 for a permanent move. It is the default in several frameworks and content management systems, which is why it happens so often. The consequence is that signals stay with an address you have abandoned.
Removing redirects during a cleanup. An old redirect looks like clutter in a configuration file. It is usually the only thing keeping an external link alive. Deleting it converts that link into a 404 and discards its value permanently.
Testing only from your browser. Browsers cache 301s aggressively — once seen, the redirect is not requested again, so a fix appears to work when it has not deployed. A server-side check bypasses that cache entirely.
Related tools
- Security Headers Checker Audit the five HTTP headers that protect your visitors
- SSL Certificate Checker Validity, chain of trust and expiry date of a certificate
- Googlebot Simulator See a page exactly as a search engine crawler sees it
- Meta Tags Analyzer Title, description, Open Graph and indexing directives of a page
Frequently asked questions
How many redirects are too many?
One is normal. Two is tolerable. Three or more is a defect worth fixing. Each hop adds a full round trip before anything renders, and Googlebot stops following after roughly five. The frequent case is a chain nobody designed: HTTP to HTTPS, then bare domain to www, then trailing slash — three hops that should be one rule.
301 or 302?
301 for anything permanent, which is almost always what you mean. It passes ranking signals and browsers cache it. 302 is for genuinely temporary situations — maintenance, an A/B test, seasonal routing. Using 302 for a permanent move is a common and costly mistake, because signals stay with the old address.
Does a redirect lose ranking power?
Google has stated since 2016 that 301 redirects lose no PageRank. What does cause loss is redirecting to an irrelevant page: pointing a discontinued product at the homepage is treated as a soft 404, and the signals evaporate. Relevance of the target matters far more than the redirect itself.
What is a redirect loop?
Two rules that send traffic back and forth — typically one forcing www and another forcing the bare domain. Browsers give up after about twenty hops and show an error. The page becomes unreachable for everyone, and crawlers drop it entirely.
Should redirects be kept forever?
Keep them at least a year, ideally indefinitely for anything that had links pointing at it. Removing a redirect turns a working link into a 404 and discards whatever value that link carried. Redirect rules cost almost nothing to keep; removing them is what costs.
Why does the address bar change on some redirects and not others?
Because a rewrite is not a redirect. A rewrite serves different content at the same address, invisibly and with no extra round trip. A redirect tells the browser to request a new address. If the address bar does not change, no redirect occurred — which is often exactly what you want.