Skip to content

301 Permanent Redirect Generator

Free

Generate 301 permanent redirect rules for Apache .htaccess, Nginx, and Vercel. Preserve link equity when moving pages or restructuring your website.

generate 301 redirect301 redirect htaccesspermanent redirect generator
All SEO Tools

Settings guide

When to use 301 vs 302:

  • ·301 Permanent: Site migrations, URL restructuring, domain moves, merging duplicate pages. Link equity transfers fully.
  • ·302 Temporary: A/B testing alternate URLs, seasonal promotions, maintenance pages, split testing. Link equity stays at the original URL.
  • ·307 Temporary (HTTP/1.1): Same as 302 but preserves the HTTP method. Use instead of 302 for modern servers.

Apache .htaccess format:

Redirect 301 /old-path https://domain.com/new-path

Or with mod_rewrite: RewriteRule ^old-path/?$ /new-path [R=301,L]

Nginx format:

return 301 https://domain.com/new-path; (inside a location block)

Vercel (vercel.json):

{ "source": "/old-path", "destination": "/new-path", "permanent": true }

Redirect chains:

Never create chains — A → B → C. Chains lose link equity at each hop and slow page load. After creating redirects, audit for chains and consolidate: A → C directly.

Format comparison

301 redirect vs canonical tag:

A canonical tag tells Google which version of a page is preferred — the original still exists and is served. A 301 redirect replaces the old URL entirely and sends users and crawlers to the new URL. For duplicate content between URLs, a 301 is a stronger consolidation signal than a canonical tag.

301 redirect vs .htaccess rewrite:

A basic 301 redirect rule in .htaccess (Redirect 301) is simpler and sufficient for most use cases. An .htaccess RewriteRule with mod_rewrite is required for pattern-based redirects (wildcards, regex), trailing slash normalization, and complex URL transformations. This generator supports both formats.

How it works

1

Enter your URL pairs

Add your old (source) URLs and their corresponding new (destination) URLs.

2

Select server format

Choose Apache .htaccess, Nginx, or Vercel based on your server stack.

3

Review the redirect rules

Preview the generated rules and confirm each source-destination pair is correct.

4

Deploy and verify

Add the rules to your server config, then test each redirect with a browser or HTTP status checker.

About this format

A 301 redirect is the HTTP status code for a permanent page move. When a user or search engine crawler requests the old URL, the server responds with "301 Moved Permanently" along with the new URL location. The browser and crawler follow the redirect automatically. For SEO, a 301 redirect signals to Google that the old URL's ranking signals — backlinks, PageRank, authority — should transfer to the new URL.

Using the wrong redirect type is a common SEO mistake. A 302 (temporary) redirect does not transfer link equity and tells Google the original URL may return. Using no redirect at all leaves a broken link that returns 404, destroying the link equity that page had accumulated. A 301 is the correct choice for any permanent page move, URL restructuring, domain migration, or site consolidation.

This generator produces properly formatted 301 redirect rules for Apache (.htaccess), Nginx server blocks, and Vercel configuration files. Paste in your source and destination URL pairs, select your server type, and download the ready-to-deploy redirect rules.

Frequently asked questions

Does a 301 redirect pass all link equity to the new URL?+
Google has stated that 301 redirects pass the vast majority of PageRank — practically all of it in modern Google. Older guidance suggested a 15% loss per hop, but current evidence shows near-complete transfer. The most important thing is to avoid redirect chains, which compound any loss across multiple hops.
How long does it take Google to recognize a 301 redirect?+
Google typically processes a 301 redirect within a few days to a few weeks. The old URL drops from the index, the new URL is indexed in its place, and ranking signals gradually transfer. For important pages, submitting the new URL through Google Search Console's URL Inspection tool speeds the recrawl.
Can I redirect an entire domain with 301 redirects?+
Yes. A domain migration — moving all content from one domain to another — uses 301 redirects for every URL. The most important redirects are your highest-traffic and highest-authority pages. Redirect the homepage and all high-value pages first, then use pattern-based redirects for the rest of the URL structure.
What happens to my rankings when I add a 301 redirect?+
Rankings typically dip temporarily after a redirect while Google processes the change, then recover and often stabilize at similar positions as the old URL. Permanent drops are usually caused by redirect chains, targeting different content at the new URL, or technical issues preventing proper crawling of the new URL.
Should I redirect old pages that have no backlinks?+
Redirect any URL that receives traffic or is linked internally, regardless of external backlinks. For truly abandoned URLs with no traffic, no backlinks, and no internal links, returning a 404 is acceptable. Maintaining unnecessary redirects for hundreds of dead pages adds configuration overhead without SEO benefit.

Related tools and guides