One setting causes this daily. To the visitor it looks like the internet not working, never like a launch failure.
Almost every launch-day failure in the Shopify Community traces back to the same handful of causes: the password page left switched on, a policy page nobody wrote, a store still sitting on its default myshopify.com address, or a checkout nobody actually tested. None of these are hard to fix. They are just easy to forget precisely because they do not feel like "real" launch tasks.
The password page nobody turned off
It happens often enough that Shopify's own support staff have a ready-made answer for it.
A store owner reported that their family could not find their store after launch, and the page said it could not open. Support recognised the pattern immediately: the storefront still had its password-protected page switched on. Everyone who visited was seeing a password gate instead of the store.
A separate merchant described the same thing from the other direction, confused that Shopify called the store "launched" while they were still building it, and asking how to hide the site from customers during setup. The mechanism is identical. It is the same single toggle, just approached from opposite ends of the same confusion.
Shopify Community, multiple threads on the password-protected page
Nothing about this looks like a launch bug from the outside. The page loads. It just says "enter password," which to a first-time visitor looks exactly like a broken link or a site that is down.
The most common reason a launch fails isn't the product, the price, or the ads. It's a single checkbox nobody remembered to uncheck. The Dropshipping Playbook
Check it right now, before reading further: open your store in an incognito window. If you see a password field, this is your launch checklist's first and only non-negotiable item.
The checklist
Tick these off. The ones marked critical are the ones that turn "launched" into "actually visible and sellable," based on what recurs most often in merchant reports.
Setup mistakes vs launch mistakes, and why the difference matters
Agencies who audit stores after the fact describe the pattern the same way, over and over. Nobody forgets to add products. What compounds quietly are small defaults left untouched: an uncompressed image, a policy page that was never written, a tax setting nobody revisited.
None of those sink a launch on their own. Together, they are often the reason a genuinely good product converts at half the rate it should, for months, without anyone tracing it back to a setup step from week one.
The order that avoids both traps
Chapter 1.4 covered why the sequence of your initial setup matters more than the tasks themselves. The same logic applies here, at the smaller scale of launch day specifically.
- Turn off the password page last, only once everything else on this list is done, so nobody arrives to an unfinished store.
- Test the checkout before you announce anything, not after. A broken discount code found by your first real customer costs more than one found by you.
- Tell a small circle before a big one. Friends and family first, so any last surprise shows up somewhere low-stakes.
- Only then post publicly, or start organic content, per chapter 2.3.
Common questions
My store says "launched" but I'm still working on it. Is that a problem?
Do I need a custom domain to launch?
How long should I test before announcing the launch?
What if I find a problem after I've already told people to visit?
One number pays for the rest
What a single order is worth decides what every other fix can afford. Chapter 4.1 is where that number moves.
Go to chapter 4.1