The Webflow SEO Checklist Before Launch
Every setting worth checking before a Webflow site goes live: site-wide SEO settings, per-page fields, CMS defaults, redirects, sitemap and indexing.
A Webflow launch checklist covers four layers: site-wide SEO settings, per-page fields, CMS template defaults, and the crawl controls — sitemap, robots and staging access — that decide whether any of the first three ever gets seen. Missing any one layer is the most common reason a technically clean Webflow build still underperforms after launch.
This checklist is the tactical companion to the bigger question of what it takes for a website builder to actually rank, narrowed down to the specific settings Webflow puts in front of you.
On this page
Site-wide settings to confirm first
Start above the page level, because a mistake here affects every page at once. Webflow's project-wide SEO settings include the default Open Graph image, the site's favicon, and — critically — whether the whole project is set to allow indexing at all, a toggle that is easy to leave off after building on staging [1].
Turn off "Disable search engine indexing" for the live domain
This project-wide switch is often left on from the build phase, and it silently blocks every page at once — check it explicitly rather than assuming it defaults correctly.
Set a default Open Graph image
Pages without their own social image fall back to this one, so a missing default means shared links look broken across the whole site, not just one page.
Confirm the canonical domain (www vs non-www)
Pick one version and set it in project settings so Webflow does not serve both as separate, competing URLs.
Password-protect or block the staging subdomain
The webflow.io staging URL is reachable and crawlable unless you restrict it, and a crawled staging site can create duplicate content against your real domain.
Per-page items to check before publishing
Once the project-wide settings are correct, move to the page level. Every static page in Webflow has its own SEO tab with a title, a meta description and an Open Graph override — the checklist item here is less "does the field exist" and more "did someone actually fill it in with something specific."
| Field | Bad default to catch |
|---|---|
| Page title | Left as the page name Webflow auto-generated, e.g. "Home" |
| Meta description | Empty, or copied identically across several pages |
| Open Graph image | Falls back silently to the site default when a page deserves its own |
| Indexing toggle | Left "on" for thank-you pages and internal-only pages |
Headings are worth a manual pass too: confirm every page has exactly one H1, that it is not identical to the page title by coincidence of a lazy template, and that the H2 structure below it actually reflects the page's real sections rather than styling-only divisions.
Image handling belongs in this pass as well. Every meaningful image needs alt text written for what it actually shows, not the filename Webflow imported it with, and large images should be compressed before upload rather than relying on Webflow's automatic optimization to fully cover for an oversized source file. A page with a dozen uncompressed hero images is a common, avoidable reason a Webflow site scores worse on Core Web Vitals than the platform is capable of.
Check internal links while you are on each page, too. A new page with no inbound link from anywhere else on the site is effectively an orphan the moment it publishes — note down every new page's planned links back from the homepage, a relevant service page or a related blog post, and confirm those links exist before you consider the page done rather than after a crawl report flags it missing.
CMS template defaults to verify
If the site has any Collections, check the template separately from individual pages, because a mistake at the template level repeats across every item published from it. Confirm the title and description are built from dynamic fields rather than static text, that the canonical setting is correct for paginated list views, and that at least one item is set to noindex correctly if you use that field for drafts or archived content.
Our Webflow CMS SEO guide goes deeper into Collection-specific structure if this is the part of the checklist that turns up problems — CMS setups tend to have more failure points than static pages simply because one misconfigured template affects everything built from it at once.
Check pagination and filtering separately if the Collection supports either. A filtered or sorted view of a Collection often generates its own crawlable URL, and without a canonical pointing back to the main list, you can end up with dozens of near-identical URLs competing against each other for the same query instead of the one page you actually wanted to rank.
Crawl and indexing controls to confirm last
This is the layer that determines whether any of the above gets discovered. Submit the generated sitemap through Search Console even though Webflow builds it automatically — submission accelerates discovery on a domain with no existing crawl history, and it gives you a dashboard to check indexing status against [2]. Review the robots.txt Webflow generates and confirm it is not accidentally blocking a section of the site you need crawled [3].
Structured data belongs in this pass too. Webflow does not add schema markup automatically the way some CMS platforms do, so if your page type benefits from it — an article, a local business, a product — confirm it was added deliberately, either through Webflow's embed field or a CMS-bound custom code block [4].
Two more checks belong here before you treat the crawl layer as done. First, 404 handling: confirm Webflow's default 404 page returns an actual 404 status code rather than a soft error dressed up to look like one, because a crawler reading the wrong status code will keep trying to index a page that no longer exists. Second, redirects for anything renamed during the build itself — if a page's slug changed twice while you were still building, make sure the earlier slugs redirect to the final one rather than quietly 404ing the moment you publish.
What to check again after launch, not just before
A launch checklist is not a one-time event. Recheck indexing status a week after launch, confirm the sitemap in Search Console shows no errors, and spot-check a handful of pages with a live URL inspection to make sure what Google sees matches what you built. If you are running the equivalent process on Squarespace instead, our Squarespace SEO checklist covers the same four layers adapted to that platform's settings — and if you are not sure Squarespace is even the right comparison, is Squarespace good for SEO lays out where it holds up and where it does not. Our roundup of the best website builders for SEO is worth reading if you are still deciding which platform's checklist you will actually be running.
Questions people also ask
What is the single most commonly missed item on a Webflow launch checklist?
Staging site indexing. Webflow's staging domain is technically crawlable unless you password-protect it or block it, and it is easy to forget after the real domain goes live, leaving a duplicate site competing with the real one.
Do I need to manually submit my sitemap to Google?
Webflow generates the sitemap automatically, but submitting it through Search Console still speeds up discovery, especially for a brand-new domain with no existing crawl history.
Should every page be set to index by default?
No. Thank-you pages, internal utility pages and duplicate landing page variants should be set to noindex explicitly, or they compete with your real pages and dilute what Google associates with your site.
How long before a new Webflow site shows up in Google?
Once submitted and indexed, days to a couple of weeks for a brand-new domain to start appearing for its own name and close variants. Ranking for competitive terms takes much longer and depends on content and links, not the checklist.
Is this checklist different for a CMS-heavy site versus a static one?
The site-wide items are identical. A CMS-heavy site adds the per-Collection template checks — dynamic titles, descriptions and schema — on top of everything here.
Sources
- SEO tools in Webflow — Webflow University (checked 23 September 2026)
- Build and submit a sitemap — Google Search Central (checked 23 September 2026)
- Robots.txt introduction — Google Search Central (checked 23 September 2026)
- Introduction to structured data markup — Google Search Central (checked 23 September 2026)
Get your Webflow launch audited before it goes live
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- Website builder SEO: can your site rank?Website builder SEO explained: what Webflow, Wix, Squarespace and Framer handle for you, where each one limits you, and when it is time to move.
- Webflow CMS SEO: Rank Collection PagesHow Webflow's CMS Collections behave for SEO, where dynamic pages default badly, and the settings that make each collection item rank on its own.
- Is Squarespace Good for SEO?Squarespace handles core technical SEO on its own, but caps out on structured data, redirects and content flexibility — here's where the line actually sits.
- Best Website Builder for SEO in 2026The best website builder for SEO depends on the site. Webflow and WordPress give the most technical control; Wix and Squarespace give the fastest setup.