Welcome to the Q&A Forum

Placing a rel=canonical on your own blogposts to HuffPost is essentially telling Google that you're not unique enough to be indexed and that you want all ranking juice to flow to HP. Which isn't the case I guess. I would leave it alone. Nevertheless it will be very hard to outrank HP in this case.

This is what Yoast tells us about cross domain canonicals: _"You might have the same piece of content on several domains. For instance, SearchEngineJournal regularly republishes articles from Yoast.com (with explicit permission). Look at every one of those articles, and you’ll see a rel=canonical link point right back at our original article. This means all the links pointing at their version of the article count towards the ranking of our canonical version. They get to use our content to please their audience; we get a clear benefit from it too. Everybody wins." _(https://yoast.com/rel-canonical/#cross-domain-canonical)

So IF you can get HP to put a canonical to your own blog, this would be highly favorable for your own ranking. You could use the 'everybody wins' argument to try to get this working.

As long as your organic traffic is doing fine I shouldn't be too concerned. That being said:

• Is your robots.txt or search console disallowing crawler access to parameters like '?count=' or '?color='?
• Is your robots.txt disallowing crawler access to urls that have a 'noindex' but were indexed before they got noindex?
• You can also take a couple of parameters from your site and test if any url's have been indexed, by using the 'inurl:parameter site:www.site.com' query.
• Are some of the canonicalized urls indexed anyway? This may indicate that page content is different enough for Google to index both versions.
• If there's a ton of articles that go in and out of stock and use dynamic ID's, Google may keep these in their index. Do out of stock articles return a 404 or are they kept alive?

You can read more here: http://searchengineland.com/faq-google-mobile-first-index-262751 

I don't think different banners, navigation or footers have real impact as you'd expect this to be different across screen sizes. I'd be concerned if my texts or internal linking are considerably different between both versions, or when there's content on the desktop version of the site that's not on the mobile version.

If 'stuff is hidden with CSS' means you're hiding texts, you should really look for a different solution as hiding text is against Google's guidelines.

Alt tags are more important for SEO as far as I know. I think titles do help, but it can get complicated really fast if you want to have unique filenames for several languages. I'd go with the unique alt tag solution.

A strong site structure, some decent backlinks and a strong, optimized site are going to have much more of an impact on rankings anyway.

Then again, if you have just a couple of images and are really concerned about everything being perfect to the last detail, you could use different image filenames.

Hi everyone,

Here's a duplicate content challenge I'm facing: Let's assume that we sell brown, blue, white and black 'Nike Shoes model 2017'. Because of technical reasons, we really need four urls to properly show these variations on our website. We find substantial search volume on 'Nike Shoes model 2017', but none on any of the color variants.

Would it be theoretically possible to show page A, B, C and D on the website and:

• Give each page a canonical to page X, which is the 'default' page that we want to rank in Google (a product page that has a color selector) but is not directly linked from the site
• Mention page X in the sitemap.xml. (And not A, B, C or D).

So the 'clean' urls get indexed and the color variations do not?

In other words: Is it possible to rank a page that is only discovered via sitemap and canonicals?

I'm not sure why you would want to do this, you use a canonical when page A and B are more or less the same and you want Google to index only page A.

When page A and page B are different, a canonical would make no sense and Google will probably ignore it.