Store Views, Basic URLs and Language Linking
Compare voice mapping and canonicals across store views. An international extension must use the appropriate public store URLs.
The language of a Store View and the public URL assignment must match the output language set. Additional internationalization extensions can generate the references independently of the store switch.
Where to check the setting in Magento
Compare Store View, base URL and voice mapping of the specific page. Additional hreflang outputs may come from an extension. Check their product or category assignment before entering a domain as an alternative language version.
Example of this specific finding
Illustrative control case: An English performance page is called as a language alternative, but its canonical points to the German version. Translation and duplicate consolidation are contradictory.
follow-up audit in Magento
Track an identical product in the intended store views and check availability, canonical and reference back. Store IDs alone are not a public language URL.
Maintain independent language versions with their respective matching canonical URL. Test language set and canonical goals together.
Derogations and scope
Almost identical regional sides of the same language may require a differentiated decision; different languages may not be combined in a blanket manner.
Reference: Magento Open Source or Adobe Commerce with classic storefront. Consider store views and extensions; other storefront architectures have their own configurations.
Classify the general error
Definition, system-independent causes and further correction examples: Keeping translations and real duplicates apart