Redirect Checker

• 301 Moved Permanently. The URL has moved for good. Google transfers the indexing signals to the destination and eventually drops the old URL from its index. This is the redirect you want after a migration.
• 302 Found and 307 Temporary Redirect. The move is temporary, so Google keeps the original URL indexed. Correct for a maintenance page or a geographic bounce, wrong for anything permanent.
• 308 Permanent Redirect. A 301 that also preserves the request method. Safe to use, and treated as permanent.
• 200 OK. No redirect at all: the URL responds directly. This is the healthy state for a URL you link to.
• 404 and 410. The destination does not exist. Any link, sitemap entry, or redirect pointing here is wasted.

Each URL you paste gets one badge, which names the single thing worth acting on. The chain underneath it lists every hop in order, so you may see where the badge came from.

• Direct. The URL answers on its own, with no redirect in front of it. Nothing to do.
• 301 or 308. One permanent redirect to the destination. This is the healthy shape for a moved URL.
• 302 temporary. The redirect is marked temporary, so Google keeps the old URL indexed. Change it to a 301 unless the move really will be reversed.
• 2 hops and 3 hops. The redirect lands on another redirect. Point the first rule at the final URL and the extra round trips disappear.
• Via http. The chain drops to an insecure http URL before it reaches https. Rewrite the first rule to send visitors straight to the https address.
• Ends on http. The chain finishes on http, so the page is served insecurely no matter how the visitor arrived. Fix this before anything else on the list.
• Loop and Too many hops. The chain never resolves within ten hops. Two rules are usually sending each other back and forth, and the trace shows you which URLs they are.
• 404 and other 4xx or 5xx codes. The chain resolves, but the destination does not load. Redirect the URL somewhere that does.
• Failed. The URL could not be reached at all, and the reason is printed beside it. A misspelled domain, an expired certificate, and a firewall that blocks unknown crawlers all land here.

A site migration succeeds or fails on its redirect map, and the failure is rarely visible on the day. Export the old URLs from the old site's sitemap, paste them here after the launch, and read the table for three things: anything ending in a 404, anything taking more than one hop, and anything answering 302.

Run it again a week later. Redirect rules get reordered, edge caches expire, and a rule that worked at launch can be shadowed by one added since. The sitemap validator will give you the URL list to check against, and the HTTP header checker shows the headers behind each response when a redirect behaves in a way the status code alone does not explain.