Skip to main content
← Changelog

Auto-detect now works on your own staging domain

Name the hosts that should load your staging build and the auto-detect embed serves them staging instead of production.

What shipped

  • Staging domains. List the hosts that should load your staging build. The auto-detect embed serves staging on those, production everywhere else. Wildcards work, so *.staging.clientsite.com covers every subdomain under it.
  • A Domains panel. The sidebar's Protection panel is now Domains, with domain protection and staging domains in one place. They answer the two questions that go together: who can load your code, and which build they get.
  • Hosts you list as staging domains pass domain protection automatically, so adding one in a single place does not lock it out in the other.
  • Included on every paid plan.

The Domains panel, with domain protection and staging domains

Why it matters

Auto-detect is the embed you paste once and stop thinking about. It has always keyed off webflow.io: staging there, production everywhere else. That fits a default Webflow setup and nothing beyond it.

So if your client is on Enterprise with a custom staging hostname, or you review work on a subdomain of your own, that site was being served production code. The way around it was to paste the staging embed by hand on those pages, then remember to swap it back before launch.

Now you name the hosts once and the same embed does the right thing on all of them. Changes take about a minute to apply.

Setup and how it interacts with domain protection are in Staging Domains.