What Is a Redirect in SEO? Types, Impact, and Best Practices

What is a redirect in SEO?

A redirect is an automatic instruction that sends both users and search engines from one URL to a different URL. When someone clicks a link pointing to an old page address, the server intercepts that request and forwards the visitor to the new location without any manual action required.

Google’s documentation describes redirects as signals that tell visitors and Google Search that a page has moved to a new location, which is also how search engines determine which URL to treat as the authoritative version of a page. That process is called canonicalization, and it sits at the heart of why redirects matter for SEO.

Redirects fall into two broad categories:

Permanent redirects (status codes 301 and 308): Tell search engines the move is final and the old URL should be replaced.
Temporary redirects (status codes 302 and 307): Signal that the original URL is still the intended destination and will return.
Client-side redirects (meta refresh and JavaScript): Handled by the browser rather than the server, with notable SEO limitations.
301 redirect: The most widely used permanent redirect, passing nearly all link equity to the new URL.
302 redirect: A temporary redirect that keeps the original URL indexed by search engines.

Why redirects matter for your SEO
Types of redirects and their SEO implications
How redirects work technically
Best practices and common mistakes in implementing SEO redirects
Key Takeaways

Why redirects matter for your SEO

Redirects do more than move traffic. They carry the ranking signals your pages have built up over time.

A well-implemented 301 redirect passes nearly all link equity to the new page, which means the authority from backlinks, engagement history, and crawl data follows the content to its new address. Without a redirect, that equity evaporates the moment the old URL stops working.

Here is what breaks when redirects are missing or wrong:

404 errors appear where working pages used to be, frustrating visitors and signaling neglect to search engines.
Backlinks lose their value because the link points to a dead URL with no forwarding instruction.
Duplicate content accumulates when the same page is accessible at multiple URLs without a canonical signal.
Crawl budget gets wasted as Googlebot revisits broken URLs instead of discovering new content.
User experience degrades when visitors hit dead ends, increasing bounce rates and reducing conversions.

Good website user experience and strong SEO are inseparable here. A redirect is often the only thing standing between a smooth site migration and a ranking collapse.

Types of redirects and their SEO implications

Not every redirect type carries the same weight with search engines. Choosing the wrong one for the situation can quietly drain your rankings over months.

Permanent redirects: 301 and 308

A 301 redirect tells search engines the move is permanent. Google will eventually update its index to show the new URL, drop the old one, and transfer the accumulated ranking signals. The 308 redirect is the modern HTTP/1.1 equivalent, preserving the original request method, though 301 remains far more common in practice.

Temporary redirects: 302 and 307

Temporary redirects do not pass ranking signals fully. Search engines continue indexing the original URL rather than the destination, which is exactly the right behavior when you genuinely intend to bring the original page back. Use a 302 when running a short-term promotion or taking a page offline briefly for updates. Use a 307 when you need to preserve the HTTP method in the request. The mistake people make is using a 302 for a permanent change, which leaves the old URL indexed indefinitely.

Client-side redirects: meta refresh and JavaScript

Client-side redirects are handled by the browser after the page loads, not by the server before it responds. Search engines may ignore them entirely or treat them as low priority during crawling. A meta refresh redirect also creates a jarring user experience, especially when set with a delay. JavaScript redirects carry similar risks. Neither should be your first choice when a server-side option is available.

Redirect type	Status code	SEO signal passed	Best use case
Permanent redirect	301	Nearly full link equity	URL changes, site migrations
Permanent redirect (modern)	308	Nearly full link equity	Same as 301, preserves request method
Temporary redirect	302	Minimal, original URL stays indexed	Short-term changes, A/B tests
Temporary redirect (modern)	307	Minimal, original URL stays indexed	Temporary moves preserving request method
Meta refresh	N/A	Unreliable, browser-dependent	Avoid for SEO purposes
JavaScript redirect	N/A	Unreliable, may be ignored	Avoid unless no server access

One risk worth flagging: redirect chains. That is when URL A redirects to URL B, which redirects to URL C. Each hop dilutes the ranking signal passed along and adds latency. Chains also create soft 404 risks if any link in the sequence breaks.

How redirects work technically

When your browser requests a URL, the server responds with an HTTP status code. For redirects, that code starts with 3, and the response includes a Location header pointing to the new URL. The browser reads that header and immediately sends a second request to the new address.

Each redirect adds an additional round-trip server request, which increases page load time. Users rarely notice a single redirect, but the delay compounds quickly in a chain. From an SEO perspective, page speed is a ranking factor, so redirect chains create a real performance drag. An automated SEO audit tool can surface these chains before they affect rankings.

Server-side redirects with explicit HTTP status codes give search engines a clear, machine-readable signal. Client-side redirects, by contrast, require the browser to load the page first before executing the forwarding instruction, which means the server initially responds with a 200 OK status. That ambiguity is why search engines treat them as lower priority.

Pro Tip: Keep redirect chains to a single hop wherever possible. If URL A used to redirect to URL B, and you now want both to point to URL C, update the original redirect so A goes directly to C. This preserves ranking signals and cuts load time.

Website speed issues from redirect chains are subtle but cumulative. Each extra hop adds server processing time, and on mobile connections, that adds up fast.

Best practices and common mistakes in implementing SEO redirects

Getting redirects right comes down to a handful of decisions made at the right moment.

Use permanent redirects for permanent changes. If a URL is gone for good, a 301 is the correct tool. Using a 302 by accident is one of the most common mistakes in site migrations, and it can take months to diagnose because rankings erode gradually rather than all at once.

Always redirect to a relevant page. Redirecting to unrelated content is treated as a soft 404 error by Google. A soft 404 happens when a redirect points to a page that does not match the original content, and Google may penalize the destination URL or simply ignore the redirect entirely. If no relevant replacement page exists, a 404 is cleaner than a misleading redirect.

Eliminate redirect chains and loops. Mapping redirects directly from the source URL to the final destination minimizes latency and preserves ranking authority. A redirect loop, where two URLs redirect to each other, will cause a browser error and make the page completely inaccessible.

Audit all redirects before and after a site migration.
Use server-side redirects (301, 302) instead of meta refresh or JavaScript wherever possible.
Check that every redirect points to a live, relevant page, not another redirect.
Monitor crawl reports after changes, since Google’s indexing pipeline updates canonical signals gradually over weeks or months.
Use an internal linking strategy alongside redirects to reinforce page authority after URL changes.

Pro Tip: During a site migration, document every URL change in a spreadsheet before going live. Map old URLs to new ones, implement all redirects at once, and then run a crawl the following day to catch any missed pages. Fixing gaps in the first 48 hours prevents ranking drops from compounding.

Site migrations are also a natural time to review periodic website maintenance practices. Redirects set during a migration need ongoing monitoring, not a one-time setup.

Key Takeaways

A 301 redirect is the most reliable way to move a URL permanently while preserving its accumulated ranking signals and link equity.

Point	Details
Permanent vs. temporary	Use 301 for permanent URL changes; use 302 only when the original URL will return.
Link equity preservation	A well-implemented 301 redirect passes nearly all link equity to the new page.
Avoid redirect chains	Each extra hop dilutes ranking signals and adds server round-trip time.
Server-side over client-side	HTTP status code redirects give search engines clear, reliable signals; meta refresh and JavaScript redirects do not.
Monitor after changes	Google updates canonical signals gradually, so crawl reports should be checked weeks after any redirect implementation.

If your site has gone through a redesign, URL restructure, or migration and you are not sure whether your redirects are set up correctly, Webby Website Optimisation can audit your setup and fix the gaps. The team specializes in website design and development that includes SEO-friendly URL architecture and redirect management from day one.

Get in touch with Webby Website Optimisation for a free consultation and find out exactly where your redirects may be costing you rankings.

What Is a Redirect in SEO? Types, Impact, and Best Practices