Platforms: Webflow
Webflow gives designers full control over the page, and that is exactly why SEO breaks quietly. A collection template with an unbound title field, a staging domain left open to Google, or a missing global canonical setting can ship to every page in one click of Publish.
This hub treats Webflow SEO as validation after each publish. You crawl the live custom domain, check every page type and collection template, and compare the result with the crawl before it.
Learn the audit workflow here, then open the guide that matches what just changed on your site.
Technical audit focus. Works for agency builds, marketing sites, and Webflow CMS blogs of any size.
Definition
A Webflow SEO audit checks what the published site delivers, not what the Designer panels say. It looks at the HTML a crawler receives on the custom domain, the status codes and redirects behind each URL, and the titles, meta descriptions, canonical tags, robots directives and structured data on every page.
It also checks each collection template. A Webflow CMS template page renders every item in a collection, so one unbound SEO field or one heading set to H1 in the wrong place repeats across every blog post, case study or team member page.
Page settings show what you intended. Only a crawl shows what the published output actually contains.
Two different jobs
Why it matters
Webflow handles hosting, SSL and sitemaps for you, which makes it easy to assume SEO is handled too. These five situations cause repeat problems on agency and marketing sites.
A single publish can ship new pages, edited collection templates, changed slugs and custom code together. There is no update log for SEO output, so a regression only shows up in a crawl.
SEO titles and meta descriptions on a template page are bound to CMS fields. If the field is empty, or the binding points at the wrong field, every item in the collection inherits the problem.
Every project has a webflow.io subdomain that stays published alongside the custom domain. If indexing is not disabled there, Google can find a full duplicate copy of the site.
Renaming a page slug, an item slug or a collection's URL changes live URLs immediately. Webflow does not create the 301 redirect for you, so internal links and backlinks hit a 404.
Moving from WordPress, or rebuilding a Webflow site from a new template, changes URL patterns, metadata, headings and schema on launch day. Without a comparison, you find out from a traffic drop.
Reference
The checks are grouped by technical category and mapped to the Webflow setting that controls each one, so you know where to fix what the crawl finds.
Confirm the custom domain is indexable, the staging subdomain is not, and the signals agree with each other.
Webflow note: the option to disable webflow.io subdomain indexing lives in Site settings under SEO. Crawl the staging URL itself to confirm it is actually blocked.
Check that every page outputs a self-referencing canonical on the preferred host, and that www and root domain versions resolve to one default domain.
Find empty, duplicated or unbound SEO fields on static pages and collection templates, plus missing Open Graph images on shared pages.
Check that changed slugs have redirects, wildcard rules capture the right paths, and internal links point at final URLs.
Test one item per collection template, then confirm the result across every item, including paginated collection lists.
Confirm the auto-generated sitemap.xml lists only live, indexable, canonical URLs and that robots.txt matches the production intent.
Validate JSON-LD added through page or site custom code, especially when it uses CMS field embeds that can render empty values.
Webflow serves most content as static HTML, but third party CMS filtering, load more scripts and tabbed content can hide links and text from the raw HTML.
Related: JavaScript SEO explains how rendering affects what crawlers see.
Workflow
Follow the same seven steps every time. A repeatable process is what makes two crawls comparable.
Crawl the published custom domain before the next publish and save the result. This is the record every later crawl is measured against.
Open the homepage, a static page, one item from each collection template, a paginated collection list and the 404 page. View the source and confirm title, canonical, robots meta, H1 and schema.
The custom domain should be fully crawlable. The staging subdomain should be blocked or noindexed. Patterns across many URLs usually point to one template or one setting.
Two hundred blog posts with empty meta descriptions is one fix on one collection template, not two hundred tasks.
Change the binding, the field, the redirect rule or the setting rather than editing items one by one, then note what you changed.
Confirm that fixed issues are gone and that the publish did not introduce new ones on other pages.
Write down what remains open and tie the next crawl to the next planned publish or content push.
Change-based QA
Different changes break different things. Each guide answers one question and starts from the workflow above.
What changed when you hit Publish?
Slugs, SEO fields, custom code, redirects and the sitemap all go live together, on the custom domain and the staging subdomain.
Unique angle: publish targets, staging indexing, slug change redirects, regression detection.
Read the publish guideWhich collection pages share the same defect?
Unbound SEO fields, thin items, duplicate headings and paginated lists repeat across every item a template renders.
Unique angle: dynamic field binding, collection URL structure, pagination parameters, thin items.
Read the CMS guideWhat changed between the old site and Webflow?
Flattened URL patterns, missing redirects, lost metadata and dropped schema are easiest to find by comparing crawls.
Unique angle: WordPress to Webflow URL mapping, wildcard redirects, CMS import parity, domain cutover.
Read the migration guideRegression detection
A single crawl tells you what is wrong today. Two crawls tell you what changed, which is usually the faster route to the cause.
Keep a crawl from before each significant publish, template edit or CMS import. After publishing, compare the same URLs and the same SEO elements. New issues point to regressions, and issues that disappear confirm your fixes.
SiteAuditLint keeps audit history and shows new, fixed and changed issues between crawls, so the comparison does not depend on spreadsheets. See Audit Comparison for how it works.
| Check | Baseline | After publish | Change |
|---|---|---|---|
| Blog posts with a meta description | 212 | 0 | -212 |
| Blog posts with duplicate titles | 0 | 212 | +212 |
| Internal links to 404 pages | 2 | 38 | +36 |
| Pages with a canonical tag | 264 | 264 | 0 |
| Sitemap URLs returning 200 | 264 | 264 | 0 |
Numbers are made up to show the method. In this example, a duplicated blog template lost its field bindings, and a renamed collection URL stranded 36 internal links.
Examples
These six problems come up again and again on Webflow builds. Each one is easy to miss in the Designer and obvious in a crawl.
| Finding | Likely cause | What the crawl shows |
|---|---|---|
| The webflow.io staging site is indexable | Subdomain indexing never disabled in Site settings | Staging URLs returning 200 with index robots meta, mirroring the live site |
| Pages have no canonical tag | Global canonical tag URL left empty | Every URL missing rel=canonical, including collection items |
| Collection items share one title | Template SEO title typed as static text instead of bound to a CMS field | Hundreds of URLs in one folder with identical titles |
| Old URLs return 404 after a slug change | Slug or collection URL edited without adding a 301 redirect | Internal links and sitemap history pointing at 404 URLs |
| Two H1 headings on every post | Template heading set to H1 and rich text content also starting with an H1 | All items of one collection with more than one H1 |
| Sitemap lists pages you meant to hide | Noindex added through custom code, page not excluded from the sitemap | Sitemap URLs carrying a noindex robots meta tag |
<head>
<title>Pricing Page Teardown | Agency Blog</title>
<meta name="description"
content="How we rebuilt a SaaS pricing page.">
<link rel="canonical"
href="https://www.example.com/blog/pricing-teardown">
</head>
Title and description bound to the post's CMS fields.
<head>
<title>Blog Post | Agency Blog</title>
<!-- meta description empty -->
<link rel="canonical"
href="https://www.example.com/blog/pricing-teardown">
</head>
The template's bindings were replaced with static text. Every post now shares one title.
Checklist
Reuse this list for every audit. It covers the baseline, the main technical checks, and verification after a publish. For a full version, see the technical SEO checklist.
Tooling
Four kinds of tools each answer a different question. They work together, and none of them replaces the others.
Site settings and Page settings control titles, descriptions, canonicals, robots.txt, redirects and the sitemap. The audit panel flags some issues before you publish.
Does not show: what every published page and collection item actually outputs.
Shows search performance and the indexing status Google reports, including staging URLs if they were ever indexed.
Does not show: every on-page signal, or problems before Google recrawls.
Fetch every URL and report status codes, metadata, headings, links and technical signals the way a search engine sees them.
Does not show: what changed, unless you keep and compare earlier crawls.
Sets two crawls side by side to expose regressions from a publish and confirm that fixes worked.
Needs: a saved baseline from before the publish.
Webflow SEO problems rarely come from a single page. They come from collection templates, site settings and slug changes that go live with one publish, so the reliable check is a full crawl before and after each one. SiteAuditLint runs that crawl from your own computer and keeps the history for comparison.
Free version audits up to 100 URLs per crawl. Pro adds audit history and comparison.
Keep going
Start with the guide that matches your change, then use the general technical SEO material for the details behind each check.
Webflow guides
Technical SEO
In SiteAuditLint
Crawl your Webflow site, review issues by template, and compare each crawl with the last one.