HTACCESS Redirect Generator

Easily generate .htaccess code snippets for 301, 302, and other common redirects.

How to use this tool

Enter each redirect pair in a separate row. For each redirect, provide the Old URL (where users are coming from) and the New URL (where they should be redirected to).

Example: If yoursite.com/old-about.html moved to yoursite.com/about:
Old URL: /old-about.html
New URL: /about

The tool generates redirects for your .htaccess file. Each redirect preserves your SEO rankings when moving pages.

Redirect Type

301

Permanent

302

Temporary

307

Temp (HTTP/1.1)

308

Perm (HTTP/1.1)

301: SEO-friendly permanent redirect (most common) • 302: Temporary redirect • 307/308: Modern HTTP/1.1 equivalents

Common Redirect Templates

Enter Your URL Redirects

Old URLs (From)

New URLs (To)

About .htaccess Redirects

The .htaccess file is a configuration file for Apache web servers that allows you to control redirects, URL rewrites, and other server behaviors without modifying the main server configuration.

Key Features

301 Redirects - Permanent (SEO-friendly)
302 Redirects - Temporary redirects
SEO Preserved - Maintains rankings
No Restart - Works immediately

Common Use Cases

Moving pages to new URLs
Domain migrations
Fixing broken links
Consolidating duplicate content

Important Notes

Backup First: Always backup your .htaccess file before making changes
Placement: Add redirect rules at the top of your .htaccess file
Testing: Test redirects in incognito/private mode to avoid caching
Old URLs: Must start with / for same-server redirects
New URLs: Can be relative (/page) or absolute (https://example.com/page)

Redirect Type Reference

301 Permanent: Page moved permanently. Search engines transfer rankings. Use for permanent URL changes.

302 Temporary: Page moved temporarily. Search engines keep original URL indexed. Use for A/B testing or maintenance.

307 Temporary: HTTP/1.1 temporary redirect. Preserves request method (POST stays POST).

308 Permanent: HTTP/1.1 permanent redirect. Like 301 but preserves request method.

Was this result helpful?

Thank you for your feedback!

Your input helps us improve our tools.

Add more details about your experience

Help us fix issues with this tool

What went wrong? *

/1000 characters (min. 10 required) (limit reached)

What output did you expect? (Optional)

/1000 characters (limit reached)

How to Use

Step-by-step guide 4 steps

1 Choose Redirect Type: Select 301 (Permanent) for a permanent move, or 302 (Temporary) for a short-term change.
2 Enter URLs: Input the Old URL (Source) and the New URL (Destination).
3 Generate Code: Click "Create .htaccess Code".
4 Implement: Paste the resulting `Redirect 301` or `RewriteRule` snippet into your website's .htaccess file.

FAQ

Common questions 3 questions

What is the SEO difference between a 301 and a 302 redirect?

A 301 redirect passes almost all (90-100%) of the link equity (PageRank) to the new URL, making it the essential choice for permanent moves. A 302 passes little to none.

Why use a server-side redirect (via .htaccess) over a JavaScript redirect?

Server-side redirects (301/302) are faster and are the official signal to search engines that a page has moved, ensuring SEO value is retained.

Can I redirect an entire folder?

Yes, you can generate code to redirect all pages within an old directory to a new one, which is crucial during a website structure change or migration.

Use Cases & Examples

Real-world applications 3 examples

SEO Link Equity

Example Keyword: generate 301 permanent redirect
Preserve SEO authority when an important page URL must be changed or deleted.

Website Migration

Example Keyword: create htaccess redirect rules
Set up bulk redirects after restructuring permalinks or moving content to a new domain.

URL Canonicalization

Example Keyword: redirect www to non-www htaccess
Force users and search engines to use the preferred domain version (e.g., with or without 'www').