How do I build a password-protected coming soon page in Webflow?

Why would I want a coming soon page before launch?

A coming soon page lets you claim your domain, capture early interest, and keep work private while you build. Instead of a broken or empty site, visitors see a clean holding page. In Webflow, you can go one step further and lock the real site behind a password, so only you and your client see the work in progress.

I use this on almost every client build. It solves two problems at once. The public sees something intentional, and the unfinished pages stay hidden from Google and from curious visitors. This guide walks through both parts, the public coming soon page and the private password lock, using only native Webflow tools.

Do I need a paid plan for Webflow password protection?

Yes, you need a paid Site plan to use Webflow's password protection. Once you add hosting, page and folder password protection unlocks on every paid Site plan, which are Basic, CMS, Business, and Ecommerce. You cannot password protect a site that is only published to the free webflow.io staging domain.

This matters for timing. If you are handing a private preview to a client, add the Site plan first, then turn on protection. The good news is that customizing the password page design is available no matter which plan you are on, so even the entry level Basic plan gives you a branded lock screen.

How do I password protect a whole site in Webflow?

You protect a whole site from your project's site settings, under the general or password area, by turning on site wide password protection and setting a password. Every visitor then hits a password gate before they can see any page. This is the fastest way to keep an entire build private during development.

I reach for site wide protection during the messy middle of a project, when nothing is ready for public eyes. Set a simple password you can share with your client, publish, and the whole site goes dark to outsiders. When you are ready to launch, you turn it off and the site becomes public in one step.

How do I password protect just one page or folder?

You protect a single page or folder in its settings panel, where Webflow gives you a password protection toggle for static pages and folders. Turn it on, set a password, and only that page or that whole folder is locked. The rest of the site stays open.

This is how I share one preview page while the marketing site stays live. First, open the page settings for the static page you want to hide. Second, switch on password protection and enter a password. Third, publish. For dynamic CMS collection pages, native per page protection is more limited, so for gated member content I use Webflow Memberships instead, which I cover in my client portal with Memberships tutorial.

How do I design the coming soon page itself?

You design the coming soon page like any other Webflow page, then set it as your home page or your published landing page. Build a simple section with your logo, a short message, and an email capture form so interested visitors can leave their address. Keep it to one screen and one clear idea.

My rule is to give visitors exactly one thing to do. That is usually joining a waitlist. I add a headline that states what is coming, a single line that sets expectations, and one form. Everything else is noise before launch. A tasteful coming soon page also tells Google the domain is alive and intentional, which is a gentle head start.

How do I customize the Webflow password page design?

You customize the password page in the Designer by opening the Pages panel, finding the Utility pages group, and selecting the Password page. This is a real, editable page in your project. You can style the form, add your logo, change the message, and match your brand instead of showing the plain default lock screen.

I always take five minutes to brand this page. A generic password box feels broken and makes clients nervous. A password screen with your logo, your colors, and a friendly line like "This preview is private, enter your password" feels deliberate and professional. Since it lives in the Utility pages group, it will not clutter your normal site navigation.

Will a coming soon page hurt my SEO?

A short coming soon phase will not hurt your SEO, as long as you do not leave the whole site locked for months while expecting Google to index it. A password protected page cannot be crawled, so search engines simply wait. Once you launch and remove protection, normal indexing resumes.

The thing to watch is your settings after launch. When you open the site to the public, confirm your pages are not still blocked and that your sitemap and robots settings are correct, which I explain in my post on Webflow canonical, robots, and sitemap settings. A clean handoff from private to public is where sites either start strong or quietly stumble.

Should I use a coming soon page or a full password lock?

Use a public coming soon page when you want to capture interest, and a full password lock when you want total privacy. They solve different jobs. A coming soon page is meant to be seen by the public. A password lock is meant to keep everyone out except the people you trust with the password.

Often I use both together on one project. Early in a build, when nothing is ready, I lock the whole site so only my client and I can see it. Closer to launch, I sometimes switch to a public coming soon page that collects emails while the finished pages stay hidden behind their own protection. Deciding which one you need comes down to a single question, which is whether you want strangers to see anything at all yet.

Can clients preview a private Webflow site without a password?

Yes, you can share a Webflow preview link that lets clients view the design in the Designer without publishing or setting a password. The share link shows the work in a read only view. This is handy for quick design feedback before you have added a Site plan or turned on hosting.

The difference matters. A preview link shows the design canvas, while a password protected published site shows the real, live site as visitors will experience it, including interactions and real performance. For early design sign off, the preview link is enough. For a true client walkthrough of the finished product, I publish to a password protected site so they see exactly what will go live. I pick the method based on what stage the project is in.

What should I check before I flip the site public?

Before you go public, confirm three things. First, turn off any site wide or page level password you no longer need. Second, replace the coming soon page with your real home page. Third, check that your key pages are set to be indexed and that internal links point to live URLs, not preview ones.

Launch day is not the moment to discover a stray lock or a missing page. I keep a short pre launch checklist for exactly this, and a well designed 404 page is part of it, so stray links land somewhere useful. If you want a hand setting up a private preview and a smooth public launch, let's connect and I will walk you through it.