Global canonical tag URL and Page Override
Check the global canonical base and any existing page-related overrides. After the change, control the published domain, not just the designer.
Compare the global base URL with the published standard domain. Webflow combines this base with the respective page path. A canonical for a static page or additional custom code can deviate from this.
Where to check the setting in Webflow
Under Site settings → SEO, check the Global canonical tag URL and additional canonicals at the page level or in the custom code. The global value describes the preferred base; a second individually inserted output must not point to another landing page.
Example of this specific finding
Illustrative control case: An article page and its tracking variant provide the same text, but not a preferred URL. The variants must first be compared in terms of content.
<!-- Auf Artikel und identischer Trackingvariante -->
<link rel="canonical" href="https://example.org/ratgeber/bremsen/">follow-up audit in Webflow
Test a static page and a collection item after publication. Do not add another canonical edition via Tag Manager or Custom Code if the native edition is already in charge.
For these identical variants, consistently specify the clean article URL. Internal links and sitemap should give the same address.
Derogations and scope
A unique page without a canonical is not automatically unindexable. Even an existing canonical does not guarantee the selection by Google.
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: A missing canonical is not a blanket indexing error