Same failure. Different thing you stand to lose.

Start with the one that matches what you are responsible for. If you look after sites for other people, read the agency or freelancer page. If you are protecting a specific moment — a campaign, a migration, a launch — read that scenario. If the thing you own is a platform, read the platform page. They describe the same product; what differs is the failures and the stakes.

That is normal, and nothing changes about the setup. An agency running WooCommerce stores for clients gets value from all three of those pages, and one Sitewatch account covers them. The pages are written for different readers, not for different products.

No. It is one product with one set of checks. What changes between these pages is which failures matter most to that reader — a broken payment script matters to a store, a missing tracking script matters to a marketing team, and a stale build matters to a dev team. All three are the same underlying check.

None of them. Sitewatch checks from the outside, the way a visitor arrives, so there is no plugin, no snippet and no server access needed. That is also why it keeps working when the site itself is in trouble, and why you can monitor a site you did not build.

Free for one site, forever. Starter is $9/month for up to 25 sites with checks every 15 minutes, and Pro is $19/month for up to 100 sites with checks every 5 minutes and a second check region. There is no per-seat pricing, so the whole team works from one account.