A common HTTP status code that you can encounter when working on SEO for clients is a 301 redirect. A 301 redirect refers to a PERMANENT redirect when you change the path of traffic to from one URL to another and link multiple URLs together. This type of redirect is thought to be the best method for executing redirects on a site in terms of SEO.
By using a 301 redirect you are stating that one URL moves to a new location because the new location has relevant content. This then passes link equity from the old URL to the new. We commonly see 301 redirects occur in the SEO industry when companies are bought out or change the branding.
A 301 redirect after the acquisition is also great for companies online reputation management. Although 301 is the most commonly seen redirect it isn’t the only option. Other redirects that aren’t permanent and may be useful to you include 302, 303, 307, and 308. Google Spokesperson Gary Illyes stated that all 300 level redirects do in fact pass PageRank so your search results from the old URL remain under the new URL.
Which Redirect Should You Use:
301: Permanent Redirect
Do you want to delete a page? Try redirecting it to a page with equivalent content.
Do you want to make a new version of a page of pdf found in place of the old one but keep your page rank? 301 makes this page permanent.
302: Found but was temporarily redirected
This temporary change redirects users and search engines to the desired page for a limited amount of time until it is removed. This isn’t a typically used redirect as it can confuse google bots in determining user experience.
303: See Other
One of the least commonly used redirects is 303. Some use this in order to prevent bookmarking of pages that hold one-time-only data. When this is used it is typically related to credit card payment information sources.
307: Temporary Redirect
This URL is equivalent to the 303 except for that it uses the same method for how information is submitted.
308: Experimental Permanent Redirect
Similar to 301. States that the request and all future requests should be repeated using another URL.
Leave some feedback about this post