In short. Set Staging indexing to off in Site settings > SEO > Indexing, save and publish, and address existing search results with a separate removal measure.
Definition: As of 17 October 2026, Webflow provides a Staging indexing switch for its
webflow.iostaging subdomain. Turning it off and publishing creates a subdomain-specificrobots.txt, a file that tells search engine crawlers which URLs they may access.
Key facts
- Webflow's search indexing documentation places the switch under Site settings > SEO > Indexing and requires a Site plan or paid Workspace.
- Google's robots.txt introduction explains that a blocked URL can still appear in search results when other pages link to it.
- Google's noindex documentation requires crawler access to read
noindex, an instruction to exclude content from search indexes. - Google's Removals tool documentation describes temporary removal lasting about six months.
Where is the staging control?
The procedure in Webflow's indexing guide is to open Site settings > SEO > Indexing, set Staging indexing to off, then click Save and publish the site.
Webflow specifies that the resulting unique robots.txt is published only on the subdomain. This scope matters for a project with a public custom domain: the staging control targets the webflow.io copy.
How does this differ from a page's noindex setting?
Google's robots.txt guide describes the file as a control over crawler access. Google can still index a blocked URL based on links from elsewhere. That distinction matters when a staging address already appears in results.
Webflow's page indexing instructions describe a separate Sitemap indexing switch under Page settings > SEO settings. For static pages, it requires the automatically generated sitemap and adds this markup when switched off:
<meta content="noindex" name="robots">
The same page setting also removes the page from the sitemap. It operates at page level; the staging switch creates a file specifically for the staging subdomain.
Google's noindex implementation guidance explains the interaction: Googlebot must fetch a page to read its tag. A robots.txt block prevents that fetch, so adding the tag while keeping the page blocked leaves Google unable to process the instruction.
What if a staging URL already appears in Google?
Google's Removals tool requires the URL to belong to a Search Console property owned by the requester. A temporary removal can hide the result while a lasting measure is applied, such as password protection or an accessible noindex tag.
For the tag approach, Google's debugging instructions recommend URL Inspection to examine the HTML Googlebot receives. Checking crawler access is part of that process: a blocked staging page prevents Googlebot from reading its markup.
Related terms
- robots.txt
- noindex
- Can Google read noindex on a page blocked by robots.txt?
- How do I disable search indexing for a Webflow page?
FAQ
Can I use the staging switch with a free Workspace?
Webflow's requirements allow a Site plan or paid Workspace. If you have neither, the documented requirement is unmet.
Does disabling staging indexing make a preview private?
Google's robots.txt documentation explains that crawlers choose whether to obey the file. For a private preview, you can restrict access with password protection, which the same documentation recommends for keeping information secure from crawlers.
Sources
- Webflow, "Disable search engine indexing", 29 April 2026
- Google Search Central, "Introduction to robots.txt", 10 December 2025
- Google Search Central, "Block Search indexing with noindex", 10 December 2025
- Google Search Console Help, "Removals tool", undated
Check how a page reads to answer engines. Open the GEO score analyzer