Redirect Link

A redirect link is a URL that automatically forwards browsers and search engines from one web address to another. When you click a redirect link, the server responds with an HTTP status code in the 3xx range and a Location header pointing to the destination — your browser follows it, usually in under a second, and you land on the new page without any visible interruption.

What Is a Redirect Link?

A redirect link is any URL that, when requested, instructs the browser to load a different URL instead. The mechanism is built into HTTP: the server sends a response with a status code beginning with 3 and a Location header that contains the target address. The browser then makes a second request to that new location automatically.

You will also see the terms URL redirect and URL forwarding used interchangeably. The underlying concept is the same: one web address resolves to another. What differs is how the redirect is implemented — at the server level, via HTTP headers, through HTML meta tags, or with JavaScript.

What Does a Redirect URL Look Like?

A redirect URL looks like any other URL. The difference is not in the address itself but in what the server returns when that address is requested. For example:

• Original (redirect) URL: https://example.com/old-page
• Destination URL: https://example.com/new-page

When you visit example.com/old-page, the server responds with a 301 Moved Permanently status and the Location header set to example.com/new-page. Your browser then loads the new page. The address bar updates to show the destination URL.

In affiliate marketing, redirect links often include tracking parameters:

• https://track.example.com/aff_c?offer_id=12&aff_id=47

This URL redirects through a tracking server that records the click and then forwards the visitor to the merchant’s product page. The user sees only the final destination.

Launch your affiliate program today

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

Request demo Start 30-days free trial

How Do Redirects Work?

When you type a URL or click a link, your browser sends an HTTP request to the server that hosts that address. The server processes the request and returns an HTTP response. For a normal page, the response is 200 OK with the page content. For a redirect, the response is different.

Step-by-Step: What Happens When a Website Redirects You

From the visitor’s perspective, steps 2 through 4 are invisible. You click one link and land on the correct page. The only performance cost is the extra round-trip between browser and server — negligible for a single redirect, but it adds up if multiple redirects chain together.

Server-Side vs. Client-Side Redirects

Server-side redirects use HTTP status codes returned directly by the web server. These are the fastest and most reliable type. Google interprets server-side redirects correctly in nearly all cases. Apache, Nginx, IIS, and most CDNs support them natively.

Client-side redirects run in the browser. They include:

• Meta refresh redirects: An HTML <meta> tag in the page head tells the browser to load a new URL after a set delay. A zero-second meta refresh is treated similarly to a permanent redirect by Google, but it is slower and provides a worse user experience than a server-side redirect.
• JavaScript redirects: Scripts that set window.location to a new URL. Google can interpret these, but they are the least reliable method. Use them only when server-side or meta refresh redirects are not possible.

Types of Redirect Links

HTTP defines several redirect status codes, each with a distinct meaning. The table below summarizes the ones you will encounter in practice.

Permanent Redirects: 301 and 308

A 301 redirect signals that the original URL has moved permanently. Search engines transfer most of the ranking signals — often called link equity or page authority — to the new URL. Use 301s when you change a page’s slug, merge two sites, or migrate from HTTP to HTTPS.

A 308 redirect works identically to a 301 with one important difference: it preserves the HTTP method of the original request. If a form submits data via POST to the old URL, the browser re-sends that POST to the new URL with a 308. With a 301, the browser may switch the request to GET. In practice, 301 covers nearly all permanent redirect needs; 308 is a niche tool for API endpoints and form submissions.

Temporary Redirects: 302 and 307

A 302 redirect tells search engines the move is temporary. The original URL remains indexed, and link equity does not transfer to the destination. Use 302s when a page is temporarily unavailable — during maintenance, for a seasonal promotion, or while you test a new version.

A 307 redirect is the temporary equivalent of 308: it preserves the HTTP method. A 307 is useful when a temporary redirect must preserve the request method. For an affiliate tracking link, choose the code supported by the tracking workflow and test the complete click-to-conversion path.

Meta Refresh and JavaScript Redirects

A meta refresh redirect is an HTML tag placed in the <head> of a page:

<meta http-equiv="refresh" content="0; url=https://example.com/new-page">

JavaScript redirects use window.location or location.href to change the page. Googlebot executes JavaScript and can follow these, but the process is less reliable than HTTP-level redirects. Use JavaScript redirects only as a fallback — for example, in single-page applications where the framework controls routing.

Join our newsletter

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

Email address

Subscribe

Redirects in Affiliate Marketing

Redirect links are the backbone of affiliate tracking. When a publisher promotes a product, they do not link directly to the merchant’s page. Instead, they use an affiliate link that routes through tracking software before reaching the destination.

How Affiliate Redirect Links Work

The typical flow for an affiliate redirect link:

1. Publisher places an affiliate link in a blog post, email, or social media post: https://track.partner.com/aff_c?offer_id=12&aff_id=47
2. A visitor clicks the link. The browser requests the tracking URL.
3. The tracking server records the click. It logs the affiliate ID, offer ID, timestamp, IP address, and any UTM parameters.
4. The server returns a 307 redirect with the Location header set to the merchant’s product page.
5. The browser follows the redirect and lands on https://merchant.com/product.
6. If the visitor completes a purchase, the merchant’s system fires a postback or pixel that credits the conversion to affiliate 47.

This entire chain happens in under a second. The visitor sees only the final product page. Behind the scenes, the redirect link has attributed the referral.

Why Affiliate Programs Use Redirect Links

For advertisers (merchants): Redirect links let you track every click and conversion by affiliate partner. You can measure campaign performance, calculate commissions accurately, and detect fraud patterns. Redirect-based tracking also works across domains — essential when affiliates promote you from their own sites, newsletters, and social channels.

For publishers (affiliates): Redirect links are often long, ugly, and filled with parameters. Cloaking them behind a shorter, cleaner URL improves click-through rates. Many affiliates use link shorteners or their own domain redirects to make links more trustworthy. A link like yourblog.com/go/tool-name looks better and earns more clicks than a bare tracking URL.

For affiliate program managers: Redirect links centralize link management. If a merchant changes their product page URL, the manager updates the redirect destination in the tracking platform — every affiliate link automatically points to the new address. No need to ask hundreds of affiliates to update their links manually.

Limitations to Be Aware Of

• Redirect chains: If an affiliate link redirects through multiple tracking systems, each hop adds latency. A chain of three or more redirects can slow page load enough to lose visitors.

• Ad blockers: Some ad blockers and privacy extensions block known tracking domains. Server-side redirects from a custom domain are harder to detect and block than client-side scripts.

• Cookie restrictions: Third-party cookie deprecation in browsers like Safari and Chrome has pushed the industry toward first-party cookies and server-side tracking. Modern affiliate platforms use both methods to maintain accurate attribution.

• SEO impact on publisher sites: Affiliate redirect links on a publisher’s site should use rel="sponsored" or rel="nofollow" attributes. This tells search engines the link is paid and prevents any ranking penalty.

• Choose the status code for the intended move. Use 301 or 308 for permanent moves, and 302 or 307 for temporary ones. Use 307 or 308 when preserving the HTTP method is required.

• Keep redirect chains to a single hop. Each additional redirect adds latency and reduces the chance that search engines will follow to the end.

• Leave permanent redirects in place for at least one year, ideally indefinitely. If a URL ever had traffic, backlinks, or bookmarks, keep the redirect live.

• Update your own internal links to point directly to the new URLs. Redirects are a safety net, not a navigation strategy.

• Match content to content. Redirect a deleted product page to a similar product, not the homepage. Redirect a removed blog post to a related article, not the blog index.

• Test every redirect after implementation. Use a redirect checker or browser DevTools. Confirm the HTTP status code and the final destination URL.

• Monitor your site regularly with a crawling tool. Redirect chains, loops, and broken redirects accumulate over time as sites grow and change.

• Use HTTPS for all redirect destinations. Redirecting from HTTPS to HTTP triggers browser security warnings and undermines trust.

• Test affiliate tracking through the redirect. A server-side redirect can work without client-side JavaScript, but no redirect code guarantees that blockers will allow the request or that a commission will be attributed.

Are Redirects Bad for SEO?

Redirects are not inherently bad for SEO. Implemented correctly, they preserve rankings and traffic. Implemented poorly, they can cause indexing problems and lost visibility.

When Redirects Help SEO

• Domain migrations: Moving from oldsite.com to newsite.com with 301 redirects preserves the search equity built over years.
• HTTP to HTTPS upgrades: A 301 redirect from http:// to https:// consolidates signals under the secure version.
• URL consolidation: If you have duplicate pages or multiple URLs serving the same content, 301 redirects to a single canonical URL prevent dilution of ranking signals.
• Content updates: When you replace an old article with a newer, more comprehensive one, a 301 redirect transfers the old page’s authority to the new version.

When Redirects Hurt SEO

• Redirect chains: Each additional hop dilutes link equity. Google recommends keeping redirects to a single hop whenever possible. A chain of three or more redirects may cause Googlebot to stop following.
• Redirect loops: If URL A redirects to URL B, which redirects back to URL A, browsers and crawlers get stuck. The page never loads, and search engines drop it from the index.
• Using 302 instead of 301: A temporary redirect for a permanent move means link equity never transfers. Months later, the old URL may still outrank the new one — or both may rank poorly.
• Redirecting to irrelevant pages: Sending all deleted pages to the homepage (a “soft 404” pattern) confuses search engines and frustrates users. Redirect to the most relevant replacement page instead.

Do Redirects Pass Page Authority?

A 301 permanent redirect passes the majority of the original page’s ranking signals to the destination URL. The small loss is negligible compared to the alternative — a broken 404 page that passes nothing.

A 302 temporary redirect does not pass link equity. Search engines continue to index the original URL and treat the destination as a temporary stand-in. Use 302s only when you intend to restore the original URL.

How Long Should You Keep Redirects in Place?

Google’s Search Relations team has recommended keeping 301 redirects in place for at least one year to ensure search engines have fully processed the change and updated their indexes. In practice, permanent redirects should stay indefinitely if the old URL has backlinks, bookmarks, or social shares pointing to it. Removing a redirect breaks every external reference to that URL.

Redirect Safety and Common Issues

Are Redirect Links Safe to Click?

Most redirect links are safe — they are standard web infrastructure. However, redirects can be abused to disguise malicious destinations. Before clicking an unfamiliar shortened or redirected link:

• Hover over the link and check the status bar for the actual destination URL.
• Use a redirect checker tool (such as whatsmydns.net/redirect-checker) to expand the link and see every hop in the chain.
• Look for HTTPS in the final destination. Legitimate services use secure connections.
• Be cautious with links in unsolicited emails or messages. Phishing attacks often use redirect chains to hide the true landing page.

What Is a Redirect Virus and How to Remove It

A “redirect virus” is malware or a malicious browser extension that forces your browser to visit unwanted sites — often ad networks, scam pages, or fake search engines — when you try to load a legitimate URL. Symptoms include:

• Your browser consistently redirects to pages you did not intend to visit.
• Search results are hijacked to unfamiliar search engines.
• Pop-ups appear even on sites that normally have none.

1. Check your browser extensions. Remove any you do not recognize or did not install intentionally.
2. Reset your browser settings to default. This clears hijacked homepages, search engines, and proxy settings.
3. Scan your computer with an up-to-date antivirus or anti-malware tool (Windows Defender, Malwarebytes, or equivalent).
4. Check your hosts file (/etc/hosts on Mac/Linux, C:\Windows\System32\drivers\etc\hosts on Windows) for unauthorized entries that redirect domains.
5. Clear your DNS cache and check that your DNS server settings have not been altered.

If the issue persists after these steps, the malware may be operating at the network level — check your router’s DNS settings and consider a factory reset.

Redirect Loops and Chains

A redirect loop occurs when two or more URLs redirect to each other in a cycle.

Common causes:

• Conflicting rules in .htaccess or server configuration.
• HTTPS redirects that send traffic back to HTTP, which then redirects to HTTPS again.
• CMS plugins that create competing redirect rules.

To fix a redirect loop, trace the redirect path with a tool like curl -L or an online redirect checker, identify the conflicting rule, and remove or correct it.

A redirect chain is a sequence of multiple redirects from one URL to another, then another, before reaching the final destination. Each hop adds latency and dilutes SEO value. Use a site audit tool (such as Semrush Site Audit or Screaming Frog) to find chains on your site and consolidate them into single-hop redirects.

How to Fix 404 Redirects After a New Site Launches

After launching a redesigned or migrated site, 404 errors appear when old URLs have no matching redirect. To fix them:

1. Run a crawl of the old site’s URL list (from your sitemap or analytics) against the new site.
2. Identify every URL returning a 404.
3. Map each 404 URL to its closest equivalent on the new site. Do not redirect everything to the homepage — match content to content.
4. Implement 301 redirects for every mapped pair.
5. Re-crawl to verify that each old URL now resolves to the correct new page.
6. Submit the old sitemap to Google Search Console one final time to help Google discover the redirects faster.

How to Test and Implement Redirects

Tools for Testing Redirects

• Browser DevTools: Open the Network tab, check “Preserve log,” and navigate to the URL. The Status column shows the HTTP response code, and the Location header shows the destination.
• Curl (command line): curl -I https://example.com/old-page returns the HTTP headers, including the status code and Location.
• Online redirect checkers: whatsmydns.net/redirect-checker and redirectcheck.com show the full redirect path and each status code.
• Site audit tools: Semrush, Ahrefs, and Screaming Frog crawl your entire site and report redirect chains, loops, and broken redirects.

How to Create a Redirect Link

The method depends on your hosting environment. Here are the three most common approaches:

Apache (.htaccess):

Redirect 301 /old-page https://example.com/new-page

RewriteEngine On
RewriteRule ^old-page$ /new-page [R=301,L]

rewrite ^/old-page$ https://example.com/new-page permanent;

HubSpot: Navigate to Settings > Domains & URLs > URL Redirects, click “Add URL redirect,” enter the original URL path and the redirect destination, and select the redirect type.

Cloudflare / CDN: Use Page Rules or Bulk Redirects to define redirect patterns at the edge, before requests reach your origin server. This is the fastest option for high-traffic sites.

Step-by-Step Implementation Checklist

1. Audit your existing URLs. Know every page that exists and every page that has changed.
2. Map old URLs to new URLs. Create a spreadsheet with source and destination columns.
3. Choose the correct redirect type. 301 for permanent changes, 302/307 for temporary ones.
4. Implement redirects at the server or platform level — not in JavaScript unless unavoidable.
5. Test every redirect with a tool or browser DevTools. Confirm the status code and final destination.
6. Update internal links on your site to point directly to the new URLs. Do not rely on redirects for your own navigation.
7. Submit your old sitemap to Google Search Console to accelerate discovery.
8. Monitor 404 errors in Search Console for the next several weeks and add redirects for any you missed.

Best Practices for Redirect Links

• Use 301 for permanent moves, 307 for temporary ones. Avoid 302 for new projects — 307 is the modern standard for temporary redirects and preserves the HTTP method.
• Keep redirect chains to a single hop. Each additional redirect adds latency and reduces the chance that search engines will follow to the end.
• Leave permanent redirects in place for at least one year, ideally indefinitely. If a URL ever had traffic, backlinks, or bookmarks, keep the redirect live.
• Update your own internal links to point directly to the new URLs. Redirects are a safety net, not a navigation strategy.
• Match content to content. Redirect a deleted product page to a similar product, not the homepage. Redirect a removed blog post to a related article, not the blog index.
• Test every redirect after implementation. Use a redirect checker or browser DevTools. Confirm the HTTP status code and the final destination URL.
• Monitor your site regularly with a crawling tool. Redirect chains, loops, and broken redirects accumulate over time as sites grow and change.
• Use HTTPS for all redirect destinations. Redirecting from HTTPS to HTTP triggers browser security warnings and undermines trust.
• In affiliate programs, prefer server-side 307 redirects for tracking links. They preserve request methods, signal temporariness to search engines, and are harder for ad blockers to intercept than client-side scripts.