WordPress Redirect CSV Validator
Check redirects for duplicates, conflicts and loops before importing.
What Is a WordPress Redirect CSV Validator?
A WordPress redirect CSV validator helps review a spreadsheet of old URLs and intended destinations before importing redirect rules into WordPress. Validation can check columns and row structure, and may identify missing destinations or conflicting mappings when supported. Import formats differ across redirect plugins, so a structurally valid CSV is not necessarily ready for every importer. Test the redirects on a live or staging site after import.
WordPress Redirect CSV Validator
Check redirects for duplicates, conflicts and loops before importing.
Check redirect rules before importing them
Accepts common Redirection or Rank Math-style columns. Checks duplicate and conflicting sources, broken targets, self-redirects, chains and cycles. This tool does not add rules to your WordPress site or follow the redirects online.
Prepare a WordPress Redirect CSV Without Import Mistakes
Bulk redirects are often planned in a spreadsheet long before they reach WordPress. That spreadsheet may contain hundreds of old article URLs, replacement product pages, merged categories or paths from a previous domain. A single wrong destination can send visitors somewhere irrelevant; a conflicting rule can make the result depend on which redirect system executes first.
Use the WordPress Redirect CSV Validator above as a pre-import review step. Follow the input method and file requirements shown by the active tool, inspect any returned findings, and compare the final CSV with the importer you actually use. The important distinction is between file validity, redirect-map consistency and live redirect behavior. These are separate tests. A spreadsheet can be perfectly formatted while pointing to missing pages, and a clean mapping file can behave differently after server, CDN and plugin rules are combined.
Read Full GuideShow Less
Start With the WordPress Plugin That Will Import Your Redirects
There is no universal WordPress redirect CSV format. The receiving plugin determines column names, redirect types and import behavior. Rank Math PRO documents an importer with lowercase, case-sensitive column headings including source, destination and type. The Redirection plugin instead documents source-and-target rows with optional regex and HTTP-code fields.
Identify the importer, export a sample when possible and preserve your original redirect map. An importer-specific sample is the safest reference for the final column layout.
Three Different Questions a Redirect CSV Review Should Answer
| Review layer | Question | What it does not establish |
|---|---|---|
| CSV structure | Can the rows and columns be interpreted as the intended data? | That a target URL exists or that a WordPress plugin accepts these headers. |
| Redirect map | Are sources missing, repeated or mapped through avoidable intermediate URLs? | That a server has applied the rules in the same order. |
| Live HTTP test | Does an old URL actually return the intended response and final location? | That every untested URL or future request behaves identically. |
The embedded tool’s exact supported checks depend on its deployed implementation. Treat any reported success as a result for the checks actually performed, not as certification that every redirect has been tested on a public website.
Build the Source and Destination Columns Carefully
A basic redirect map has one source address and one destination address per planned rule. The source is the old URL that visitors may still request; the destination is the replacement they should reach. For a same-domain migration, many importers accept paths such as /old-guide/ and /new-guide/. For a domain migration, complete HTTPS URLs can make the intended host clear, but only use full URLs if your importer supports them in that field.
Review capitalization, trailing slashes and query strings: some systems compare paths exactly; others normalize them. Do not silently strip meaningful parameters. Browsers do not send fragments such as #section in HTTP requests.
A Small Rank Math CSV Example
This illustrative file uses documented Rank Math PRO column names and exact-match entries. It is not a tested output from the tool above, and it should not be imported into a different plugin without conversion.
source,destination,type,matching,status
/old-services/,/services/,301,exact,active
/previous-contact/,/contact/,301,exact,active
/temporary-offer/,/current-offer/,302,exact,active
Rank Math’s documented CSV import requires at least its source and destination columns; other fields control behavior when supplied. Its bulk CSV import and export interface is a PRO feature. If you use a different plugin or an older version, inspect that product’s actual import documentation rather than assuming the example works unchanged.
Why a Redirection Plugin CSV Is Not the Same File
The plugin named Redirection documents a simple row format with source and target URL fields, optionally followed by regex settings, an HTTP code and a type. An example of its documented two-column style is:
/old-services/,/services/
/previous-contact/,/contact/
This example has no header row, unlike Rank Math. Redirection requires comma-separated values; tab or semicolon separators may fail. Follow the chosen importer’s specification, particularly for regex rules.
Common CSV Errors and How to Correct Them
| Potential issue | Why it matters | Recommended review |
|---|---|---|
| Missing target | No usable replacement address is defined. | Choose the appropriate new page; do not invent a destination just to fill a cell. |
| Duplicate source | One old address appears in more than one rule. | Remove redundant duplicates or resolve conflicting destinations. |
| Source equals destination | A self-redirect may create repeated requests. | Remove the rule or correct the intended new address. |
| Unexpected delimiter | All values may be read as one column. | Export as comma-separated CSV in the encoding accepted by the importer. |
| Unsupported status | The target plugin may reject an HTTP code. | Use only statuses documented for that importer. |
| Destination typo | The rule could point to the wrong page or host. | Review the destination manually and verify it after deployment. |
Keep editorial notes and content owners in a separate working sheet unless the importer supports those fields.
Understand Redirect Chains, Loops and Conflicting Rules
Imagine an old post redirects to an intermediate page, which then redirects again to a final guide. That is a redirect chain. If the confirmed final destination is /new-guide/, it is usually better for the first rule to point directly there. Every unnecessary hop adds another request and can complicate migration checks.
Chain: /old-guide/ → /draft-guide/ → /new-guide/
Better: /old-guide/ → /new-guide/
Loop: /category-a/ → /category-b/
/category-b/ → /category-a/
Conflict: /old-offer/ → /sale/
/old-offer/ → /clearance/
These examples are hypothetical. A map-only validator may identify them with exact-path tracing, but cannot necessarily identify host, CDN or other WordPress redirects. Confirm destinations before making changes.
Choose the Appropriate HTTP Status Code
For a lasting move where the original page has a suitable replacement, 301 Moved Permanently is a common choice. 308 Permanent Redirect is another permanent status with different method-preservation semantics. For temporary moves, 302 and 307 are commonly used, with 307 explicitly preserving the request method. Search engines interpret permanent and temporary redirects differently as canonicalization signals.
Do not choose a status simply because it appears in a generic CSV sample. The target WordPress plugin may support a narrower set of codes. A deleted page with no meaningful replacement may be better left as a genuine 404 or 410 response rather than redirected to an unrelated homepage. A 410 is a gone response, not a substitute for a successful redirect.
What Makes a Redirect Mapping Useful for SEO?
A redirect should connect a visitor’s original intent to a closely matching destination. If several old tutorials merge into one accurate guide, they may reasonably redirect there. Sending every obsolete page to the homepage is often unhelpful and may be interpreted as an irrelevant replacement.
During a migration, compare the old URL inventory with the new site architecture. Review important organic landing pages, pages with external links, and URLs present in your old sitemap. The Website Migration URL Mapper can support planning, while the Redirect Format Converter for WordPress Plugins is a relevant next step when import formats differ.
After Import, Verify the Redirects That Really Run
CSV validation does not deploy redirects. Importing a file also does not prove that its rules override existing redirects from another plugin, the web server or a CDN. Test a representative set of important old URLs after the import, including high-traffic pages, redirects across domains, unusual path capitalization and URLs with parameters.
- Back up the current rules. Export the active redirects and record the plugin version before replacing anything.
- Import on staging when practical. Check the import summary for skipped rows, duplicates or changed rules.
- Request the old URLs. Inspect the actual HTTP status,
Locationresponse header, redirect hops and final page. - Check the landing page. Confirm that the final response and content are appropriate, not just that a redirect happened.
- Fix internal references. Link directly to the new URLs in navigation, articles and sitemaps instead of repeatedly depending on redirects.
The Bulk HTTP Status and Redirect Checker and Redirect Rule Tester are useful related workflows when their installed features are available. A clean import and a successful live crawl together are more meaningful than either result alone.
Questions That Come Up Before Bulk Redirect Imports
Can the validator fix every redirect automatically?
Not necessarily. A report covers its supported checks; choosing the best replacement requires editorial judgment. Review any corrected export before importing.
Is a CSV accepted by Rank Math also accepted by Redirection?
Not necessarily. Their documented import layouts differ. A file using Rank Math headers may need conversion before it can be used by Redirection or another plugin.
Does passing validation mean there are no redirect loops?
Only if loop analysis is actually supported, and only within the rules examined. A separate host-level redirect can still create a loop after the CSV has been imported.
Should I delete old URL rows once Google finds the new pages?
Not automatically. Old addresses may still receive bookmarked visits, external-link traffic or crawler requests. Keep redirects while they remain useful and review removal decisions against your migration and server logs.