I guess not. What do you mean by "indexed differently"?

If the content is the same, within the desktop and mobile version yes. The rel=canonical only points the search engine about which page should be indexed. As the content is the same, indexing the main (desktop) page should do it, as you would need to redirect mobile traffic to the mobile version once they click in the result.

Hope that helps!

Here's a video from Matt Cutts about mobile content:

watch?feature=player_embedded&v=mY9h3G8Lv4k

The favicon.ico is named like that, in the root and accessible both with SSL and without.

Google used to show it, but a few weeks ago I noticed the issue while I was posting a link to my site in G+.

Several sites use Google favicon to load favicons instead of loading it from the Website itself.

Our favicon is not being pulled from our site correctly, instead it shows the default "world" image.

https://plus.google.com/_/favicon?domain=www.example.com

Is the address to pull a favicon. When I post on G+ or see other sites that use that service to pull favicons ours isn't displaying, despite it shows up in Chrome, Firefox, IE, etc and we have the correct meta in all pages of our site.

Any idea why is this happening? Or how to "ping" Google to update that?

In my case, xml-sitempas works extremely good. I fully understand that a DB solution would avoid the crawl need, but the features that I get from xml-sitemaps are worth it.

I am running my website on a powerful dedicated server with SSDs, so perhaps that's why I'm not getting any problems plus I set limitations on the generator memory consumption and activated the feature that saves temp files just in case the generation fails.

I would go with the paid solution of xml-sitemaps.

You can set all the resources that you want it to have available, and it will store in temp files to avoid excessive consumption.

It also offers settings to create large sitemaps using a sitemap_index and you could get plugins that create the news sitemap automatically looking for changes since the last sitemap generation.

I have it running in my site with 5K pages (excluding tag pages) and it takes 10 minutes to crawl.

Then you also have plugins that create the sitemaps dynamically, like SEO by Yoast, Google XML Sitemaps, etc.

According to Matt Cutts, if you don't want to get all those localized domains, such as domain.it, domain.es, etc., then you are better of using subdomains.

The the video: http://www.youtube.com/watch?v=GyWx31GeQWY

But it is really up to you. Make sure whatever route you take, add each subdomain / domain/folder to WT, that way, you can target specific markets for each language.

Hope that help!

As far as I know, a 301 redirect passes pagerank to the final destination, therefore if you get too many bad links it will affect your main domain rankings.

I would suggest you to create javascript tags that your affiliates can use to display banners, and links to your site and adding the nofollow attribute to those links created by the js.

There's a Matt Cutts video where he explains how 301 redirects work:

watch?feature=player_embedded&v=Filv4pP-1nw

Here's the link that Fracisco refers to (I guess): http://www.seomoz.org/article/recommended

Oh, just spotted this video that refers to your question:

watch?v=421aTJI2Nxc

Google indexes PDF contents and files almost like regular HTML. Links are followed, you can block indexing, etc. Just like regular HTML. The only thing Google can't index from PDFs are images, unless you have it in HTML format elsewhere.

I would definitely recommend converting those PDF menus to regular HTML.

You can find more info here:

What file types can Google index?

Can google fully index pdf files?

Hope that helps!

I guess not, at least they shouldn't. But they were caught doing pretty ugly stuff

They could still use your IP to personalize search, there's nothing wrong there.

The only personalization Google can make if you are not logged in and have no cookies stored would be using your IP to trace your location. There's no need to keep track of your IP. Every request you make goes with your IP address, a simple IP tracing can reveal lots of information about you: http://tracethisip.com/myip