This Webflow SEO checklist covers 28 settings I check on every Webflow site, from the global canonical URL and staging indexing to CMS template bindings, 301 redirect rules, schema and Localization.
By Kristijan GjorgjioskiIndependent SEO consultantPublished 18 October 2026 · 8 min read
Webflow sites start with an advantage most platforms don't have: clean code and fast hosting.
Then the build gets in the way. Headings picked for their size, CMS templates nobody filled in, redirects added in the wrong order.
This Webflow SEO checklist covers the 28 settings I check on every Webflow site, grouped by where they live in the platform. Each one has a pass state, so you'll know when it's done.
You don't have to work top to bottom. Pick your starting point:
Several settings below need a paid Site plan or a paid Workspace. Where that's the case, I've said so, so you know before you start.
If you'd rather hand over the whole pass, it's how my Webflow SEO projects start.
Most of these live under Site settings > SEO.
Get them wrong and every page inherits the problem. They're the Webflow end of the wider technical SEO checklist.
Webflow builds a canonical tag for every page by combining this base URL with each slug.
Webflow's canonical tag guide says to include the protocol and the www prefix if your default domain uses it, and to leave off the trailing slash.
Pass: view the source of any page and see one canonical tag with your full domain and no double slashes.
Your webflow.io staging address can get indexed alongside your real domain, so you end up competing with yourself.
Set Staging indexing to off under Site settings > SEO > Indexing, then publish. This needs a paid Site plan or Workspace.
Pass: the staging subdomain's robots.txt tells search engines to stay away.
You'll find it under Site settings > SEO > Sitemap.
Webflow updates the sitemap on every publish and adds it to robots.txt automatically.
Pass: /sitemap.xml loads, lists only pages you want found and is submitted in Search Console.
The robots.txt field also sits under Site settings > SEO > Indexing.
It's public, so never use it to hide anything sensitive.
Pass: every rule has a reason, and nothing blocks pages you want to rank.
The same Indexing section has toggles for search engine crawlers and AI bots.
Both are allowed by default. Switch either off and you may lose visibility in search or AI answers.
Pass: you've made a deliberate choice about AI bots, rather than finding out later that a teammate switched them off.
Webflow has no site-wide title or meta description setting. You set them page by page.
Go to Pages panel > Page settings > SEO settings.
Webflow suggests you keep titles under 60 characters.
Pass: no static page uses a default or empty title. Test the important ones in the SERP snippet preview tool.
Designers often pick heading tags for their size.
Change the tag in the heading's element settings and keep the look with a class. Your visitors won't see a difference; search engines will.
Pass: each page has exactly one H1, and headings run H2 then H3 without skipping.
Without them, social shares show random content or none at all, according to Webflow's own Open Graph guide.
Pass: each key page has an Open Graph title, description and image under Page settings > Open Graph settings.
Alt text set on an asset in the Assets panel carries over to every place you use that image.
Purely decorative images can be marked as Decorative instead.
Pass: the Audit panel shows no missing alt text on meaningful images.
Webflow converts slugs to lowercase and strips most special characters for you.
That still leaves room for long, vague or leftover slugs, which you'll need to fix by hand.
Pass: slugs describe the page in a few words, with no leftover "copy" or test names.
Turn off Sitemap indexing under the page's SEO settings. Webflow's guide to disabling search engine indexing explains that this adds a noindex meta tag and removes the page from the sitemap.
A robots.txt disallow doesn't do either. The page stays in your sitemap.
Pass: thank-you, test and legal-only pages carry a noindex tag.
A collection template sets the SEO for every item at once.
That's efficient, and it's also how one mistake spreads to hundreds of pages.
Each collection's items sit under a folder, such as /post/ or /case-studies/.
You can rename it later, but Webflow says you'll then need 301 redirects. One wildcard rule handles the whole folder.
Pass: each collection folder name is short, readable and matches what the content is.
On the template's SEO settings, use Add field to pull values from the collection.
Pass: when you spot-check five items, each has a unique title and description, with no blank or repeated text.
The template's Open Graph image must come from an Image field in the collection. Webflow requires all Open Graph images in a collection to share the same dimensions.
Pass: sharing any item's URL shows its own image, not a blank card.
A template with only a name, a date and one rich text field produces thin, similar pages.
Reference fields help too: they drive links between related items. My internal linking strategy guide explains why those links matter, and content SEO covers what to put in the fields.
Pass: templates for important collections have fields for an intro, key details and FAQs where they fit.
On paid Site plans, each CMS item has its own Sitemap Indexing toggle in Item details.
Turning it off adds noindex and drops the item from the sitemap.
Pass: placeholder, duplicate or very thin items are noindexed until they're worth indexing.
Images on templates can pull alt text from a collection field, so each item describes its own image.
Pass: template images output item-specific alt text, not one generic phrase.
Webflow handles redirects under Site settings > Publishing > 301 redirects, on paid plans. The rules are powerful, which is exactly why they need care.
Changing a slug in Page settings offers to permanently redirect the old URL. Ticking it creates the 301 for you.
Pass: every renamed page has a matching rule in the 301 redirects list.
A rule like /old-folder/(.*) to /new-folder/%1 moves every page in a folder with one line, per Webflow's redirect setup guide.
Pass: folder moves use one wildcard rule each, not hundreds of single rules.
Webflow runs redirects in the order they were added, oldest first.
A broad wildcard you added early will catch URLs before a later, specific rule can fire.
Pass: test a handful of specific old URLs and confirm each lands on its intended page.
Characters such as ?, =, &, - and _ need a % in front of them in old paths. Webflow also strips a trailing slash directly before a query string before matching.
Pass: redirects from old query-string URLs fire when tested in a fresh browser tab.
Webflow's 301 redirects don't apply to localized slugs or subdirectories. Redirecting /old-url and /es/old-url takes two rules.
Pass: each locale's old URLs have their own redirect rules.
Webflow recommends staying around 1,000 redirects at most.
A spreadsheet of each rule and why it exists stops chains building up.
Pass: you can explain every rule in the list. For bigger moves, see my redirect map guide.
Structured data helps search engines and AI tools understand your pages. Webflow now gives each page a dedicated Schema markup field.
According to Webflow's schema markup guide, you can use the Schema markup field or custom code, but not both, to avoid duplicate structured data.
Pass: each page outputs one set of schema. The schema markup generator helps if you're writing it by hand.
On collection templates, bind schema values to fields so each item outputs its own data. Reference, multi-reference and multi-image fields aren't supported in the Schema markup field.
Pass: Google's Rich Results Test validates a sample of template items without errors.
Old tracking snippets and unused libraries build up in the site-wide head and footer code over the years.
Each one is code your visitors download on every page.
Pass: every script in the site-wide custom code still has an owner and a purpose.
Only relevant if your site uses Webflow Localization.
Webflow adds page-level hreflang tags and sitemap hreflang entries automatically.
You can switch generation on or off in the Localize panel's SEO settings.
Pass: pages show one set of hreflang tags. If you use a custom sitemap instead, you've added hreflang to it by hand, and the hreflang generator can build the tags. New to the tag? Start with what hreflang is.
Titles, descriptions and Open Graph settings can be localised per page.
They don't translate themselves, so you'll need to write or check each one.
Pass: each locale's key pages have titles and descriptions in that language.
| Priority | Items | Why |
|---|---|---|
| Fix this week | 1, 2, 3, 11, 20 | Duplicate domains, missing sitemap or broken redirects |
| Fix this month | 6, 7, 12 to 16, 24 | Weak titles and thin templates hold back rankings |
| Schedule | 8 to 10, 17, 21 to 23, 25 to 28 | Real gains, but lower urgency |
Migrating to Webflow? Move every redirect item into the first row. My website migration SEO checklist covers the rest of a move.
Pick your busiest collection, usually the blog or case studies. Open the template's SEO and Open Graph settings and spot-check five items.
That one check often finds the problem affecting the most pages on the site.
Still choosing a platform? My Webflow vs WordPress comparison covers how the two differ for search. And if you'd like someone to run all 28 checks and fix what's broken, that's the core of my Webflow SEO service, with migration support for sites moving on or off the platform.
Webflow is a strong platform for SEO. It gives you control over titles, meta descriptions, canonical tags, redirects, the sitemap, robots.txt and schema without plugins. The weak points are usually in how a site was built: heading tags chosen for looks, CMS templates with empty bindings and content hidden behind interactions. Those are fixable with a checklist like this one.
Only once you set a global canonical tag URL in the site's SEO settings. Webflow then combines that base URL with each page's slug to create a canonical tag for every page. You can also set a canonical URL on individual static pages, which overrides the global one. Don't add canonicals through Google Tag Manager as well, or pages end up with two.
Open the page's settings, go to SEO settings and turn off the Sitemap indexing toggle, then publish. Webflow adds a noindex meta tag and removes the page from the auto-generated sitemap. CMS items have their own Sitemap Indexing toggle in Item details on paid Site plans. Both require the auto-generated sitemap to be switched on.
Webflow doesn't set a hard limit, but its help centre recommends a maximum of about 1,000 as best practice, because every rule adds to a file visitors' browsers download. Use wildcard rules with capture groups for whole folders instead of one rule per URL. That keeps the list short and much easier to maintain.
About the author
Kristijan Gjorgjioski
Independent SEO consultant · 6+ years in SEO · 60+ client websites worked on
I'm an independent SEO consultant with 6+ years in SEO. I run audits, migrations and content programmes for businesses in Europe, the UK and the USA, and I build the automation behind my own research.
Book a free 30-minute call. I look at your site first and tell you plainly what I would fix, and in what order.