Webflow
Webflow wrong canonical: the global tag field
Webflow fills canonicals automatically, and three documented mistakes break them: a stale global tag URL, a page override, or a duplicate tag.
Webflow canonical errors usually come from a stale "Global canonical tag URL," a page-level canonical override, or a second tag injected through custom code or Google Tag Manager. Correct the global domain, remove or fix the page override, delete the duplicate source, publish, and confirm the live page has one canonical.
Why Webflow does this
Webflow's Help Center states "Note that canonical tags are automatically included in your site's <head> section", so the platform does the base work. Their docs name the ways it goes wrong. First, the global field under "Site settings > SEO > Global canonical tag URL": it "should match your site's default domain", and "You must exclude the trailing slash at the end of your URL" or "the canonical URLs for all of your site's subpages will include double slashes (e.g., //contact)". Second, the per-page override: "Enter the full canonical URL for the page in the Page canonical URL field" under Page settings, SEO settings, and "This overrides the global canonical tag for that page only." Third, a second tag from elsewhere: "If you inject your site's canonical tag through another tool (e.g., Google Tag Manager), you shouldn't set a global canonical tag in Webflow. This will create multiple canonical tags on your pages, which search engines may ignore entirely."
Check it right now
Before changing anything, confirm what a crawler actually sees. The check is free, takes one URL and needs no account.
How to fix it
- Go to Site settings > SEO > Global canonical tag URL.
- Confirm the domain matches the live site, the protocol is included, and there is no trailing slash.
- Open the affected page, click the Page settings cog, go to SEO settings, and check the "Page canonical URL" field for a stale override.
- Remove any second canonical injected through custom code or a tag manager.
- Publish the site.
- Re-check the page with the free canonical checker below.
Why it happens again
The global field is set once at site setup and the site outlives the person who set it: a domain migration leaves the old domain in the field, a trailing slash corrupts every subpage, and page-level overrides set for one campaign linger for years. Their docs even suggest asking Google to recrawl after changing the global tag, because the field goes stale quietly.
stillindexed re-checks the URLs you give it every 30 minutes on Starter and alerts when a directive changes, at most 30 minutes after it does. It is a monitor rather than a crawler: it watches a list you choose and tells you when one of seven things changes. Card first, no trial, and a 30 day refund.
Catching it next time
Fixing it once is the easy half. The setting that caused this can be changed again by anyone with access, and the page will keep returning 200 while it happens.
Other ways Webflow loses pages
A canonical tag pointing at the wrong URL, on other platforms
Sources
Every claim about Webflow above is from their own documentation, read on 2026-08-30. Platforms change their settings; if one of these is out of date, their page wins and we would like to know.