Website uptime monitoring
AI-powered content checks as often as every 30 minutes. When a key page starts erroring, goes blank, or loses the content that matters, you get one clear alert — not a flood.
Classic uptime monitoring pings a URL and reports whether it answered. WebMonitor.fyi works one level higher: on each check it fetches the page, reads the actual content, and evaluates your plain-language criteria — catching the failure modes a ping misses, like a page that returns HTTP 200 but renders an error banner, a blank template, or a checkout button that vanished. Checks run on the schedule you pick, as often as every 30 minutes on the Pro plan. For sub-minute up/down paging, pair WebMonitor with a dedicated ping tool — and use WebMonitor to catch "up but broken".
What it does
Content validation, not just pings
HTTP 200 isn't always "up". The AI reads the rendered page and alerts when an error banner appears, the page goes blank, or content named in your criteria disappears.
Plain-language checks
Write the rule in normal words: "alert me if this page shows an error message or the pricing table is missing". No scripting, no selectors.
Checks as often as every 30 minutes
Pick a frequency per monitor — 30 minutes or hourly on Pro, 6-, 12-, or 24-hour intervals on Basic. Detection time is bounded by the interval you choose.
One alert per incident
Smart deduplication means a page that stays broken doesn't re-alert on every check. You get the first alert, then quiet until something actually changes.
Slack and webhook delivery
Email always sends; add a Slack incoming webhook or a generic JSON webhook to route alerts into the channel or tooling the team already watches.
How to set it up
Add the URLs to monitor
Homepage, pricing page, signup page, key landing pages — the public pages where breakage has direct business consequences.
Set check frequency per monitor
30-minute checks (Pro) for business-critical pages; hourly or daily for less critical surfaces.
Configure alert routing
Email by default; add a Slack webhook for team visibility or a generic JSON webhook to feed your own tooling.
Review the history
The dashboard keeps the last 50 checks per monitor, each with an AI summary — enough to see when a page broke and when it recovered.
Common use cases
- E-commerce sites where a broken product or checkout page is direct lost revenue
- SaaS marketing sites where a blank pricing page quietly kills conversions
- Marketing pages that must stay intact during a launch campaign
- Agencies keeping an eye on client sites without logging into each one
- Vendor status pages — get alerted when a provider posts an incident
Honest limits
WebMonitor is not a ping-based uptime tool: the fastest check interval is 30 minutes, and there is no SSL-certificate expiry tracking, multi-region probing, response-time measurement, or sub-minute paging. For hard-downtime detection in under a minute, use a dedicated ping service (UptimeRobot, Pingdom) — and use WebMonitor for the content-level failures those tools can't see.
Frequently asked questions
What's the right check frequency for uptime monitoring?
The fastest interval is 30 minutes on the Pro plan, which bounds detection time to about half an hour. That suits catching broken content on important pages; if you need to page an on-call engineer within a minute of hard downtime, run a dedicated ping tool alongside.
How is this different from Pingdom, UptimeRobot, or StatusCake?
Those tools ping a URL at sub-minute intervals and tell you up or down. WebMonitor fetches the page and has AI read the content, so it catches "up but broken" — error banners, blank renders, missing sections — that a status-code check reports as healthy. Many teams run both: a ping tool for downtime paging, WebMonitor for content health.
Can I monitor an authenticated page?
No. Pages behind a login wall aren't supported — the monitor detects the login wall and reports it rather than guessing. Monitor the public pages that matter, or a public status or health page if your team publishes one.
How fast are the alerts?
Within one check interval: on 30-minute checks, you'll know within about half an hour of the page breaking. Smart deduplication means you get one alert when it breaks, not a repeat on every check while it stays broken.
Related
Solution
Web application performance monitoring
WebMonitor doesn't time your pages — it reads them. Catch the content regressions performance dashboards miss: broken templates, missing sections, error text, and vendor incidents.
Read moreSolution
Slack & webhook alerts
Route every detected change to the channel your team already lives in. One field on the monitor, a formatted Slack message or a JSON webhook, no extra setup.
Read moreTry it on the page you want to monitor
Free to try. No credit card. Paste a URL, write a criterion, see the analysis.
Start free