SEO for Webflow: configuration and publishing guide

Webflow SEO brings together the default domain, canonical configuration, and CMS Collection data. A common failure is a setting that works for one static page but produces incorrect output across Collection items after a domain or template change.

Align the domain and canonical base

Choose the default domain before configuring the global canonical URL. Include the protocol and match the domain intended for visitors. Do not use custom code that assigns the homepage address to every page. If another tool already injects canonical markup, choose one owner to avoid duplicate elements. Publish the website and request a subpage rather than assuming a saved configuration proves the public output is correct.

Derive Collection metadata from meaningful fields

Use service names, locations, or article titles to create item-specific metadata. Inspect an item with missing fields so fallback behavior is visible. A Collection containing many interchangeable pages does not become useful search content merely because each title changes. Add examples, specifications, or answers specific to each item before making the whole group available for indexing.

Treat publication as part of SEO maintenance

Distinguish the custom-domain website from staging when inspecting links and canonicals. After changing a slug, follow an existing external link and confirm its new destination still serves the same purpose. Document exceptions for static pages with custom canonical targets so later template changes do not propagate them across the site. Recheck the menu, sitemap, and one newly published item after significant releases to catch errors introduced at the shared-template level.

A worked publishing scenario

Illustrative scenario: an agency launches a site on its branded domain after working on staging. Align the default domain and canonical base, publish, then inspect a static page and a Collection item. Each should retain its individual path under the intended domain instead of sharing the homepage canonical. Keep a record of the previous settings so an incomplete domain transition can be reversed. Test navigation from the published homepage, not only direct links copied from the Designer.

A release checklist you can repeat

Keep a small inventory of important pages before changing the website: record the current URL, intended audience, title, and preferred canonical. Make one category of changes at a time and preserve a way to restore the previous configuration. Start with an accessible, useful page rather than optimizing a score while its content remains unavailable.

For translated content, publish a complete version in each language at its own address. Review self-referencing canonicals and reciprocal language links, then include eligible URLs in the sitemap. A translated page is not automatically a duplicate merely because its meaning matches another language. Search engines still decide which pages to index; no configuration promises a ranking or a traffic increase.

Tools and related guidance

• Follow the Webflow diagnostic workflow
• Check a public URL
• Inspect a redirect chain

Official references

• Webflow: canonical tags
• Webflow: default domain