Webflow SEO audit: fast by default, easy to misconfigure
Webflow builds clean markup. Almost every problem we find is a setting.
Webflow produces some of the cleanest HTML of any site builder, so audits of Webflow sites rarely find markup problems. What they find instead are configuration mistakes: a staging domain indexed alongside production, a CMS template writing one title for a hundred items, or a sitemap that hasn't been regenerated since launch.
Here is the specific list, and what each one looks like from inside Webflow.
What goes wrong on Webflow sites
The webflow.io staging domain in the index
Every project has a .webflow.io address, and unless you disable indexing for it, that copy can be crawled and indexed next to the real site. It is a textbook duplicate-content problem and one checkbox to fix.
CMS collection templates with static meta
The template page's SEO settings apply to every item unless you bind them to fields. Bound badly, you get a hundred pages titled "Blog Post". The fix takes two minutes and it is the highest-value change on most Webflow sites.
Auto-generated sitemap left switched off
Webflow generates a sitemap when you turn it on and otherwise serves whatever you pasted in manually, which goes stale the moment the CMS grows.
Redirects not carried over at launch
Redesigns move URLs. Webflow has a good 301 manager under hosting settings; the problem is that it is a separate step from publishing, so the old URLs keep 404ing after launch.
Interactions hiding content from crawlers
Content revealed by a Webflow interaction is usually in the HTML, which is fine — but load-more and tab patterns built on external data are not, and that content simply doesn't exist for a crawler.
Collection pages with nothing but a heading
A CMS collection makes it trivial to publish fifty items with a title and an image each. Those pages are indexable by default, and fifty near-empty URLs compete with the pages you actually want ranking. Either give each item real content or keep the collection template out of the index.
Images exported at full size
Webflow serves responsive variants, but a 3000px hero dropped into a 1200px section still ships far more than the layout needs. It is the most common cause of a poor mobile Largest Contentful Paint on an otherwise fast Webflow build.
What an AuditOpti crawl looks for
- Whether the staging subdomain is indexable, and whether it duplicates production
- Titles and descriptions across CMS collection pages, grouped by template
- The sitemap: whether it exists, what it lists, and whether the CMS items are in it
- 404s from the previous site structure, and which links still point at them
- Canonical tags across collection and static pages
- Mobile Core Web Vitals, including the image sizes Webflow serves
Check part of it right now, free
These read a live page and tell you what a search engine sees. No signup, no email.
XML sitemap checker
Find your sitemap, prove it parses, and see what it is actually telling Google.
Meta tag checker
Every tag in the head of your page, read back to you the way a crawler sees it.
Canonical tag checker
The tag that decides which URL gets the credit — checked properly.
The issues behind this
Each has a full entry in the issue library: what it is, what it costs a business, and step-by-step fixes for WordPress, Shopify, Webflow and custom builds.
Duplicate title tags
Several pages share one identical title.
Missing XML sitemap
No sitemap to tell search engines what exists.
Canonical mismatch
The page points at a different URL as the original.
4xx pages
Pages returning a not-found or forbidden status code.
Questions
Related
Crawl the published site and confirm every one of these settings landed
The free audit crawls the site, groups every finding, and returns the five things worth fixing this month in plain English. No card, no call.
Run a free audit