stillindexedStart monitoringOpen the app

Webflow

Webflow staging site indexed by Google: fix it

Stop a webflow.io staging site appearing in Google by turning off Webflow staging indexing and removing the existing result.

Webflow staging domains allow crawlers unless "Staging indexing" is turned off in "Site settings > SEO > Indexing." Disable that setting, save and publish the staging site, then inspect the exact webflow.io robots.txt to confirm Webflow now disallows crawling before requesting removal of an existing Google result.

Why Webflow does this

Webflow allows search-engine crawler traffic by default. The webflow.io staging subdomain can therefore appear unless Site settings > SEO > Indexing has "Staging indexing" set to off. Webflow says this publishes a unique robots.txt file only on the staging subdomain.

Check it right now

Before changing anything, confirm what a crawler actually sees. The check is free, takes one URL and needs no account.

Run the check

How to fix it

  1. Open Site settings > SEO > Indexing.
  2. Set "Staging indexing" to off.
  3. Click "Save" and publish the site. Webflow says the setting does not take effect until you publish.
  4. Run the robots.txt tester on the exact webflow.io staging subdomain and confirm its robots.txt tells search engines to ignore that host.
  5. If the staging host is already in Google, use Search Console > Removals > Temporary Removals > New Request for the webflow.io prefix. Webflow warns that robots.txt alone may not remove content that was indexed earlier, and Google says a removal request is temporary.

Why it happens again

The setting takes effect only when the site is published. If "Staging indexing" is turned back on and the site is published again, crawler access returns to the webflow.io host.

stillindexed re-checks the URLs you give it every 30 minutes on Starter and alerts when a directive changes, at most 30 minutes after it does. It is a monitor rather than a crawler: it watches a list you choose and tells you when one of seven things changes. Card first, no trial, and a 30 day refund.

See what monitoring covers

Catching it next time

Fixing it once is the easy half. The setting that caused this can be changed again by anyone with access, and the page will keep returning 200 while it happens.

Other ways Webflow loses pages

A staging or preview site indexed by Google, on other platforms

Sources

Every claim about Webflow above is from their own documentation, read on 2026-08-30. Platforms change their settings; if one of these is out of date, their page wins and we would like to know.