Webflow Staging Site vs Published Site: What Is the SEO Difference?

Why is my Webflow staging site showing up in Google?

Your Webflow staging site shows up in Google because indexing of the webflow.io subdomain is still switched on. Every Webflow site gets a free staging address, and by default search engines can crawl it. If you never disabled that, Google can index your staging copy right next to your real site.

I see this on client sites more often than you would think. Someone searches the business name and the yoursite.webflow.io version appears in the results, sometimes above the real domain. It looks unprofessional, and it quietly splits your SEO between two copies of the same pages.

The good news is that this is easy to fix once you understand how staging and published sites differ in Webflow. Let me walk through what each one is, why an indexed staging site hurts you, and the exact settings I check before any launch.

What is the difference between a Webflow staging site and a published site?

A staging site is your work-in-progress copy on the webflow.io subdomain. A published site is the public version on your custom domain. Both come from the same project, but they live at different addresses. Staging is for previewing changes. The custom domain is the one you want customers and search engines to see.

When you hit publish in Webflow, you choose where the site goes live. You can publish to the webflow.io staging address, your custom domain, or both. That flexibility is useful during a build, since you can preview on staging before pushing to the real domain.

The problem starts when both addresses are public and crawlable. Now the same content sits at two live URLs. Search engines see two copies, and that is where the trouble begins. The fix is making sure only your custom domain is meant for search.

What is the webflow.io subdomain for?

The webflow.io subdomain is Webflow's built-in staging address for every site. Webflow's Help Center describes it as the staging subdomain, a place to preview and share work before it goes live on a custom domain. It is handy during a build, but it is not meant to be your public, indexed site.

I use the staging URL all the time while working. It lets a client see progress without buying a domain yet, and it gives me a live link to test on real devices. For that purpose, it is great.

The mistake is treating staging as if it were the real site once you launch. After you connect a custom domain, the webflow.io address should step back into its staging role. If it stays open to search engines, it competes with your real domain instead of supporting it.

Why does an indexed staging site hurt my SEO?

An indexed staging site hurts you because it creates duplicate content. Google finds the same pages at two addresses and has to guess which one matters. That can split your ranking signals, show the wrong URL in results, and confuse your analytics. One clean, canonical version always beats two competing copies.

Duplicate content is the core issue. Your custom domain and your webflow.io copy hold identical pages. Search engines do not know these are the same site run by the same person, so the authority you earn can get divided between them instead of stacking on one domain.

There is a trust cost too. A visitor who lands on yoursite.webflow.io sees an odd address that does not match your brand. It looks unfinished. I want every search result to point at the real domain, because that is the version I control and optimise. Duplicate URLs work against that goal, which is why I treat this as a launch-blocking issue.

How do I stop Google from indexing my webflow.io staging site?

Turn on Webflow's setting to disable search engine indexing of the webflow.io subdomain. Per Webflow's Help Center, this publishes a unique robots.txt on the subdomain that tells search engines to ignore it, without touching your custom domain. You need a paid Site plan or Workspace to use this option.

You find it in your site settings, under the SEO or publishing area, as a toggle to disable Webflow subdomain indexing. Switch it on, then publish so the change goes live. From that point, the robots.txt on your staging address asks crawlers to stay away.

This is one of the first things I set on any project with a custom domain. It is a two-minute change that prevents a messy, hard-to-undo problem later. I treat it as part of the standard SEO setup, right alongside the canonical, robots, and sitemap settings in Webflow.

Does disabling indexing remove a staging URL that is already in Google?

Not on its own. A robots.txt block stops crawlers from visiting, but a page that is already indexed, or linked from elsewhere, can stay in Google's results for a while. To remove staging URLs that already rank, you need to request removal in Google Search Console as well.

This trips people up. They flip the setting, then wonder why the staging URL still appears a week later. Blocking crawling is not the same as forcing removal. The two jobs are separate, and you often need both.

The cleaner path is to disable staging indexing before you ever publish widely, so the URLs never get indexed in the first place. This is also a good moment to understand the gap between crawling and indexing, which I break down in my post on crawling versus indexing.

Should I use canonical tags to point at my custom domain?

Yes, canonical tags are a smart backup. A canonical tag tells search engines which URL is the true version of a page. Pointing your canonicals at the custom domain reinforces that your real site is the one to rank, even if a staging or parameter URL slips through somewhere.

Webflow lets you set canonical URLs in your SEO settings, and it adds self-referencing canonicals by default on many sites. The key is making sure the canonical always points at the custom domain, never at a webflow.io address. A canonical aimed at staging would send the wrong signal.

Canonicals are not a substitute for disabling staging indexing. They work together. I use both, because layered signals are more reliable than one. I go deeper on this in my post on canonical tags and duplicate content in Webflow.

What about noindex on individual pages?

For single pages you want hidden, use the page-level indexing control. Webflow's page settings include a sitemap and indexing toggle that adds a noindex meta robots tag to that page. This is the right tool for a thank-you page, a private landing page, or any single page you do not want in search.

This is more precise than a site-wide block. The staging toggle handles the whole webflow.io copy. The page-level noindex handles one page on your live domain. They solve different problems, so I keep them straight and reach for whichever the situation needs.

A noindex tag is also stronger than a robots.txt block for keeping a page out of results, because it directly tells search engines not to index the page. Just remember that a page must be crawlable for the engine to read that tag, so do not block it in robots.txt at the same time.

How do I check which version of my site Google has indexed?

Check by searching Google for your domain with a site colon query, like site:yoursite.com, and again for site:yoursite.webflow.io. If staging pages appear, indexing is still open there. Google Search Console gives a fuller picture through its coverage and pages reports, which show exactly what Google has indexed.

The site colon search is my quick spot check. It takes seconds and instantly shows whether a webflow.io copy is floating around in results. If I see one, I know the staging indexing setting was missed.

Search Console is the deeper tool. I connect it on every site so I can see indexing status, catch duplicate URLs, and request removals when needed. If you have not set it up yet, it is the single most useful free tool for watching how Google sees your site.

What is the safe setup before I launch a Webflow site?

The safe setup is simple: publish to your custom domain, disable indexing on the webflow.io subdomain, confirm your canonicals point at the custom domain, and connect Google Search Console. Do these four things before you promote the site, and search engines will focus on the one URL you want to rank.

Run through this list every launch and you avoid the duplicate staging problem entirely. It is far easier to prevent than to clean up after a staging URL has already been indexed and shared. A few minutes of setup saves weeks of untangling later.

If you are launching a Webflow site and want a second pair of eyes on the technical SEO setup, reach out. Getting these foundations right so your real domain gets all the credit is exactly the kind of work I do, and I am happy to walk through your setup with you.