301 Redirect

A 301 redirect is an HTTP status code — 301 Moved Permanently — that tells browsers and search engines a page has moved to a new URL for good. When a visitor or crawler requests the old address, the web server responds with the 301 status and a Location header pointing to the new destination. The browser follows it automatically, and search engines transfer ranking signals — including link equity — from the old URL to the new one.

Think of it as filing a permanent change-of-address form with the post office. Mail sent to your old house gets forwarded to the new one. A 301 redirect does the same for web traffic.

What Does a 301 Redirect Indicate?

A 301 redirect indicates that the requested resource has been permanently moved to the URL specified in the Location response header. It is one of several HTTP redirection status codes, grouped in the 3xx class, and is the most widely used method for permanent URL forwarding.

Key characteristics of what a 301 signals:

• Permanence: The old URL will not serve content again. Search engines should de-index it and replace it with the new URL in their index.
• SEO value transfer: Google and other search engines pass ranking signals — including PageRank — through 301 redirects to the new destination.
• Automatic browser behavior: All major browsers follow a 301 response without user interaction. The redirect happens server-side, before any page content loads.

The HTTP response itself looks like this:

HTTP/1.1 301 Moved Permanently
Location: https://www.example.com/new-page

Launch your affiliate program today

Set up advanced tracking in minutes. No credit card required.

Request demo Start 30-days free trial

How Does a 301 Redirect Work?

The process follows a simple request-response cycle involving the client (browser or crawler) and the web server.

Step 1: Client Requests the Old URL

A user clicks a link or types https://example.com/old-page. The browser sends an HTTP GET request to the server hosting that domain.

Step 2: Server Responds with 301

Instead of returning page content, the server responds with the 301 Moved Permanently status code and a Location header containing the new URL. The Location header identifies the destination; a response body may also be present.

Step 3: Browser Follows the Redirect

The browser reads the Location header and immediately issues a new GET request to the destination URL. This happens in milliseconds — the user sees only the final page.

Step 4: Search Engines Update Their Index

When a crawler like Googlebot encounters a 301, it notes the permanent move. Over subsequent crawls, it transfers ranking signals to the new URL and eventually drops the old URL from the index.

Why Should You Use 301 Redirects?

Without a 301 redirect, moving a page leaves behind a dead end. Visitors see a 404 error. Search engines lose the ranking value built on the old URL. Both outcomes hurt your site.

Preserve SEO Rankings

When you redirect an old URL to a new one with a 301, search engines pass the accumulated link equity — backlinks, authority signals, and ranking history — to the destination. As Google’s John Mueller has stated, PageRank can forward through both 301 and 302 redirects, with the redirect helping Google pick a canonical URL and concentrate signals there.

Protect User Experience

Visitors who bookmarked the old URL or followed an outdated link land on the correct page instead of a 404 error. The redirect is seamless — no intermediate page, no “click here to continue” message.

Join our newsletter

Be the first to know about new features and product updates.

Email address

Subscribe

When to Use a 301 Redirect

Use a 301 redirect whenever the old URL will never serve content again. Here are the most common scenarios:

When NOT to Use a 301

• Temporary content moves: If you plan to restore the original URL, use a 302 (temporary) redirect instead. A 301 tells search engines to de-index the old URL, which makes reverting slow and unpredictable.
• A/B testing: Redirecting traffic for split tests should use JavaScript-based or 302 redirects so the original URL stays indexed.
• Geotargeting or device-based serving: These scenarios call for conditional logic, not blanket permanent redirects.

What Is the Difference Between a 301 and 302 Redirect?

A 301 signals a permanent move, while a 302 signals a temporary one. Choose based on the intended duration and the URL you want search engines to treat as canonical.

Neither code guarantees a ranking outcome. Test the destination, tracking parameters and attribution independently of the status choice.

301 vs. 308: Which Should You Use?

Both 301 Moved Permanently and 308 Permanent Redirect signal a permanent move. The difference is in how the HTTP method is handled during the redirect.

• 301: The client may change the request method from POST to GET on the redirected request. This is the default behavior per the Fetch Standard and is almost always what you want for web pages.
• 308: The client must preserve the original HTTP method. If the original request was a POST, the redirected request remains a POST.

Guidance: For standard web page redirects — the vast majority of use cases — use a 301. Reserve a 308 for API endpoints or form submissions where preserving the POST method matters.

How to Create a 301 Redirect

The implementation method depends on your web server and CMS. Here are the most common approaches.

Apache: .htaccess File

For sites running on Apache, add redirect rules to the .htaccess file in the site’s root directory:

Redirect 301 /old-page.html /new-page.html

RewriteEngine On
RewriteCond %{HTTP_HOST} ^oldsite\.com [NC]
RewriteRule ^(.*)$ https://newsite.com/$1 [L,R=301]

Nginx

Nginx does not use .htaccess. Add redirect rules to the server block configuration:

server {
    listen 80;
    server_name oldsite.com;
    return 301 https://newsite.com$request_uri;
}

WordPress Plugins

Plugins like Redirection or Yoast SEO Premium let you manage 301 redirects from the WordPress admin panel without editing server files. This is the most accessible method for non-technical users.

CMS-specific methods

Some hosted platforms provide redirect settings in their administration interface. Check the platform’s current documentation and confirm that the configured rule returns the intended HTTP status; an interface label alone does not verify the response.

PHP Header Redirect

For custom applications, you can send a 301 redirect programmatically:

header("HTTP/1.1 301 Moved Permanently");
header("Location: https://www.example.com/new-page");
exit();

How 301 Redirects Affect SEO

Link Equity Transfer

A permanent redirect is a strong canonicalization signal. Search engines must crawl and process the move, so timing and search visibility can vary. Avoid assuming that every migration has a fixed ranking dip or recovery period.

Indexing Timeline

Indexing changes depend on crawling and other canonicalization signals. Monitor the source and destination URLs instead of promising a fixed number of days.

Redirect Chains

A redirect chain occurs when a URL redirects to another URL, which itself redirects to a third. Each hop adds latency and another point of failure; avoid unnecessary chains rather than assuming a fixed loss of ranking value per hop. Google recommends keeping redirect chains to a minimum. Ideally, update all internal links to point directly to the final destination URL.

Common SEO Mistakes

• Redirecting everything to the homepage: Mass-redirecting old pages to the home page instead of relevant new pages creates a poor user experience and wastes link equity. Map each old URL to its closest equivalent new page.
• Using 302s for permanent moves: Search engines may not de-index the old URL, splitting ranking signals between two pages.
• Forgetting to update internal links: Even with redirects in place, update your site’s internal links to point directly to the new URLs. This reduces redirect chains and improves crawl efficiency.
• Leaving redirects in place forever without monitoring: Redirects accumulate during site migrations and redesigns. Audit them periodically and remove any that are no longer needed.

Can You Have Too Many 301 Redirects?

Yes. While there is no hard limit on the number of 301 redirects a site can have, excessive redirects create problems:

• Server overhead: Each redirect requires an additional HTTP request-response cycle. Hundreds of thousands of unnecessary redirects add server load.
• Crawl budget waste: Googlebot spends time following redirect chains instead of discovering new content. This is especially relevant for large sites.
• Redirect chains: Multiple sequential redirects slow navigation and complicate troubleshooting.

Best practice: Keep redirects to what is necessary. After a site migration, audit your redirect map and remove rules for URLs that no longer receive traffic or backlinks.

How Long Should You Keep 301 Redirects?

Keep migration redirects available while visitors, backlinks and crawlers still use the old URLs. Plan their lifetime as part of the migration:

• At least one year after the move, as a minimum.
• Permanently for URLs with significant backlinks or referral traffic. The cost of maintaining a redirect rule is negligible; the cost of losing link equity is not.
• Until traffic to the old URL drops to near zero for at least several months, if you must eventually remove them.

Monitor old-URL traffic in your analytics. A quiet analytics period does not prove that every external link or crawler has stopped using the old URL. Review backlinks, referral traffic and operational constraints before retiring a rule.

Can You Change a 301 Redirect?

Yes. You can update the destination URL of an existing 301 redirect at any time by modifying the rule in your .htaccess file, Nginx config, or CMS redirect manager.

However, be aware that:

• Search engines may have already indexed the intermediate destination. Changing it creates a new redirect chain that takes time to reprocess.
• If you change a 301 within days of implementing it, the impact is minimal. If you change one that has been in place for months, expect a longer reprocessing period.
• Best practice: plan your redirect map before implementing it, so you minimize mid-course corrections.

How Long Before 301 Redirects Take Effect?

From a user perspective, a 301 redirect takes effect immediately — the moment the server configuration is deployed, visitors are forwarded to the new URL.

From an SEO perspective, the timeline varies:

• Crawling: Googlebot must recrawl the old URL to discover the redirect. For high-authority sites, this can happen within hours. For smaller sites, it may take days or weeks.
• Indexing: After discovering the redirect, Google processes the signal and updates its index. This typically takes a few days to a few weeks.
• Ranking stabilization: The new URL may fluctuate in rankings for several weeks while signals are consolidated. Full stabilization can take a month or more for large-scale migrations.

Relevance to Affiliate Marketing & Affiliate Software

301 redirects matter in affiliate marketing for three groups: advertisers (merchants), publishers (affiliates), and affiliate program managers.

For Advertisers & Merchants

When you run an affiliate program, your affiliate links are the pipeline between your partners and your store. If you change your site structure — migrating to a new domain, switching from HTTP to HTTPS, or restructuring product URLs — every affiliate link pointing to the old URLs breaks unless you implement 301 redirects.

Practical example: A merchant rebrands from oldstore.com to newstore.com. Hundreds of affiliates have deep-linked to product pages on the old domain. Without 301 redirects, every one of those links returns a 404. Affiliates lose commissions, and the merchant loses revenue. With a proper 301 redirect map, visitors can reach the corresponding pages on the new domain, and affiliate tracking parameters must be deliberately preserved and tested through the redirect.

Limitations to know:

• Some affiliate platforms append click IDs and campaign parameters to URLs. Ensure your redirect rules preserve query strings. In Apache, using RewriteRule with the QSA (Query String Append) flag handles this. In Nginx, $request_uri includes the query string by default.
• Redirect chains can strip or mangle tracking parameters. Test your redirect path end-to-end with a sample affiliate link before deploying broadly.

For Publishers & Affiliates

Affiliates often use link cloaking or redirect plugins to manage their outbound affiliate links. A common setup is:

publishersite.com/recommends/product → 301 → merchant.com/product?aff_id=123

This approach offers two benefits:

1. Cleaner, more trustworthy links: Users see a link on your domain, not a long, parameter-heavy affiliate URL.
2. Flexibility: If the merchant changes their URL structure, you update one redirect rule on your site instead of editing every instance of the link across your content.

Caution: Do not chain multiple 301 redirects (e.g., your cloaked link → merchant redirect → final product page). Each hop adds latency and risks losing the affiliate tracking parameter. Link directly to the merchant’s final destination URL whenever possible.

For Affiliate Program Managers

A 301 redirect from the old tracking domain to the new one preserves affiliate traffic during the cutover. However, this works only if:

• The new platform can parse the old tracking parameters, or
• You map old affiliate IDs to new ones server-side.

Workflow recommendation:

1. Audit all existing affiliate links before migration.
2. Build a redirect map from old tracking URLs to new ones.
3. Implement 301 redirects at the server level.
4. Notify affiliates to update their links to the new format.
5. Monitor traffic for 30–60 days, then phase out old redirects once affiliate adoption of new links reaches target levels.

What does a 301 response look like?

A simplified response to a moved resource can look like this:

HTTP/1.1 301 Moved Permanently
Location: https://merchant.example/new-product