Webflow handles SEO better than most visual builders. What it does not do is set anything up for you, and a designer-built project reliably ships with the same handful of gaps. Here is the list, in the order worth fixing.
Site-wide settings
1. Disable .webflow.io subdomain indexing. Project Settings → SEO → toggle it off. Otherwise your staging subdomain competes with production on duplicate content. This is the most common serious mistake on Webflow sites.
2. Set the site-wide robots.txt. Project Settings → SEO. Block /search and any utility paths, and point to your sitemap.
3. Enable auto-generated sitemap — or upload your own if you need control over what is included.
4. Confirm SSL and a single canonical host. Force HTTPS, and pick either www or non-www and redirect the other. Both resolving independently splits your signals.
5. Set the global canonical tag in Project Settings, so every page defaults to self-referencing.
6. Add Organization schema to the site-wide head via custom code. Webflow has no plugin ecosystem, so structured data is hand-written — see which schema types are worth implementing.
Static page settings
7. Write unique titles and meta descriptions per page. Page Settings → SEO. Webflow leaves these blank by default, so Google invents your snippet.
8. Set Open Graph fields. Separate tab from SEO settings, frequently missed entirely, which is why the site looks broken when anyone shares it.
9. Check heading hierarchy. Webflow makes it trivially easy to pick an H1 for visual size. One H1 per page, no skipped levels — the header tags guide covers the structure.
10. Add alt text to every meaningful image. The Assets panel lets you set it once per asset rather than per placement.
CMS Collection settings — where the real problems are
11. Template the Collection page title and meta description. Page Settings on the Collection template, using field references like Name and Summary. Leave these static and all 200 items ship an identical snippet, which is the single biggest SEO problem on most Webflow sites.
12. Template the Open Graph fields too, including the OG image bound to the item’s own image field.
13. Bind the canonical tag on Collection templates so each item self-canonicalises.
14. Add item-level schema — Article, Product or whatever matches — as a custom code embed on the template with field references bound into the JSON-LD.
15. Fix orphaned Collection items. Items reachable only through a paginated Collection List sit several clicks deep with almost no internal link equity. Add related-item modules, category hub pages and breadcrumbs so every item has real internal links. This is the leading cause of orphan pages on Webflow builds.
16. Create redirects when you change a slug. Editing a CMS slug silently breaks every URL pointing at the old one, and Webflow does not create the redirect for you. Project Settings → Publishing → 301 Redirects, every time.
Performance
17. Compress and resize images before upload. Webflow serves responsive variants but will not fix a 4MB hero. This is usually the largest single Core Web Vitals win available — see the Core Web Vitals guide for what to target.
18. Cut unused fonts and heavy embeds. Four font weights loaded for two, plus a Lottie animation on a page that did not need one, is a routine finding. Each custom font weight is a separate render-blocking request.
What you cannot fix in Webflow
Be realistic about the ceiling before you spend months against it:
- No server log access, so crawl-budget analysis on large sites is guesswork
- No server-side redirect logic beyond simple path matching
- CMS item limits that bite hard on large catalogues and programmatic pages
- Limited control over rendering and headers compared to a custom stack
None of these matter for a marketing site of a few hundred pages. All of them matter at ten thousand. If you are hitting them, the honest answer is a migration rather than more optimisation.
Working through it
Items 11 through 16 are template-level: fix the template once and every item using it is corrected at the same time. That is why Webflow SEO work tends to cost less per page than the WordPress equivalent — and why it is worth doing properly once rather than page by page.
If you would rather have it done in your project, that is our Webflow SEO service.
