Protection Coverage
You're monitoring the homepage. What about the other six pages?
Coverage gaps are the silent risk in every portfolio. You set up monitoring on the homepage at launch and never revisit it — while Checkout, Login, and Pricing go unwatched for months. Sitewatch reads every page it finds on your site — checkout, booking, login, pricing — and tells you which ones aren't protected yet. "All good" becomes "82% covered, 3 important pages unprotected," and one click closes the gap.
- Reads every page it finds — checkout, booking, login, pricing
- Importance-weighted coverage score (0–100%) on every site
- Names each unprotected page — and why it matters
- One-click "Protect this page" to close each gap
01The green-dashboard lie
Your monitoring coverage, scored — so "healthy" never hides a gap
It reads your pages — and you still get the final say
A page called /get-started can be a booking form. A checkout can sit behind a URL with no clue in it. So Sitewatch opens each page it finds and looks at what's on it — the payment provider, the login form, the booking widget — before deciding what matters. Every rating is a suggestion: pin any page to the importance you think it deserves and the score updates instantly.
A score that reflects risk, not page count
Coverage is importance-weighted — a critical page like Checkout counts far more than a low-priority page. The number tells you how much risk you actually cover, not how many URLs you happened to add.
The gaps, named — with the reason
Sitewatch names the unmonitored important pages and why each one is on the list: takes payments via Stripe, has a login form, booking widget detected. Not a green checkmark hiding them.
Close the gap in one click
Every unmonitored page gets a one-click "Protect this page." No re-onboarding, no hunting through settings.
Portfolio-wide gap visibility
Every site row shows a compact coverage % chip. Spot the under-protected client sites across your whole portfolio at a glance.
Upgrade prompts that name the risk
Hit a plan limit and you see "This site has 4 unmonitored important pages including the Checkout" — never a generic "limit reached." Gates work for you, not against you.
0–100%
Importance-weighted coverage score
1-click
Protect any unmonitored page
Day one
Gaps surfaced at first scan
02From blind spot to covered
How protection coverage works
- 01
Add a site
Point Sitewatch at a domain. It runs a full first scan across every monitoring category — no configuration required.
- 02
Sitewatch reads the pages it finds
Not a guess from the URL. Sitewatch opens each page and looks at what's on it — the forms, the buttons, the payment and booking tools — then rates how much it would cost you if that page quietly stopped working. The First-Scan Risk Report shows what was checked, what passed, and which pages aren't covered yet.
- 03
See your coverage score
Each site carries an importance-weighted coverage score and a card naming the unmonitored important pages. The portfolio list shows a coverage % chip on every row.
- 04
Protect the gaps
Click "Protect this page" on any unmonitored page. After an upgrade, a single click adds all previously-blocked pages to monitoring at once.
03Transparency on day one
The First-Scan Risk Report: what we checked, and what we didn't
What we checked
Every monitoring category — availability, broken assets, redirects, API health, SSL & domain, security headers, performance — reported as pass or issues. Breadth you can see, not a black box.
What we're not covering yet
The page-coverage gap, named in plain language, right next to the passing checks. Honesty and breadth on one screen — the two things you need before rolling a tool across a client portfolio.
Re-openable anytime
The report doesn't vanish like a celebratory toast. It's pinned to the site header so you can reopen it whenever you revisit a site.
See what's unprotected on your site
Add a site and Sitewatch reads its pages, then shows you which ones aren't protected yet. No credit card.
04Coverage assurance, not just detection
A green dashboard vs. a coverage score
| Scenario | Typical monitoring | Sitewatch coverage |
|---|---|---|
| What a healthy site shows | A green checkmark | "82% covered — 3 pages unprotected" |
| Unmonitored pages | Invisible until they break | Named, scored, one-click protect |
| Coverage metric | None — you guess | Importance-weighted score per site |
| Portfolio view | No gap visibility | Coverage % chip on every site row |
| Plan limits | Generic "upgrade" nag | Named risk: "Checkout is unmonitored" |
What a healthy site shows
- Typical monitoring:
- A green checkmark
- Sitewatch coverage:
- "82% covered — 3 pages unprotected"
Unmonitored pages
- Typical monitoring:
- Invisible until they break
- Sitewatch coverage:
- Named, scored, one-click protect
Coverage metric
- Typical monitoring:
- None — you guess
- Sitewatch coverage:
- Importance-weighted score per site
Portfolio view
- Typical monitoring:
- No gap visibility
- Sitewatch coverage:
- Coverage % chip on every site row
Plan limits
- Typical monitoring:
- Generic "upgrade" nag
- Sitewatch coverage:
- Named risk: "Checkout is unmonitored"
05FAQ
Frequently asked questions
It is importance-weighted. Every page is rated critical, high, normal, or low — Sitewatch suggests the rating after reading the page, and you can change it. A critical page like Checkout contributes far more to the score than a low-priority page, so the percentage reflects how much business risk you cover — not a raw count of URLs.
It reads them. Sitewatch checks each page it finds for the things that make a page matter to a business — a payment provider like Stripe, a login form, a booking widget, a lead form, pricing content — and then rates how much it would cost you if that page quietly stopped working. Each rating comes with a confidence level, and where Sitewatch isn't sure, it keeps the previous rating and tells you so. In your dashboard this is the Smart Protection card, on each site's Overview tab.
No. Sitewatch itself finds what's on the page — the payment script, the login form, the booking widget — and those are verified, not inferred. The AI's job is only to rate how much that adds up to in business terms, and it tells you how sure it is. You can override any rating, and the score updates instantly.
A short summary of the public page: its title, its headings, the labels on its buttons, which types of form field exist, and which third-party scripts load. Never what anyone typed into a form, never query strings, never personal data. Sitewatch only fetches pages that are already public — it doesn't log in to anything.
Critical page monitoring is the capability to monitor specific pages you choose — checkout, login, pricing. Protection coverage is the assurance layer on top: it scores how many of a site's important pages you have actually picked, names the ones you haven't, and lets you protect them in one click. One is the monitoring; the other tells you what you forgot to monitor.
Yes. Protection coverage, the First-Scan Risk Report, and gap visibility are available on every plan, for every site. The reason to upgrade is to monitor more pages and more sites, and to have Sitewatch re-read your site for you as it changes — not to unlock the feature.
When a newly added site finishes its first scan, you land on a persistent report with two halves: "what we checked" (every monitoring category with a pass/issues result) and "what we're not covering yet" (the page-coverage gap). It replaces a vanishing success toast with a structured payoff you can reopen anytime.
No. Plan limits are expressed as named risks tied to the gap you already have — "this site has 4 unmonitored important pages including the Checkout" — not "page limit reached." After you upgrade, a single click adds all the previously-blocked pages to monitoring at once.
06Explore more