Redirect Map Validator
Inspect exact redirect CSV maps while preserving every original column and row
Inspect literal exact-match HTTP(S) URLs or single-slash root paths in CSV. All fields, row order and original CSV are preserved. No URLs are requested; regex, wildcard rules, status codes and platform precedence are not evaluated. Limits: 1 MiB, 10,000 data rows, 64 columns.
Input is processed in this page without saved drafts. Analytics records fixed actions and counts, excluding CSV, URLs and diagnostic text.
About this tool
Redirect Map Validator inspects comma-separated exact source-to-target mappings for literal HTTP(S) URLs or single-slash root paths. It requires unique headers and exactly one recognized source and target alias, reports original physical line numbers, and preserves all columns, row order, blank lines and the browser input’s line endings in the CSV snapshot. Browsers may normalize pasted newlines to LF. Different targets for one source are ambiguous: the tool assumes no first-row or platform winner and stops dependent paths. Same-target duplicate rows remain in the CSV. Each cycle is reported once; cached iterative traversal avoids rescanning long chains. Slash checks compare pathnames with the same query, and target fragments stop traversal because fragments are not sent in server requests. The tool makes no network requests, resolves no relative base, evaluates no regex/wildcard rules or status codes, and does not confirm deployed behavior or canonical signals. Limits are 1 MiB, 10,000 data rows and 64 columns. The page shows the first 200 findings; diagnostic downloads include all findings. The CSV download retains reported problems and is not repaired or approved for deployment.
Suggested Workflow
Scenario Recipes
Review a migration CSV without losing routing metadata
Goal: Find exact-map problems while retaining every original field for further review.
- Paste comma-separated CSV with exactly one source alias and one target alias. Additional status/note columns are preserved but not interpreted.
- Read physical source lines for missing values, unsupported URL forms, duplicate sources, cycles and chains. Conflicting targets stop traversal rather than choosing the first row.
- Download the original CSV snapshot or the complete diagnostic report. Resolve findings in the source data, then test status, Location and precedence on the actual server or CDN.
Result: A bounded graph diagnostic and an unchanged input snapshot; neither is a deployable-rule certification.
Failure Clinic (Common Pitfalls)
Different targets for the same source produce a different loop result after sorting rows
Cause: A first-row-wins graph invents platform behavior that the CSV alone cannot establish.
Fix: This checker marks the source ambiguous and stops dependent paths there. Decide precedence on the target platform before rechecking a deterministic map.
A slash inside a query value is called a trailing-slash conflict
Cause: The end of the full URL is not necessarily the end of its pathname.
Fix: The checker compares pathname slash variants with the same query. It does not rewrite URLs or impose a site-wide slash policy.
Importing the downloaded CSV as if its problems were repaired
Cause: The download is the original input snapshot, including reported problems and extra columns.
Fix: Edit the original mapping and review the actual deployment format. The tool makes no network requests and does not evaluate regex, wildcard, status-code or platform-specific rules.
Production Snippets
A multiline CSV field changes physical line numbers
csv
source,target,note
/a,/b,"two
lines"
/c,,missing
The missing target starts on physical line 4.
The note remains one field containing a newline.
All columns are retained; browsers may normalize pasted newlines to LF.Frequently Asked Questions
Which headers are supported?
Source aliases are source, from, old, url and path; target aliases are target, to, destination, new and redirect. Exactly one alias per role is required. Duplicate or ambiguous headers are rejected; additional columns are preserved.
Does the CSV download remove extra columns or repair rows?
No. It is the original CSV snapshot, including status/note columns, blank lines and any reported problems. It does not claim that the rules are deployable.
How are conflicting duplicate sources handled?
Different targets for one source are marked ambiguous. Traversal stops there without choosing a row by order. Identical source/target duplicates retain all rows and share one graph edge.
How are chains and cycles calculated?
Only literal targets that also appear as sources are followed. Each cycle is reported once. Ambiguous or invalid sources and target fragments stop traversal; no deployed URL requests are made.
Why does a line number differ from the data-row number?
Quoted CSV fields can contain newlines, and blank lines also count physically. The report uses the original record’s starting physical line.
Which URL forms are outside the checker’s scope?
Relative, query-only or network-path references, source fragments, whitespace, controls, backslashes, credentials, dot segments and wildcard rules are excluded. Some may be valid in other HTTP contexts; this tool only models its stated literal mapping subset.
Keep browsing