Webflow Subdomain Indexing: Hide Your Staging Site from Google

Every Webflow site has a staging subdomain: something like your-site.webflow.io. This domain is active from the moment you create the project. If you publish your site without disabling subdomain indexing, Google can find and index both your-site.webflow.io and yourdomain.com — two versions of the same content, competing with each other.

This is a duplicate content problem with a direct consequence: the ranking signals that should concentrate on your main domain get split between two URLs. In some cases, the Webflow subdomain outranks the custom domain because it was indexed first.

Disabling subdomain indexing doesn't remove the staging URL. Your site still lives at your-site.webflow.io. It adds a noindex directive to the subdomain so it won't appear in search results. The staging URL stays accessible for previewing and testing — it just won't compete with your main domain.

How to do it in Webflow. Go to Project Settings → Publishing. Enable the option to disable Webflow subdomain indexing. Publish your site for the change to take effect.

After publishing, verify by searching site:your-site.webflow.io in Google. If subdomain pages appear in results, they were previously indexed and the noindex tag needs time to propagate. Google typically deindexes noindex pages within a few weeks of recrawling.

If you've been running your site for a while. Use Google Search Console's URL Inspection tool to check whether any subdomain URLs are indexed. If they are, disabling subdomain indexing starts the deindexing process on the next crawl.

In Webflow Site Settings under SEO, you can also add a custom robots.txt rule blocking the subdomain for an extra layer of protection — though the built-in noindex setting is usually sufficient.

Subdomain indexing is one of those things most Webflow users never think about. The ones who notice it usually discover it after wondering why their custom domain rankings seem weaker than expected.