Comments on: The anatomy of a server sided redirect: 301, 302 and 307 illuminated SEO wise http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/ If you've read my articles somewhere on the Internet, expect something different here. Fri, 16 May 2008 17:09:40 +0000 http://wordpress.org/?v=2.2.3 By: Why storing URLs with truncated trailing slashes is an utterly idiocy http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1128 Why storing URLs with truncated trailing slashes is an utterly idiocy Wed, 06 Feb 2008 08:03:53 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-1128 [...] What works great for major search engines like Google can fire back when a Web service like Yahoo thinks circumcising URLs is cool. Proper URL canonicalization might, for example, screw your blog’s reputation at [...]

[…] What works great for major search engines like Google can fire back when a Web service like Yahoo thinks circumcising URLs is cool. Proper URL canonicalization might, for example, screw your blog’s reputation at […]

]]> By: Everybody’s Free (To Add Good Content) - Hobo SEO UK http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-930 Everybody’s Free (To Add Good Content) - Hobo SEO UK Fri, 04 Jan 2008 17:21:30 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-930 [...] 301 those old pages and domains, throw away your old notes about getting into DMOZ. Stumble! [...] […] 301 those old pages and domains, throw away your old notes about getting into DMOZ. Stumble! […]

]]> By: Act out your sophisticated affiliate link paranoia http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-669 Act out your sophisticated affiliate link paranoia Tue, 13 Nov 2007 20:10:06 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-669 [...] If the requestor is not a verified crawler, router.php does a 307 redirect to the sponsor’s landing page: $sponsorUrl = "http://www.seobook.com/262.html"; $requestProtocol = $_SERVER["SERVER_PROTOCOL"]; $protocolArr = explode("/",$requestProtocol); $protocolName = trim($protocolArr[0]); $protocolVersion = trim($protocolArr[1]); if (stristr($protocolName,"HTTP") && strtolower($protocolVersion) > "1.0" ) { $httpStatusCode = 307; } else { $httpStatusCode = 302; } $httpStatusLine = "$requestProtocol $httpStatusCode Temporary Redirect"; @header($httpStatusLine, TRUE, $httpStatusCode); @header("Location: $sponsorUrl"); exit; A 307 redirect avoids caching issues, because 307 redirects must not be cached by the user agent. That means that changes of sponsor URLs take effect immediately, even when the user agent has cached the destination page from a previous redirect. If the request came in via HTTP/1.0, we must perform a 302 redirect, because the 307 response code was introduced with HTTP/1.1 and some older user agents might not be able to handle 307 redirects properly. User agents can cache the locations provided by 302 redirects, so possibly when they run into a page known to redirect, they might request the outdated location. For obvious reasons we can’t use the 301 response code, because 301 redirects are always cachable. (More information on HTTP redirects.) [...] […] If the requestor is not a verified crawler, router.php does a 307 redirect to the sponsor’s landing page: $sponsorUrl = "http://www.seobook.com/262.html"; $requestProtocol = $_SERVER["SERVER_PROTOCOL"]; $protocolArr = explode("/",$requestProtocol); $protocolName = trim($protocolArr[0]); $protocolVersion = trim($protocolArr[1]); if (stristr($protocolName,"HTTP") && strtolower($protocolVersion) > "1.0" ) { $httpStatusCode = 307; } else { $httpStatusCode = 302; } $httpStatusLine = "$requestProtocol $httpStatusCode Temporary Redirect"; @header($httpStatusLine, TRUE, $httpStatusCode); @header("Location: $sponsorUrl"); exit; A 307 redirect avoids caching issues, because 307 redirects must not be cached by the user agent. That means that changes of sponsor URLs take effect immediately, even when the user agent has cached the destination page from a previous redirect. If the request came in via HTTP/1.0, we must perform a 302 redirect, because the 307 response code was introduced with HTTP/1.1 and some older user agents might not be able to handle 307 redirects properly. User agents can cache the locations provided by 302 redirects, so possibly when they run into a page known to redirect, they might request the outdated location. For obvious reasons we can’t use the 301 response code, because 301 redirects are always cachable. (More information on HTTP redirects.) […]

]]> By: The people I sleep with… • Tim Nash UK SEO Blog http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-572 The people I sleep with… • Tim Nash UK SEO Blog Thu, 25 Oct 2007 10:42:52 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-572 [...] agree. Of all his articles the one that ended on my bedside cabinet was his excellent work on 301,302, & 307 Status codes it might not be headline grabbing but it was damn [...] […] agree. Of all his articles the one that ended on my bedside cabinet was his excellent work on 301,302, & 307 Status codes it might not be headline grabbing but it was damn […]

]]> By: disco4me http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-541 disco4me Thu, 11 Oct 2007 15:07:34 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-541 Sorry for the quick addon. I asked my webhosting company to add the line you suggested but instead they added the following instead. Is this OK? I asked to add: redirect 301 /actuarial-jobs/actuarial-jobs-casualty.htm /actuarial-jobs/actuarial-jobs-casualty.php Instead they added: RewriteRule ^actuarial-jobs/actuarial-jobs-casualty.htm$ http://example.com/actuarial-jobs/actuarial-jobs-casualty.php/dontfollow [R=301,L] Sorry for the quick addon.

I asked my webhosting company to add the line you suggested but instead they added the following instead. Is this OK?

I asked to add:
redirect 301 /actuarial-jobs/actuarial-jobs-casualty.htm /actuarial-jobs/actuarial-jobs-casualty.php

Instead they added:
RewriteRule ^actuarial-jobs/actuarial-jobs-casualty.htm$ http://example.com/actuarial-jobs/actuarial-jobs-casualty.php [R=301,L]

]]> By: disco4me http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-540 disco4me Thu, 11 Oct 2007 14:17:36 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-540 Thanks for your help. Much appeciated. What is the difference between RedirectMatch 301 and redirect 301? If everything is being redirected to the same server, is it really necessary to have the http://www.example.com/dontfollow included in the redirect? Won't the path without that work? Thanks for your help. Much appeciated.

What is the difference between RedirectMatch 301 and redirect 301?

If everything is being redirected to the same server, is it really necessary to have the http://www.example.com included in the redirect? Won’t the path without that work?

]]> By: Sebastian http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-539 Sebastian Thu, 11 Oct 2007 14:02:32 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-539 1) If that's a virtual URI probably RedirectMatch 301 ^/joblistings http://www.example.com/acturial-jobs//dontfollow would do the trick and avoid multiple redirects (your server actuary.com does a redirect from /joblistings to /joblistings/ first). 2) Add the http://www.example.com/dontfollow part to the 2nd URL 3) This kind of redirect affects each and every request, so search engines and users see the same header. 1) If that’s a virtual URI probably
RedirectMatch 301 ^/joblistings http://www.example.com/acturial-jobs/
would do the trick and avoid multiple redirects (your server actuary.com does a redirect from /joblistings to /joblistings/ first).

2) Add the http://www.example.com part to the 2nd URL

3) This kind of redirect affects each and every request, so search engines and users see the same header.

]]> By: disco4me http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-538 disco4me Thu, 11 Oct 2007 12:59:32 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-538 Sebastian, Thanks for your help on Google. Just to make sure I have this correct, 1) If I want to add a permanent redirect for the just the individual page that now comes up at www.example.com/joblistings/dontfollow (no underlying pges) and redirect it to just the individual page www.example.com/actuarial-jobs/dontfollow (no underlying pages) would it look like this add to my htaccess file? redirect 301 /joblistings/ /actuarial-jobs/ 2) If I want to add a permanent redirect for the page http://www.example.com/actuarial-jobs/actuarial-jobs-casualty.htm/dontfollow to go to http://www.example.com/actuarial-jobs/actuarial-jobs-casualty.php/dontfollow would it look like this added to my htaccess file? redirect 301 /actuarial-jobs/actuarial-jobs-casualty.htm /actuarial-jobs/actuarial-jobs-casualty.php 3) Do permanent redirect only affect search engine indexing or does this mean anyone who tries to go to the old page will now end up at the new page? Thanks Sebastian,

Thanks for your help on Google. Just to make sure I have this correct,

1) If I want to add a permanent redirect for the just the individual page that now comes up at www.example.com/joblistings (no underlying pges) and redirect it to just the individual page www.example.com/actuarial-jobs (no underlying pages) would it look like this add to my htaccess file?

redirect 301 /joblistings/ /actuarial-jobs/

2) If I want to add a permanent redirect for the page
http://www.example.com/actuarial-jobs/actuarial-jobs-casualty.htm to go to http://www.example.com/actuarial-jobs/actuarial-jobs-casualty.php would it look like this added to my htaccess file?

redirect 301 /actuarial-jobs/actuarial-jobs-casualty.htm /actuarial-jobs/actuarial-jobs-casualty.php

3) Do permanent redirect only affect search engine indexing or does this mean anyone who tries to go to the old page will now end up at the new page?

Thanks

]]> By: Jab http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-534 Jab Wed, 10 Oct 2007 05:49:06 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-534 Well written post. Although I knew all that beforehand it is nice to see all these information on one page. It took me a couple of hours to gather all these information back than, when I learned all this. Great Post. Jab Well written post. Although I knew all that beforehand it is nice to see all these information on one page. It took me a couple of hours to gather all these information back than, when I learned all this.

Great Post. Jab

]]> By: John http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-533 John Wed, 10 Oct 2007 04:22:32 +0000 http://sebastians-pamphlets.com/the-anatomy-of-http-redirects-301-302-307/#comment-533 Great post, Sebastian. Thanks for taking the time to write something so comprehensive! Great post, Sebastian. Thanks for taking the time to write something so comprehensive!

]]>