Why does my Shopify store show as up when customers see a password page?

Because the password page is a real page that returns HTTP 200. A storefront that is password-protected, or a store that has been paused or whose plan lapsed, serves a perfectly valid HTML page — it just is not your store. A basic HTTP check sees the 200 and is satisfied. The fix is a keyword check that looks for text only your live storefront contains, such as a collection or navigation heading. Note that Powered by Shopify appears on the password page too, so it cannot be the keyword.

Can I monitor Shopify checkout?

Not directly with an HTTP check — checkout is a Shopify-hosted, session-bound flow, and its availability is Shopify's responsibility, reported on their status page. What you can and should monitor is the path to checkout that runs on your domain: the homepage, a top collection, your best-selling product pages, and the cart page. If those load and Shopify's status page is clear, checkout is almost certainly fine. If you run a headless storefront, the checkout hand-off from your frontend is yours to monitor like any other API dependency.

Is monitoring a Shopify store free?

The core setup is. CronAlert's free plan covers 25 monitors at 3-minute intervals with SSL expiry tracking, so the homepage, both domain variants, top collections, best sellers, and the cart page all fit at no cost. The keyword check that catches password and paused pages returning 200, and 1-minute checks for stores where every minute of checkout downtime is revenue, are on the Pro plan at $5 per month.

Uptime Monitoring for Shopify Stores: What Merchants Actually Need to Watch

Q: Does a Shopify store need uptime monitoring?

Yes, though not because Shopify goes down — its platform is highly available and you cannot fix it when it is not. Monitoring catches the failures that are yours: a custom domain whose DNS stops pointing at Shopify, an SSL certificate that never provisioned after a DNS change, a storefront accidentally left password-protected, a plan that lapsed, a best-selling product whose URL changed, or a third-party app whose widget stopped loading. Each of those loses sales silently, and Shopify has no reason to notify you about any of them.

If you sell on Shopify you're paying, in part, so that servers are not your problem — and they aren't. Shopify's storefront infrastructure handles Black Friday for millions of stores; its outages are rare, brief, and entirely out of your hands. So the useful question isn't "will Shopify go down." It's "what else makes my store unreachable or unbuyable," and the list is longer than most merchants expect. Every item on it is something you own, and every one fails without Shopify telling you, because from Shopify's side nothing is wrong.

This guide is for merchants and the agencies who run stores for them. (If you build Shopify apps, the surfaces are different — see uptime monitoring for Shopify apps.) It covers what actually breaks, why some of it breaks with a green 200 status, and a ten-minute setup that mostly fits on a free plan.

What actually takes a Shopify store down

Your domain's DNS. A custom domain reaches Shopify through records at your DNS provider. Someone migrates email and deletes "unused" records, changes registrars, or follows a domain-connection guide halfway. Shopify is fine; yourstore.com just doesn't get there anymore. The .myshopify.com address still works — which is exactly why you won't notice from the admin. See DNS monitoring for the general case.
SSL on the custom domain. Shopify provisions and renews certificates automatically once DNS is exactly right. A CAA record, a proxied DNS setup, or an A record where a CNAME was expected can leave the certificate unissued — visitors get a browser warning and leave. SSL monitoring turns this into an alert.
Apex and www. yourstore.com and www.yourstore.com are separate DNS records. One is your primary domain and the other should redirect to it; it's common for the redirect to be broken for months on whichever variant is printed on the packaging.
The password page. Storefront password protection is on for every new store and gets re-enabled during theme launches and redesigns. Forget to turn it off — or have a collaborator toggle it — and every visitor sees a password form. This is the big one, covered below, because it returns a 200.
A paused or lapsed plan. A failed card, a billing contact who left, a "Pause and Build" plan someone forgot about. The storefront serves a Shopify placeholder that loads perfectly well as far as an HTTP check is concerned.
Product and collection URLs. Renaming a product changes its handle and therefore its URL. Shopify can create a redirect, but only if someone remembers to. Your best seller — the one in every ad, email, and Google Shopping listing — now 404s. Monitor the top few by URL with an expected 200.
Third-party apps. Reviews, upsells, subscriptions, size guides, chat — most inject scripts or app blocks into your theme, and each is a separate company with its own outages. When one dies, your pages still load; they just lose the widget that converts. Some of these apps expose a public endpoint or hosted page you can monitor directly; see monitoring third-party dependencies.
Shopify itself. Rare and real. Worth knowing within minutes so you can tell customers "platform incident, back soon" instead of tearing apart your DNS looking for a problem that isn't yours. Bookmark Shopify's status page; that's your first check when an alert fires.

The core setup: six monitors, all free

Everything below fits on CronAlert's free plan (25 monitors, 3-minute checks) and takes about ten minutes. Create an account, then add HTTP monitors for:

The homepage on your primary domain, exactly as customers type it. This one check covers DNS, the plan state, platform availability, and — because every HTTPS check on CronAlert tracks certificate expiry — SSL.
The other domain variant (www or apex, whichever isn't primary). A redirect to the primary is the correct result; a timeout or certificate error is a real problem.
Your top collection page. The one your navigation leads with.
Your two or three best-selling product URLs. These are the pages ads and emails point at, and the ones that silently 404 after a handle change. Expected status 200 — a redirect chain is a hint someone renamed something.
The cart page at /cart. It's the last page on your domain before Shopify's checkout takes over, and it's the one that matters most.
The .myshopify.com address. If your custom domain fails and this one loads, the problem is your DNS or SSL. If both fail, look at Shopify's status page. One extra monitor turns "the store is down" into a diagnosis.

Alerts go to email, Slack, Discord, webhook, or push on the free plan. For a one-person store, push to your phone is the one you'll actually see at 6 AM.

The 200 that isn't your store (Pro)

Here's what basic uptime checks miss. The password page, the paused-store page, and the plan-lapsed placeholder all return 200 OK. They are valid pages. They are just not your store. An HTTP monitor sees the 200 and stays green while your conversion rate drops to zero.

The fix is a keyword monitor: the check passes only if the response contains a phrase that exists on your real, live storefront. Two Shopify-specific notes:

"Powered by Shopify" is the wrong keyword. It appears on the password page too. So does your store name, in the page title. Pick something only the live theme renders — a navigation label, a collection heading, the text of your announcement bar, a footer link like "Shipping & Returns."
Pick from the HTML, not the browser. Shopify themes are server-rendered Liquid, so most visible text is safely in the source — but app blocks and some sections inject content with JavaScript. Right-click, View Page Source, search for your phrase. If it's there, it's safe to key on.

Keyword monitoring is a Pro feature ($5/month, 100 monitors, 1-minute checks). If the store is your income, it's the one upgrade that closes the gap between "loads" and "sells." Landing page monitoring covers the same idea for campaign pages.

Headless storefronts are a different job

If your storefront is Hydrogen on Oxygen, or a Next.js or Remix app on your own hosting talking to the Storefront API, you've taken the frontend back from Shopify — and with it, the frontend's failure modes. Now you monitor it like any web app: health endpoint, deploys, your host's availability, plus the Storefront API as a dependency your pages can't render without. The Next.js and Remix guides apply directly; the checkout hand-off from your app to Shopify is a third-party dependency to test with a real product URL.

When the alert fires

Check Shopify's status page. Incident listed? It's them. Post a note on your own status page if you have one, and wait.
Compare the two domains. Custom domain down, .myshopify.com up: DNS or SSL. Check your DNS provider before anything else.
Keyword check failing, HTTP check passing: open the store in a private window. You're looking at a password page or a plan notice.
One product URL failing: someone renamed it. Add the redirect in the admin.

Before the busiest season, run the Black Friday checklist — including a deliberate alert fire drill, because a monitor whose alert you've never seen arrive is a hope, not a system.

Frequently asked questions

Does a Shopify store need uptime monitoring?

Yes — not for Shopify's servers, but for your DNS, SSL, password setting, plan state, product URLs, and apps, none of which Shopify will alert you about.

Why is my store "up" when customers see a password page?

The password page returns 200. Add a keyword check for text only the live theme shows — not "Powered by Shopify," which the password page also contains.

Can I monitor checkout?

Not directly — it's Shopify-hosted and session-bound. Monitor the path to it on your domain (homepage, collection, products, cart) and rely on Shopify's status page for checkout itself.

Is it free?

The six core monitors are. Keyword checks and 1-minute intervals are Pro at $5/month.

Agencies running several stores?

Six monitors per store fits four stores on the free plan and sixteen on Pro. The agency guide covers team access and per-client status pages.

Ten minutes, six monitors, and you'll know before a customer emails

Shopify runs the servers. Everything between those servers and a completed order — the domain, the certificate, the password toggle, the plan, the product URLs, the apps — is yours, and every one of those fails quietly. Set up the six free monitors, add the keyword check if the store is your livelihood, and the next outage arrives as an alert instead of a refund request. Related reading: uptime monitoring for e-commerce, monitoring Webflow, Squarespace, and Wix sites, uptime monitoring for Shopify apps, and what downtime actually costs.