SEO Redirects: The Complete Guide to 301, 302, 307 & 308 Redirects in 2026

TL;DR: 301 redirects permanently transfer SEO value to a new URL. 302 redirects are temporary and keep the original URL indexed. Google's John Mueller has confirmed that all 3xx redirects now pass PageRank equally — so choosing the right type is about technical accuracy, not PageRank optimization. Redirect chains dilute value and slow load time. This guide covers every redirect type, the 8 most common mistakes, step-by-step implementation across every platform, and how to audit your redirects properly.

Every time a URL on your website changes — whether from a page rename, a site migration, an HTTPS upgrade, or a content consolidation — you face a choice that can either preserve your SEO equity or silently dissolve years of ranking authority. That choice is the redirect.

Done correctly, redirects are invisible to users and transparent to search engines. Done incorrectly, they become silent ranking killers — causing index confusion, link equity dilution, and crawl budget waste that compounds over time without appearing in any obvious error report.

This guide covers every redirect type you will encounter in modern SEO, explains the mechanics of how each interacts with Google's crawlers, documents the most common and costly mistakes, and provides platform-specific implementation guidance.

What Are HTTP Redirects and How Do They Work?

An HTTP redirect is a server instruction that tells web browsers and search engine crawlers to move from one URL to another. Technically, redirects are HTTP response codes issued by the server — a status code in the 3xx range, where the "3" signals a redirection response.

When a user types a URL into a browser (or when a crawler attempts to access a page), the server responds with an HTTP status code. For redirect responses, the code is accompanied by a Location header that specifies the destination URL. The browser or crawler then automatically navigates to that destination.

The critical point for SEO: the server-level redirect happens before the browser renders any content. This means the redirect instruction reaches search engine crawlers with full context about whether the move is permanent or temporary — which directly affects how the crawler treats the original and destination URLs for indexation and ranking purposes.

The Complete Redirect Type Reference

301 Redirect — Permanent Move

A 301 redirect is the most commonly used redirect in SEO, and for good reason. It signals to both browsers and search engines that a URL has permanently moved to a new location. When a search engine crawler encounters a 301, it does three things:

1. Follows the redirect to the destination URL
2. Transfers the ranking signals (link equity, PageRank) from the original URL to the destination
3. Updates its index to replace the original URL with the destination URL

The SEO implications are significant. Most link equity — often cited as 90–99% of the original value — is passed through a 301 redirect. This means that backlinks pointing to your old URL continue to provide ranking benefit to the destination URL after the redirect is in place.

When to use a 301:

• Domain migrations (moving from one domain to another)
• URL restructuring (changing slug patterns across a site)
• HTTP to HTTPS migration
• Consolidating duplicate content onto a single canonical URL
• Retiring old content with a relevant equivalent page available
• Rebranding a business or product with a new domain

Example: Moving mysite.com/old-product-name to mysite.com/new-product-name after a product rebrand. The 301 ensures all backlinks to the old URL pass their value to the new URL, and Google updates its index to reflect the canonical destination.

302 Redirect — Temporary Move

A 302 redirect signals that a URL has temporarily moved to a new location. The key distinction from a 301 is that search engines interpret this as a short-term change — they keep the original URL in their index and continue to assign ranking signals to it rather than transferring them to the destination URL.

As Google's John Mueller has confirmed: the technical choice between 301 and 302 doesn't meaningfully affect PageRank transfer — what matters is the intent signal. A 302 tells Google to keep ranking the original URL because it will return. A 301 tells Google to update its index and transfer authority to the new destination.

When to use a 302:

• A/B testing a new page design while keeping the original URL indexed
• Temporarily redirecting to a promotional or seasonal landing page
• Sending users to a maintenance page while repairs are underway
• Redirecting while you finalize whether a URL change will be permanent

What you should NOT do: Use a 302 when you intend the change to be permanent. This is one of the most common and costly redirect mistakes in technical SEO — it results in the original URL staying indexed while your new URL fails to accumulate ranking signals.

307 Redirect — Temporary Move (Method-Preserved)

The 307 redirect is the HTTP/1.1 equivalent of the 302, with one important technical distinction: it guarantees that the request method (GET, POST, PUT, etc.) is preserved when the redirect is followed. A 302 may technically allow the browser to change the method to GET regardless of the original request type, whereas a 307 explicitly prohibits this.

For SEO, the practical difference between 302 and 307 is minimal. Both signal temporary moves and both preserve the original URL's indexed status. The 307 is most commonly used in scenarios involving form submissions, APIs, and web application redirects where preserving the request method matters for technical correctness.

When to use a 307:

• Modern web servers handling HTTPS internal redirects where request method preservation is required
• Application-level redirects involving form submissions or API calls
• When your web framework specifically generates 307 for temporary redirects

308 Redirect — Permanent Move (Method-Preserved)

The 308 is the permanent version of the 307. Like the 301, it signals a permanent move and transfers SEO equity to the destination URL. Like the 307, it preserves the HTTP request method during the redirect. The 308 is less commonly encountered in standard web SEO but has become more relevant as HTTP/2 and modern application architectures have evolved.

When to use a 308:

• Modern application frameworks that prefer explicit method-preserving permanent redirects
• Progressive web applications with complex request routing requirements
• When technical architecture specifically requires 308 over 301 for application logic

Meta Refresh Redirect — Avoid in SEO Contexts

A meta refresh is a client-side redirect implemented through HTML rather than server-side HTTP headers. The HTML <meta http-equiv="refresh"> tag instructs the browser to navigate to a new URL after a specified delay. Unlike server-side redirects, meta refreshes are browser-level events — they happen after the page has been partially loaded.

From an SEO perspective, meta refreshes are generally discouraged. Google can follow them, but they are less efficient for link equity transfer and create poor user experience (particularly with delay timers). They can be misused for cloaking and are often associated with spam patterns, which may trigger additional scrutiny from Google's quality systems.

When meta refresh might be necessary:

• When a CMS repeatedly overwrites .htaccess files, making server-side redirects impractical
• When you have no server-side redirect capability and no alternative exists

The rule: Use server-side redirects (301, 302, 307, or 308) whenever possible. Reserve meta refresh for genuinely constrained technical situations where no server-side option is available.

JavaScript Redirects — Fallback Only

JavaScript redirects execute on the client side, using browser scripting to navigate the user to a new URL. Common implementations include window.location.href = "newURL" and window.location.replace("newURL").

Search engine crawlers handle JavaScript redirects with varying reliability. Google can follow JavaScript redirects, but the processing requires JavaScript rendering — an additional crawl step that introduces delay and uncertainty. Bing and other crawlers may handle JavaScript redirects inconsistently. Link equity transfer through JavaScript redirects is less reliable than through server-side redirects.

When JavaScript redirects might be necessary:

• SPAs (Single Page Applications) where server-side routing isn't available for specific transitions
• Third-party embedded content where server configuration isn't accessible

The rule: Always prefer server-side redirects. Use JavaScript redirects only when server-side options are genuinely unavailable for the specific URL in question.

PageRank and Redirect Equity: The Definitive Answer

One of the most persistent misconceptions in technical SEO is the belief that different redirect types pass different amounts of PageRank. This was partially true in earlier versions of Google's algorithm, but has been definitively updated.

In 2016, Google's Gary Illyes confirmed that "30x redirects don't lose PageRank anymore." Subsequently, John Mueller reinforced this position: "302 or 301. Which one should you choose for maximum PageRank? The good news is it doesn't matter. Use the technically correct redirect type. It can also be a 307 or a 308 redirect. Search engines have dealt with redirects since the beginning."

The correct framework for redirect selection:

The choice between 301 and 302 should be driven by the intent and permanence of the URL change, not by PageRank optimization. The signal the redirect type sends about permanence affects indexation behavior — which URL Google keeps in its index — and this indexation signal has significant ranking implications separate from link equity transfer.

Critical Mistakes That Silently Damage Your SEO

Mistake 1: Using 302 for Permanent Changes

This is the single most damaging redirect mistake in practice. Using a temporary redirect for a permanent URL change means Google continues to index and rank the old URL rather than updating its index to the new destination. The new URL never accumulates its own ranking signals because Google treats it as a temporary holding location. Users searching for the content may find the old, redirected URL appearing in SERPs — which then redirects them to the destination — creating a poor experience and a less authoritative ranking outcome.

Fix: Audit all existing redirects for intent-type mismatches. Any URL change that has been in place for more than 3–4 weeks and was not intended to revert should use a 301.

Mistake 2: Redirect Chains

A redirect chain occurs when a series of redirects connects multiple URLs before reaching the final destination — for example, URL A → URL B → URL C → URL D (final). Each hop in the chain introduces server response time, increasing total page load latency. Each hop also introduces a small amount of link equity dilution as the signal travels through multiple redirects rather than a single direct hop.

Additionally, Google's crawlers have a redirect follow limit per crawl session. Long chains risk the crawler abandoning the redirect sequence before reaching the final destination, potentially leaving intermediate URLs indexed rather than the canonical final URL.

Fix: Collapse all redirect chains to a single direct hop. Use tools like Screaming Frog SEO Spider to audit redirect chains and update source redirects to point directly to final destinations.

Mistake 3: Redirect Loops

A redirect loop occurs when a URL is configured to redirect to another URL that eventually redirects back to the original — creating an infinite loop. Browsers display a "too many redirects" error. Crawlers give up and cannot access either URL. Any pages caught in a loop are effectively deindexed.

Fix: Always verify redirect destinations before deployment. Use a redirect checker to confirm the final destination of each redirect and watch for reciprocal redirect pairs.

Mistake 4: Redirecting Everything to the Homepage

During site migrations or content deletions, a common shortcut is to redirect all old URLs to the homepage rather than to relevant equivalent content. Google has clearly stated that this pattern is often treated as a soft 404 — meaning the search engine recognizes that the redirected URL doesn't have a genuine equivalent at the destination and discounts the redirect accordingly. Homepage redirects from hundreds of individual product or content pages waste crawl budget and fail to preserve link equity.

Fix: Map each old URL to its most relevant equivalent destination. Only redirect to the homepage if the old URL was a general site entry point with no specific content equivalent.

Mistake 5: Redirecting to Irrelevant Pages

Link equity transfer through a redirect works most effectively when the destination page is thematically relevant to the source URL. Redirecting a detailed technical tutorial to an unrelated product category page, for example, creates confusion for both users and search engines. Google's quality systems evaluate the relevance relationship between the redirect source and destination when determining how much authority to transfer.

Fix: Map redirect destinations by topical relevance. When a genuinely relevant destination doesn't exist, a 404 is often preferable to an irrelevant redirect.

Mistake 6: Removing Redirects Too Soon

301 redirects should be maintained indefinitely for any URL that had external backlinks or meaningful traffic. Removing a redirect causes the original URL to return a 404, immediately breaking all existing backlinks and eliminating the link equity they were passing to the destination URL. The lost equity cannot be recovered without reinstating the redirect.

Fix: Never remove 301 redirects for URLs that received external links. Redirect maintenance is a permanent operational responsibility, not a temporary task.

Mistake 7: Not Updating Internal Links

When you redirect a URL, internal links throughout your site that still point to the old URL will trigger redirect hops with every crawl. Multiply this by dozens or hundreds of internal links and you generate significant unnecessary crawl overhead. While not as damaging as external link issues, stale internal links create crawl inefficiency and can confuse site architecture signals.

Fix: After implementing redirects, run a full internal link audit and update all internal references to point directly to the final destination URL.

Mistake 8: Failing to Update Sitemaps

XML sitemaps should only contain current canonical URLs. If your sitemap continues to list redirected or deprecated URLs, you waste crawl budget and may delay the indexation of your new canonical pages.

Fix: Remove all redirected URLs from your sitemap after implementing redirects. Ensure the sitemap is updated as part of every content migration or URL restructuring workflow.

How to Implement Redirects: Platform-by-Platform Guide

Apache Web Servers (.htaccess)

The most common implementation for Apache-served websites uses the .htaccess file. Place .htaccess in the root directory of your site or in specific subdirectories where you want the rules to apply.

Single URL redirect (301):

Redirect 301 /old-page https://www.yoursite.com/new-page

Single URL redirect (302):

Redirect 302 /temporary-page https://www.yoursite.com/destination

Full domain redirect (HTTP to HTTPS):

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Wildcard redirect (entire old domain to new domain):

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

Nginx Web Servers

Nginx handles redirects in the server configuration file (nginx.conf or site-specific config files in /etc/nginx/sites-available/).

Single URL redirect (301):

location /old-page {
    return 301 https://www.yoursite.com/new-page;
}

Full domain redirect:

server {
    server_name old-domain.com www.old-domain.com;
    return 301 https://new-domain.com$request_uri;
}

WordPress

WordPress handles redirects through plugins or via .htaccess file editing. The most reliable approach for non-developers is using a dedicated redirect plugin.

Recommended plugins:

• Redirection — Free, manages 301/302 redirects with logging and import/export
• Yoast SEO Premium — Includes redirect manager integrated with SEO workflow
• Rank Math — Includes redirect manager with .htaccess import/export capability

For .htaccess-based implementation on WordPress, the same Apache rules apply as above.

Shopify

Shopify's admin panel includes a built-in URL redirect manager. Navigate to Online Store → Navigation → URL Redirects. Add the old path and new URL, select the redirect type (Shopify defaults to 301 for all URL redirects created through this interface). For large-scale redirects, Shopify supports CSV import/export through the URL Redirects section.

How to Audit and Monitor Your Redirect Strategy

Step 1: Crawl Your Site for Redirect Issues

Use Screaming Frog SEO Spider (free for up to 500 URLs; paid for larger sites) to run a comprehensive redirect audit:

1. Enter your domain and run a full crawl
2. Navigate to Response Codes → Redirection (3xx) to see all redirect responses
3. Check the Status Code column to verify each redirect uses the correct type
4. Navigate to Reports → Redirect Chains to identify multi-hop sequences requiring simplification
5. Check Reports → Canonical Errors for redirects conflicting with canonical tag implementations
6. Export all redirect data for documentation and cross-referencing

Step 2: Monitor with Google Search Console

Google Search Console provides two key reports for redirect monitoring:

Coverage Report: Navigate to Indexing → Pages. Filter by "Redirect" status to see which URLs Google is processing as redirects. Look for unexpected redirected pages that should be indexed canonically.

Crawl Stats: Check for unusual crawl error spikes after redirect implementations — these often indicate redirect loop or chain issues that emerged post-deployment.

Step 3: Verify Keyword Rankings Post-Redirect

After significant redirect implementations (site migrations, major URL restructuring), monitor keyword rankings across your target terms to verify that ranking signals have successfully transferred to destination URLs. A temporary ranking dip is normal during Google's re-indexation period (typically 2–6 weeks for small sites, longer for large sites). Persistent ranking decline after 8–10 weeks warrants investigation.

Dageno AI: Monitoring AI Search Visibility During and After Site Migrations

Site migrations and URL restructuring create a critical gap that traditional SEO tools don't address: how AI search engines like ChatGPT, Perplexity, and Google AI Mode are representing your brand during and after the redirect transition. When URLs change, AI systems that have trained on or recently crawled the old URLs may continue to cite old content, outdated descriptions, or incorrect page associations for weeks or months after the migration — even when Google's traditional index has updated correctly.

Dageno AI is the dedicated platform that closes this visibility gap. During site migrations, Dageno AI monitors whether AI systems are citing your new canonical URLs or still referencing deprecated pages, whether brand descriptions in AI-generated answers have updated to reflect new positioning or content, and whether competitor brands are using your migration window to claim AI citations in categories you previously dominated.

Dageno AI's semantic gap analysis identifies when AI systems are still associating your brand with old URL structures, outdated product names, or deprecated content — providing specific recommendations for accelerating the AI re-indexation process. For brands with active link building and digital PR programs, Dageno AI's citation source tracking reveals which third-party sources (that AI systems heavily reference) still contain old URLs or outdated information, enabling proactive outreach to update those references before they influence AI-generated answers at scale.

For technical SEO teams managing complex site migrations, Dageno AI provides the AI visibility measurement layer that makes migration success verification complete — not just checking traditional SERP rankings and Search Console coverage, but confirming that the migration has successfully propagated through the AI search ecosystem as well.

Explore how Dageno AI monitors technical SEO migrations →

Redirect FAQ

Do 301 redirects lose PageRank?
No. Since 2016, Google has confirmed that all 3xx redirects pass PageRank equivalently. The choice between redirect types should be based on technical correctness for the intent of the move, not PageRank optimization.

How long should I keep a 301 redirect in place?
Indefinitely for any URL that had external backlinks or meaningful traffic. Removing a 301 redirect causes the original URL to return a 404, immediately breaking all backlinks and losing the equity they were passing.

Can I redirect an entire domain to a new domain?
Yes — this is a common use case for 301 redirects. Map each individual URL from the old domain to its equivalent on the new domain, rather than sending all traffic to the homepage.

How many redirects in a chain is too many?
Any chain longer than 1–2 hops creates unnecessary latency and potential equity dilution. Simplify all chains to a single direct hop wherever possible.

Will a 302 redirect hurt my rankings?
Using a 302 for a temporary change is fine. Using a 302 for a permanent change is harmful — it prevents the destination URL from accumulating ranking signals and may result in Google continuing to index and rank the original URL.

Redirect Checklist for Site Migrations

• Create a complete URL map from old URLs to new URLs before migration
• Implement server-side 301 redirects for all permanent URL changes
• Collapse any existing redirect chains to single direct hops
• Verify all redirects are functioning correctly in staging before going live
• Update XML sitemap to remove redirected URLs after deployment
• Update all internal links to point directly to final destination URLs
• Submit updated sitemap to Google Search Console post-migration
• Monitor Google Search Console Coverage Report for crawl errors
• Monitor keyword rankings for 6–8 weeks post-migration
• Keep all 301 redirects in place permanently for URLs with backlinks
• Monitor AI search visibility for brand description accuracy post-migration

References

• Google Search Central – Managing Redirects for SEO
• Ahrefs – 301 Redirects: How They Affect SEO
• Screaming Frog SEO Spider – Redirect Audit Tool
• Google Search Console – Coverage and Crawl Reports
• McKinsey – The Economic Potential of Generative AI
• Dageno AI – Best LLM SEO Trackers for 2026