301 Redirect Generator
Generate bulk redirect rules for Apache, Nginx, Netlify, Vercel, Cloudflare, Next.js, IIS and CSV — instantly. Built for SEO migrations, domain changes and URL restructures.
Passes full SEO link equity · CSV upload · Download file · No signup
Generate Redirect Rules
Paste one URL per line. Old and new URLs must match line by line.
ⓘEach old URL must match a new URL on the same line number. Empty lines are ignored automatically.
Redirect 301 /old-page https://example.com/new-page
What is a 301 redirect?
A 301 redirect is a permanent HTTP status code that tells browsers and search engine crawlers that a URL has moved to a new address — permanently. The number 301 is the HTTP status code itself, sitting in the 3xx "redirect" range.
When a user or Googlebot visits a URL that has been 301-redirected, they are automatically forwarded to the new destination. From an SEO perspective, Google treats a 301 as a signal to consolidate ranking signals: the authority, backlinks, and content relevance built by the old URL are transferred to the new one over time.
This makes the 301 the correct redirect to use for any permanent URL change — domain migrations, URL restructures, HTTPS upgrades, trailing slash fixes, and page merges.
| HTTP Status | Type | SEO Value Passed? | Use Case |
|---|---|---|---|
| 301 | Permanent | Yes (majority) | Domain moves, URL restructures, HTTPS migration |
| 302 | Temporary | Partial / unclear | A/B tests, maintenance pages, short-term redirects |
| 307 | Temporary (strict) | Partial | Method-preserving temporary redirects |
| 308 | Permanent (strict) | Yes | Method-preserving permanent redirects |
Supported redirect formats
This tool generates production-ready redirect rules for every major server and platform:
Apache (.htaccess)
ServerRedirect 301 /old-page https://example.com/new-page Add to your .htaccess file in the site root.
Nginx (rewrite)
Serverrewrite ^/old-page$ https://example.com/new-page permanent; Place inside your server{} block.
IIS (web.config)
Server<rule name="Redirect …" stopProcessing="true"> Requires the URL Rewrite IIS module.
Netlify (_redirects)
Platform/old-page https://example.com/new-page 301 Save as _redirects in your publish directory.
Vercel (vercel.json)
Platform{ "source": "/old", "destination": "…", "permanent": true } Merge into the redirects array in vercel.json.
Next.js (next.config.js)
Platform{ source: '/old', destination: '…', permanent: true } Return array from the redirects() function.
Cloudflare Redirect Rules
Platformif (http.request.uri.path eq "/old") then redirect to "…" status 301 Create one rule per block in Cloudflare Dashboard.
CSV Export
ExportOld URL,New URL Import into spreadsheets, crawlers, or other tools.
When should you use a 301 redirect?
Any time a URL permanently changes its address, a 301 ensures you don't lose organic traffic or ranking signals. Here are the most common scenarios:
Site migrations
Moving your entire website to a new domain, subdomain, or CMS. Every old URL needs a 301 to its new equivalent.
HTTPS upgrades
Redirecting all http:// pages to https://. Critical for security and now a confirmed Google ranking factor.
URL restructuring
Changing URL slugs, removing category prefixes, or flattening your site architecture.
Merging duplicate pages
Consolidating two pages covering the same topic into one stronger, authoritative page.
Domain rebranding
Carrying existing authority to a new brand domain without losing years of link equity.
Trailing slash fixes
Ensuring /page and /page/ resolve to the same canonical URL to avoid duplicate content.
301 vs 302 redirects: what's the difference?
The distinction between a 301 and a 302 is one of intent and permanence — and it carries real SEO consequences.
A 301 (Moved Permanently) tells Google and other search engines that the old URL is gone for good. Google will update its index to the new URL, transfer the accumulated link equity, and eventually stop crawling the old address. This is what you want for any structural change to your site.
A 302 (Found / Moved Temporarily) signals that the redirect is short-lived. Google will typically keep indexing the original URL and treat the destination as a temporary address. Link equity transfer is inconsistent. If you accidentally use a 302 for a permanent move, your new page may take much longer to rank — or may never fully inherit the authority of the old URL.
Rule of thumb: If you are not going to restore the original URL within a few weeks, always use a 301. When in doubt, use 301.
Common redirect mistakes to avoid
Even a well-intentioned redirect strategy can harm your SEO if implemented incorrectly. Avoid these frequent errors:
Redirect chains
Chaining multiple redirects together (A → B → C) forces crawlers to make several HTTP requests. Each hop in the chain can dilute the equity passed and slow down page crawling. Always redirect directly from old to new.
Redirect loops
When two URLs redirect to each other, browsers and crawlers get stuck in an infinite loop. This creates 5xx errors for users and prevents Google from indexing either page.
Using 302 for permanent moves
As covered above, using a temporary redirect for a permanent URL change causes link equity loss and delays ranking recovery. Always use 301 for permanent changes.
Redirecting everything to the homepage
Mass-redirecting hundreds of deleted pages to the homepage is called a "soft 404" in Google Search Console. Google ignores these and may penalise the site for manipulative redirect use.
Not redirecting protocol or www variations
Failing to redirect http:// to https://, or www to non-www, creates duplicate content signals and splits your link equity across multiple versions.
Forgetting to update internal links
Redirects are a safety net, not a permanent solution for internal link hygiene. Update your internal links to point directly to the new URL to avoid unnecessary redirect hops.
How to use this 301 Redirect Generator
Five steps from pasting URLs to deploying your redirect rules:
- 01
Paste your old URLs
Enter each source URL on its own line in the Old URLs field. You can paste a few or hundreds — the tool handles bulk input without any extra formatting.
- 02
Paste your new URLs
Enter each destination URL on its own line in the New URLs field. The order must match exactly: line 1 in Old URLs connects to line 1 in New URLs.
- 03
Select your redirect format
Choose from 8 formats: Apache (.htaccess), Nginx, Netlify _redirects, Vercel JSON, Cloudflare Redirect Rules, Next.js next.config.js, IIS web.config, or CSV export.
- 04
Generate, copy, or download
Click Generate Redirects. Review the output, then click Copy to copy to clipboard or Download to save the file directly with the correct filename.
- 05
Deploy and monitor
Add the rules to your server configuration. Test in a staging environment first, then monitor Google Search Console → Coverage and Crawl Stats after deployment.
- 06
Optional: upload a CSV
If you have an existing redirect map in a spreadsheet, export it as CSV with columns Old URL and New URL, then drag it into the tool or use the Upload CSV button to auto-populate both fields.
Need help with a site migration?
Our technical SEO team handles full migration planning, redirect mapping, and post-migration audits.
Frequently asked questions
Everything you need to know about 301 redirects and how this tool works.
What is a 301 redirect?
A 301 redirect is a permanent HTTP redirect that tells both browsers and search engines that a URL has permanently moved to a new location. It is the correct redirect type for any lasting URL change and transfers the majority of ranking signals from the old URL to the new one.
Does a 301 redirect pass SEO value?
Yes. Google has confirmed that 301 redirects pass the majority of PageRank (link equity) to the destination URL. While there was a historical belief that some value was lost, Google has clarified that 301s are treated equivalently to the destination URL for ranking purposes.
When should I use 301 instead of 302?
Use 301 any time a URL has moved permanently and you will never restore the old address. Use 302 only for genuinely temporary situations such as A/B test variants, geo-targeted landing pages, or maintenance pages. Using 302 for permanent changes causes confusion in Google's index and can delay or prevent proper ranking consolidation.
Can I use this tool for bulk redirects?
Yes. The tool is designed for bulk use. Paste one old URL per line and one new URL per line — the tool matches them by position and generates all the rules at once. It can handle hundreds of URL pairs in a single session.
What format should I use for Apache or Nginx?
Select "Apache (.htaccess)" if your web server uses Apache. The output is ready to paste into your .htaccess file. Select "Nginx" if your server uses Nginx — the output generates rewrite rules suitable for an Nginx server block. The tool automatically uses the URL path for Apache and Nginx rules.
Do redirects help after a site migration?
They are essential. Without 301 redirects from every changed URL, users and search engine bots will land on 404 pages. This causes organic traffic to drop, backlink equity to be lost, and indexed pages to disappear from Google. A complete redirect map is the single most important deliverable in any site migration.
How long does a 301 redirect take to be picked up by Google?
It depends on your crawl frequency. Highly-crawled sites may see the change reflected in Google Search Console within days. For lower-traffic sites, it can take a few weeks. Submitting an updated sitemap after migration helps accelerate re-indexing.
Related SEO Tools
Other free tools that work well alongside the 301 Redirect Generator.
Robots.txt Generator
Control which pages crawlers can access — essential after any site migration or URL restructure.
Meta Title & Description Checker
Audit page titles and meta descriptions to ensure redirected pages meet on-page SEO standards.
Free SEO Audit Tool
Run a full on-page SEO audit post-migration to catch missing tags, broken links and crawl issues.
Page Speed Test
Check Core Web Vitals and load performance, critical metrics after switching servers or hosting.
LLMs.txt Generator
Create an llms.txt file to guide AI crawlers across your new URL structure post-migration.
Local SEO Auditor
Check local SEO signals after migration to ensure location pages are correctly indexed.
Explore more free SEO tools
Meta checker, robots.txt generator, page speed test and more.