The Webflow SEO Checklist
Webflow ships clean code, which is more than most platforms promise, and it leaves four settings at their defaults that quietly cost you rankings. The staging domain, the global canonical, the CMS template titles, and the redirect rules are where the traffic is. This checklist covers the 20 checks that sit in those four places.
20 checks for a Webflow site, each with the exact admin path, the frequency, and the time it takes.
What Webflow Already Handles
Webflow's code is good. The pages are server-rendered, the markup is semantic, and the platform does not slow the site down with a theme you did not ask for. Most ranking problems on a Webflow site are not the platform. They are four settings that were never opened.
The one that catches everybody is the staging domain. Every Webflow site also lives at a subdomain on webflow.io, and if that is left indexable, Google sees two copies of the same site and the ranking signals split between them. The fix takes a few minutes and it needs a paid Site plan, which is why it is on this list.
This page sits inside the complete technical SEO checklist, and the platform-specific work it covers is the same work the general pages cover, with the exact admin path to each setting.
Handled by Webflow
The 20 Webflow SEO Checks
Every check with the admin path it lives in, how often to run it, and how long it takes.
| # | Check | Frequency | Tool | Time |
|---|---|---|---|---|
The Staging Domain That Splits Your Site
Every Webflow project is published twice. One copy sits on your domain, and the other sits on a webflow.io subdomain that Google can see.
1 What the setting does
In Site settings, then SEO, then Indexing, turn off the indexing of the Webflow subdomain and publish. Webflow then serves a robots.txt on the subdomain only, so the copy is not crawled. It needs a Site plan or a paid Workspace, and it is the first thing to check on any Webflow site.
2 Why blocking is not enough on its own
Blocking stops new crawls, and it does not remove what has already been indexed. Search the site operator for your webflow.io address. If pages show up, verify the webflow.io address as its own property in Search Console and use the removals tool to clear the index.
3 The default domain and the sitemap
In Site settings, then Publishing, then Production, click Make default next to the version you want. The sitemap uses the default domain, so if the wrong one is set, every URL in the sitemap answers with a redirect, which tells a crawler those pages do not exist where it says they do.
What Webflow Cannot Do For You
The limits worth knowing before you start.
It cannot make a static title work for a collection
If the collection template has a fixed title, every blog post in it shares one title tag. The template has to pull from a CMS field, and that takes twenty minutes per collection.
It cannot check the alt text on your content images
The Audits panel skips CMS-bound images, and images inside rich text fields need their own alt attribute. The check that catches the rest will never catch these.
It cannot warn you about a long slug
Webflow builds the slug from the item name, so a title with a year in it becomes a URL with a year in it, and changing it later means a 301.
It cannot rescue a redirect chain
Rules run oldest first, so a broad wildcard added early swallows the specific rules added later. And importing a CSV replaces every existing redirect, which is why the export comes first.
It cannot show you a collection past 100 items
A collection list caps at 100 items unless pagination is on, and the items beyond that are not in the page HTML at all. A crawler cannot link to a page it cannot see.
It cannot make a page live on its own
Page settings, custom code, and SEO fields are all saved in the Designer. Nothing reaches the live site until you publish to your custom domain.
Get the Full Checklist as a Template
Every checklist in the library, in a printable PDF and a spreadsheet with a Status and an Owner column, so the work can be assigned and tracked between passes.
The data is open source under CC BY 4.0 on GitHub. The broader platform work is in the technical SEO checklist.
Webflow SEO FAQs
Direct answers on the platform, the settings that get missed, and the AI layer.
Yes. Webflow is one of the few platforms where the code is the point: pages are server-rendered, the markup is semantic, and there is no theme layer between you and the HTML. The ranking ceiling is set by four settings left at their defaults, and all four are on this checklist.
Turn off the indexing of the Webflow subdomain in Site settings, then SEO, then Indexing, and publish. That stops new crawls. For what has already been indexed, verify the webflow.io address in Search Console as its own property and use the removals tool, because a block alone does not clear an index.
Not for the fundamentals, which the platform covers. A plugin earns its place when the volume is in the CMS, because the collection template needs a dedicated field per item and that is a build rather than a setting. A static site with twenty pages does not need one.
The collection template has a title tag and a meta description, and both can pull from a CMS field. The setup that works is a plain text field called SEO title, the template bound to it, and the brand suffix typed after it. The same pattern applies to the description.
In Site settings, then Publishing, then 301 redirects. Add the old path as relative, such as a path with a leading slash, and the new one beside it. A whole folder takes a wildcard. Export the existing list before importing a new one, because an import replaces every rule rather than adding to them.
Check three things in order. The default domain has to be set, because the sitemap reflects it and a wrong default makes every URL redirect. The robots.txt must not carry a leftover block on the whole site. And the Sitemap indexing toggle has to be on for the pages you want included, because the automatic file includes every live page.
Webflow publishes server-rendered HTML, so there is no rendering delay and no second wave. The pages are readable as they are sent, which is also why they are readable by AI crawlers that never execute JavaScript at all, and by the answer engines pulling passages out of your content.
It can be, and the place you add the code matters more than how much there is. Code in the site settings head renders on every page, and the head and footer panels each hold up to 50,000 characters. A tag manager gives you control over when scripts run, which is usually the better answer.