Welcome to WebmasterWorld Guest from 22.214.171.124
Eric Enge: Let's say you move from one domain to another and you write yourself a nice little statement that basically instructs the search engine and, any user agent on how to remap from one domain to the other. In a scenario like this, 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: That's a good question, and I am not 100 percent sure about the answer. I can certainly see how there could be some loss of PageRank. 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]
I wouldn't say that means never use a 301 - it is one of the useful tools in our toolkit. But it does mean don't throw 301 redirects around like confetti. Do get legacy backlinks changed when a domain changes. And it's better to fix a server infrastructure issue directly, whenever you can, instead of just doing a patch job.
whether it's getting legacy backlinks changed or fixing website infrastructure problems
I kind of see this the way duplicate content filtering would deceive webmasters into think a penalty existed , when all it was only a filter at work.
[edited by: TheMadScientist at 2:45 am (utc) on Mar 15, 2010]
But similar to crobb305 and g1smd, I had incoming external links (valid ones from other websites) pointing to /index.html. I 301 all requests for /index.html to /.
It's not a simple as a browser redirecting, because a browser simply takes you there and if the redirects change between your visits it doesn't really matter
But similar to crobb305 and g1smd, I had incoming external links (valid ones from other websites) pointing to /index.html.
The question is, do bots revisit the 'intermediate' URLs in a chain after the head of a chain is altered to redirect someplace else?
[edited by: TheMadScientist at 8:18 am (utc) on Mar 15, 2010]
[edited by: g1smd at 8:25 am (utc) on Mar 15, 2010]
as separate items in Google WebmasterTools and look at both reports, especially the 'crawl errors' and the 'internal links' and the 'sites that link to you' reports.
becomes a link to
and so on.
So if I have .examplw.com redirect serverwide to it's www.example.com I am loosing PR?
[edited by: tedster at 3:42 pm (utc) on Mar 15, 2010]
[edit reason] switch to example.com in the quote [/edit]
The best practice here is to try to avoid rewriting URLs if at all possible when changing platforms/CMS systems.
No. As jdmorgan said above, a rewrite would be a much better thing to use, instead of a redirect. With the rewrite in place, you would continue to use the same URLs 'out on the web' to access the content, even though the internals on the server are completely different.
You say that those incoming links were valid and pointed to index.html. Can you clarify? Are those inbound links incorrectly linking to your homepage as "index.html" or do they link to the the canonical '/' as you intended?
. If your new URL is
make sure that both
requests now redirect directly to the new URL, not from A to B to C in a chain.
the user who originally implemented a link to the site didn't link to it on the new domain