Five questions. Asked of every page you protect.
Each one is answered by a real browser looking at the public page. KeyPages works out which checks the page in front of it actually needs, and leaves the rest switched off. Every check has an exact definition you can read.
The five protection areas
- 01Reachability
Can customers actually get to this page?
- HTTP failures
- Broken routing
- Unexpected redirects
- Dead or soft-404 behavior
- 02Rendering
Does the page appear the way it is supposed to?
- Blank page
- Incomplete render
- Runtime failure in the browser
- Major visible layout damage
- 03Critical Content
Is the important stuff still on the page?
- Required content disappears
- Indexing signals vanish
- Critical copy or media is missing
- 04Dependencies & Performance
Did something underneath the page break?
- Critical scripts disappear
- Third-party dependencies fail
- Material performance regressions
- 05Key Action
Is the one thing this page exists for still there and usable?
- Add-to-cart present and enabled
- Checkout entry reachable
- Lead form present and usable
- Login form present
- Search input and seeded results present
- Pricing CTA present
These five areas are the shape. The Test Catalog is the full list: every check KeyPages can run, what it looks for, which pages it applies to, and how serious a failure is.
Open the full Test CatalogA check that does not apply is not a check that passed.
Dashboards full of green are easy to build if you count every irrelevant test as a win. KeyPages leaves a check that does not apply out of the result entirely. It never shows as a pass. So when a page reads healthy, that means every check that was actually asked came back clean.
See which checks apply to which pageWhat actually turns on, page by page.
A client's product page and their blog post do not fail the same way, so they are not checked the same way. Pick a page type to see exactly which checks apply, which stay off, and why.
Add-to-cart present and enabled
Price, image and the buy button all have to be there. Nothing is added to a cart.
Switched on for this page
- Add-to-cart missingCritical
- Add-to-cart disabledCritical
- Product price missingWarning
- Product image missingWarning
- Script domain changedWarning
Plus the 31 checks every page gets
- TLS Certificate Expiring SoonWarning
- HTTP Status FailureCritical
- Redirect LoopCritical
- Redirect To HomepageWarning
- TLS Certificate FailureCritical
- Unexpected 4xx ErrorWarning
- Critical DOM Selector MissingWarning
- H1 Heading RemovedWarning
- Major DOM DropWarning
- Major Text Content DropWarning
- Title Tag RemovedWarning
- Canonical URL ChangedWarning
- Mixed Content DetectedWarning
- Noindex Tag AddedWarning
- OpenGraph Tags RemovedWarning
- Sitemap Invalid or MalformedWarning
- Sitemap RemovedWarning
- Structured Data RemovedWarning
- Third Party Dependency FailureWarning
- Core Web Vitals RegressionWarning
- Unexpected Script AddedWarning
- Large HTML Size JumpWarning
- Severe Slow Page LoadWarning
- Slow Response TimeWarning
- TTFB Spike DetectedWarning
- Blank Page DetectedCritical
- Critical Bundle FailureCritical
- High Resource Error RateWarning
- JavaScript Crash DetectedWarning
- Script Shell OnlyCritical
- Script Injection DetectedWarning
Switched off, and why
- Checkout button missingthere is no checkout button on a product page
- Account login form missingthis is not a login page
- Search results missingthis is not a search page
Switched off is not a pass. A check that does not apply is left out of the result entirely. It never shows as green, so a healthy product page means exactly the checks above came back clean.
See the exact definition of every checkWhat the words on this page mean.
The check names are precise on purpose. This is the boundary between what KeyPages verifies and what it deliberately leaves alone.
- Present and usable
- A form, button or link is on the page, visible and not disabled. KeyPages does not press it, fill it in or submit it.
- Reachable
- The route answers, is not redirected somewhere unexpected, and lands where it should. No order or account is ever created.
- Public pages only
- KeyPages looks at what a signed-out visitor sees. It never logs in, and it never sees anything behind a login.
- Setup-dependent checks
- A few checks, such as expected checkout script domains, only run once the page is told what to expect. They are marked as such in the catalog.
Start with one page. The right checks turn on.
Pick the page a client would call you about. Checks that do not apply stay off, and stay honest.