: Changing 301 redirect multiple times Let's say I am a mortgage broker that has an entire neighborhood of houses to sell. I sell one of the houses, call it House A. For whatever reason, House

@Gloria169

The 301 redirect is considered a permanent redirect, and clients (browsers, search engines, etc.) are entitled to take the response and cache that.

For example if you open Chrome and the network tab of its developer tools and request the page for House A, and Chrome receives a 301 to House B, you would see the request for both pages in the traffic. If you later change the redirect to House C, and then request House A again Chrome often won't issue the request to House A, but will go to House B directly. Similarly for Googles index: if the crawler sees a permanent redirect it is encouraged to update its links accordingly.

From the W3C spec on status codes


The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.


If you know you are likely to change these often I would recommend either using the 302 Found (temporary redirect), or as you suggest linking to the neighbourhood results page, possibly with some note that the requested house is no longer available.

Vote Up Vote Down

@LarsenBagley505

The line is drawn at one redirect.

There should be at most one redirect. In your case, that means if house A is out and house B and C are out but house D is still active, rather than going from A to B, B to C, then C to D, you would simply redirect the "link juice" from A to D for these reasons:


It places less load on the server. Only one extra request is made to the server instead of three.
It creates an environment which gives the user the impression that the site loads faster. In other words, a blank screen won't last as long when the page is requested. This can be easily observed if you test your URLs in webpagetest.org
It puts less strain on search engine robots since they don't have to examine all three redirects, thereby increasing the odds that the destination page is indexed faster.I believe google has a set budget in the number of page crawls it makes per website, and adding extra unnecessary redirect pages counts as a page crawl.


See developers.google.com/speed/docs/insights/AvoidRedirects for more info on why a redirect to a redirect is bad.

Also, www.lostsaloon.com/technology/seo-how-to-avoid-landing-page-redirects-in-your-website/ explains an example of how a redirect should be done.

Vote Up Vote Down