Redirect Map Checker
Find the detours in your redirect plan before a site move.
One redirect per CSV row: source,target,status. Use complete URLs and a status such as 301 or 308. Up to 1,000 rows / 1 MiB. Your CSV stays in this browser; input URLs are not visited.
For a permanent move, review chains against Google’s migration guidance. Next, compare the page metadata before release.
About Redirect Map Checker
Upload or paste a CSV of exact source URLs, target URLs and HTTP redirect status codes. The checker traces relationships in your map, identifies loops and conflicting rules, and shows where each unambiguous path ends. It flags chains, duplicate rules, temporary redirects and HTTPS-to-HTTP steps. Review the report, then test your actual server redirects and destination content before release.
Frequently Asked Questions
No. It only checks the mappings in your CSV. URLs are never fetched, and HTTP statuses come from your input. A final destination means that URL has no source row in this map; its availability, content, canonical URL and indexing status are unverified.
Use source,target,status headers in any order, with complete HTTP or HTTPS URLs. Supported statuses are 301, 302, 303, 307 and 308. Quote URLs containing commas. Extra uniquely named columns are ignored. Limits are 1 MiB, 1,000 rows and 2,048 characters per URL. Include redirect rows only, not final pages with a 200 status.
The standard URL parser normalizes host casing and default ports. Path casing, trailing slashes and query parameters remain significant. Fragments, credentials, raw whitespace and backslashes are rejected. Regex rules, wildcards, relative URLs and server-specific matching are not evaluated; expand them into concrete URLs first.
Loops and conflicting mappings need investigation. Temporary redirects can be intentional. For a permanent move, review whether a chain can lead directly to its correct final destination. This tool cannot judge content equivalence, server rule precedence or method-preservation requirements and does not generate deployable redirect rules.
If a source has different targets or statuses, there is no unambiguous next step. The checker stops there, including for upstream paths. Identical duplicate rows are flagged but can still be traced. Only the first 12 URLs in each path are displayed and exported; hop counts and destinations use the full map.