Start with the scope, not the number
Before you act on a score, check which pages were inspected and what the tool actually tested. A five-page source audit cannot describe every part of a large website. Note any pages that failed or were skipped, and distinguish a missing HTML attribute from a proven visitor problem.
Confirm the finding in its page context
Open the affected page and look at the evidence. Is the issue still present? A contact link might use wording or navigation the tool did not recognise. An image can have an alt attribute but still need better text. Automated findings should make investigation easier, not decide every change for you.
Deal with blocked journeys and clear omissions
If a page returns an error, investigate it before polishing its wording. If an important page has no useful title or no obvious way for visitors to contact you, those are practical review candidates. Consider the purpose of the page: a checkout, service page and article will have different priorities.
Make a small, testable change
Give your developer the page URL, the observed result, the intended outcome and any relevant constraints. For example: “The services page title is Home. Please give it a descriptive title identifying the service and business.” Work on a small group of related issues so you can test the result and identify what changed.
Verify rather than chase a perfect score
After a change, inspect the page again and test the visitor journey. Recheck on mobile and confirm that forms, links and navigation behave as intended. A further scan is a new audit; the original one-off report stays a snapshot. A perfect source-check score would still not establish good rankings, accessibility compliance or strong conversion performance.
Know when a specialist review is needed
Use specialist testing for keyboard access, contrast, real-user performance, security vulnerabilities or business conversion analysis. SiteCheckpath currently provides source-based technical signals. It does not render pages, measure Core Web Vitals or make automatic website changes.
Google: creating helpful, reliable content ↗
This guide is general information. Review changes in the context of your website and use the original documentation for your platform and tools.