Welcome to WebmasterWorld Guest from 220.127.116.11
[edited by: tedster at 2:20 pm (utc) on Oct 17, 2012]
[edit reason] defeat the auto-linking [/edit]
[edited by: Robert_Charlton at 7:43 am (utc) on Nov 9, 2012]
[edit reason] delinked sample url [/edit]
Eric Enge: Let's say you move from one domain to another... is there some loss in PageRank that can take place simply because the user who originally implemented a link to the site didn't link to it on the new domain?
Matt Cutts: I am not 100 percent sure whether the crawling and indexing team has implemented that sort of natural PageRank decay, so I will have to go and check on that specific case. (Note: in a follow on email, Matt confirmed that this is in fact the case. There is some loss of PR through a 301). [my emphasis]
As I remember, the 10% to 15% number came in a video that was published slightly later. Because video content is hard to research I haven't come up with that one so far - will post it if I can find it.
302 found is http 1.1 and moved temporarily is http 1.0
#3 we test: using Webbug
#A URLA: HTTP/1.1 302 Moved Temporarily > the same url > we receive HTTP/1.1 404 Not Found (clicking HTTP 1.0)
#B URLB: HTTP/1.1 302 Found > the same url > we receive HTTP/1.1 302 Found (clicking HTTP 1.0)
#2 we read: <snip>
#3 we test: <snip>
#4 we are confused
joined:Oct 17, 2012
Since the 302 bug of years ago, the handling of 302 redirects by Google is not strictly by protocol, which isn't cool for protocol freaks, but is for those on the receiving end of 302 redirects, because they're treated much closer to 301 'permanent' redirects than they were 'back in the day'.
[edited by: TheMadScientist at 5:37 pm (utc) on Nov 11, 2012]