Website Checkup · alpha · worked example
How to turn website check results into a repair list
An automated finding needs context before it becomes a fix. Reproduce the issue on the actual page and decide whether it blocks a visitor or is simply an improvement opportunity.
Updated October 10, 2026 · by thecreatingco
A small example to work through
Our original fictional triage list separates a broken project link, a missing description and a contact form with no visible success state. It is not a scan of your site.
| Item | Example | Notes |
|---|---|---|
| Broken project link | Visitor cannot open work | Reproduce and repair destination |
| Missing description | Search preview may be unclear | Write page-specific copy |
| No form success state | Visitor cannot tell whether submission worked | Test on your own form with harmless data |
| Decorative image label | May be intentionally empty | Check purpose before changing |
Download the editable text worksheet · Download the CSV worksheet
Use the blank observation and decision fields to record your own result. These downloads are planning worksheets; they do not load an app project or demonstrate a completed export.
Try it and inspect the result
- Open Website Checkup and follow its current hosted preview entry. Choose only a site or material the tool supports.
- Reproduce each finding manually. Record the affected URL, observed behaviour and an expected result rather than copying a severity label blindly.
- Fix the most consequential issue first, then repeat that journey. Keep a dated repair log; one clean scan does not establish complete site quality.
When the result differs
- Tool cannot inspect a page
- Access restrictions or rendering may limit the checker; test the actual visitor path.
- Everything is labelled urgent
- Prioritise blocked actions and broken content before cosmetic improvements.
- Scan looks clean
- Still review keyboard use, phone layout and meaningful user tasks.
What this example establishes
The sample repair list is not a Website Checkup output or a certification. The backend remains in a dedicated hosted preview. A check cannot certify accessibility, security, search performance or every form integration.
This page supplies a worked example and a review method. It does not report a newly completed end-to-end app test. For current availability and edition details, read the Website Checkup overview.