Welcome to the Q&A Forum

Thanks for this! 2 things: I'd suggest that if Site A republishes duplicate (syndicated) content from Site B and references Site B as the original source, you might want to consider simply blocking that content from search engines (on Site A). This will ensure that Google doesn't penalize for dupe content and also will prevent them from seeing the critical errors on the Site B AMP pages. Overall I've tested your example page and couldn't find anything seriously wrong, but one thing I did notice was that in your structured data markup (NewsArticle) you have an error: On the page: http://m.businesstoday.in/lite/story/reliance-jio-is-preparing-new-tariffs-and-exciting-offers-for-you/1/249662.html You list "mainEntityOfPage" as "http://m.businesstoday.in/" However, the Google guidelines state that "mainEntityOfPage" should be the canonical URL of the article page: https://developers.google.com/search/docs/data-types/articles#type_definitions (in this case: http://www.businesstoday.in/sectors/telecom/reliance-jio-is-preparing-new-tariffs-and-exciting-offers-for-you/story/249662.html) Although the markup does pass the structured data testing tool validation, it is possible that this is breaking the structured data and using NewsArticle markup is something that Google states you must have implemented to feature in the News Carousel. If fixing this doesn't help, I'd suggest cleaning up the non-critical errors next to see if that fixes the issue.

I personally have not seen this before, but that is due to being English speaking only. I don't see much else on the web about it either which lead me to wonder if it was due to account settings for some reason. I'll flag this up as a discussion, see if we can find someone that has dealt with this before.

Hi there, In any case I would not expect a lot of traffic to posts that are syndicated. Generally people use syndicated content to supplement what's already there. So if the idea is to get more traffic through these posts, I would suggest finding another way. Having said that, my understanding is that syndication-source still works, but canonical will override it. If you have something that says they no longer recognize it I have never seen it. I've used syndication-source when I don't know the URL or where a CMS/API doesn't allow me to get the URL, as you can point syndication-source back to the root domain URL. I've also seen sites just post something like "Originally published on http://example.com/page" without incurring any penalties. To do it by the book, I'd suggest canonical first, syndication-source second, and a source link third. And in this case I'd suggest doing it by the book because syndicated content is generally not going to give you a lot of organic search benefit. Hopefully that helps.

Making sure that the https pages are canonicalized to https pages should be relatively easy and within your control. I would get that done right away. If the canonicalization wasn't done right in the migration, it makes me wonder what else may not be right with the move to https. You might want to look here https://moz.com/blog/seo-tips-https-ssl, especially the links under "best practices" and double check all that. The unnatural link clean up and reconsideration request will be more work intensive and take a lot more time and is on some level not entirely within your control, as you are left at Google's mercy. Both need to be done, but they seem like very different sized problems with very different timelines to payoff. Best of luck! ... Mike

My understanding is that AMP pages don't need to be HTTPS themselves, but the resources they link to often need to be (see https://www.ampproject.org/docs/reference/validation_errors.html). I think that is so it can be cached by Google and served on an HTTPS site without problems.

Thanks a lot for your response ! Much appreciated.