Make sure products are in your sitemap and it has been re-submitted. You can also submit your products to request indexing for them in Google Search Console.

While you may not want context indexed, it's still valuable to be crawled and access your most important content like products.

If you are blocking your /collections pages, Google will not be able to see that page's meta robots set to noindex, causing an issue for you. You may consider allowing robots to crawl your /collections pages but noindex them if they are low value or duplicative.

Recently @JohnMu mentioned that site: is not reliable to check pages in index. The new GSC should help you better understand how Google is seeing and valuing your content.

Regardless can you change it so that root file without params is a page that has value? and potentially a page that provides a means of navigation to your parameterized results? This would be a more search friendly setup IMO.

It's getting harder and you may see a gradual decline for that ranking if it does not match the intent. Some queries are harder than others and will have mixed results so it always will depend on what you are seeing longer term for trends and ranking performance in your space.

Take a look at the top results manually for the query you target and you should be able to better understand the intent. Depending on your niche or vertical, pricing on queries in Adwords can also help as queries with a higher purchase intent (for example) will have higher CPCs.

It's a signal that may be valuable for sites but one that may not have a huge impact on it's own.

I like to have shorter URLs because it ends up being easier and more friendly to share. Longer URLs can be a deterrent. I also like to pay closer attention to the click depth of the page, not just length of the URL.

I'm not sure you'll be hurt by a long URL like:
http://www.yourtld.com/blog/02/08/18/some-crazy-long-slug-nested-with-dates-that-triggers-moz-errors

I would bet you can get that page ranked if the content is valuable enough, even with a longer URL. But the issues start to pop up If you have a site that has content only found by browsing the nested pages it is a larger issue.

For example:
http://yourtold.com/services/cleaning/windows/indoors
This is an example where I'm really worried about the length, but more importantly the overall structure of the URL and site. It may be difficult users, and crawlers to find this content making it less search friendly overall when the content is 4-5 layers deep.

You don't want to canonicalize to another country version. Keep that rule in mind and generate all the hreflang tags you have for language/locations.

Use this to guide you:
http://www.aleydasolis.com/en/international-seo-tools/hreflang-tags-generator/

Another great doc outlining using the same language in different regions:
https://support.google.com/webmasters/answer/189077?hl=en

Hey Matt,

The canonical tags should not be used across different language or country versions.

http://example.com/fr/sample-post -> canonical: http://example.com/fr/sample-post

http://example.com/sample-post -> canonical: http://example.com/sample-post

Each page would have the alternate version hreflang tags setup.

Hope this helps!

Per FAQ: https://sites.google.com/site/webmasterhelpforum/en/faq-internationalisation#q20