Page Health shows how a stable set of your pages responds in a real browser. It combines response status, rendered-page checks, content facts, links, and lab performance observations in one diagnostic view.
What Page Health measures
Each audit checks up to 200 monitored URLs. Stride selects the same normalized URLs in a stable order so completed audits remain comparable. If Stride discovers more than 200 URLs, Page Health states how many are outside the monitored scope instead of implying that the whole site was measured.
For each monitored URL, Page Health records:
- Whether the page returned readable HTML directly, redirected, failed, or could not be reached
- Rendered title, description, canonical,
noindex, heading, and visible-word observations - Unique internal and external link destinations
- Lab Largest Contentful Paint (LCP), First Contentful Paint (FCP), Cumulative Layout Shift (CLS), Time to First Byte (TTFB), and page-load timing
- Resource and transfer observations when Chromium reports them
Where to find it
Dashboard → Site Health → Page health.
Page Health is released through a controlled rollout. If the item is not visible for your site yet, your existing Content Index remains available in Settings.
Audit cadence
Stride schedules one Page Health audit each week. You can also choose Run audit for a manual refresh. If an audit is already queued or running, another trigger uses that active run rather than starting duplicate work.
A fixed desktop Chromium profile and a three-second post-load observation window keep the measurement conditions consistent. Previous completed evidence stays visible while a refresh runs or if the latest refresh stops early.
Status definitions
| Status | Meaning |
|---|---|
| Readable | The requested URL returned readable HTML directly |
| Redirected | The request reached readable HTML after one or more redirects |
| Blocked by robots | The applicable robots policy does not allow the path |
| Robots unavailable | Stride could not obtain a trustworthy robots policy, so the request failed closed |
| HTTP error | The final response returned a 4xx or 5xx status |
| Unreachable | Chromium received no usable response before the bounded timeout |
| Non-HTML | The final response succeeded but was not an HTML document |
| Unsafe URL | The request, redirect, or subresource targeted a destination Stride does not permit |
| Not monitored | Stride discovered the URL, but it is outside the stable 200-URL audit scope |
Lab data is not field data
Page Health uses a controlled desktop lab. Its timings describe this specific browser profile and observation window; they are not real-user Core Web Vitals, mobile measurements, or Chrome UX Report data. Use the distribution, sample size, and comparison with your previous comparable audit rather than treating one URL’s value as universal user experience.
Robots handling
Page Health identifies itself with the Stride audit user agent and evaluates the
robots rules that apply to it. A missing robots.txt allows measurement. Access
denials, rate limits, server failures, and network errors fail closed, so Page
Health does not continue when the policy cannot be trusted.
What Page Health does not report
Page Health does not report Google indexing or URL Inspection status. A
readable page may still be absent from search results, and a noindex observation
is not proof of Google’s current index state. It also does not report backlinks,
mobile or field performance, Lighthouse scores, or JavaScript error logs.
From diagnosis to action
Use Overview to inspect scope, status, and individual URL observations. Use Health to review access outcomes, lab-performance distributions, content depth, SEO conditions, and link profiles.
Page Health diagnoses what Stride measured. It does not create a second work queue or apply fixes automatically. Take technical and content remediation into Actions or AI Readiness, where work can be prioritized with the rest of your visibility program.