Two Configs, One Source
Generate idiomatic Apache .htaccess and Nginx return rules from the same list, so you never hand-translate rewrite syntax between servers.
Build clean Apache and Nginx redirect blocks from a simple list of old and new URLs.
Updated
Loading tool interface...
/old-page) or a full URL; destinations can be a path or an absolute URL.2 redirects ready — no loops or conflicting sources detected.
# Apache .htaccess redirect rules
# Place at the document root, above any existing rewrite rules.
<IfModule mod_alias.c>
Redirect 301 /old-page /new-page
Redirect 301 /blog/2020/launch https://example.com/launch
</IfModule># Nginx redirect rules
# Add inside the relevant server { } block, then reload Nginx.
server {
location = /old-page {
return 301 /new-page;
}
location = /blog/2020/launch {
return 301 https://example.com/launch;
}
}Use 301 for permanent moves so search engines transfer ranking signals to the destination, and 302 only for temporary changes you intend to reverse. Apache rules go in a .htaccess file at your document root; Nginx rules go inside the matching server block and require a reload to take effect. Always test on staging before deploying redirects to production.
The .htaccess & Nginx Redirect Generator turns a plain list of source and destination URLs into production-ready redirect rules for both Apache (.htaccess) and Nginx, side by side. Add a row for each move, choose 301 or 302, and copy the exact block your server needs.
Why it matters for SEO: Redirects are how you preserve ranking signals when URLs change. A correct 301 passes link equity to the new page; a malformed rule, an accidental redirect loop, or two rules fighting over the same source can deindex pages, trap crawlers, and burn crawl budget.
Site migrations & redesigns: When you restructure URLs, change your CMS, or move domains, generate the full mapping once and paste it into your server config instead of hand-writing fragile rewrite syntax.
Loop & conflict safety: The tool detects redirect loops (A→B→A and self-redirects), multi-hop chains that waste a request, and duplicate or conflicting sources that point one path at two destinations — so you catch the dangerous cases before they hit production.
301 vs 302 done right: Pick permanent (301) for moves that should pass ranking signals, or temporary (302) for changes you intend to reverse, and the generator emits the correct status code in both Apache and Nginx syntax.
After generating redirect rules, deploy them and confirm each chain with the Redirect Checker, then verify the destination's response headers and canonical alignment.
Generate idiomatic Apache .htaccess and Nginx return rules from the same list, so you never hand-translate rewrite syntax between servers.
Catch redirect loops, self-redirects, multi-hop chains, and duplicate sources that point one path at two destinations before they reach production.
Emit permanent or temporary status codes per rule so ranking signals pass on moves that should be permanent and stay reversible on the ones that should not.
Answers about .htaccess & Nginx Redirect Generator
Use a 301 for permanent moves and a 302 only for temporary ones. A 301 tells search engines the change is permanent so they transfer ranking signals to the new URL, while a 302 keeps the original URL indexed because the move is expected to be reversed.
Apache rules go in a .htaccess file at your site's document root, and Nginx rules go inside the relevant server block in your site config. After adding Nginx rules you must reload or restart Nginx; .htaccess changes apply on the next request with no reload needed.
It follows each source through your rules and flags any path that eventually points back to itself. It catches direct loops like A to B and B to A, self-redirects where a URL targets itself, and multi-hop chains where one redirect lands on another redirect instead of the final destination.
You can redirect to either an on-site path or a full external URL. Enter a path like /new-page for same-site moves or a complete address like https://example.com/new for cross-domain redirects, and the generator emits valid Apache and Nginx syntax for both.