Create 301 and 302 redirect rules for .htaccess, nginx.conf, or next.config.js. Add as many URL pairs as you need and copy the ready-to-paste configuration snippet.
A 301 is a permanent redirect — it tells search engines that the page has moved forever and passes virtually all link equity to the new URL. A 302 is temporary; Google continues to index the original URL and does not pass equity.
Historically Google reported a small loss, but current guidance is that well-implemented 301 redirects pass virtually all link equity. The key is to redirect directly from old to new URL — avoid chains.
Redirects
| From | To | Type | |
|---|---|---|---|
Output
Redirect 301 /old-blog-post /new-blog-post Redirect 301 /services https://sluggenius.com/tools
Use 301 for permanent moves so link equity passes to the new URL. Use 302 only for temporary redirects.
Generate redirect rules for Apache, Nginx, or Next.js in seconds — protect your SEO during any URL change.
Enter the old (From) path and the new (To) URL for each redirect you need.
Select 301 (permanent) or 302 (temporary) for each redirect rule.
Switch between Apache .htaccess, Nginx config, or Next.js config output.
Paste the generated rules into your server configuration and reload.
When you move or delete a page, any backlinks pointing to the old URL become broken references. Search engines follow those links and encounter a 404 error, causing the link equity (PageRank) accumulated by those backlinks to simply disappear. A 301 redirect preserves that equity by telling search engines: “This page has permanently moved — transfer all ranking signals to the new URL.” Every major site migration, domain change, or URL restructure should include a comprehensive redirect plan built and tested before the new site goes live.
The difference between 301 and 302 redirects matters far more than most site owners realize. A 301 (permanent) redirect signals that the original URL is gone forever and passes close to 100% of its link equity to the destination. A 302 (temporary) redirect tells Google to continue indexing the original URL and does not pass equity to the new page. Using a 302 when you mean a 301 — a surprisingly common mistake — means your new page may never inherit the ranking power of the original, even if the "temporary" redirect stays in place for years.
Redirect chains compound crawl and equity problems.A chain occurs when URL A redirects to URL B, which redirects to URL C. Each additional hop costs crawl budget, introduces latency for real users, and dilutes the amount of link equity passed to the final destination. Google recommends flattening chains so the old URL redirects directly to the final target URL. When auditing your redirects, trace every chain back to its source and update it to point directly to the canonical destination.