You Can Publish Different Language Variations of Content Without Using Subdomains or Subdirectories
Content in different language variations should be on different URLs, but it doesn’t necessarily need to be put on subdirectories or subdomains. For example, this could be achieved with different parameters.
Only One Version of Same Content On Different Country Sites will be Indexed & Appear in GSC Performance Reports
If you have the same content on multiple language variation sites, Google will pick one to index but will use hreflang attributes to swap out versions of the page based on a user’s location. However, only the page that has been chosen to be indexed, and used as the canonical, will be displayed in the GSC performance report.
Translated Content is Treated as a Completely New Piece of Content
Content that has been translated by a translator is treated as unique content and not seen as spun content, this is because the words are different when translated from one language to another.
Both ccTLDs and GSC Geo-targeting are Equivalent Methods of Country Targeting
When determining a country to target, John recommends two main methods. The first is using a ccTLD, the other is using a generic TLD and specifyng the geo-targeting in GSC. Both of these methods are equivalent and used by Google to determine language targeting for websites.
Adding New Language Versions Alongside Migration Can Delay Processing
For Google to be able to process site migrations quickly, they need to be one-to-one moves. Adding new language versions alongside a migration means Google will need to process each of these versions separately which will take longer.
Consider Number of Language Variations When Deciding on Approach to Internationalization
Consider the number of language variations when deciding how to configure international versions of a website. If there are many versions you may want to let the user decide which version they want to view, but if there are only a few versions you may be able to guess for them.
Make Pages Accessible to Googlebot For Each Language Version of a Page
For sites with redirects based on the user’s IP or browser language, John recommends having landing pages available for each individual language, including hreflang on each with an x-default to the main page.
Use Hreflang & Canonical Tags to Handle Partially Translated Websites
John recommends using canonical tags and hreflang tags to tell Google which language version is preferred if you only have parts of a website that are translated, instead of the entire site.
Same Language Country Versions Can Cause Problems With Location-specific Information in SERPs
Google swapping out URLs for same language country versions of a page can be problematic when the title or structured data shown in the SERPs includes location-specific information, such as pricing. E.g. a Swiss searcher sees the Swiss URL but German pricing in Euros.