A redirect is a way to forward visitors and search engines from one URL to another. This is useful when moving content to a new URL, when deleting pages or when changing domain names or merging websites.
Whenever possible avoid using redirects, but when you have to use them, make sure to follow these best practices:
Redirects are a way to forward visitors and search engines to a different URL than the one they requested. Redirects play an important role within SEO, so it's important to know what types of redirects there are, when to use which ones, and how they measure up against one another.
When on-boarding clients I always use the Monty Python Song "Every Sperm Is Sacred" as a memory anchoring technique to make them remember that "every URL is sacred". The song goes:
🎵 Every URL is sacred, Every URL is great,
When one URL is wasted it makes Google irate 🎵
Redirects are important for both visitors and search engines when content has moved:
To illustrate these points: say you have a temporary summer sale campaign for flip flops. When people request the flip flop category page at
https://www.domain.com/flip-flops/, you want them to be redirected to
https://www.domain.com/flip-flop-summer-sale/, which has a different design and contains the limited offer.
https://www.domain.com/flip-flop-summer-sale/ will be removed after 2 weeks, and then
https://www.domain.com/flip-flops/ is back in play. In this case, you want search engines to remember
https://www.domain.com/flip-flops/ and to keep it in the index, because the redirect was only temporary in nature. In this case you'd use a 302 redirect.
Other situations in which to use redirects:
Ideally every internal link on a website points directly to the final destination page. Internal redirects can result in crawl waste and loss of link value, so it's a key priority to minimise redirects on your website as much as possible. You can't always control where external links to your site point to, but all your internal links should be accurate and not result in any form of redirect.
Redirects can be divided into server-side redirects and client-side redirects. Both types of redirects can be implemented in various ways. Be very careful about your choice for the type of redirect: choosing the wrong redirect for the job could lead to SEO troubles.
Not sure when to use which redirect? Keep this cheatsheet handy and always pick the right redirect for the job!
A server-side redirect is a forwarding method in which the server sends a 3xx HTTP status code when a URL is requested. The server determines what URL visitors and search engines should be sent to.
The most common HTTP status codes are:
A 301 redirect is a server-side redirect which redirects users from URL A to URL B, while signaling to search engines that URL A's content has been permanently moved to URL B.
When it comes to redirects, the 301 redirect usually is your best choice. It's worth noting that browsers will often cache 301 redirects because of their permanent nature, so keep that in mind when you're dealing with redirects.
The general consensus is that a 301 redirect passes 95-99% of the page authority from an old URL to a new URL. While a visitor won’t notice the difference between a 301 redirect and a 302 redirect, for a search engine, these are completely different signals.
Be careful about using 301 redirects when redirecting isn't permanent. If you intent to remove the 301 redirect shortly after implementing it: be prepared to wait several weeks, if not months, to see the redirected URL back in the search engines' indexes.
One of the easiest things to forget about redirects is that they have to move with the domain. Try not to think of them as site level, but domain level. So if you redesign the site, or move to a new domain or CMS, all those legacy redirects need to go with you. If you forget them, you create potentially bad UX for both visitors and search engines, and you can lose a lot of link value in the process. Make sure you check all the places redirects "live": .htaccess, httpd.conf, XML files on the server, and plugins in your CMS. If possible, standardize on one place for all redirects now so that someday when you make a move, you’re less likely to miss one.
A 302 redirect is a server-side redirect that redirects users from URL A to URL B, while signaling to search engines that URL A's content has been temporarily moved to URL B.
By default, a 302 redirect passes no page authority from the old URL to a new URL. 302 redirects are rarely used, since in most cases you want to pass a page's authority, and only a 301 redirect will let you do that.
SEO specialists have conducted research on what happens if a 302 redirect is in place for a long time, let's say longer than 6 months. They found that over time, search engines started to regard the 302 redirect as a 301 redirect, due to its permanent nature. This also means that in this situation the 302 redirect will pass page authority similarly to a 301 redirect.
Situations in which to use 302 redirects:
Google often make statements such as 302 redirects passing full page rank, which may be the case after a 302 redirect has been in place for a long time, but it often hides the fact that 302 redirects and 301 redirects send a very different message to search engines, and how Google at least handles them. A 301 redirect consolidates URLs, whereas a URL that's been 302 redirected is kept in the index and keeps on ranking. Always pick the right redirect for the job!
A 303 redirect is a server-side redirect that ensures visitors won't be able to re-submit forms when using the Back button in their browser, because the 303 redirect indicates that the follow-up request to the temporary URL should be made using the GET HTTP method. 303 redirects should only be used for handling form submissions on websites.
The 303 redirect doesn't play a role in SEO, as search engines don't perform POST requests. Don't use the 303 redirect when you need to redirect URLs after content has moved; it's not what it's intended for.
A 307 redirect is a server-side redirect that is the HTTP 1.1 equivalent of the 302 redirect. The 307 redirect was brought to life to make sure the HTTP method used to make a request doesn't change when the server responds with a redirect. If GET HTTP method was used, the GET is passed on as part of the redirect. If POST was used, then a POST is passed on as part of the redirect.
Similar to the usage of 302 redirects, a 307 redirect should only be used when content has been temporarily moved to another URL. At the moment, it's still unclear how search engines handle the 307 redirect, so we recommend using the 302 redirect instead to indicate that content has temporarily moved.
HTTP Strict Transport Security, HSTS for short, is a way for web servers to declare that web browsers should interact with it using secure HTTPS connections only, and never via the insecure HTTP protocol. That sounds complicated, but conceptually it's not. Let's take an example:
When your browser knows that a website is using HSTS (because it was told so when previously visiting the website), it will force you to only access the HTTPS version of the website by internally redirecting any HTTP URL to HTTPS whenever you try to visit the HTTP version.
The browser will use a 307 to internally redirect from HTTP to HTTPS. So while the 307 redirect is a server-side redirect, it can also be used as an internal redirect within a browser. In reality, it's not a "real redirect" that search engines will encounter, so don't think you're safe from harm when you see the 307 redirect: it could be an internal redirect. Read more about this on Troy Hunt's website.
A 307 these days is mostly from HSTS and being browser cached, there could be a 301 or a 302 behind it. You can check which bots will see by checking the status on a page with no history such as in incognito mode, or check the header response using Fetch within Google Search Console.
The 308 redirect is the permanent version of the 307 redirect. As can be expected with a permanent redirect, the 308 redirect does pass page authority.
Similar to the 307 redirect, the 308 redirect keeps the originally used HTTP method. At the moment, it's still unclear how search engines handle the 308 redirect, so we recommend using the 301 redirect instead to indicate that content has permanently moved.
A client-side redirect is a forwarding method in which a visitor's browser handles redirection. Using client-side redirects has several drawbacks, namely:
For all these reasons, we strongly recommend against using client-side redirects.
Due to the nature of this article, it is still important to describe the client-side redirects:
A meta refresh redirect is implemented using the
meta refresh element, located in the
<head>-section. It's used to instruct a browser to refresh a page or load another URL after a certain number of seconds.
Here's an example of what the meta refresh redirect looks like to send a visitor to
http://domain.com/other-url/ after loading a page:
Redirects may be holding back your SEO performance.
Check your website for excessive redirects right away!
When using redirects, keep the best practices below in mind, to make sure you offer your visitors an optimal user experience and preserve as much page authority as you can.
Yes, you read it correctly: avoid using redirects whenever you can. They increase load time and waste crawl budget.
Please note that it’s totally fine to use 301 redirects for configuring your web server so that it serves URLs according your preferences.
Even when link equity is maintained, redirects add load time to the user and bot journey. It's best to reduce redirects whenever possible. Internal links should be direct. 302 redirects will become 301 redirects over time, but in the interim serve a different purpose and will behave differently. That being said, redirects are a completely normal part of a website. They just need to be handled correctly.
When implementing redirects, it's essential that you redirect old URLs to the most relevant alternative URL. This is obviously important from a user point of view, and because of that search engines deem it important as well. If you redirect to URLs that aren't relevant, you're risking search engines not consolidating the value of the old URL with the new one. This results in what's called a soft 404 error.
When implementing 301 redirects, it's best to use a target URL that closely resembles the original in both topic and intent. Too often, webmasters lazily redirect pages to their homepage or other off-topic pages, which can result in a soft 404, and Google dropping link equity through the redirect."
When using redirects, be vigilant against chained redirects. A chained redirect is when one URL is requested, a redirect is used to redirect it to another URL and in turn this particular URL is redirected as well. It's important to avoid chained redirects for two reasons:
Example: let's assume URL A redirects to URL B, URL B to URL C and URL C in turn redirects to URL D. Now, let's say you lose 5% of the authority in a redirect. Then the authority arriving at URL D is: 0.95 x 0.95 x 0.95 = 0.857.
It's important to choose a preferred version of your website URL and stick with it. Below we describe two important topics you need to think about when linking. Consistently using the preferred version of your website URL prevents unnecessary redirects, which cause loss of page authority.
For example: if you prefer to have your website on the
www subdomain, make sure requests for URLs without the
www subdomain are 301 redirected to the version with the
www subdomain. Remember: for search engines,
example.com are two separate domains.
If you're using HTTPS, then make sure the HTTP variants of URLs are 301 redirected to their HTTPS counterparts.
Choose your preference when it comes to trailing slashes as well. For search engines,
www.example.com/page-a/ are different URLs. When both URLs serve the same page, and no canonical URL or
meta name=”robots” content=”noindex” is used, then this causes you to have duplicate content. If you prefer the trailing slash: make sure requests to the version of the page without the trailing slash are redirected to the version with the trailing slash.
When people link out to other sites, they sometimes make mistakes. They could introduce a combination of lowercase and uppercase characters into your URL. Example:
https://www.example.com/about-Us/. In case people request a URL like that, make sure to 301 redirect it to the lower-case version of the URL:
https://www.example.com/about-us/ page, to prevent possible duplicate content and unexpected 404 issues.
People will link to your website the way they want to. Often they won't adhere to your preferred version for your website URL. They may link to your contact page with the URL
http://yourdomain.com/contact while in reality your URL lives at
http://www.yourdomain.com/contact/. When you’ve correctly configured your web server, visitors will end up at the right URL, but you'll lose a bit of authority in the redirect. Monitor your inbound links with a tool such as Majestic and reach out to the ones linking to the wrong version of your URLs.
Tons of websites employ campaign URLs to support their online and offline campaigns. After such a campaign, these URLs are often just 301 redirected, but that's often incorrect, because these campaigns may return one month later.
When a campaign is simply temporarily inactive and will return in the future: use a 302 redirect to be able to keep the campaign URL in the search engine indexes when you need it again.
When you're absolutely sure a campaign URL will never be used anymore, it's safe to 301 redirect the URL to the most relevant URL within your website. If there's any doubt about it, use a 302 redirect so that you basically have the URL on standby. The URL will remain in the index, and the URL can be used to rank again in the search engines.
Having (hundreds of) thousands of redirects may, depending on the way the redirects are implemented, slow a website down significantly. On top of that, sometimes old redirects can play a vital role in strange website behavior. An old redirect could be causing inexplicable behavior within your website. Keep things simple; keep the number of redirects within your website to a minimum. Periodically check which redirects are necessary and which can be cleaned up. Only URLs that have inbound links and/or get serious referral traffic should be redirected. These URLs can be found by analyzing the inbound links to pages on your website using services such as Majestic and Ahrefs combined with referral data from your web analytics service. All URLs that redirect but have no inbound links and referring traffic can be removed.
I prefer to clean up redirects where possible to preserve SEO authority, and I aim to have as little redirects as possible on internal links in general to reduce impact on Googlebot crawling. When prioritizing development resources on fixing redirects, I usually put an estimate of user impact being a 100-200ms delay for each hop.
IP canonicalization is the process of implementing redirects for an IP address to a domain name. This is done to prevent duplicate content.
If your web server is set up incorrectly, it may serve your website both for your web server’s IP address and your domain name. Aside from the strange user experience, having your website accessible to search engines through both your IP address and your domain name leads to duplicate content and should be avoided. But good news: this problem is not that hard to solve. If you're using Apache web server, this can be fixed by including the code below in your .htaccess file.
Note: replace 220.127.116.11 with your server IP address, and example.com with your domain name.
Traditionally URL redirects had to be configured on the web server level. Nowadays most common Content Management Systems offer at least basic support for configuring them.
Setting up URL redirects in a CMS has the benefit that it's much more accessible for people without a development or system administration background, but it comes at a cost. When there are problems with the CMS, the redirects might stop working, and in most cases the redirects will be slower, as the CMS needs to be loaded for every redirect. On top of that, redirects set up within the CMS and on the web server level can co-exist, leading to confusion and possible mistakes.
Therefore it's always advisable to set up URL redirects on your web servers, and only use CMS redirects when there is no other workable way to redirect.
Regular expressions (regexes) are a language that can be used to search within text using patterns. For example, to search a string of text for digits, the regex
[0-9] can be used. Another example is using a regex to match optional characters.
filename.html? matches both filename.htm and filename.html.
Regular expressions are extremely useful for setting up redirects, as it saves you the hassle of setting up redirects for individual URLs. For example, let's say you have the following URL structure:
Then instead of setting up three different redirect rules, you can use the following regular expression to match all these subdirectories:
When you're using the Apache web server, you need to use the
RewriteEngine, which is part of the
modrewrite module. This module is loaded by default in Apache, but if it's not being loaded, make sure that you load it specifically in your Apache configuration using the following directive:
When this module is loaded, you can set up redirects using the following formatting:
This will instruct Apache to redirect all subdirectories of /blog/ (the categories) to the new location in /news/.
Another common use case for redirecting URLs is to ensure that all URLs include the 'www' part of your domain name. In that case you can set up a rewrite rule that only runs when a certain condition (the URL not containing the 'www' part of the domain name) is met.
This rewrite rule redirects all URLs to the version that includes the 'www' part, but only if that part is actually missing (the rewrite condition).
Pro tip: Aleyda Solis has created a handy tool that will generate the .htaccess redirects needed in a dozen situations.
It depends on the situation:
The general consensus is that a 301 redirect passes 95-99% of the page authority from an old URL to a new URL.
While these redirects are both meant for situations in which content has been temporarily moved, it's unclear how search engines handle the 307 redirect.
Therefore, it's better to use the 302 redirect for temporary redirects.