Localization and published language variants
Compare published language versions and their associated pages. A not yet published locale cannot form an achievable reference target.
Check the existing locales and the configured generation of the language references. Not every translated text preview already corresponds to a published own language URL.
Where to check the setting in Webflow
Compare published locale pages, their paths, and the issued alternative language URLs. For dynamic pages, check the specific collection item in each language. An activated language alone does not ensure a complete translation of all items.
Example of this specific finding
Illustrative control case: The German side calls the English version, which knows only itself. The language set is incomplete.
follow-up audit in Webflow
Compare the specific localized pages with canonical and counter references. Check domain/path changes after re-publishing.
Retrieve the assignment from both URLs and supplement backlinks. For multiple languages, check the entire set instead of just a single pair.
Derogations and scope
A link in the voice menu does not replace the hreflang assignment. Both can come from different data sources.
Reference: Websites published on Webflow and CMS Collections. Exported HTML or an upstream own proxy layer may have other responsibilities.
Classify the general error
Definition, system-independent causes and further correction examples: Check language references as a related group