It is inline with Google policies as long as you add the rating to your organisation & not to an individual product.

If you check the different guidelines
(sources: https://developers.google.com/structured-data/policies & https://developers.google.com/structured-data/rich-snippets/reviews)

• When you have multiple entity types on a page, we recommend you mark up all entities on that page to help Google algorithms better understand and index your content  
  => OK -both organisation & product are being tagged
• Make sure the review or ratings markup refers clearly to a specific product or service as shown in the examples above
  => OK - aggregate reviews are done on item: organisation
• Review and rating markup should be used to provide review and/or rating information about a specific item, not about a category or a list of items.
  => same as above
• Make sure the reviews and ratings you mark up are readily available to users from the marked-up page. It should be immediately obvious to users that the page has review or ratings content.
  => I imagine you put the rating quite visible on the page, you probably also provide a link to the original source (trustpilot)

Don't see any issue here.

rgds,

Dirk

You can put in all your product pages. It seems a logical thing to do both for your company & and your users - a good score from a reliable source will reassure potential buyers that you're a serious company that can be trusted to buy stuff.

I am not sure if the aggregate rating will be displayed in the SERP's (most examples you see are ratings & reviews for individual products), but it will certainly do no harm.

rgds,

Dirk

Hi,

I don't really agree with the answer of Verbinteractive: disavowing links in WMT only concerns Google - there is no way Moz OSE is able to know that these links have been disavowed.

If these sites no longer exist than it's quite possible they will disappear in OSE, but not because of the disavow. If the links are from crappy sites it's quite possible that Moz crawled them once, but is not crawling them again (while the number of pages they crawl is huge - it's still limited).

Wait for the next crawl (Sept. 9th) & if these links are still present I would contact Moz directly.

rgds

Dirk

Hi Pete,

Personally I am not a big believer in trying to funnel link juice across the site - but theoretically yes, if you reduce the number of (unique) links on the home, the more link juice is passed to the categories below.

On the other side, the fewer links you have on the homepage, the more you are pushing content deeper in your site (number of clicks from the homepage to reach pages).

The other point - you can structure your URL anyway you want (best is to keep them quite simple so that they are easy to remember and not too long). For the depth - Google is looking at the number of clicks to reach this page (starting from home) - they are not counting the number of "/" in your url.

Hope this helps,

Dirk

Edit: you might want to check these resources: http://searchenginewatch.com/sew/news/2316757/matt-cutts-on-linking-guidelines-how-many-links-on-a-page - and this one https://moz.com/blog/how-many-links-is-too-many

Agree, coffee does make a difference. 3pm here in Europe so I already had my daily dose

Hi

Well - given the troubles Moz has to build the regular index in the past months I doubt they will add this feature anywhere soon.

Don't forget that DA & Trust is an internal metric of Moz - which tries to predict how well your site will rank in the SERP's. As all tools, it is just an estimate of the real thing.

Dirk

Just to add to the answer of Luis - in most cases Google is quite capable of guessing the intention of the searcher.

Even in countries that traditionally have a lot of accents, a lot of people are searching for the words without the accents. This is probably partially due to the fact that on mobile it's not always easy to get the accents right, but also due to laziness (it's generally faster to just type the word without the accents).

If you search on google.fr for référencement (correct spelling) or referencement - the results are identical. All the results however use the correct spelling in the meta description & title.(if you check Google trends for this keyword you'll notice that the wrong spelling is even slightly more popular than the correct version) 
If you take the example given in the question Luis is referencing - the results for Google.es for cursos de inglés & cursos de ingles are now identical as well

So my advice would be to use the correct spelling on your page - Google should normally be able to figure it out. 
Just make sure that you escape the foreign characters in your HTML.

rgds,

Dirk

Hi Sam,

To clarify - for me the correct spelling is the spelling using the accents. For the foreign characters I meant to encode them. In the example above: not use référencement in the HTML but rather référencement

rgds

Dirk

Hi Sander

Redirecting based on ip address can be quite tricky. If you would redirect US visitors based on ip address to the US site rather than the corporate site you risk that you will redirect the main Googlebot (who is crawling your site with a Californian ip) to the US site as well. You could exclude the Google ip's from the redirection - but that would be against the Google Guidelines (check http://googlewebmastercentral.blogspot.be/2008/06/how-google-defines-ip-delivery.html : "Googlebot should see the same content a typical user from the same IP address would see.")

You could consider to use the ip detection to show a message to US visitors - inviting them to visit the US site rather than the corporate one. This way you give the choice to the user - continue the visit on the corporate site or going to the dedicated US version (which is probably better in terms of usability as well - personally I always find it annoying when a site redirects me somewhere based on my location). For frequent visitors you could store their choice in a cookie & redirect them automatically if the cookie is set for this particular visitor)

Hope this helps,

Dirk

Hi Egol,

You can mask the url of the CDN behind your own url - so rather than displaying d3vam04na8c92l.cloudfront.net/imagename.jpg (the example is Cloudfront but it's possible for most CDN's) it could be something like images.mysite.com/imagename.jpg - so links to these pages would still be beneficial to your domain rather than the cdn.

Dirk

Hi Eva,

The setup you describe is quite a standard approach in countries with multiple languages - and should work just fine, even without the hreflang attributes. Check this article from https://support.google.com/webmasters/answer/182192?hl=en. I live in Belgium - as we have 3 languages most sites have this configuration. On first visit -the user is offered a choice of preferred language, which is stored in a cookie. On subsequent visits - based on his previous choice the user is than redirected to the chosen language version

Adding the hreflang can help, but can also introduce new problems  - you can check here how to avoid them -http://moz.com/blog/hreflang-behaviour-insights

Hope this helps,

Dirk

Hi,

First of all, are you sure that Google didn't take the migration into account?I just did a quick check on other https sites. Example: when I look for "Google Analytics"  in Google - the first 3 results are all pointing to Google Analytics site, however only for the 3rd result the https is shown, even when all three are in https. So it's possible it is just a display issue rather than a real issue.

Second, I did a quick crawl of your site and I noticed that on some pages you still have links to the http version of your site (they are redirected but it's better to keep your internal links clean - without redirections).

When I checked one of these pages (https://www.gomme-auto.it/pneumatici/pneumatici-cinesi) I noticed that this page has some issues as it seems to load elements which are not in https - possible there are others as well.

example: /pneumatici/pneumatici-cinesi:1395 Mixed Content: The page at 'https://www.gomme-auto.it/pneumatici/pneumatici-cinesi' was loaded over HTTPS, but requested an insecure image 'http://www.gomme-auto.it/i/pneumatici-cinesi.jpg'. This content should also be served over HTTPS.

The page you mention as example: the http version still receives two internal links from https://www.gomme-auto.it/blog/pneumatici-barum-gli-economici-che-assicurano-ottime-prestazioni and https://www.gomme-auto.it/pneumatici/continental with anchor texts 'pneumatici Barmum' & 'Barum'

Guess google reasons, if the owner of the site is not updating his internal links, I'm not going to update my index

On all your pages there is a part of the source which contains calls to the http version - it's inside a script so not sure if it's really important, but you could try to change it to https as well

My advice would be to crawl your site with Screaming Frog, and check where links exist to http versions and update these links to https (or use relative links - which is adviced by Google (https://support.google.com/webmasters/answer/6073543?hl=en see part 'common pitfalls')

rgds

Dirk

To be very honest I don't think it will make a difference if it's going to the /us/ version rather than the root.

If you prefer - you could keep the us version on the root & only redirect the non-us visitors to a country version.

Dirk