Redirect Checker

Redirect Checker follows a URL's redirects from our server hop by hop, showing each status code, Location and time, and flags chains, loops and temporary redirects.

At a glance

Accepts: A URL, or up to 20 URLs in bulk
Outputs: Every redirect hop with status code, permanent or temporary, Location header and time, the final status, and flagged problems
Where it runs: On our server
What leaves your device: The URLs are sent to our server, which requests them (not stored)
Limits: Up to 10 hops per URL and 100 checks an hour; JavaScript redirects are detected best effort, not run; no cookies kept
Account: Not required - there is no sign-up
Price: Free, with no watermark and no usage cap
Made by: Visrut
Last updated: 14 October 2026

A redirect sends browsers and crawlers from one URL to another. Done well it is invisible; done badly it costs a round trip per hop, splits ranking signals, or loops forever. This checker requests a URL from our server, follows each redirect itself, and shows every hop with its status code, Location header and response time, then flags the problems worth fixing.

What it flags

Chains of more than 2 redirects, and loops.
http to https to www in two hops, where one redirect straight to the final address would do.
A 302 or 307 that only adds https, www or a trailing slash - a change that is almost always meant to be permanent (301 or 308).
A final 4xx or 5xx status.
Meta refresh redirects (followed when instant) and, best effort, JavaScript redirects in the final page.

Sources, checked 13 October 2026: Google's Redirects and Google Search (how permanent, temporary, meta refresh and JavaScript redirects are treated) and HTTP status codes and Google Search (Google follows up to 10 hops).

Bot or browser-like?

By default we identify ourselves honestly as a checker bot. Some sites redirect bots differently, or block them outright, so Browser-like sends an ordinary desktop browser user agent instead. We never send Googlebot's user agent: sites verify the real Googlebot by where its requests come from, so a fake one shows you what an impostor gets, not what Google sees. For Google's own view, use URL Inspection in Search Console.

Honest limits

Timings are from our server's location, not yours, and vary between runs.
We keep no cookies, so a site that sets a cookie and redirects to itself shows as a loop here.
Private and local addresses are refused, including redirects that point to them.
Up to 20 URLs per bulk run, and 100 checks an hour.

Related SEO checks

Link Preview Checker - see how a link looks when shared
Sitemap Validator - check or build a sitemap.xml
Schema Markup Checker - test structured data for rich results
Domain Info - look up a domain's age and registrar

Frequently asked questions

Does this send the URL to your server?

Yes. A browser can't see another site's redirects, so the URL is sent to our server, which requests it and each redirect target in turn and reports what came back. We don't store the URLs.

What's the difference between 301, 302, 307 and 308?

301 and 308 are permanent: Google treats them as a signal that the target is the canonical URL. 302, 303 and 307 are temporary: Google follows them but doesn't treat the target as canonical. 307 and 308 also keep the request method (a POST stays a POST), which matters for forms and APIs, not for normal pages.

How many redirects is too many?

Google's crawlers follow up to 10 hops and then give up. Every hop also adds a round trip for visitors, so the goal is one redirect from any old URL straight to the final one. This checker flags chains of more than 2 hops and follows up to 10, like Google.

Why can't I check as Googlebot?

Because pretending would show the wrong answer. Sites and firewalls verify Googlebot by checking that the request really comes from Google's network, so a fake Googlebot is often blocked or served something different from what the real one gets. Use the Browser-like option to see what a normal visitor gets, and Google Search Console's URL Inspection to see what Google itself fetched.

Does it find JavaScript and meta refresh redirects?

An instant meta refresh is followed as a hop, since Google treats it as a permanent redirect. A delayed one is reported. JavaScript redirects are detected on a best-effort basis by reading inline scripts, without running them, so redirects built at runtime or in separate script files can be missed.