Tell shipped checks from planned checks
Confirm which documented checks currently run in the desktop app.
Last checked 21 August 2026
Some checks are available in the current desktop app. Others appear only in product documentation as planned. A documented check name by itself does not prove that TechDash currently schedules that check or opens incidents for it.
How to confirm a check is available
Use the app first:
- Open a website and review Optional checks on a monitored page.
- Open Sitewide Checks for website-level and site-resource results.
- Open Incidents and confirm whether that check can appear as an open issue.
- Compare what you see with current product documentation for cadence and limitations.
Available checks usually show up in at least one of those places, or they run automatically as always-on page gates such as HTTP availability. Planned items do not appear as active optional checks, sitewide results, or incident sources.
Current planned inventory
Current product documentation marks two capabilities as Planned:
- External links won and lost, a proposed weekly backlink feed
- Core Web Vitals field data, a proposed real-user field-data check for LCP, INP, and CLS
Neither is current monitoring. Do not expect them to create evidence, open incidents, or appear as available check sources until product documentation marks them Shipped and the app exposes them.
Related shipped features should not be confused with them. TechDash does probe links found on monitored pages and detect external outbound link spikes, but that is not an external backlink index. It also measures a narrow mobile viewport and horizontal overflow regression, but that is not real-user Core Web Vitals field data.
Why a documented alert can still overstate behavior
Even for an available check family, product documentation can describe alert variants that the current app does not open. Trust the incident evidence and current result you see in TechDash. For example, structured data validity currently opens JSON-LD parse error, while related required-property or gallery-type alerts may remain documentation-only until they appear in the app.
The same caution applies to thresholds and scope. Documentation may describe a broad page group, while the current check can operate page by page. The before-and-after evidence in the incident is the reliable guide to what triggered today.
Verify before you rely on a claim
When reviewing a roadmap or documentation claim:
- Confirm the check appears in Optional checks, Sitewide Checks, or as an automatic page gate.
- Confirm a result or incident can appear for it in the current app.
- Confirm the cadence and limitations in current product documentation.
- Treat any remaining planned item as roadmap inventory, not a monitoring promise.
A planned item becomes a current capability only when the app exposes it and product documentation marks it Shipped.