- Webflow SEO happens at three levels: site-wide settings you set once, page settings you check on every page, and CMS templates that set SEO for hundreds of items at once.
- Set the site-wide basics first: one primary domain, an auto-generated sitemap, staging indexing turned off and redirects for every changed URL.
- Every page needs a unique title tag, meta description, one H1, a clean slug and an Open Graph image.
- Bind CMS template SEO fields to dedicated CMS fields, so every new post publishes with correct metadata without a developer.
- Webflow handles the technical basics well: when we audited our own site, crawl, links, speed and security scored 98 to 100.
What should a Webflow SEO checklist cover?
It should cover three levels: site-wide settings, individual pages and CMS templates. Most SEO problems we find on Webflow sites come from one level being set up and the others forgotten, for example perfect static pages and a blog template with no meta descriptions.
Yes, Webflow is good for SEO. It outputs clean code, generates your sitemap and gives you a field for every important setting. But it does not fill those fields for you. This checklist covers the settings. For strategy, like content clusters and which keywords to target, see our guide to growing traffic on a Webflow site.
Which site-wide SEO settings should you set once?
Set these when the site launches and review them after every major change. Most live in Site settings, under the SEO and Publishing tabs.
- One primary domain. Choose www or non-www and set it as the default, so every other version redirects to it.
- Auto-generated sitemap on. In Site settings, then SEO, turn on the auto-generated sitemap. Webflow updates it on every publish and adds a last-modified date to each URL.
- Staging indexing off. Turn off indexing for your webflow.io staging domain, so Google does not find a duplicate copy of your site.
- AI and search bots allowed. Webflow's traffic control settings can block groups of search and AI bots. Leave them allowed if you want to appear in ChatGPT, Claude and Gemini answers. Our guide to getting cited by AI search explains why.
- 301 redirects for every changed URL. Add them in Site settings, then Publishing, and avoid chains where one redirect points to another.
- Search Console connected. Verify the domain in Google Search Console and submit your sitemap.
- A useful 404 page. Link it to your main pages, so lost visitors and crawlers find their way back.
What should you check on every static page?
Check the same six things on every page before it goes live. This table shows where each one lives in Webflow and what good looks like:
Also check heading order (H2s under the H1, H3s under H2s) and add at least two internal links to related pages. Turning “Sitemap indexing” off adds a noindex tag and removes the page from your sitemap, which is the right setting for thin pages like form confirmations.
How do you set SEO on Webflow CMS templates?
Set it once on the template, and every item in the collection inherits it. This is where Webflow SEO saves the most time, and where most sites cut corners.
- Create dedicated SEO fields. Add “SEO title” and “Meta description” fields to each collection and bind the template's SEO settings to them. Falling back to the post name works, but dedicated fields let you write for search without changing the visible headline.
- Bind the Open Graph image to the featured image field, so every shared post has a preview.
- Add an alt text field for CMS images, or use the asset's alt text, and make it required for your editors.
- Control indexing per item. Turn “Sitemap indexing” off for thin or outdated items instead of deleting them.
- Keep rich text headings in order. Editors should start sections at H2, never a second H1.
From our projects: Kolibri's marketing team published 30+ ebooks and articles in under eight months with no developer involved, on a modular CMS we built for exactly that. When SEO fields are part of the template, every new resource goes live with a title, meta description and preview image without anyone having to remember.
How do you optimize images and speed in Webflow?
Keep images small and described, and keep third-party scripts to a minimum. Speed problems on Webflow sites almost always come from what was added to the site, not from Webflow itself.
- Write alt text for every meaningful image in the asset settings. Leave decorative images empty.
- Convert images to WebP or AVIF in the Assets panel and upload them at the size they display.
- Avoid heavy background videos and Lottie files above the fold. They hurt Largest Contentful Paint, the Core Web Vitals score for load speed.
- Audit third-party scripts. Chat widgets, heatmaps and old tracking pixels add up. Remove what nobody uses.
- Test on mobile. Run your key pages through Google PageSpeed Insights after every major change.
What schema should a Webflow site have?
Most marketing sites need four types of structured data: Organization on the homepage, Article on blog posts, FAQ on pages with a FAQ section, and Breadcrumb on deeper pages.
Webflow does not add schema automatically. Add it as custom code in the page head, and on CMS templates use CMS fields inside the code, so each post gets its own title, date and author. Validate every template with Google's Rich Results Test, because schema with errors is ignored.
If you run a site in more than one language, Webflow's auto-generated sitemap adds hreflang tags for each locale.
What should you check before every publish?
Run a short routine before each publish. It takes five minutes and catches most problems before Google does:
- Every new page has a unique title tag, meta description and one H1.
- New CMS items have their SEO fields, alt text and Open Graph image filled in.
- Any page you renamed or moved has a 301 redirect from its old URL.
- Test, thank you and draft pages have “Sitemap indexing” turned off.
- New links work and point to live pages, not staging.
Webflow's site audit panel flags some of these, like missing alt text. It does not replace the routine, because it cannot judge whether your title tag matches what people search for.
Who should own SEO settings on a Webflow site?
The marketing team should own page and CMS SEO day to day, and the site should be built so that the defaults are already right. When templates have the SEO fields built in, publishing correctly becomes the easy path instead of a checklist someone forgets.
When we audited our own site this year, crawl, links, speed and security scored 98 to 100. That is the pattern we see on most Webflow sites: the settings are usually in good shape, and the bigger gains come from the content and structure built on top of them. If you are moving from another platform, our WordPress to Webflow migration guide shows how to keep rankings during the move.
If your templates were not built this way, a Transform project rebuilds them so every page and post your team publishes starts with the right SEO setup.
