This is the reference. Each entry says what it looks for, which pages it applies to, how serious a failure is, and what to do about it. KeyPages picks the ones each page needs; you never choose from this list.
A check that does not apply to a page is never counted as a pass.
Every protected page is checked for...
Choose a catalog view
Reachability
Can customers actually get to this page?
Checks that the page responds, resolves securely, and does not disappear into a broken route or redirect.
HTTP Status FailureRedirect LoopTLS Certificate FailureUnexpected 4xx Error
What it catches
Same URL redirect or redirect chain >3 hops
Why it matters
Users will be unable to access the page, often seeing browser errors. Search engines may stop crawling the page entirely, which can remove it from search results.
How to fix
Review all redirect rules across your stack (application, CDN, DNS, hosting platform). Ensure you are not applying the same redirect in multiple places (e.g. both app and CDN).
Check for conflicts like HTTP → HTTPS and www → non-www happening simultaneously. Test the URL manually and trace the redirect chain to identify where the loop begins.
Next protection area
Rendering — Does the page appear correctly?
Checks that the browser can render a complete, usable page instead of a blank, crashed, or partial shell.
