Guides
Webflow SEO Checklist: Static Pages, CMS Collections & Launch QA
Webflow makes SEO fields accessible, but collection patterns and publishing choices can repeat one error across every CMS item. Audit the output by template.
Run a fresh DomainLens audit and use the report as your priority list.
Map the Webflow site before opening page settings
List static pages, each CMS Collection template, ecommerce templates, localized variants, utility pages, old paths, and custom-code integrations. Mark which URL types should be indexable. This exposes a common problem: the sitemap contains technically valid pages that have no distinct search intent.
Set the canonical host once—and verify the result everywhere
Set the default domain and match it in Site settings → SEO → Global canonical tag URL. Webflow’s canonical documentation warns against also injecting a canonical with another tool, because duplicate tags create conflicting signals.
- 1Inspect one static and one CMS URL for exactly one absolute canonical.
- 2Confirm staging.webflow.io and alternate hostnames do not appear in canonicals, sitemap entries, or internal links.
- 3Use a page-level override only when the page intentionally consolidates into another URL.
- 4After slug changes, add a 301 in Site settings → Publishing → 301 redirects and test the complete chain.
Treat CMS SEO fields as data quality rules
Test the weakest CMS item, not only the polished example. Empty optional fields, long names, archived items, and duplicated categories reveal whether the template degrades safely.
| Pattern | Failure mode | Better rule |
|---|---|---|
| {Name} | Brand | Empty or vague item names create weak titles | Require a descriptive SEO title or validate Name before publish |
| {Summary} | Missing summaries produce blank descriptions | Dedicated SEO description with a controlled fallback |
| {Slug} | Imported IDs or duplicate slugs become public URLs | Human-readable unique slug reviewed before publish |
| Generic H1 text | Every collection item has the same heading | Bind H1 to the item’s primary topic field |
| Shared schema JSON | All items claim identical values | Bind valid fields and omit schema when required data is absent |
Control sitemap and indexability deliberately
Webflow can generate sitemap.xml and updates it on publish. Its sitemap controls are useful, but inclusion should follow your indexability plan. Exclude utility, campaign duplicate, gated, and thin CMS pages rather than hoping Google filters them correctly.
- Do not block a URL in robots.txt when you need Google to see its noindex directive.
- Keep only canonical 200 URLs in the sitemap; redirects and noindex pages create mixed signals.
- With Webflow Localize, verify reciprocal hreflang and localized titles/content on real published URLs.
- Ensure filters and site search do not expose unlimited crawlable parameter combinations.
Audit design choices that hide meaning or shift layout
Webflow lets a designer use any text element as any heading level. Inspect the rendered outline: the page topic belongs in one H1, major sections in H2, and card titles at the appropriate lower level. Do not select headings for font size.
- Add useful alt text to informative images and empty alt text to decorative assets.
- Provide width/height or aspect ratio for images, embeds, and CMS media to prevent CLS.
- Avoid loading the hero as a CSS background when a responsive image element would be discoverable and prioritizable.
- Limit interactions, large Lottie files, background video, and third-party embeds above the fold.
Launch validation for a Webflow publish
Use the site migration checklist when a Webflow launch also changes domains, URL paths, or CMS structure.
- 1Publish to the production domain and crawl that host, not the Designer preview.
- 2Run DomainLens on one URL per template and compare status, robots, canonical, H1, schema, links, and performance.
- 3Open sitemap.xml and robots.txt and check that each references the production host.
- 4Test redirects with old URLs and confirm one-hop 301 responses.
- 5Inspect live URLs in Search Console, submit the sitemap, and monitor excluded pages and duplicate canonicals.