Website Monitoring for E-commerce
You hear about a down store or a broken product page before shoppers give up and buy elsewhere. WebPixie checks that your storefront, product, cart and checkout pages load and show what they should, and emails you when one doesn't.
No credit card required·Nothing to install·Free plan with no time limit
Downtime
Your store goes down in the middle of a sale
The newsletter is out and the ads are live when the store stops answering. Every order in that window goes to another shop, and you find out when the order feed goes quiet or a customer writes in. You can do the sum with your own numbers: orders per hour, times your average order value, times the hours down.
WebPixie checks your store from multiple global locations, such as London and New York, on a schedule you choose, from every 30 seconds to once a day depending on your plan. When it stops answering, every workspace member gets an email, and from the Starter plan a Slack message too. From the Starter plan, each outage is also kept as an incident with how long it lasted.
Response time is recorded on every check, so you can catch slowdowns before they become outages as sale traffic builds. Even 99.9% uptime allows about 43 minutes of downtime a month; the free Uptime Calculator turns any percentage into minutes.
Uptime monitors
Tag: black-friday
- Up
yourstore.com
Status 200 · 386 ms
- Down
yourstore.com/sale
Timeout after 15 s
- Up
yourstore.com/cart
Status 200 · 1,240 ms
Alert sent by email and Slack
Product, cart and checkout pages
The store opens, but the product page or cart is broken
A plugin update, a theme change or a failed connection to the database can leave the homepage working while product pages lose their Add to cart button or the cart shows an error. Shoppers give up, and nothing tells you.
You can add the pages that take money, such as a bestseller, a category page, the cart and the checkout, as their own uptime monitors. You can tell WebPixie text that must appear, like "Add to cart" or the price, and text that must never appear, like "Fatal error" or "There has been an error processing your request". If you turn off follow redirects, a product page that starts redirecting to the homepage fails the check too.
Keyword checks read the HTML your server sends. On a headless or JavaScript-heavy storefront, the text you pick needs to be in the page source.
WebPixie checks that these pages load and show the right content, the way an anonymous visitor sees them. It does not add products to a cart, fill in the checkout form or place a test order.
Uptime monitors
yourstore.com
/product/linen-shirtMust contain "Add to cart"
Missing
Down/cartMust not contain "Fatal error"
Not found
Up/checkoutAccepted status codes: 200
200
Up
Alert email sent for /product/linen-shirt
SSL certificate
Shoppers won't pay past a security warning
When the certificate expires or stops being trusted, browsers replace your checkout with a full-page "Your connection is not private" warning, and few shoppers type their card details after that. If your store runs on your own server or hosting, keeping the certificate valid is your job or your host's, and automatic renewal can fail after a server move or a settings change.
SSL Monitoring checks the certificate your store serves every day, warns you 15 days before it expires by default and alerts you if it stops being trusted or no longer matches your address. If the store runs on several servers behind a load balancer, WebPixie checks each address and shows you one that serves a different certificate. Certificates Manager lists the certificates issued for your domain and its subdomains, so an unexpected one stands out.
Certificate · yourstore.com
Checked today
Certificate expires
Renew at your host
6 days
High- Pass
Trusted by browsers
Chain and address match
- Review
Same certificate on every server
1 of 3 addresses serves a different one
Domain
If the domain lapses, the store and its emails stop together
Your domain carries the storefront, the order confirmations and the replies from customers. Wherever the store runs, renewing the domain is usually your job, and auto-renewal can fail quietly when the card on file expires and the reminder goes to an old mailbox.
Domain Monitoring checks your registration every day, warns you 30 days before it expires by default, with more urgent warnings as the date gets closer, and alerts you if the registrar puts the domain on hold. If you sell under several country domains, each one is watched the same way.
Renewal still happens at your registrar. WebPixie tells you in time.
Domains
Checked today
yourstore.com
Registration · renew at your registrar
21 days
Mediumyourstore.de
Registration · renew at your registrar
6 days
Criticalyourstore.com
Status · not on hold
Active
OK
Order emails
Order confirmations end up in spam
Mailbox providers such as Gmail look at your domain's SPF and DMARC records before they trust mail from you. Your store, your email service and your newsletter tool may all send as your domain, and each of them has to be allowed. The records live in your domain's DNS, so this is usually your job wherever the store runs.
DNS Monitoring reads your domain's records every day, analyzes SPF and DMARC and lists what is missing or set up incorrectly, with guidance to fix it. It also keeps every DNS change with its old and new value, so after a switch to a new email service you can see exactly what changed.
WebPixie cannot see whether a particular email reached the inbox, but a missing or broken record is one of the first things to rule out.
Email records · yourstore.com
Checked today
- Found
Email sender check (SPF)
Lists who may send mail as your domain
- Missing
Email protection (DMARC)
No DMARC record found
Mail server record changed
Old and new value kept
Yesterday
Change
Broken links
Product links that lead nowhere after a catalog change
Discontinued products, renamed categories and a platform migration leave menus, banners and related-product blocks pointing at pages that no longer exist. A shopper who clicks one lands on a 404 instead of a product.
The Link Crawler starts at your homepage, follows internal links up to your plan's limit and crawls again about once a week. It lists links that return a 404, a server error or a redirect, and shows which of your pages link to each one, so you know where to fix it. From the Starter plan, Sitemap Monitoring also shows crawled pages that are missing from your sitemap.
A large catalog can have more links than your plan's crawl limit, so it helps to add your best-selling product pages as uptime monitors too.
Links · yourstore.com
Crawled 3 days ago
88
OK
8
Redirect
4
Broken
Broken links
/category/outleton 31 pages404/product/summer-dress-2025on 12 pages404/brands/northwindon 2 pages500
Search and AI
Can search engines and AI assistants reach your products?
Stores keep the cart, the checkout and filter pages out of search with robots.txt, which is normal. But a relaunch can ship the staging file with "Disallow: /", and then search engines such as Google and Bing, and the crawlers behind AI assistants such as ChatGPT and Claude, are kept away from the whole catalog while the store looks normal to shoppers.
The Indexability Checker reads your robots.txt and llms.txt line by line every day, shows which AI crawlers, such as GPTBot and ClaudeBot, have their own rules, and checks that robots.txt points to your sitemap. The Link Crawler marks product pages that robots.txt blocks, and on key product pages you can add "noindex" as text that must not appear.
These checks cover access, not rankings or what AI assistants say about your products.
robots.txt · yourstore.com
Read today
- Valid
Disallow: /checkout
Keeps checkout out of search
GPTBot
Own rule
Allow /
AllowedClaudeBot
Own rule
Disallow /
Disallowed- Pass
Sitemap line
Found in robots.txt
Team
Your developer or agency hears about it too
Alerts go by email to everyone in the workspace by default. On paid plans you can invite the developer or agency that runs the store as an Admin, and a colleague who only needs to look as a read-only User. Slack alerts start on the Starter plan, and from Pro a webhook can pass alerts to the on-call tool your developer already uses.
Every monitor keeps its uptime rate, how many times it went down and each check with its time, location and error, so a talk with your host starts from facts. A PDF report arrives on your plan's schedule. If you run more than one store, you can keep them in one workspace and sort them with folders and tags.
Workspace members · Your Store
- YOOwner
You
Billing, members and every monitor
- DVAdmin
Your developer
Sites, monitors and incidents
- CSUser
Customer service lead
Read-only, gets alert emails
You can start monitoring your store in three steps
Checks run from outside, so there is no plugin to install and no theme to change. Works with WooCommerce, Magento, PrestaShop, OpenCart or a custom storefront.
- 1
You add your store
You enter your domain and choose what to watch. Monitoring begins right away.
- 2
You add the pages that take money
You add a bestseller, the cart and the checkout as uptime monitors, each with text that must appear or must never appear.
- 3
You choose who hears about it
Alerts go to every workspace member by email. Slack starts on the Starter plan and webhooks on Pro, and paid plans let you invite your developer or agency.
The free plan covers 1 website and 3 uptime monitors with email alerts, with no time limit. When orders depend on the store, paid plans add faster checks, more monitors, outage history, Sitemap Monitoring and Slack alerts. You can compare them on the pricing page.
Frequently Asked Questions
Common questions from online store owners and the people who run their stores.
Yes. WebPixie checks that your cart and checkout pages load and show the content you expect, but it does not add products, fill in the checkout form or place an order. You can add each page as its own uptime monitor and set the status code it should return. Then you can add text that must never appear, such as "Fatal error" or "There has been an error processing your request", and text that must appear, such as the page heading. If a plugin update or a broken theme replaces the page with an error, the next check fails and you get an alert. The check arrives the way an anonymous visitor does, with an empty cart, so some stores show a short message or send it back to the cart page; text that appears in that state works best. Keyword checks read the HTML your server sends, which matters on headless storefronts that build the page in the browser. Product pages work the same way, with "Add to cart" as the text to look for. The Link Crawler adds a weekly look at the links that lead to these pages.
On a hosted platform, the platform keeps its servers and your certificate running, so WebPixie helps with the parts that are still yours. The first is your domain: if it is registered in your name, domain monitoring warns you weeks before it expires, because a lapsed domain takes the store and your order emails down together. The second is your email records: DNS monitoring checks the SPF and DMARC records that mailbox providers look at before they trust your order confirmations. The third is your content: a theme or app change can leave a product page without its Add to cart button, and a keyword check on that page catches it. The Link Crawler also lists menu and product links that lead to deleted pages. Nothing needs to be installed in your store, and the free plan is often enough for these checks. If the store later moves to hosting you manage, SSL monitoring and faster uptime checks can be turned on then.
WebPixie works with any store that is reachable on the public internet, because every check runs from outside, the way a shopper reaches your site. That includes WooCommerce, Magento and Adobe Commerce, PrestaShop, OpenCart and custom or headless storefronts, and nothing is installed on the store. On a store you host yourself, the server and the certificate are yours or your host's to watch, so it is worth turning on uptime monitoring and SSL monitoring for it. Uptime monitors accept a custom HTTP method, request headers and a request body, so on a headless setup you can also check the API your storefront calls, with text the response must contain. If a staging store sits behind a password, Basic, Token or Digest authentication lets the check through. Keyword checks read what your server sends, not what JavaScript adds later in the browser. For a quick one-off look at whether a store is reachable, you can use the free Website Down Checker.
For a small store where a short outage costs little, the free plan can be enough, and it has no time limit. It covers 1 site and 3 uptime monitors at 15-minute check intervals with email alerts, plus SSL, DNS, domain and link checks for that site, with a crawl of up to 20 links. Paid plans make sense once orders depend on the store: they check more often, re-check a timeout from the monitor's other selected locations before alerting, and leave room for more product, cart and checkout monitors. They also add incident management with a history of each outage and how long it lasted, Slack alerts, Sitemap Monitoring and room for your team. You can start free and upgrade later without setting anything up again. You can compare the plans on the pricing page.
You can add the pages the sale sends traffic to as their own monitors a few days ahead, so you see their normal response times before the traffic arrives. That usually means the sale landing page, the main category, a bestseller and the cart, each as an uptime monitor with text such as the offer headline or "Add to cart". Tagging them with the campaign name shows them together. The response-time chart is worth watching in the days before: a page that keeps getting slower is a warning you can act on before it turns into an outage. Short network hiccups are retried before an alert goes out, and on paid plans a timeout is checked again from the monitor's other selected locations. If a busy page tends to flap, you can set it to alert only after a number of failed checks in a row. Planned maintenance before the sale? You can pause the monitor, and the paused time is left out of your uptime rate. During the sale, Slack alerts on paid plans put the alert where the team is already talking, and incident management records how long each outage lasted.
The sum uses your own numbers: orders per hour, times your average order value, times the hours the store was down. On top of that comes what you spent on ads and emails that sent shoppers to a page that did not load, and the time spent answering customers whose orders failed. It is worth running the sum for your busiest hour as well as a normal one, because an outage during a sale or a campaign costs far more than one at 4 a.m. How long nobody notices often decides the total, so the time between the outage starting and someone hearing about it is the part worth shortening. The free Uptime Calculator turns an uptime percentage into minutes of downtime and has a cost mode for this estimate; even 99.9% uptime allows about 43 minutes a month. Uptime monitoring checks your store on a schedule and emails you when it stops answering and again when it is back. To check right now whether a store is reachable, you can use the free Website Down Checker.
Everything WebPixie can watch on your store
You can turn on the checks your store needs.
Related Solutions
You can start with the page that takes the most orders
Free plan, no credit card required.