Redirect Rule Generator

Pick the right redirect type — 301, 302, 307, 410, or 451 — and get the correct, ready-to-paste config for Apache, Nginx, Next.js, Cloudflare, Netlify, or IIS. Using the wrong status code costs rankings or link equity, this makes sure you use the right one.

Why use our Redirect Rule Generator

Every redirect type that matters

301, 302, 307, 410, and 451, each does something different to how Google treats the URL. Pick the right one instead of defaulting to 301 for everything.

Correct syntax for your actual platform

Apache, Nginx, Next.js, Cloudflare, Netlify, and IIS each need different config syntax, generated correctly so you don't have to memorize it.

Bulk migrations with pattern matching

Match by exact URL, "starts with", "contains", or full regex, migrate an entire URL structure with one rule instead of one redirect per page.

Free, no signup, nothing installed

This generates config you copy into your own server, it never touches your live traffic or requires installing anything on our end.

Redirect type

Match type

From path

To path

Real Redirect Rule Generator example: before vs. after

A site migration where 40 old product pages needed to map to a new URL structure, one wildcard rule instead of 40 individual redirects.

Before · Manual approach

Individual redirects to write

One rule per URL, error-prone, and easy to get the status code wrong across a big migration.

After · With pattern matching

Wildcard rule, correct syntax

One "starts with" rule covers the whole old /products/ structure, generated in the correct syntax for the actual server.

Frequently Asked Questions

Does this tool actually apply the redirects to my site?

No, and no tool honestly can without controlling your DNS or running on your server. This generates the correct config, you copy it into your own Apache/Nginx config, next.config.js, Cloudflare account, Netlify _redirects file, or IIS web.config. We never touch your live traffic.

When should I use 302 instead of 301?

Use 302 (or 307) when the redirect is genuinely temporary, an A/B test, a seasonal page, planned maintenance. 302 tells search engines to keep the original URL indexed and not pass ranking signals to the destination, which is exactly wrong for a permanent move.

What's the actual difference between 302 and 307?

Both are temporary, but 307 strictly preserves the original HTTP method. A 302 redirect on a POST request may get re-sent as GET by some clients, a 307 guarantees it stays POST, this matters for API endpoints and form submissions.

Should I use 410 or just delete the page and let it 404?

410 is a deliberate signal, it tells Google you intentionally removed the content, which gets it dropped from the index faster than a 404 (which Google treats as "maybe temporary, I'll keep checking"). Use 410 when you're certain the content is gone for good.

Check your existing redirects too

SEOMentor's full scan flags redirect chains, loops, and broken links automatically, no manual checking needed.

Scan your site free