Signing in is optional: it keeps your account, watches and connections on any device. Every free check, the audit and the score work with no account at all.
Paste URLs, one per line. For each one you get the status code, every redirect hop, where it finally lands, and whether that page can be indexed. Built for migrations, sitemap clean-ups and Search Console exports.
How to read the result
A green OK answers 200 straight away. Redirect means one hop to the final page, which is fine for an old URL but not for a link you control. Chain is two or more hops: point the first URL straight at the last. Broken is a 4xx or 5xx, or a loop. Any row can also say its final page is noindex or canonicalised to another URL, which means Google will not index that address even though it loads. To write the fixes, use the redirect generator; to find broken links across a whole site, the broken links check.
Questions
What does it check for each URL?
The status code, every redirect in order (301, 302, 307, 308) with where each one points, the final URL, and whether that final page can be indexed: a noindex in the meta tag or the X-Robots-Tag header, or a canonical that names a different URL.
How many URLs can I check?
25 per run for free, 100 on a paid plan. Duplicates are removed first, and a URL without https:// is read as https.
Why does a redirect chain matter?
Each hop costs crawl time and some of the signal a link passes. Google follows a few hops, but a URL that takes two or more to answer should point straight at its final address, and internal links should use the final URL directly.
Is a 302 bad?
Only when the move is permanent. A 302 or 307 says "back soon", so search engines keep the old URL indexed. For a page that has moved for good, use a 301 or 308.
When should I use this?
After a migration (paste the old URLs and confirm each lands in one hop), before submitting a sitemap, when cleaning a Search Console export of "Page with redirect" or "Not found" URLs, or to check backlinks still resolve.