Redirect Map Validator
Audit CSV source-to-target maps for duplicate sources, loops, chains, self-redirects, and trailing-slash conflicts
Redirect map issues will appear here.
About this tool
Redirect Map Validator audits CSV source-to-target mappings before a site migration or routing release. It recognizes common source/from and target/to header names, normalizes whitespace, reports missing values and unusual URL shapes, detects identical self-redirects, duplicate source rows, slash and no-slash source conflicts, graph cycles, and multi-hop chains, then emits a normalized CSV for review. Loop and chain detection follows only exact targets that also exist as sources in the uploaded map; it does not crawl live URLs, resolve relative bases, execute regex or wildcard rules, apply platform precedence, inspect HTTP status codes, or confirm canonical and hreflang signals. Use the report to clean the map, then test the exported rules in the actual CDN or server environment.
Scenario Recipes
Audit a migration redirect map before CDN deployment
Goal: Remove graph errors before translating rows into platform rules
- Export the approved source and target inventory to CSV and run the validator before adding regex or wildcard rules.
- Resolve every duplicate, self-redirect, loop, slash conflict, and chain by pointing old sources directly to one final canonical target.
- Generate platform rules, deploy to staging, crawl representative URLs, and compare status, Location, canonical, sitemap, and internal-link signals.
Result: A clean exact-match map that is ready for platform-specific rule and live-response testing.
Frequently Asked Questions
Which CSV headers are recognized?
Source aliases include source, from, old, url, and path; target aliases include target, to, destination, new, and redirect.
How are redirect loops detected?
The tool builds an exact source-to-target graph and follows targets that also appear as sources until a cycle or final destination is found.
What counts as a redirect chain?
A source that points to another source in the same map and requires more than one redirect is reported as a chain.
What is a trailing-slash conflict?
Both /path and /path/ appearing as separate source rows are flagged because platform slash behavior can make them collide.
Does it crawl live URLs?
No. It does not make requests or verify deployed status codes, headers, platform precedence, regex rules, or canonical tags.
Is the CSV uploaded?
No. CSV parsing, graph analysis, issue sorting, and normalized output happen locally.
Keep browsing