A client's store
- Product page
add to cart usable - Cart
reaches checkout - Checkout entry
loads, not redirected - Search
returns results
For freelancers and small agencies
Know a client page broke before the client does.
You built the site, and you get the call when it stops selling, booking, or collecting leads. KeyPages checks each client's important pages in a real browser and hands you the evidence first.
7-day trial, 5 pages, no card. Public pages only. KeyPages never signs in, fills forms, or places orders.
The agency problem
The site is up. The client is still calling you.
A theme update, a plugin change, a popup nobody tested on mobile. The server keeps answering 200 OK, and the first person to notice the add-to-cart button is dead is a customer, then the client, then you.
- Customer
Tries to buy or book. Cannot. Leaves.
- Client
Hears about it days later. Calls you. “The site is broken.”
- You
Start from nothing: which page, what broke, since when, and is it still happening?
KeyPages moves you to the front of that sequence, with a screenshot and a plain sentence about what changed.
Three to five pages per client
You do not need to monitor the whole site. Just the pages that make the client money.
Add the live URLs. KeyPages works out what each page is for and checks that it still does that one job. A check that does not apply to a page is never counted as passed.
A client's booking site
- Booking page
form present and usable - Services / pricing
CTA present - Contact
form present
A client's lead-gen site
- Contact / quote
form present and usable - Pricing
primary CTA present - Landing page
content and CTA intact
Starter covers 10 pages, Growth 40, Agency 100. Most client sites need three to five. See plans
Clients workspace
Every client's pages, grouped by client.
Assign each protected page to a client. See at a glance who is Protected, who needs attention, and which client has not been verified recently.
ClientsOrganize the public pages you protect for each client.
5 clients · 17 pages · 1 needs attention| Client | Pages | Status | Last verified |
|---|---|---|---|
| Northstar Outdoors | 4 | 1 needs attention | 9 min ago |
| Harbor Dental | 3 | Protected | 12 min ago |
| Fernwood Landscaping | 3 | 1 warning | 6 min ago |
| Maple & Co. Bakery | 5 | Protected | 14 min ago |
| Ridgeline Physio | 2 | Could not verify | 1 h ago |
Evidence you can forward
Send the developer proof, not “the site looks broken.”
Every confirmed failure arrives written up well enough to forward straight to the client or whoever maintains the site, with the context they need to fix it.
- Client and page
- Rendered screenshot
- Expected vs observed
- First and last seen
- Plain-language next step
- Recovery state
Needs attentionNorthstar Outdoors / Product page
- Page
- northstar-outdoors.com/products/travel-jacket
- Expected
- The add-to-cart button is present and usable.
- Observed
- The add-to-cart button is disabled. The page returned 200 OK.
- Seen
- First 09:42 today. Still happening as of the last check.
- Recovery
- Watching for a verified fix. It will close itself.
Rendered screenshot attachedWhat the client's customer actually saw
Example from a KeyPages test fixture, not a customer site.
Client reports
Show each client what was protected, caught, and recovered. Under your name.
A Protection Report is scoped to one client's pages. Add your agency's name, logo, and accent colour, then share it by an expiring link you can revoke at any time.
Ridgeback StudioProtection Report · Northstar Outdoors
1–30 Aug- Protected
- 4 pages
- Caught
- 1 issue
- Recovered
- 1, verified
- Add to cart disabledProduct page · found 14 Aug 09:42 · screenshot saved
- Recovery verifiedLater check passed · 14 Aug 11:05 · 1 h 23 m
- Your branding
Agency name, logo, accent colour and contact line on every new client report.
- Share by expiring link
7, 30 or 90 days. Revoke it whenever you like. Internal notes and dashboard links stay out.
- Recovery is verified
A fix appears in the report only after a later real-browser check passes.
Alongside your site-care stack
Keep your uptime tool. KeyPages watches the layer it cannot see.
Uptime and site-care tools are good at the server. They are not designed to know whether the rendered page still lets a customer buy, book, or get in touch.
Uptime or site-care tool
- Server responds
- SSL certificate valid
- Assets load
- Plugins and core updated
KeyPages
- The rendered page still does its job
- Add to cart, booking, contact still usable
- Screenshot evidence of what broke
- Recovery verified by a later check
KeyPages checks public pages only. It does not sign in, fill forms, place orders, or submit payments. What we do and do not touch
Start with one client
The page they would call you about. Protect that one first.
Paste the live URL. KeyPages works out what the page is for and starts checking.