Webflow gives you control — which also means more places for launch-blocking issues to hide. Scan every page before you go live.
Static HTML on a fast CDN, with every SEO control exposed. Webflow publishes real static HTML and gives you direct access to titles, descriptions, canonicals, redirects and robots.txt. Nothing is hidden from you — which means nothing is done for you either, and the settings you skipped are precisely what a scan finds.
Webflow is the most capable builder on this list from an SEO standpoint, and that cuts both ways. Every control you need is there, exposed, and switched off until you set it. There is no sensible default quietly protecting you.
The findings on Webflow sites are consequently about omission rather than breakage. Metadata bound on the template but never filled per CMS item. A staging subdomain still indexable. Old URLs that changed slug and were never redirected.
The other recurring one is that publishing to webflow.io and publishing to the custom domain are separate actions, so it is entirely possible for the live site to be weeks behind the one you have been reviewing.
These are the launch-blockers we actually find on Webflow builds, roughly in order of how often they come back positive — each with the specific change that clears it.
Your site exists on both yoursite.webflow.io and your real domain, with identical content. If the staging subdomain is indexable, Google has two complete copies and may well pick the wrong one to rank.
The fix: Turn on "Disable Webflow subdomain indexing" in Site Settings → SEO, and confirm the subdomain's robots.txt actually disallows crawling after you publish.
Collection page titles and descriptions must be bound to the item's own fields. Left as static text, every blog post or project ships identical metadata — the single most common reason a Webflow CMS collection fails to get indexed.
The fix: In the collection page settings, bind the title and description to field values rather than typing them. We report which URLs currently share metadata.
Renaming a page or CMS item changes its URL and leaves the old one returning 404. Any ranking, backlink or bookmark pointing at the old URL is lost, and Webflow does not create the redirect for you.
The fix: Add a 301 in Site Settings → Publishing → 301 Redirects for every URL you have changed. We crawl your internal links and report the ones that 404.
Webflow Interactions and Lottie animations are easy to add and rarely budgeted for. A multi-megabyte Lottie in the hero is a common cause of a poor Largest Contentful Paint and a Cumulative Layout Shift as it pops in.
The fix: We report LCP, CLS and TBT from real Lighthouse runs with the asset responsible for each, so you can decide what is worth its weight.
Webflow does not emit Schema.org markup. Without it you forfeit rich results and give AI answer engines nothing machine-readable to attribute — which matters most for articles, products and local businesses.
The fix: Add JSON-LD via an embed on the relevant templates. We report which schema types your page types are missing.
Paste your Webflow link and get a free Launch Score with your top problems.
Unlock the report for $12 (₹299 in India) — we scan every page and write the fixes for Webflow.
Paste the fixes into Webflow, say "repair it", and re-scan to confirm. Done.
The short version, if you would rather do it by hand. Everything here is something you can verify yourself in a few minutes.
Yes, in nearly every case. Leaving it indexable gives Google a complete duplicate of your site on a different hostname, and Google — not you — decides which one to rank. The setting is in Site Settings → SEO and takes effect on republish.
The usual cause is metadata that was typed as static text on the collection template instead of bound to each item's fields, so every page in the collection ships the same title and description. Google treats that as duplicate content and indexes one.
No. Webflow emits no Schema.org markup of its own, so rich results and AI attribution both need JSON-LD added by hand via an embed on the relevant templates. We report which schema types your page types are missing.
Usually, yes — add a 301 redirect from the old URL to the new one in Site Settings → Publishing. That passes the accumulated ranking signals across. Until you do, the old URL 404s and everything pointing at it is wasted.
The free Launch Score covers your home page with no signup. Crawling every CMS page for duplicate metadata and broken links, plus the Webflow-specific fixes, is the paid report, from $12 (₹299 in India).