206 means partial content, which is what your Website/Server is delivering to Facebook's request. Have you tested the "Fetch as Googlebot" under Webmaster tools to see if Google can get the files? https://www.google.com/webmasters/tools/googlebot-fetch

If you get an error there, then it must be something IP related with your server, as my test returned a 200 and a test using Googlebot as the user agent also returned 200, which means that the IP wasn't blocked (nor the user agent excluded), basically telling me that if Googlebot is unable to access your site (nor facebook) it must be something IP related.

Hope that helps!

Hi Rob,

I personally wouldn't go the way you are heading... that could be seen by Google as a technique to manipulate search engine results (which you stated it is).

But to respond to your question, why don't you use the "definitive" version of the page as the canonical? If the one including "near downtown" is the most accurate (and complete one as I guess the hotel IS near downtown) then you should go with that and noindex the alternatives... although I know that's not your intention, that is the way it should be done.

Hope that helps!

Yeah, they offer free and paid hosted versions too. But I found the server side version much simpler to setup and control.

I have been using xml-sitemaps (paid version) for all my sites over 5 years and they work like a charm, scraping and indexing what it needs to be indexed ans scraped, plus it consumes really low resources. 100% recommended (they have nice plugins too for extra sitempas (video, news, images, etc).

Hope that helps!

Implementing the redirect at the server level will be much better as you can redirect all pages to their correspondent page in the .com version.

You will need the URL-rewrite extension: http://www.iis.net/downloads/microsoft/url-rewrite

Then create a "Canonical Hostnames" rule to redirect the other domains.

Hope that helps!

Probably an API rate limiting? I don't know that tool, don't know if it uses Moz's API or their own, but Moz's has a rate limit, and most likely that other one too, which could be causing that "0" response code (as that response does not exist aside of an ajax call return when the request fails).

Yup, just wait. However, I would consider switching to a better server, a 5 day downtime is a long downtime! Look for more reliable solution.

Hmmm.. seems to be a very common issue.

How about creating script that fires the map load on a div that loads a static map image instead of the iframe by default? Then using a simple function switch that image to the iframe of the map. That should do it for the "sorry we have no imagery here" problem.

If it doesn't, you could try using some kind of internal catching to get the static image and save it in your server to serve that as the "1st" image, you can then load the iframe.

Hope that makes sense

Hey Tina,

I'm afraid your colleagues saying that the best way to go is to have it under a subfolder are right. Basically, all search engines consider subdomains as separate domains, meaning that if you put the learning center on learning.website.com will have the same effect as having it on somenewdomain.com, neither will help website.com unless you link from one to the other, and that could be seen as doorway pages which will ultimately hurt more than they could help.

Using a subfolder, any advantage you get from website.com/learn/ will influence website.com without putting website.com at risk (unless you post completely unrelated stuff in that new folder). But as you trying to write about the same niche, it is like basically having a blog. Take this Moz section for example. The community folder in a subfolder under their "money site" and I assure you it is working far better than if it was a subdomain.

I'm with your colleagues on this one

Hope that helps!

I think you are completely correct. Making a responsive design does not mean "hiding the content that doesn't fit" rather "displaying it differently" so any user under any device is able to see the entire content without having to zoom in/out.

The example you posted about Wikipedia is the exact live example.

You could, however, remove areas of the page that have no actual value to a user browsing from a mobile device, that is acceptable, as even if you showed it they wouldn't be even able to see it (ex: flash content). This can be seen on sites that have floating social media buttons, than when on a mobile site, they usually accommodate those buttons elsewhere or completely hide them

Well, you are right, manual are easier to fix, although most likely, sites with manual penalties usually fall into an algorithmic penalty too.

Steps I'd suggest:

• Don't reinstate the redirect.
• Do some cleaning, extensive cleaning.
• Use it just as a redirection for users, but not for crawlers, rankings (using robots.txt disallow site A and 302 redirect the domain to site B).

Hope that helps!