Welcome to the Q&A Forum

Aha I see! That makes some sense. If the products are 'branded' and therefore the name never changes in any language, you have two options Let's imagine you are selling a branded air conditioning unit, with the made-up name of GreenAir (maybe it's more economical and uses less electricity, thus the name from the 'green movement') You could just leave it duplicate: EN: GreenAir | GreenWave Solutions FR: GreenAir | GreenWave Solutions Or you could add more contextual info, which would be better: EN: GreenAir Environmental Air Conditioning Unit | GreenWave FR: GreenAir Unité de Climatisation Environnementale | GreenWave I know, I know - my French sucks (actually that's from Google Translate). But still, you can see that - you could add more in there. The hurdle for you will be, what is required in terms of costs to deploy to that level of complexity? From a straight-up SEO POV, I stand by my preference. But once mass translation work is factored and targeted, dev-based implementation... you may feel otherwise!

Hey, Try fetch and render from Google Search Console. There you could check if there is an X-Robots-Tag in the response header. For reference: https://developers.google.com/search/reference/robots_meta_tag

Simple. If SEO tactics are a part of your scope of services contracted with the client, you need to implement the H1. If not, there's no reason to.

Nick, I've inherited a number of sites with this same problem, some of them quite large sites with rampant singe-keyword landing pages that required a lot of cleanup. In my opinion, in the long run it's definitely worth the effort to prune where you can and get same/similar content combined into one higher quality page. I've had pretty good success in combining pages into topical focused LPs. There's been a lot of talk in the SEO world over the last year about "topics, not keywords", and this discussion is exactly where that idea comes into play. With Google's increasing effort at better understanding keyword intent, they've gotten really good at determining synonymous phrases. As a result, sites with single-keyword LPs are suffering (or will eventually) due to content cannibalization. Let's say you have a LP for "blue widgets" and another for "widgets that are blue", eventually those 2 pages are going to compete with each other and Google will choose to rank neither very well. If you do go down the road to combining pages, here's a few tips: Look in Google Analytics for page metrics like organic entrances, conversions, whatever other KPIs are important for you site Check Moz metrics like Page Authority and links Grab bits of content from the pages going away - just because the overall page is lower quality than others doesn't mean it doesn't have some good content you can 301 redirect the old pages to the new one so search engines, people, and links will still lead to relevant content Update internal links and your XML sitemap to reflect the changes Hope that helps, happy optimizing!

Added to note - you can also use GDC to inform Google which URL parameters should be ignored when indexing - can be a quick shortcut initially, but you'll definitely want to get rel-canonical properly implemented for Google as well as all the other search engines.

There quite few you can use for this purposes. I use Seranking.com and their site audit here is a list of 100 free SEO tools

In general, redirects can cause you to lose a small amount of equity. Both a 301 and a Canonical are forms of redirects except a canonical really only redirects the bots without redirecting the user. So much in the same way that it is not best to 301 to a 301 (though you can), it isn't best to Canonical to a 301. Now, it most likely won't hurt you doing that, if you prefer the easier of the two solutions, but its also important to remember that a canonical is a suggestion (not a directive). So the search engines can choose to disregard your canonical if they feel it is manipulative or not relevant. With this in mind, it is always better to point your canonical at the best, most relevant canon page instead of to another redirect.