Redirect Map Builder

Planning a website migration, domain consolidation, or URL restructuring? This free browser-based redirect map builder validates your URL mappings in real time, automatically flattens multi-hop redirect chains, detects dangerous circular loops, and exports clean, server-ready rules for Apache, Nginx, Cloudflare, WordPress, Netlify, and Vercel. Your sensitive site URLs are processed entirely in your browser — nothing is ever uploaded, tracked, or saved.

# Enter URL mappings above to generate server redirect configuration.

What is a redirect map and why is it essential for website migrations?

A redirect map is a structured inventory connecting legacy or obsolete URLs to their corresponding new destinations on a website. During site migrations, redesigns, domain mergers, CMS replatforming (such as moving from Magento to Shopify, or Drupal to WordPress), or structural permalink changes, every single URL that previously received traffic or accumulated external backlinks must be accounted for. Without a comprehensive redirect map, visitors encounter frustrating 404 Not Found errors, search engine crawlers lose the indexation footprint of your content, and historical PageRank equity built over years evaporates overnight.

Modern search engines like Google, Bing, and Yandex utilize 301 redirects as authoritative legal deeds signaling permanent content transfers. When a 301 redirect is verified by search crawlers, canonical signals, anchor text relevance, and ranking equity are transferred to the target destination URL. However, creating these maps manually in spreadsheets frequently introduces human errors: circular redirect loops that crash browsers, multi-hop redirect chains that bleed crawl budget, or malformed syntax that causes web servers to crash upon restart. This free redirect map builder eliminates these hazards by validating, chain-flattening, and syntax-formatting your rules entirely in your browser.

HTTP status codes compared: 301, 302, 307, 308, and 410

Selecting the correct HTTP status code is paramount when configuring server-level routing. Each status code conveys a distinct instruction to web crawlers and browser caches:

For standard organic SEO site migrations, 301 Moved Permanently is the undisputed industry standard. If you are pruning obsolete product variants, discontinued services, or outdated thin articles that have no logical topical replacement, using a 410 Gone response is vastly superior to generic homepage redirects. A 410 status explicitly instructs search bots to purge the URL from the index promptly, conserving crawl budget without generating soft 404 warnings.

The hidden SEO cost of redirect chains and redirect loops

Why redirect chains degrade organic performance

A redirect chain occurs when a request for an initial URL hops through one or more intermediate redirects before reaching its final destination (for example: URL A → URL B → URL C → URL D). Chains commonly accumulate on legacy websites when previous redesigns and historical HTTP-to-HTTPS or non-www to www migrations were stacked on top of one another.

Redirect chains impose three distinct penalties on your site:

• Compounded latency & slower Time to First Byte (TTFB): Every intermediate redirect requires an additional DNS resolution, TCP handshake, and TLS negotiation. On mobile 4G/5G networks, a 3-hop redirect chain can introduce 600–1,200ms of unnecessary latency, directly degrading your Core Web Vitals and user conversion rates.
• Crawl budget exhaustion: Search engine bots allocate a finite time budget to crawling each site. If Googlebot spends its allocated crawl allotment resolving intermediate hops, deeper organic pages remain uncrawled and unindexed.
• Crawl abandonment at 5 hops: Google's official webmaster guidelines state that Googlebot will abandon following a redirect chain after 5 consecutive hops. Any link equity or indexing signals beyond 5 hops are permanently lost.

Our tool's Auto-flatten redirect chains feature inspects your entire mapping graph and condenses every multi-hop sequence directly into a single 1-hop rule (A → D). This guarantees maximum PageRank transfer and instantaneous page delivery.

The danger of circular redirect loops

A redirect loop occurs when two or more URLs point back to one another (for example: /page-1 → /page-2 → /page-1), or when a page points directly to itself. Browsers trap the request until reaching a timeout limit, displaying an unsightly ERR_TOO_MANY_REDIRECTS screen. Web crawlers immediately abort and flag the URL as non-indexable. Our audit engine isolates loops before you deploy, preventing catastrophic production downtime.

Web server export syntax: Apache vs. Nginx vs. Cloudflare vs. WordPress

Different web servers and hosting architectures require exact syntax configurations. Misplacing a single regular expression character or flag can bring down your entire web server. Here is how our builder structures configurations across popular environments:

1. Apache (.htaccess)

Apache uses the mod_alias module for simple prefix redirects. The standard directive follows:

Redirect 301 /old-path /new-path

Our generator wraps your directives in <IfModule mod_alias.c> guards to ensure seamless execution without server crashes. For absolute external destinations, full URLs (https://example.com/target) are fully supported.

2. Nginx (nginx.conf)

Nginx processes routing rules within server { ... } blocks using the rewrite directive. Nginx syntax requires precise regex escaping and destination flags:

rewrite ^/old-path/?$ /new-path permanent;

Using the permanent flag sends an HTTP 301 status, while the redirect flag sends an HTTP 302. For pruned pages, Nginx uses dedicated location blocks: location = /pruned-page { return 410; }.

3. Cloudflare Bulk Redirects

Cloudflare executes redirects at the edge across hundreds of global points of presence (PoPs) before traffic ever reaches your origin server. Cloudflare's Bulk Redirects feature accepts a standardized CSV schema with exact boolean flags for query string preservation, subpath matching, and suffix forwarding. Our tool outputs ready-to-import Cloudflare CSV files that meet all API schema requirements.

4. WordPress (Redirection Plugin)

For non-technical site owners utilizing John Godley's ubiquitous Redirection plugin (active on over 2 million WordPress installations), our tool exports the exact CSV format expected by the plugin's native import wizard, complete with matching types, action flags, and grouping attributes.

5. Netlify & Vercel Modern Jamstack

For modern headless applications deployed on Netlify or Vercel, server rules must reside in _redirects plain text files or structured vercel.json objects. Our exporter formats rules to respect platform-specific syntax, including force-redirect exclamation marks (301!) and JSON boolean attributes.

Step-by-step site migration redirect mapping workflow

1. Extract legacy URL inventory: Crawl your existing website using an SEO desktop crawler like Screaming Frog or Sitebulb. Export all internal HTML URLs that returned a 200 OK status code. Combine this crawl list with historical traffic reports from Google Analytics 4 and ranking landing pages from Google Search Console to capture orphan URLs that may not be linked internally.
2. Identify new target destination URLs: Map your staging or newly redesigned website architecture. Group pages logically by topic, product category, or informational intent. If you are also restructuring internal linking hierarchies, consult our Internal Link Planner to ensure your pillar content receives balanced link equity.
3. Pair old URLs to new counterparts: Match each legacy URL to its closest topical equivalent. If an exact replacement exists, route directly to it. If a legacy blog post has been consolidated into a comprehensive pillar guide, redirect the old URL to the pillar guide. Never redirect all deleted pages indiscriminately to your homepage; Google treats mass homepage redirects as soft 404s, neutralizing ranking power.
4. Paste and audit in Redirect Map Builder: Paste your URL pairs into Step 1 above. Review the Migration Safety Score, inspect the Direct 1-Hop ratio meter, and review any flagged loop or syntax warnings. Ensure the Auto-flatten redirect chains option is enabled.
5. Export and deploy to server: Select your server format (Apache, Nginx, Cloudflare, WordPress, Netlify, or Vercel). Click Copy Server Config and paste the directives into your server configuration or deployment repository.
6. Verify and monitor post-launch: After DNS propagation, crawl the old URL list to verify that every URL returns a clean 301 response pointing directly to the final 200 OK destination without hops. Run our Broken Link Checker to ensure no internal hyperlinks point to redirected or broken endpoints, submit your updated XML sitemap using the Sitemap Validator, and monitor robots directives with our Robots.txt Generator.

Handling URL parameters, query strings, and hash fragments

URL parameters and fragment identifiers require special attention during redirect mapping:

Query strings (?utm_source=... or ?id=123)

By default, Apache's Redirect 301 directive appends query strings from the source URL directly onto the target URL. If your legacy URLs contain tracking parameters or legacy CMS query variables that should be stripped, you must utilize Apache mod_rewrite rules with an empty question mark flag (QSD or ?), or Cloudflare edge rules with query string preservation disabled. In Nginx, adding a question mark to the end of the destination URL (/new-path?) instructs Nginx to strip the incoming query string.

Hash fragments (#section-id)

A hash fragment (such as /about#team) is strictly a client-side browser anchor. HTTP request specifications dictate that browsers never transmit hash fragments to web servers in HTTP GET headers. Therefore, web servers cannot match or redirect based on fragments in source URLs. Our tool automatically detects and strips hash fragments from source URLs while alerting you in the diagnostics log.

Seven critical redirect mapping pitfalls to avoid

• 1. Mass-redirecting everything to the homepage: When a site deletes hundreds of legacy URLs and redirects them all to https://example.com/, Google's algorithms classify these as soft 404s. The incoming link equity is largely discounted. Always redirect to the most relevant topical parent or category page instead, or emit an explicit 410 Gone status.
• 2. Leaving multi-hop chains unresolved: Allowing historical redirects to chain together creates latency and squanders crawl budget. Always flatten chains into direct 1-hop routes.
• 3. Mixing HTTP and HTTPS protocols: If your new site operates on HTTPS, ensure all target URLs in your redirect map specify https:// or clean root-relative paths (/new-page). Never redirect an old page to an HTTP destination only for it to be redirected a second time to HTTPS.
• 4. Case sensitivity mismatches: Linux web servers (Apache, Nginx) treat URLs with differing cases as distinct resources (for example, /About-Us vs. /about-us). Standardize all redirected paths to lowercase to avoid duplicate content collisions.
• 5. Overlooking trailing slashes: A mismatch between /blog/post and /blog/post/ can trigger an unintended secondary redirect. Configure your server rules to match both variants seamlessly.
• 6. Conflicting duplicate source rules: Entering the same old URL twice with differing destination endpoints creates server rule shadowing. The server executes whichever rule is parsed first, while the second rule remains dead code.
• 7. Neglecting internal links post-launch: After deploying server redirects, update your internal website hyperlinks so that internal navigation links directly to the new 200 OK URLs. Relying on redirects for internal site navigation slows down internal browsing and exhausts crawler resources.

Frequently asked questions about redirect maps

How many 301 redirects can a website have?

There is no technical ceiling on the total number of 301 redirects a website can host. Major enterprise sites, e-commerce stores, and publishers routinely maintain hundreds of thousands of active 301 redirects. However, server performance depends on implementation. While Apache .htaccess files with tens of thousands of lines can slow down disk read times on every page request, server-level Nginx maps or edge-routed Cloudflare rules execute in sub-millisecond lookups with virtually zero performance overhead.

Do 301 redirects pass 100% of PageRank link equity?

Google's search relations team has confirmed that 301 redirects pass approximately the same degree of PageRank equity as direct internal hyperlinks (historically estimated around 95% to 99%, accounting for normal link decay). However, link equity is only transferred effectively when the destination page is topically relevant to the original source URL. Redirecting an article about “B2B email deliverability” to an unrelated page about “office furniture” will not transfer ranking power.

How long should you keep 301 redirects active?

Google recommends maintaining 301 redirects active for a minimum of one full year following a site migration. This extended window ensures that search engine crawlers have discovered, re-crawled, and updated the canonical URL for every redirected page, and provides ample time for external third-party websites linking to your old URLs to update their backlink references. For high-authority legacy domains, keeping server redirects active permanently is optimal.

What is the difference between a 301 and a 308 redirect?

Both 301 and 308 redirects signal permanent address changes and transfer search engine link equity identically. The distinction lies in HTTP request method preservation. Under early HTTP specifications, browsers frequently mutated an HTTP POST request into a GET request when following a 301 redirect. The newer HTTP/1.1 308 Permanent Redirect specification explicitly forbids method mutation, ensuring that form submissions and API payloads remain intact.

Why does my browser cache 301 redirects so aggressively?

Because an HTTP 301 status code signifies a permanent move, modern web browsers cache the redirect response in local storage. Once your browser visits a 301 redirect, subsequent visits to that URL will bypass your server entirely and jump immediately to the target page from local browser cache. When developing and testing new redirect rules, always test using Private/Incognito browsing mode or keep developer tools open with Disable cache checked.

When should I use a 410 Gone status code instead of a 301 redirect?

Use a 410 status code when an old page has been permanently deleted, discontinued, or pruned from your site, and no relevant counterpart or parent category exists to take its place. While Google will repeatedly re-crawl a 404 Not Found URL for weeks to verify whether it was deleted by accident, a 410 Gone response explicitly signals intentional deletion. Googlebot purges 410 URLs from search result indexes much faster, protecting your crawl budget.

For strategic support in scaling organic SaaS visibility and enterprise growth, explore our SaaS Promotion and SEO Services.