How to use the redirect checker
Enter one or more web addresses, one per line, and click Check status. The checker requests each address exactly as a browser would, but instead of jumping straight to the end, it stops at every redirect and records it. You see each step in order: the status code, the address, the response time and the server's headers, followed by the final page and its status.
Each result includes a short verdict. A single permanent redirect to a working page is marked as ideal. Chains, loops, temporary redirects, redirects that drop from https back to http, and redirects that end on a broken page are flagged with an explanation of how to fix them.
Check your www and https setup
Every website should have one preferred address, for example https://example.com, with every other version redirecting to it in a single step. Paste these four versions of your domain to test it:
http://example.comhttp://www.example.comhttps://www.example.comhttps://example.com
The first three should each show one 301 redirect to your preferred address, and the last should load directly with 200 OK. If one of them shows two redirects in a row, such as http to https and then www to non-www, combine the rules so they happen in one hop. If one fails with a certificate error, your SSL certificate doesn't cover that version of the domain.
Redirect chains and loops
A redirect chain happens when one redirect leads to another, for example after a site has been restructured more than once. Each hop adds a delay for visitors, especially on mobile connections, and Google stops following after 10 hops. Fix chains by pointing the first address straight at the final destination, and update internal links, menus and sitemaps to use the final address so no redirect is needed at all.
A redirect loop sends the visitor back to an address it already passed through, so the page never loads and browsers show a "too many redirects" error. Loops usually come from two rules fighting each other, for example an https rule in the server config and another in a plugin or CDN, or a Cloudflare "Flexible" SSL setting combined with an https redirect on the server.
301 or 302?
Use a 301 (or 308) when a page has moved for good: a new URL, a merged article, a domain change or the switch to https. It tells search engines to index the new address in place of the old one. Use a 302 (or 307) only for genuinely temporary moves, such as a short promotion or a page under maintenance. Google has said that all redirect types pass ranking signals, but a permanent redirect is the clearest way to tell it which address should appear in search results.
Frequently asked questions
How many redirects are too many?
Aim for one. Two is acceptable for a short time after a migration, but anything longer should be fixed. Googlebot follows up to 10 redirects before giving up and reporting an error.
How do I fix a redirect chain?
Update the rule for the first address so it points straight at the final page, then change internal links and your sitemap to use the final address. On Apache servers these rules are usually in the .htaccess file; on WordPress they are often in a redirect plugin.
Why does my site redirect twice, from http to https and then to www?
Two separate rules handle the protocol and the host name. Combine them into one rule that sends every variation straight to the preferred https address in a single redirect.
Can I check redirects as Googlebot?
Yes. Choose Googlebot under Check as. The request uses Googlebot's user agent, which shows you whether a site redirects crawlers differently from visitors.
Last updated