The short answer
- Webflow covers technical SEO natively: per-page titles, meta descriptions and Open Graph, an auto-generated sitemap, global and page-level canonical tags, 301 redirects, and robots.txt controls.
- On CMS template pages, use dynamic fields in the SEO settings so every item gets a unique title and description.
- There is no built-in schema builder. Add JSON-LD in the page's custom code, and on Collection templates insert CMS fields into it.
- When you change a slug, tick the option to permanently redirect the old URL, or add the 301 under Site settings, Publishing.
- The settings are the easy part. Webflow sites rank on CMS content published consistently against real keyword demand.
Webflow SEO is mostly configuration you do once, plus a CMS you have to keep feeding. Webflow handles the technical layer well. What it cannot do is decide what to write.
This guide walks through every native setting, how to handle CMS collections, schema via custom code, and the publishing habit that turns a fast site into a ranking one.
Page-level SEO settings
Every static page has an SEO section in Page settings with three fields that matter: the SEO title, the meta description, and the Open Graph title, description and image used when the page is shared.
Webflow's own SEO guidance recommends:
- Titles under 60 characters to avoid truncation.
- Meta descriptions of 150 to 160 characters.
- The primary keyword in both, written naturally.
- Unique metadata on every page.
Webflow AI can draft titles and descriptions from page content. Read every draft before publishing; a generated description that misstates a price or feature does more harm than a plain one.
Slugs
Static page slugs live in Page settings. CMS item slugs are created automatically from the item name, so a post titled "The Complete Guide to Choosing a CRM for Small Teams" gets a long slug unless you shorten it. Trim it before publishing.
One structural limit to plan around: Webflow does not let a Collection and a page folder share the same slug. A single directory cannot mix static and CMS pages. If you want /guides/ to hold both a hand-built landing page and CMS articles, design the URL structure before you build.
CMS collections and dynamic SEO
Blog posts, case studies, location pages and glossary entries all live in CMS Collections, each rendered through one Collection template page. The SEO settings on that template apply to every item.
Use dynamic fields
In the Collection template's page settings, the SEO title, meta description and Open Graph fields accept CMS fields. Set a pattern once:
| Field | Pattern | Result for one item |
|---|---|---|
| SEO title | [SEO Title field] | CRM for Small Teams: How to Choose in 2026 |
| Meta description | [Meta Description field] | Compare pricing, pipeline features and setup time for small-team CRMs, with a checklist. |
| OG image | [Main Image field] | The post's hero image |
Add dedicated SEO Title and Meta Description fields to the Collection instead of reusing the post name and summary. The H1 and the SEO title often need different wording, and a separate field lets you write each properly.
Index only what deserves it
Webflow lists CMS item indexing control among its plan features, so you can keep individual items out of search. Use it for thin items: tag-style collections with one entry, placeholder locations, or old announcements.
Sitemap, robots.txt and canonical tags
Sitemap
In Site settings, under the SEO tab, turn on Auto-generate sitemap. Webflow then builds sitemap.xml and updates it each time you publish.
Submit yourdomain.com/sitemap.xml in Google Search Console after the first publish on your custom domain.
robots.txt and llms.txt
Webflow's plan comparison lists robots.txt and llms.txt controls and crawler access controls that can allow or block search engine crawlers and AI bots. Do not block AI crawlers by reflex if you want to be cited in AI answers. The AEO grader checks how ready a page is to be quoted by AI assistants.
Canonical tags
Set the Global canonical tag URL in Site settings, under SEO, to your primary domain, in the exact form you use (www or non-www). Webflow then outputs a canonical tag on every page. Page-level canonicals are available for cases where one page should point to another.
Set it as soon as the custom domain is live, so search engines treat that domain, not the webflow.io staging address, as the primary version of every page.
301 redirects
Redirects live in Site settings, under Publishing, in the 301 redirects section. Enter the old path, the new path, add it, and publish.
When you change a slug in Page settings, Webflow offers a checkbox to permanently redirect the old URL to the new one. Tick it every time. A changed slug without a redirect turns every backlink and ranking for that page into a 404.
Before a migration into Webflow, export every URL from the old site, map each to its new path, and load the redirects before you switch DNS. Webflow's guidance on URL changes during migration is the same: redirects are what keep visibility.
Schema via custom code
Webflow has no built-in structured data generator. You add JSON-LD as custom code in the head of a page through Page settings. Webflow recommends JSON-LD over Microdata as the format that scales best.
Static pages
Add Organization schema on the home page, and FAQPage, Product or Service schema where the visible content supports it. Validate with Schema.org's validator or Google's Rich Results Test before publishing.
Collection templates
This is where Webflow's approach pays off. Add the JSON-LD pattern to the Collection template's custom code, then replace values with CMS fields using the Add Field option. Every item page gets its own markup automatically. A BlogPosting block might pull:
- headline from the Name field
- image from the Main Image field
- datePublished from the Published Date field
- author.name from a referenced Author collection
Watch for quotes and line breaks inside CMS text fields; they can break the JSON. Keep fields that feed schema short and plain.
Performance
Webflow serves sites through a global CDN, so the slowdowns usually come from what you add:
- Large hero images and background videos. Upload images at the width they display and compress them first.
- Heavy Lottie files and interactions firing on page load.
- Third-party scripts added in site-wide custom code: chat widgets, heatmaps, multiple tag managers.
- Custom fonts with many weights.
Check the Core Web Vitals report in Search Console for field data across your templates, and fix the Collection template first, since it affects every item page.
Webflow SEO launch checklist
| Setting | Where | Target |
|---|---|---|
| Auto-generate sitemap | Site settings, SEO | On, submitted in Search Console |
| Global canonical tag URL | Site settings, SEO | Your custom domain, exact form |
| Static page titles and descriptions | Page settings | Unique, title under 60 characters |
| Collection template SEO | Template page settings | Dynamic SEO Title and Meta Description fields |
| Redirects from the old site | Site settings, Publishing | Every old URL mapped before DNS switch |
| JSON-LD | Page and template custom code | Organization on home, BlogPosting on posts |
| Alt text | Every image, including CMS images | Descriptive, no "image of" |
Webflow's own alt text guidance makes the same last point: screen readers already announce an image, so skip "image of" and describe what matters in context.
Publishing content that ranks
A well-configured Webflow site with ten pages will not outrank a site with a hundred useful articles. The settings above make each new piece count; the publishing habit is what produces rankings.
- Choose topics from keywords with verified search volume and clear intent.
- Check what currently ranks and match its format.
- Write, fill the SEO title, meta description and slug fields, and link to two to four related items.
- Refresh posts sitting in positions 8 to 20 in Search Console before writing new ones.
Sprites' AI SEO agent runs this loop for Webflow sites. It does keyword research with search volume checked against real search behavior, finds competitor keyword gaps, audits pages, writes SEO blog posts and updates existing ones, and publishes to Webflow after you approve each change on an editable approval card. It reads Google Search Console and Google Analytics 4 to choose what to refresh.
The SEO optimization use case shows the workflow, and how to judge an AI blog writer covers what to look for in any tool. The pricing page shows which plan includes what, and every plan starts with a 7-day trial for $1.
Open Site settings now and check two things: auto-generated sitemap on, global canonical URL set. Then build the content plan.