Webflow SEO Checks After Publishing

Every Webflow publish can change slugs, template SEO fields, custom code and the sitemap at once. Crawl before and after, check the staging subdomain, and compare to catch regressions before Google does. Pair it with the launch checklist for first releases.

5 risky edits5 steps before publishing10 post-publish checks1 baseline to compare

Webflow · Publish targets, staging subdomain, slug changes and 301 redirects

In Webflow, nothing reaches search engines until you publish, and then everything does at once. Design edits, slug changes, new collection items, custom code and site settings all ship in the same release.

That makes the publish the natural checkpoint. Crawl before, publish, crawl after, and compare. Anything that changed and was not on your list is a regression.

Baseline crawl→List slug changes→Add 301s→Publish→Crawl both domains→Compare

What can go wrong after a publish

Most publish regressions come from edits that look harmless in the Designer. The table maps each edit to what it does to the published output.

Edit before publishing	Risk level	What usually breaks
Text, image or style changes	Low	Heading levels changed on a symbol, missing alt text on new images
Page or CMS item slug renamed	Medium	Old URL returns 404, internal links and backlinks break, no redirect is created automatically
Collection template duplicated or rebuilt	High	SEO title and meta description bindings lost, every item gets the same static title
Collection URL or folder renamed	High	Every item in the collection moves to a new path at once
Site or page custom code edited	High	Stray noindex meta tag, duplicate canonical, broken JSON-LD, a tracking script that blocks rendering

What one publish can push live

Publish targetsThe custom domain, the webflow.io subdomain, or both, chosen in the publish dialogWrong version live

Slugs and collection URLsRenamed in Page settings or collection settings, live the moment you publish404s

Template SEO fieldsDynamic title, description and Open Graph bindings on collection template pagesDuplicate titles

Custom codeHead code in Site settings and Page settings, plus Embed elements on the canvasSilent noindex

Webflow's publish dialog shows which domains you are publishing to, not what changed in the SEO output. Only a crawl shows that.

Before publishing

Crawl the live custom domain and save the audit. This is the baseline: URL count, status codes, titles, H1s, canonicals, meta descriptions and schema.
List every URL you renamed or removed. Webflow will not warn you when a slug change breaks an indexed URL, so keep the old and new paths side by side.
Add the 301 redirects first. In Site settings under Publishing, add one rule per old path, or a wildcard rule with a capture group when a whole folder moved.
Check the publish targets. Publishing to the webflow.io subdomain only is a safe way to review a staged change. Publishing to the custom domain is the release.
Preview one item per edited template. Open the item in the Designer and confirm the SEO title and meta description still show purple CMS field bindings, not static text.

After publishing: what to check

Run these within the first hour, then crawl the full site and compare against the baseline in Audit Comparison.

Check	Expected result
yoursite.webflow.io	Blocked by robots.txt or noindexed, not a crawlable duplicate
robots.txt on the custom domain	Production rules, no Disallow: /
Meta robots, sitewide	No noindex on pages indexable in the baseline, via Custom Source Search
Canonical tags	Self-referencing, on the default domain, one per page
Default domain	The non-default version (www or root) returns one 301 to the default
Renamed slugs	Each old URL returns one 301 to the new URL
Collection items	Unique titles and descriptions, one H1 per item
Internal links	No links to 404s or to URLs that redirect
sitemap.xml	Only 200, indexable, canonical URLs, new pages included
Structured data	JSON-LD renders with real values for each item

How to identify the scope

Where the failures sit tells you which edit caused them.

Every URL fails the same waySite setting or site codeSitewide noindex or missing canonicals point to Site settings or site custom code.

One folder failsCollection templateEvery item under one path shares the issue: the template page or its bindings changed.

Scattered 404sSlug changesCheck your list of renamed page and item slugs against the redirect rules.

Only on webflow.ioStaging indexingThe custom domain is fine but the staging subdomain is open to crawlers.

How to validate the fix

Fix the cause, not the symptom: rebind the template field, add the missing redirect, or correct the custom code.
Publish to the custom domain and wait for the publish to finish before crawling, so the CDN serves the new version.
Recrawl and compare against the pre-publish baseline.
Target: every difference is one you planned, and every renamed URL has a single 301.
Inspect changed URLs in Search Console and resubmit the sitemap if many URLs moved.
Schedule Scheduled SEO Audits to match your publish rhythm, so every release gets a comparison.

0Unplanned differences from the baseline

1Redirect hop for each renamed URL

0Indexable URLs on the webflow.io subdomain

Before and after example

Baseline crawl/case-studies/acme → 200
Title: Acme Rebrand Case Study
Case studies with unique titles: 48 / 48

→

After publish/case-studies/acme → 404
/work/acme → 200
Case studies with unique titles: 0 / 48

Cause: the collection URL was renamed from case-studies to work, and the rebuilt template replaced its bound SEO title with static text. One wildcard 301 and one rebinding fix all 48 items.

Common mistakes

Renaming a slug and adding the redirect later. Google and visitors hit the 404 in between. Add the redirect before the publish that changes the URL.
Leaving the webflow.io subdomain indexable. A full duplicate of the site competes with the custom domain.
Duplicating a collection template and assuming the bindings came with it. Always check the SEO and Open Graph fields on the new template.
Adding a noindex meta tag in site-wide custom code to hide one page. Use page-level settings or page custom code instead.
Checking only the homepage after publishing. Template regressions show up on collection items, not on the homepage.
Testing redirects on the webflow.io subdomain. Redirect rules are built for the published custom domain, so test them there.

Every publish is a release

Treat Publish the way a developer treats a deploy. Save a baseline, add redirects before URLs move, check both domains, and compare. Most Webflow SEO drops trace back to one publish that nobody crawled.