May 26 2011

The Latest On Panda Straight From Google

Google’s Matt Cutts engaged in a live chat with webmasters on YouTube, and had some things to say about the Panda update. Barry Schwartz posted the above video , capturing a Panda-related segment of the chat, in which Cutts discusses the update. “It came from the search quality team,” he says. “It didn’t come from the web spam team, so web spam engineers have been collaborating with search quality folks on it since the initial launch, but it originated from the search quality team, and it’s just an algorithmic change that TENDS to rank lower quality sites lower, which allows higher quality sites to rank higher, so it’s not a penalty, and I talked about how algorithms are re-computed, so there’s been no manual exceptions.” “I don’t expect us to have any manual exceptions to Panda,” he says. “This is something where the signal is computed, and then when the signal is re-computed, if the sites are slightly different, then that can change the sites that are affected, and we’re going to keep iterating.” “So we’ve had Panda version 1 in February and Panda version 2 in April I believe, and…possibly March…and that started to use blocking of sites along with some other signals,” he continues. “And then we’ve had smaller amounts of iterations…” Referring to before the update came about, he says, “We had heard a lot of complaints. We’ve been working on it even before we’d heard a lot of the complaints to try and make sure that lower quality sites were not ranking as highly in Google search results.” He then mentions the list of questions Google released a few weeks ago for content providers to ask themselves about their own content quality. The list, he says, “Helps to step into the Google mindset and how we think about these sorts of things.” In the talk, Cutts mentioned that the update will still roll out internationally in other languages in time, “maybe in the next couple months”. So far, it’s been launched globally, but only in the English language.

May 19 2011

Reasons Google Might Skip Your Canonical Tag

This week, Google’s Matt Cutts has been discussing rel=canonical, providing some info that webmasters might find pretty helpful. “A user submitted a question to Matt, which said, “It takes longer for Google to find the rel=canonical pages but 301 redirects seem to lose impact (link juice) over time. Is there similar churn with rel=canonical?” He addressed this in the above video. Cutts’ response was to say that some people ask how much PageRank/link juice if they lose if they use a 301 redirect, and that they lose just a “tiny, little bit” or “not very much at all”. “If you don’t lose any, then there’d be some temptation for people to use 301 redirects for all the stuff on their site rather than links, since some amount of PageRank always sort of evaporates or disappears whenever you follow a link – people would say, ‘Oh, why use links and not just use 301 redirects for everything?’” he says. In regards to 301 redirects vs. rel=canonical, he says in general, he would use 301 redirects if you can, because they’re more widely supported, everyone knows about how to follow them, and any new search engine is going to have to handle those. Also, if you can have it work within your own CMS, he says, then the user’s browser gets carried along with the redirect. Cutts also took to his personal blog to discuss rel=canonical a bit more, and said that Google actually doesn’t use it all cases. “Okay, I sometimes get a question about whether Google will always use the url from rel=canonical as the preferred url. The answer is that we take rel=canonical urls as a strong hint, but in some cases we won’t use them,” he says. This applies to cases where Google thinks you’re “shooting yourself in the foot by accident,” like pointing it to a non-existent/404 page, or if they think your site has been hacked and the hacker added a malicious rel=canonical. Google will also not use rel=canonical if it is in the HTML body or if it sees “weird stuff” in the HEAD section of the HTML. “For example, if you start to insert regular text or other tags that we normally only see in the BODY of HTML into the HEAD of a document, we may assume that someone just forgot to close the HEAD section,” he says, suggesting that you make rel=canonical one of the first things (if not THE first thing) in your HEAD section. Here’s what Cutts had to say about the canonical tag when it was announced and WebProNews interviewed him about it a couple years ago: