A redirect is a method of sending both users and search engines from one requested URL to a different URL. Also known as URL redirection, it ensures visitors reach intended content when pages move, consolidate, or change address. For marketers and SEO practitioners, redirects preserve search rankings during site migrations, prevent traffic loss from broken links, and consolidate signals from duplicate URLs.
What is a Redirect?
A redirect resolves an existing URL to a different location, effectively telling browsers and Google Search that content has a new address. While the general English definition means simply to change direction, the technical implementation involves specific HTTP response codes or client-side scripts that automate the forwarding process. This differs from domain forwarding, which specifically redirects entire domains rather than individual pages.
Redirects operate through server-side configurations (such as .htaccess files on Apache or PHP headers) or client-side methods (such as HTML meta refresh tags or JavaScript). The mechanism you choose signals to search engines whether the move is permanent or temporary, influencing how Google indexes and ranks the destination page.
Why Redirects Matter
- Preserve search rankings: Permanent redirects pass link equity and ranking signals from the old URL to the new one, preventing organic traffic drops during migrations.
- Consolidate duplicate URLs: When multiple paths lead to the same content (for example,
http://andhttps://versions, orwwwand non-wwwvariants), redirects unify traffic and signals to a single canonical destination. - Eliminate 404 errors: Redirecting deleted or moved content prevents users from hitting dead pages, reducing bounce rates and maintaining engagement metrics that influence SEO.
- Support site maintenance: Temporary redirects allow you to display alternative content while fixing backend issues without removing the original URL from Google's index.
- Enable domain changes: When rebranding or acquiring expired domains, redirects transfer authority and user traffic from old properties to new ones.
How Redirects Work
When a browser or crawler requests a redirected URL, the server returns an HTTP status code indicating the resource has moved. Server-side redirects (301, 302, 308, 307) execute before page content loads, making them the most reliable method for SEO. Client-side methods (meta refresh and JavaScript) execute after the initial HTML loads.
Google Search uses redirect signals to determine which URL to show in search results. Google Search interprets instant meta refresh redirects as permanent redirects (Google Search Central), while delayed meta refresh redirects trigger after a set number of seconds and Google Search interprets delayed meta refresh redirects as temporary redirects (Google Search Central). For JavaScript redirects, Google Search interprets and executes JavaScript using the Web Rendering Service once crawling of the URL has completed (Google Search Central).
Types of Redirects
Choose your redirect type based on whether the move is permanent or temporary, and your technical capabilities.
| Type | Signal Strength | Implementation | When to Use |
|---|---|---|---|
| 301 (Moved Permanently) | Strong canonical signal | Server-side (.htaccess, PHP, Nginx) | Permanent URL changes, domain migrations |
| 308 (Moved Permanently) | Strong canonical signal | Server-side | Permanent moves requiring HTTP method preservation |
| 302 (Found) | Weak canonical signal | Server-side | Temporary content unavailability, A/B testing |
| 307 (Temporary Redirect) | Weak canonical signal | Server-side | Temporary moves requiring HTTP method preservation |
| 303 (See Other) | Weak canonical signal | Server-side | Redirecting after form submissions (POST to GET) |
| Meta Refresh (0 seconds) | Permanent signal | Client-side HTML <head> |
When server-side access is impossible |
| Meta Refresh (>0 seconds) | Temporary signal | Client-side HTML <head> |
Delayed redirects for temporary messages |
| JavaScript Location | Interpreted by Web Rendering Service | Client-side JS window.location |
Dynamic redirects based on user conditions |
| Crypto Redirect | Disputed/pseudo-redirect | Manual HTML links | Last resort when no technical redirects are possible |
Google Search uses permanent redirects as a strong signal that the redirect target should be canonical (Google Search Central). Conversely, Google Search uses temporary redirects as a weak signal that the redirect target should be canonical (Google Search Central), meaning the original URL may remain in search results.
Best Practices
Redirect to similar content. Always point old URLs to pages with topical relevance. If you delete a product, send users to the category page or a related product, not the homepage. Mismatched redirects increase bounce rates and signal poor user experience.
Avoid redirect chains. When URL A points to URL B, which points to URL C, you create a chain that slows crawling and dilutes link equity. Update redirects to send traffic directly from the original URL to the final destination.
Prevent redirect loops. Audit your implementation to ensure URL A does not redirect to URL B while URL B redirects back to URL A. This creates an infinite loop that returns errors to users and traps crawlers.
Update internal links. Do not rely on redirects for site navigation. Change internal links to point directly to the new URL, reserving redirects only for external links and bookmarks.
Choose the correct HTTP status. Use 301 for permanent moves and 302 only for temporary situations. Using 302 for permanent migrations prevents search engines from transferring ranking signals to your new URLs.
Verify domain health before forwarding. When implementing domain forwarding, use Google Search Console to check the Manual Actions report for penalties before implementing domain forwarding (New Media Campaigns). This prevents inheriting negative SEO history from expired domains.
Common Mistakes
Using 302 for permanent moves. Search engines treat 302 as temporary, keeping the old URL indexed instead of replacing it with the new destination. Fix: Implement 301 redirects for any URL you do not plan to restore.
Creating redirect chains. You redirect /old to /interim, then later redirect /interim to /new, leaving /old pointing through an unnecessary hop. Fix: Update the original redirect to point /old directly to /new.
Building redirect loops. Page A redirects to Page B, but Page B redirects back to Page A. Fix: Remove one redirect to create a linear path, or delete the obsolete page entirely.
Redirecting all deleted pages to the homepage. Sending every 404 to your home page frustrates users expecting specific content. Fix: Map deleted URLs to relevant category pages or create custom 404 pages with navigation options.
Neglecting mobile redirects. Ensure redirects work across device types and do not accidentally send mobile users to desktop-only pages or vice versa.
Examples
Domain Migration: You move from oldbrand.com to newbrand.com. Implement server-side 301 redirects from every page on the old domain to the corresponding page on the new domain. Update Google Search Console using the Change of Address tool to notify Google of the move.
URL Structure Change: You reorganize content from /blog/2023/post-name to /insights/post-name. Create 301 redirects for each old path to prevent 404 errors from external links and bookmarks.
Temporary Maintenance: Your checkout page requires emergency maintenance. Implement a 302 temporary redirect to a status page explaining the outage, preserving the original URL in search indexes while you fix the issue.
Consolidating Duplicates: You discover both /service and /services return the same content. Choose one as canonical and 301 redirect the other to it, concentrating link equity onto a single ranking page.
FAQ
What is the difference between 301 and 302 redirects?
A 301 redirect signals a permanent move and Google Search uses permanent redirects as a strong signal that the redirect target should be canonical (Google Search Central). A 302 redirect indicates a temporary move and Google Search uses temporary redirects as a weak signal that the redirect target should be canonical (Google Search Central), meaning the original URL likely remains in search results.
How long should I keep a 301 redirect active?
Maintain permanent redirects indefinitely. While Google may eventually stop crawling the old URL, users with bookmarks and external sites with backlinks may continue referring traffic for years. Removing the redirect causes those visitors to encounter 404 errors.
Can I redirect without server access?
Yes, using meta refresh tags or JavaScript redirects within your HTML. However, Google Search interprets instant meta refresh redirects as permanent redirects (Google Search Central), while server-side methods provide clearer signals and faster performance. Crypto redirects (manual links to new pages) work as a last resort but do not pass SEO signals reliably.
What is a redirect chain?
A redirect chain occurs when multiple redirects stand between the original URL and the destination (A → B → C). This slows page load times and reduces the link equity passed to the final URL. Always redirect directly from the original to the final destination.
How do I check if my redirects are working?
Use a redirect checker tool to analyze HTTP status codes and detect chains. Verify each redirect returns the intended status code (301 for permanent, 302 for temporary) and reaches the correct destination without intermediate hops.
Do redirects pass link equity?
Permanent (301) redirects pass the majority of link equity to the destination, though not necessarily 100%. Temporary (302) redirects may not pass equity because search engines treat them as temporary and maintain the original URL in their index.
