The official store for JNews, a WordPress theme for news, blog and magazine websites. Build a successful publishing website with JNews.
SEO Tools
Redirect Mapping Validator
Review local redirect maps for conflicting sources, chains, loops, invalid URLs, and migration risks. Import and export CSV entirely in your browser.
Review your redirect map
Find conflicts, loops, and chains before implementing a migration. Open a local CSV or paste a table. Nothing is uploaded or fetched.
Limits: 5 MiB UTF-8, 5,000 data rows, 100 columns, 10,000 characters per cell, and 2,048 characters per URL. Quoted commas and multiline cells are supported. Blank lines are skipped; malformed CSV is rejected without a partial import.
Map your columns
Source and destination are required. Status is optional: choose a default when your map has no status column. A blank or invalid mapped code remains an issue.
Root-relative sources use the origin above. Without one, they stay in a separate unknown-origin scope. A root-relative destination uses its absolute source origin, or that unknown scope. Directory-relative and protocol-relative URLs are unsupported.
Imported rows
Rows with issues
Conflicting source groups
Rows in chains
Rows entering loops
Rows reaching an unmapped URL
Mapping review
Record numbers count logical CSV records, including the header, rather than physical lines inside quoted cells. Scroll inside the table to see more rows and columns. Expand a trace to inspect up to 20 URLs; outcome and hop count use the entire supplied map.
| Record | Source | Destination | Code / mapped outcome | Findings |
|---|
Understand your redirect map
What does this validator check?
It checks individual exact URL pairs, supported supplied codes, repeated or conflicting sources, self redirects, chains, and loops including routes leading into a loop. Repeated sources with different normalized destinations or codes are conflicts. Identical duplicates are review notes. It does not model regex, wildcard rules, rule precedence, host aliases, or server-specific query matching.
How are URLs matched?
The browser URL parser normalizes host case, default ports, dot segments, and Unicode hostnames. Percent-escape hex case is normalized. Path case, trailing slashes, encoded versus literal characters, query parameters, and query order remain significant. Fragments are ignored for HTTP matching and flagged for review. Explicit destination fragments are preserved in original values and normalized destination exports, but fragment inheritance is not simulated. Credentials, backslashes, whitespace inside URLs, malformed percent escapes, wildcard patterns, and non-HTTP schemes are rejected.
What does a terminal result mean?
A terminal HTTP URL has no further source rule in your supplied map. It is not a verified live destination, a successful response, or proof of a complete migration. Missing mappings cannot be inferred. Traces stop at invalid or ambiguous sources rather than assuming the first rule wins. Correct those rows and recheck. Origin changes and temporary redirects are review notes because they may be intentional.
Should I flatten every chain?
Review direct redirects to the final destination to reduce unnecessary hops. Check intended query handling, fragment behavior, method preservation, and temporary steps before changing a rule. This tool does not rewrite rules or generate server configuration. Codes 301 and 308 are permanent; 302 and 307 are temporary; 303 is See Other. Codes 307 and 308 preserve the request method. Supplied or default codes are never verified against a live server.
What is exported and is my data private?
CSV reports include all matching rows across pages, original mapped values, normalized URLs, assumed-code flags, source groups, mapped hop counts, terminal HTTP URLs, and findings. Other imported columns are omitted. Spreadsheet formula prefixes are escaped with a leading apostrophe. Files are decoded locally as UTF-8. No processing requests, uploads, crawling, API calls, or browser storage are used. Edits invalidate old results; failed file reads preserve the current input.
References: Google site migration guidance · HTTP redirections.