Redirect Map & .htaccess 301 Generator
Build bounded literal-path Apache RewriteRule snippets, NGINX exact locations, or a generic migration CSV locally. Review and test generated configuration before applying it.
Redirect Rule Workspace
Paste old and new URL pairs to inspect redirect loops, format rule directives, and export code snippets.
URL Mapping & Server Settings
Generated Directives & Export
Awaiting Rules| # | Source URL (Old) | Target URL (New) | Status |
|---|---|---|---|
| No URL pairs entered yet. | |||
Your URL lists and website migration paths are computed locally and never sent to external servers.
Identifies cyclic redirect loops and self-referencing URLs before deployment.
Generates root .htaccess RewriteRule snippets, case-sensitive NGINX exact locations, and generic migration CSV maps.
Redirect Directives & Engine Specifications
Apache .htaccess
Uses Redirect 301 or RewriteRule within mod_alias or mod_rewrite modules. Ideal for cPanel and shared Linux hosting environments.
NGINX Server Block
Uses high-performance rewrite or return 301 rules inside NGINX server configuration blocks without per-directory file lookup overhead.
Generic CSV Migration Map
Exports a generic Old URL, New URL, Status Code CSV for review. This is not a vendor-specific importer format.
How to Generate 301 Redirect Maps
-
1
Paste URL Mappings
Enter your old and new URL pairs separated by commas, tabs, or spaces into the input box (or select a demo preset).
-
2
Select Target Web Server
Choose Apache RewriteRule, NGINX exact locations, or generic CSV. Unsupported vendor-specific formats are not offered.
-
3
Copy or Download Snippet
Click "Generate Redirect Code", review the loop validation table, and copy or download your configuration file.
How the Browser Redirect Engine Works
A 301 permanent redirect informs web browsers, search engine crawlers, and HTTP clients that a resource has moved permanently to a new URL location. Transferring link equity (PageRank) and preserving organic traffic search visibility during site migrations requires accurate URL mapping.
This tool processes raw text or CSV inputs line-by-line using client-side regular expressions. It normalizes protocol schemes, trims trailing query parameters, checks for duplicate source paths, and alerts you if an old URL points directly to itself (which causes infinite browser redirect loops). It excludes duplicate and cyclic rows and formats the remaining rules. It does not inspect your server, existing rules, filesystem or routing setup.
Redirect Code Examples by Platform
Apache .htaccess Syntax
Place the generated rules in the root .htaccess on Apache 2.4 with mod_rewrite enabled.
RewriteRule ^old-page$ /new-page [R=301,L,NE,QSD]
NGINX Syntax
Place exact locations inside the appropriate NGINX server block.
location = /old-page { return 301 /new-page; }
CSV Mapping Format
CSV header: Old URL,New URL,Status Code
CSV entries are quoted and preserve HTTP status values. Adapt them to the importer you use.
Who Needs a 301 Redirect Generator?
- SEO Specialists & Consultants: Map old URLs to new URLs during website migrations, CMS domain switches, or permalink structure updates.
- Web Developers & DevOps Engineers: Generate reviewable
.htaccessand NGINX configuration snippets without writing regex rules manually. - WordPress Site Owners: Export a generic CSV migration map. Check your plugin’s required columns before importing.
- E-Commerce Managers: Redirect discontinued product pages and old category taxonomies to active replacement products.
Frequently Asked Questions
What is the difference between a 301 and 302 redirect?
A 301 redirect indicates a permanent move and signals that the destination replaces the old URL; search engines determine how to consolidate ranking signals. A 302 redirect indicates a temporary move and tells search engines to keep indexing the original source URL.
What causes a redirect loop?
A redirect loop occurs when URL A redirects to URL B, and URL B redirects back to URL A (or URL A redirects directly to URL A). Browsers will show an "ERR_TOO_MANY_REDIRECTS" error. This tool flags potential loops automatically.
Is there a limit on how many rules I can put in .htaccess?
While Apache has no hard line limit, adding thousands of individual Redirect 301 lines to .htaccess can slow down server TTFB because Apache parses .htaccess on every HTTP request. For bulk migrations over 5,000 URLs, NGINX server blocks or edge platforms (Cloudflare) are recommended.
Are my URL lists stored or logged anywhere?
No. All text parsing, URL validation, and code generation take place inside your web browser's local memory. No data is transmitted to remote servers.