Product tour
Every way a site can break, checked like a customer would.
Uptime says the server answered. Website is Up goes further: it signs in, searches, adds to cart and checks out, looks at the page on a phone, and when something fails, names the update that landed just before.
01 / Uptime
Checked from outside, confirmed before anyone is woken.
Every site is checked around the clock from outside your hosting. A failure is checked again before it becomes an alert, so a single slow response at 3am stays a line in the history, not a phone call.
- Response time and status on every check, kept as hourly history for 90 days
- Confirmed failures only, and flapping detected rather than alerted on repeat
- Maintenance windows, so planned work stays quiet
- A security report for any domain: outside scripts, hidden frames, obfuscated code and reputation lists
- shop.example.com212 msUp
- clinic.example.org388 msUp
- studio.example.net-Down
02 / Journeys
Journeys that find themselves.
Switch journeys on and the scan reads your menus, recognises sign in, search, cart, checkout and contact forms, and tries each one. Only what runs from start to finish is kept, so nothing has to be scripted by hand.
- A trial run before anything is kept, and never an alert about our own guess
- Sign in with a test account, encrypted, typed only into your own site
- Desktop and phone layouts, with a screenshot of the step that failed
- Scan again any time to pick up new pages, or journeys you removed
- Homepage loads/Added
- Search works/?s=Added
- Add to cart/product/linen-throwAdded
- Sign in/my-accountWaiting for a test login
- Contact form/contactAdded
03 / Cause
The alert names what changed just before.
Most breaks follow an update. The WordPress plugin records every plugin, theme and core update, and when a journey fails the alert says which change landed between the last good run and the first bad one.
- The update, both versions and how long before the failure
- Bounded by the last good run, so a cause is never claimed without evidence
- Script errors traced to the page and the plugin that threw them
Checkout stopped at Place order: the payment form did not load.
WooCommerce updated 9.4.1 to 9.4.2, 14 minutes earlier
04 / Visual checks
See the page the way your customer does.
Key pages are screenshotted on desktop and phone and compared with a baseline. A button pushed off screen or a stylesheet that failed to load is caught even when the server answers 200.
- Your homepage plus the shop, product and contact pages the scan found
- Two strikes before a rendering defect is alerted on
- Accept an intentional redesign in one click, and ignore regions that always move
Add to cart moved below the fold after the theme update.
05 / Alerts
One message that already says where to look.
Alerts go by email and Telegram, with the failed step, a screenshot of the page as it broke and the likely cause. When the site recovers, you hear that too.
- Set up and test every channel from Settings
- Incident history that records what happened, not only who was told
- Recovery messages, so nobody keeps fixing what is already fixed
Step 4 of 5, Place order: the payment form did not load. Checked twice, 10 minutes apart.
Payment form missing on /checkout
Plugin stripe-gateway updated 8.1.0 to 8.2.0
06 / Status and reports
Status pages and reports for your clients.
Give each client a public status page and a monthly report in your own colours. They see uptime and incidents in plain words; the technical detail stays with you.
- Your logo and brand colour, not ours
- Shows little by default, more only if you choose
- Monthly uptime and incident reports, ready to send
07 / WordPress
Goes deeper on WordPress.
Install the plugin and connect it in one step. It proves the site is yours, reports what is installed and every update as it happens, and lets journeys introduce themselves to your site as the monitoring browser.
- Plugin, theme and core versions, with every change timestamped
- Ownership proved by the plugin, no DNS record needed
- Works on any site without it; WordPress simply gets more
- WooCommercePlugin, 09:289.4.1 → 9.4.2
- StorefrontTheme, Yesterday4.6.0 → 4.6.1
- WordPressCore, Mon6.6.1 → 6.6.2
08 / AI
AI where the rules run out, on a key you control.
When the scan finds a product page but not its buy button, AI can read the page outline and point at it. Bring your own Claude or Groq key, or use ours within a daily limit.
- Only page outlines are sent, never your test logins
- Selectors AI invents are refused unless they exist on the page
- A daily cap on what our key can spend, so the bill never surprises us or you
- Read 10 pages from the menus
- Product page /product/linen-throw, no buy button found by rules
- AI: button.single_add_to_cart_button, found on the page
- Trial run passed, Add to cart kept
Start with one site
Add a site, and the first check runs straight away.
Start free, and move up when you want journeys, visual checks and reports in your own colours.