A results page should explain the inputs, method, outcome, and limits. If the output is a score, define what is counted and what is not. Link each finding to evidence and a practical next step. Avoid presenting an automated result as a definitive decision when it is only an estimate or public-site observation.
Example: A site scan reports that a privacy page was not found. Explain the URL patterns searched, provide the evidence, and say the owner should open the page manually if the scan missed a custom route. Do not label the site “noncompliant” based solely on an absent pattern. Google’s own site-status guide makes clear that account-side status is checked in AdSense.
Run a SiteReadyScore scan to see a structured report of public signals. The results page should make the scan’s scope visible, show the checked date, and tell the user what to verify. This transparency makes the tool more useful and sets accurate expectations.