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.
.htaccess & Nginx Redirect Generator for 301 and 302 Rules
DR: .htaccess & Nginx Redirect Generator checks turn from→to redirect rows into ready-to-paste apache and nginx rules. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Build clean Apache and Nginx redirect blocks from a simple list of old and new URLs.
Atualizado
Loading tool interface...
Repeatable from-to redirect rows Per-rule 301 or 302 status Side-by-side Apache and Nginx output Redirect loop and chain detection Duplicate and conflicting source warnings
What does .htaccess & Nginx Redirect Generator do?
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.
When should you use .htaccess & Nginx Redirect Generator?
.htaccess & Nginx Redirect Generator is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
Como usar esta ferramenta
- 1 Add a row for each redirect with its source and destination URL.
- 2 Choose 301 (permanent) or 302 (temporary) per row.
- 3 Review the loop and conflict warnings on the right.
- 4 Copy the Apache or Nginx block straight into your server config.
What should you do next?
After generating redirect rules, deploy them and confirm each chain with the Redirect Checker, then verify the destination's response headers and canonical alignment. Then move to the related checks below to confirm the fix on the live canonical page.
O que você ganha
Loop & Conflict Detection
Catch redirect loops, self-redirects, multi-hop chains, and duplicate sources that point one path at two destinations before they reach production.
Correct 301 vs 302
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.
Frequently Asked Questions
Respostas sobre .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.