How to Monitor a WooCommerce Store for Downtime

Your WooCommerce store loads. Products show up. The homepage looks fine.

Then a plugin auto-updates at 3 AM. The checkout button stops working. Your homepage and product pages still return 200, but /checkout throws a fatal PHP error. By the time you wake up, you've lost six hours of sales — and the only reason you found out is that a customer emailed support.

WooCommerce is powerful precisely because it's flexible: WordPress + a stack of plugins + your theme + your hosting. That same flexibility is what makes monitoring it harder than monitoring a hosted platform like Shopify. Any layer can break independently and silently kill conversions.

This guide covers exactly what to monitor on a WooCommerce store so the next plugin update, certificate expiry, or payment gateway outage does not cost you a day of revenue.

Why WooCommerce Needs Specific Monitoring

WooCommerce stores have more moving parts than most ecommerce platforms:

WordPress core — The base CMS that powers everything
WooCommerce plugin — The ecommerce engine itself
Payment gateway plugins — Stripe, PayPal, Klarna, Adyen, regional providers
Shipping plugins — Real-time rate calculators that hit external APIs
Theme — Often heavily customized, can break product or checkout layouts
Caching layer — Object cache, page cache, CDN, and full-page caching plugins
Hosting — Shared, VPS, managed WordPress, or dedicated
Database — MySQL or MariaDB powering products, orders, and sessions
Third-party integrations — ERPs, email, reviews, search, loyalty

Any one of those failing can break the buying flow while the rest of the site looks healthy. You need monitoring that watches the customer journey, not just whether the homepage returns 200.

What to Monitor

1) Storefront Availability

Start with the basics:

Homepage — Verify it loads and contains your store name, navigation, and a known product or category link
Shop page (/shop) — Confirm product cards render, not just a "no products found" message
Top category pages — At least one category page where your bestsellers live
Featured product page — Your best-selling SKU, with content validation for the product title and price

Use content validation, not just status codes. A WordPress fatal error often returns a 500, but a broken theme or plugin can return 200 with a blank or partially-rendered page.

2) The Checkout Flow

This is where revenue happens, and where WooCommerce stores break most often.

Cart page (/cart) — Verify it loads without PHP errors
Checkout page (/checkout) — Confirm the order form renders fully, including the payment method selector
Account / login — Returning customers log in here; if it breaks, repeat purchases stop
My Account — Important for subscription stores

Validate that the page contains expected text like "Place order", "Payment", or your payment method names. A checkout page that returns 200 but shows an empty form is the most common silent failure in WooCommerce.

3) Payment Gateways

WooCommerce delegates payment to plugins, and each one can fail independently:

Gateway plugin status — Many gateways expose a status endpoint or test mode URL
Webhook delivery — Stripe, PayPal, and others send webhooks for order status updates. If those stop arriving, orders get stuck in "pending payment"
Provider status pages — Subscribe to incidents for your gateway

If you take Stripe payments, monitoring its webhook endpoint with webhook monitoring catches stuck orders before customers complain.

4) WordPress and PHP Health

The platform underneath WooCommerce can fail in WordPress-specific ways:

wp-admin login page — If /wp-admin is broken, you cannot fix anything
REST API (/wp-json/) — Used by the admin, the block editor, mobile apps, and many integrations
Memory exhaustion — PHP fatal errors often appear after a plugin update
PHP version mismatches — Hosting upgrading PHP can break older plugins overnight

A simple HTTP check on /wp-json/ that validates JSON response gives you an early warning that the WordPress core is healthy.

5) Custom Domain, SSL, and DNS

Domain-level issues take a WooCommerce store fully offline:

DNS resolution — Verify your apex and www records resolve
SSL certificate — Monitor expiry and chain validity (Let's Encrypt renewals fail surprisingly often on shared hosts)
HTTPS redirects — Confirm HTTP redirects to HTTPS without loops
CDN — If you use Cloudflare or another CDN, monitor that the CDN is forwarding correctly to your origin

See SSL Certificate Expiration: A Preventable Outage for why this is non-negotiable.

6) Plugins, Updates, and Background Jobs

WooCommerce relies on WordPress's wp-cron for many tasks: scheduled emails, subscription renewals, abandoned cart recovery, inventory sync. wp-cron is notoriously flaky on low-traffic sites.

Heartbeat monitoring for wp-cron — Have a scheduled task ping a cron job monitor every hour
Plugin auto-updates — If you allow auto-updates, monitor more aggressively right after the update window
Action Scheduler — WooCommerce's internal job queue. A backed-up Action Scheduler queue causes delayed emails, stuck orders, and broken syncs

7) Performance

WooCommerce sites get slow as the catalog and order history grow. Slow stores convert worse and rank worse.

Response time on the shop and checkout pages — Alert if median response time crosses 2x your normal baseline
TTFB — Especially important on the checkout, where slow server response correlates with cart abandonment
Core Web Vitals — LCP, INP, and CLS on key pages

Common WooCommerce Failure Modes

Failure	User Impact	How to Detect
Plugin update breaks checkout	Customers cannot place orders	Content validation on `/checkout`
PHP fatal error after auto-update	White screen or 500 across site	HTTP check + content validation
wp-cron stopped running	No emails, no abandoned cart recovery	Heartbeat from a scheduled WP task
Stripe webhook outage	Orders stuck in "pending payment"	Webhook heartbeat monitoring
SSL certificate expired	Browser security warning blocks visitors	SSL monitoring
Cache plugin caching the cart	Customers see each other's carts	Authenticated checks on `/cart`
Theme update breaks product page	Broken layout, missing add-to-cart	Content validation on featured product
Hosting PHP version upgrade	Older plugin throws fatal	HTTP check + 5xx alert
Action Scheduler queue stuck	Emails and renewals delayed	Custom heartbeat from a scheduled action
MySQL connection errors	"Error establishing a database connection"	Content validation for known good text

Monitoring by Hosting Setup

Shared / cheap hosting

If you're on shared WordPress hosting, you have less control and more noise:

1-minute HTTP checks on homepage, shop, and checkout
Response time alerts — Shared hosting commonly slows down without going fully offline
Aggressive SSL monitoring — Let's Encrypt renewals fail more often on shared environments
Multi-region checks — Confirm the slowness is your host, not your monitoring location

Managed WordPress (WP Engine, Kinsta, Pressable, etc.)

Managed hosts handle some monitoring, but not your store-specific behavior:

Checkout content validation — Hosts do not test that your checkout works
Plugin update health — Many managed hosts auto-update; monitor more aggressively after the update window
Staging-to-production parity — Monitor both environments to catch issues that only appear post-deploy

Self-hosted VPS / dedicated

You own everything, so you must monitor everything:

All of the above, plus:
Server-level checks — Disk space, memory, CPU
MySQL connection health
Nginx or Apache health — Often the first thing to fall over under load (see Nginx Monitoring: Uptime, Errors, and Performance)

Setting Up Monitoring for Your WooCommerce Store

Quick start (5 minutes)

Homepage — https://yourstore.com with content validation for your store name
Featured product page — Your top SKU with content validation for the product title and price
Checkout — https://yourstore.com/checkout with content validation for "Place order" or your payment method names
SSL — Automatic expiry alerts on your domain

Comprehensive setup (20 minutes)

Add to the quick start:

Cart page — /cart with content validation
/wp-json/ — REST API health check
DNS — Verify domain resolution
Cron heartbeat — A scheduled WordPress action that pings a heartbeat URL once per hour
Webhook heartbeat for your payment gateway (Stripe, PayPal)
Multi-region checks — Especially if you sell internationally

What to Do When Monitoring Detects an Issue

Store completely down (HTTP check fails):

Check your hosting provider's status page
SSH or use your host's file manager to check wp-content/debug.log for fatal errors
Look at recently updated plugins — disable the most recent update
If you cannot access wp-admin, rename the offending plugin folder via SFTP to disable it

Checkout broken (content validation fails on /checkout):

Check Action Scheduler for failed actions
Test in incognito to rule out caching
Disable plugins one at a time starting with payment, shipping, and checkout-related ones
Check your theme's functions.php for recent edits

Slow response time alert:

Check WordPress for a runaway cron task
Look at MySQL slow query log
Check disk space and memory on the server
Disable caching plugins temporarily to confirm they aren't caching errors

SSL or DNS alert:

Confirm the alert is real with an external SSL checker
Check your DNS provider for unexpected changes
If using Cloudflare or a proxy, verify origin and edge certificates separately

How Webalert Helps

Webalert monitors your WooCommerce store the way your customers experience it:

60-second checks from global regions — detect outages within 2 minutes
Content validation — verify checkout, cart, and product pages render correctly, not just return 200
SSL monitoring — catch certificate issues before browsers block your store
DNS monitoring — detect domain resolution failures
Cron and webhook heartbeats — confirm WordPress scheduled tasks and payment gateway webhooks keep firing
Response time tracking — catch slowdowns from plugins or hosting before customers do
Multi-channel alerts — Email, SMS, Slack, Discord, Microsoft Teams, webhooks
Status pages — communicate incidents to customers and build trust
5-minute setup — paste your store URL and start monitoring

See features and pricing for details.

Summary

WooCommerce gives you flexibility, but every layer (WordPress, plugins, theme, hosting, gateway) can fail independently.
HTTP 200 does not mean your store works. Use content validation on shop, cart, checkout, and key product pages.
Monitor wp-cron and gateway webhooks with heartbeats so background failures do not silently break your store.
SSL, DNS, and CDN issues take the entire store offline; monitor them separately.
Set tighter alerts immediately after plugin auto-updates or deploys.
Use a public status page to keep customers informed during incidents.

Plugins keep your store flexible. Monitoring keeps it selling.

Stop losing sales to undetected store issues

Start monitoring with Webalert →

See features and pricing. No credit card required.