Redirect Rule Generator

Old path

New address

Where it goes

Response code

301, 302, 307 or 308.

Result

The rulelocation = /old-page { return 301 https://example.com/new-page; }
Formatnginx
Code301
What the code meansa permanent redirect; signals pass to the new URL
Source path/old-page
What mattersAvoid chains: every extra hop loses signals and slows crawling. Point the old URL straight at the final one.

301 forever, 302 for now

Builds a redirect rule for nginx, Apache or Next.js with the response code you choose.

The code is picked by meaning, not by habit. A 301 tells a search engine 'this URL is not coming back, move everything to the new one', and the old URL gradually leaves the index. A 302 says 'this is temporary', and the old URL is the one that stays.

307 and 308 do the same but preserve the HTTP method: a POST stays a POST rather than turning into a GET. For ordinary pages that makes no difference; for forms and APIs it is essential.

What this calculator shows

A ready rule in the syntax of the server you chose
What the chosen response code means
A warning about redirect chains

What to keep in mind

The rule targets a single URL. Section-wide moves use regular expressions or a redirect map.
A redirect should lead to a page with matching content: sending every old URL to the homepage is treated as a soft 404.

FAQs

301 or 302 — which should I use?

301 when the URL changes for good. 302 only for genuinely temporary situations like maintenance or an A/B test.

Does a 301 pass link equity?

Yes, essentially all of it. Google has confirmed the loss is negligible when the redirect points to a relevant page.

Why are redirect chains a problem?

Every hop spends crawl budget and adds latency for the visitor. Past three hops a crawler may simply stop following.

How does a 308 differ from a 301?

308 preserves the request method: a POST stays a POST. To search engines both mean the same thing — a permanent move.

Worked example

Moving one page

Input: /old-page → https://example.com/new-page, 301, nginx

Output: location = /old-page { return 301 https://example.com/new-page; }

Note: The equals sign makes the match exact: without it the rule also catches /old-page-2 and /old-page/anything. It is the commonest mistake in single-URL nginx redirects.

Useful links

All tools in Dev Tools

Redirect Rule Generator

Result

Related tools

HTTP Status Code Lookup

Robots.txt Generator

Meta Tag Length Checker

Useful links