Redirect Mapper

Map old URLs to new URLs and export as .htaccess, Nginx config, or CSV. Perfect for site migrations, URL restructuring, and redirect audits.

Redirect Rules


            

            

            

Frequently Asked Questions

A 301 redirect is permanent — it tells search engines that the resource has moved permanently and to transfer PageRank (link equity) to the new URL. A 302 redirect is temporary — search engines keep the old URL in the index and do not transfer PageRank. Use 301 for site migrations and permanent URL changes; use 302 for temporary promotions or A/B testing.

Redirect chains (A → B → C) slow down page load and dilute PageRank at each hop. Google recommends keeping chains to a maximum of 3–5 hops, but ideally every URL should redirect directly to its final destination. When mapping redirects, always check that new URLs are not themselves redirects — link old URLs directly to the final destination.

Google has confirmed that 301 redirects pass full PageRank (previously there was a small loss, but Google updated their algorithm around 2016 to treat 301s the same as direct links). However, links pointing to deeply chained redirects may still lose some value due to crawl inefficiency.

Redirect directives in .htaccess should be placed before your RewriteRule block (before mod_rewrite rules) so they are processed first. If using Redirect directives, place them at the top. If using RewriteRule for redirects, include them at the top of your RewriteEngine block. Always test redirects in staging before applying to production.

How It Works

Add URL Mappings

Add old URL → new URL pairs manually, or paste a CSV to import dozens of redirects at once. Set the redirect type (301/302) per row or globally.

Generate Config

The tool generates correctly formatted redirect rules for Apache .htaccess, Nginx server blocks, or a clean CSV for import into other tools.

Deploy & Test

Copy or download the config file and apply it to your server. Test each redirect to confirm the correct status code and destination URL.

Common Use Cases

Website Migration

Map hundreds of old URLs to their new equivalents during a domain migration, CMS change, or URL structure redesign to preserve rankings and traffic.

Domain Consolidation

When merging multiple websites or domains, create a complete redirect map to ensure all inbound links and bookmarks resolve correctly on the consolidated site.

URL Structure Cleanup

Simplify messy URL structures (e.g., removing category prefixes, changing /page/ to /article/) while redirecting old URLs to prevent broken links and ranking loss.

Deleted Pages

Redirect deleted or discontinued pages to the most relevant alternative page or category page, rather than serving 404 errors that waste crawl budget.

CMS Platform Change

Moving from WordPress to another CMS often changes URL structures. Use this tool to map all old WordPress permalink structures to new URLs.

HTTP to HTTPS

Generate bulk 301 redirects from HTTP to HTTPS versions of all your key URLs as part of an SSL migration, alongside server-level redirect rules.