Welcome to the Q&A Forum

I'd say it's mostly transferable as plenty of content is found in both news and the main index. News is more of a service overlay that attempts to better handle user expectations for frequency and speed of response when it comes to news items. Still, old news gets into the index and treated like content from most any site so if you have a subscription based model that aligns with what they're recommending for more news orientated sites, at least you're fitting into a form of what they outline.

yeah basically, but I have to convince my MD and he doesn't want to do it. I need to show evidence of companies that have done it right and recovered and improved rankings

Not really no. I only use it per instance versus as a more constant change tool. If you have a dev in-house though they could probably setup something that runs on a virtual machine and sends reports on changes.  Or you could run it after getting a change report from one of the other, more standard types of page change tools to see if the site is now making different HTTP requests as well.

Matt is 100% correct, there are definite delays on Google's side.

Hi, If it's just a new template and all the other factors remain the same - you should have no (negative) impact. If you switch to a mobile template, don't forget to also test the speed of your pages & the size of your images - it's nice that the site is responsive but if you have a lot of very heavy images, and the sites loads slow on mobiles, the gain will be minimal. The traffic drop related to site migrations is very often related to changing the structure, generating a lot of 404's when not all the pages are redirected. Google seems to be cautious when suddenly there is a spike of 404's and reduces the traffic for a while. Once everything is back to normal, traffic (normally) returns. rgds, Dirk

I, like Cocoonfxmedia, would like to think that given Google has to be aware that not everyone will be able to remedy their situation quickly, they'll go easy at first and ramp up penalties over time. That said, I don't think anyone outside of Google knows the answer to your question. You're smart to push. I recommend you baseline traffic, conversions and rankings now, before the change, so you can use that push even harder should a negative impact be felt and you need evidence to support your request for approval.

Hi there, Just checking in to see if you figured this one out? I have an alternative theory: Google may be pulling the page title and meta description from Dmoz for both the mobile and the desktop site. That's what I was actually seeing with Amazon. If this is true, then the page title is not indicating that Googlebot mobile is crawling the desktop version of the site (which is good!). Best, Kristina

I assume these are pretty deep in the site structure, so I don't think those "links" being reported are very powerful or important. Some people claim that, since PageRank is recursive, you don't want to cut off paths, but when the paths are deep I've rarely seen any evidence to support this. A big, bloated index full of thin content, especially content available on other sites, is a much bigger danger. I would not recommend using both a NOINDEX and a rel=canonical on these pages. It's a mixed signal, and that can cause Google to ignore one or both signals (and at their choosing, not yours). I think NOINDEX is fine here. I've built structures like this for things like event websites (where we index the main event but NOINDEX all of the cities/dates, because they change so often) and have never seen any major issues. Actually, in one notable case, even before Panda came along, the site's rankings improved measurably.

I would definitely add it to both as Google sees these as two different sites.

It would be better to indicate the "nofollow" on the level of the link rather than on page level (as it will only impact the paid rather than all the links) but if this is not possible, the tag you want to use is ok. rgds, Dirk

I totally agree with Ryan. Let sleeping dogs lie

That's a good idea.   Then you will have some evidence that you were correct in advising not to go down this path.   I would get screenshots to document. There are lots of interesting comments on that google announcement, and lots of articles about it, as it was only released yesterday.

Totally agree with Dirk.  If the links offer value to the visitor and if grouped are tightly and obviously associated with the theme of the page then they should always be left as is.  If there is a hint of paid for they should be no-follow, but in essence having no-follow means you don't trust the page/site so why have it there in the first place (unless there is some commercial interest in having it there).

Fully agree - would definitely ask for nofollow links.

HeY!!! We have a coupons and deal website. Coupons are added and removed from the website on a daily basis. But crawler isn't crawling it that often. Lately we started fetching and rendering the page, but that is a time taking task as we have more than 500 stores with coupons. So, I was looking for some API or some method using which the crawler would crawl the website as defined. Suppose "x" store page should be crawled every alternate day as we daily update the coupons there, whereas "y"  store coupons are update fortnightly so , they can be crawled weekly. Can somebody suggest me something..

Hey!! We have a coupons and deal website. Coupons are added and removed from the website on a daily basis. But crawler isn't crawling it that often. Lately we started fetching and rendering the page, but that is a time taking task as we have more than 500 stores with coupons. So, I was looking for some API or some method using which the crawler would crawl the website as defined. Suppose "x" store page should be crawled every alternate day as we daily update the coupons there, whereas "y"  store coupons are update fortnightly so , they can be crawled weekly. Can somebody suggest me something..

Marcus, Arnout, Cyrus, excellent comments. Thanks a lot.

Personally I would find a way of thinking laterally about generating new and unique content for your existing and potential users. "Poetry is when you make new things familiar and familiar things new," according to marketing guru Rory Sutherland. This rings true with content.

Thanks everyone, every bit of info was very much appreciated!

It would sure help to get more specifics on the geographical area you intend to serve and the amount of traffic you expect. Where is your app/db server(s) and what kind of hardware will you be running? What kind of data will you be serving? Generally speaking, CDNs are built to scale to high traffic loads with low latency and high availability. A VPS would need to be configured for the type of data being served and would need to be constantly and consistently monitored for performance, whereas a CDN could be considered more of a set-it-and-forget-it service, granted you've built your application to utilize it properly. My best answer for you is to go with a CDN. The only case I could see you wanting to use a VPS is if it's cheaper and you server load is known and constant.