ES
navigate Enter open Esc close
E-commerce Migration

E-commerce Store 301 & 308 Redirect Generator

Generate bulk redirect rules for e-commerce store migrations across WooCommerce, Shopify, and PrestaShop. Export verified syntax for Nginx, Apache (.htaccess), and Cloudflare Bulk CSV.

Diagnostics & Mapping Validation
0 valid
Enter URL mappings above to run live diagnostics.

            

Technical Guide: E-commerce Redirects & Store Migrations

When migrating an online store across platforms or restructuring catalog slugs, choosing the right HTTP status code and server directives provides strong signals to search engine crawlers and prevents broken customer links.

HTTP Status Codes (301 vs 308)

301 Moved Permanently: Permanent redirect for SEO migrations. Method preservation is not guaranteed; POST may be changed to GET by clients.

308 Permanent Redirect: Defined in RFC 9110, 308 mandates that the client strictly preserves the request method and body.

302 Found: Temporary redirect; method preservation not guaranteed.

307 Temporary Redirect: Temporary redirect with strict method preservation.

Server Directives & Context

NGINX: Uses exact location matching location = /old { return 301 /new$is_args$args; } inside the server { } block.

Apache: Uses mod_rewrite with anchored regex RewriteRule ^old$ /new [R=301,L] for exact 1:1 matching and query control (using QSD when query strings should be discarded).

Cloudflare Bulk Redirects

Cloudflare Bulk Redirects handle high-volume URL migrations at the edge without putting load on your origin server. The generated CSV conforms to the official 7-column schema: Source URL, Target URL, Status code, Preserve query string, Include subdomains, Subpath matching, Preserve path suffix.

Avoiding Chains and Loops

Redirect chains (A → B → C) waste crawler crawl budget and add latency. Redirect loops (A → B → A) cause browser failure. Our live diagnostics detect duplicate sources, self-redirects, chains, and circular loops before you deploy.

Frequently Asked Questions

Should I use 301 or 308 redirects for e-commerce catalog migrations?
Use 301 (Moved Permanently) for standard web pages, products, and categories where search engines update indexation and method preservation is not required (POST requests may be changed to GET by clients). Use 308 (Permanent Redirect) for API endpoints and checkout/cart POST requests where the original HTTP request method and body must be strictly preserved across the redirect.
Where should generated NGINX redirect rules be placed?
NGINX location blocks with return directives must be placed inside the active server { ... } block configuration for your domain (usually located in /etc/nginx/sites-available/ or /etc/nginx/conf.d/).
Why use Apache mod_rewrite instead of mod_alias for 1:1 e-commerce redirects?
Apache mod_alias Redirect uses prefix/path matching and cannot strip incoming query strings. mod_rewrite with anchored regex patterns (^product$) ensures strict 1:1 exact matching without accidental subpath redirects (such as /product/reviews), and provides full control over query string preservation or stripping via the QSD (Query String Discard) flag.
Can URL fragment identifiers (#) be matched and redirected server-side?
No. According to RFC specifications, web browsers never transmit URL fragments (#section) in HTTP request headers. Servers only receive the path and query string. However, you can safely specify a fragment in the target URL (e.g. /product#reviews).
How do I import the generated CSV into Cloudflare Bulk Redirects?
In the Cloudflare dashboard, navigate to Account Home > Configurations > Lists. Create a new Redirect List, click "Upload CSV", and select the downloaded file. Then create a Bulk Redirect Rule referencing that list.

Related Webmaster & E-commerce Tools

PrestaShop CSV Validator

Validate product and category import files before store upload

Individual Redirect Generator

Generate single 301/302 redirects with PHP and Meta Refresh snippets

.htaccess to NGINX Converter

Convert Apache configuration files and rewrite rules to NGINX

Technical SEO Auditor

Inspect HTTP status codes, canonicals, and indexability

Share this tool

Help others by sharing this free tool.