Verified vs Unverified Data in a Website Audit
Website intelligenceVerified vs Unverified Data in a Website Audit
A good report distinguishes between a signal that was measured and a signal the scan could not verify. This distinction matters because an unavailable result does not necessarily mean that the website is missing or misconfigured.
Read scan status before interpreting findings
Check whether the scan completed and whether the requested URL returned the expected page. If a page timed out, blocked the request or redirected somewhere unexpected, later checks may be absent or incomplete.
Review the source for each result where it is provided. SiteBoost findings can come from its crawler or from Lighthouse-based checks; those sources have different scopes and limitations.
Avoid turning missing data into a false error
If a score is unavailable, first check whether the audit source completed. If a field is blank, inspect the live page source and response before changing the website. A missing measurement is not the same as a measured failure.
Keep the report's verified and unverified states separate in your task list. This gives a developer a specific next check rather than an instruction to change something without evidence.
- Confirm HTTP status and final URL.
- Check whether the scan source completed.
- Inspect the live source when a value is missing.
- Record unresolved checks separately from confirmed findings.
Rerun after fixing access or delivery
When the cause of incomplete data is resolved, run the same scan again. Compare the checks that were previously unavailable and confirm whether the report can now measure them.
If a result remains unavailable, use the appropriate manual test or investigate the source limitation. Do not assume that every scan gap can be fixed through page metadata.
