A useful free website audit tells you what was checked, what happened, and what to do next. A long list of red badges is not enough. Before changing a site or forwarding a report to a client, check the evidence behind the recommendation.
Start with scope, not the score
Ask these five questions about any report:
- Which exact URL was tested, including its final redirect destination?
- When was it tested, and with which device or scan profile?
- Which checks completed and which were unavailable?
- Does each finding include evidence you can inspect?
- Can you repeat the same check after a repair?
A single-page audit is not a crawl of the entire site. Public HTML and response headers also cannot reveal everything inside a hosting account, a payment workflow, or a login-protected application.
Separate the types of evidence
Performance evidence may come from a simulated visit or from aggregated real visitors. Ask which one you are reading before drawing conclusions about an individual deployment. The Core Web Vitals guide explains the difference.
Configuration evidence can show, for example, a returned header or canonical tag. It does not by itself prove that every route uses that configuration correctly.
Content evidence can show that a title or image alternative exists. Someone still needs to decide whether its wording is useful. Google's SEO starter guide emphasizes content that people can understand and use; passing a tag check is a much narrower result.
Security signals help locate configuration questions. They are not a penetration test, a compromise investigation, or a compliance certification.
Use a finding-quality checklist
For each issue you might act on, fill in this small record:
Observation: what the report actually returned. Scope: the URL and test conditions. Consequence: the visitor task that might be affected. Confirmation: how a person will reproduce it. Action: the proposed change and its owner. Recovery evidence: what a later comparable check must show.
Consider a missing title on a service page. The report can point you to the page. The editor decides the wording, the developer confirms how it reaches the document, and a fresh inspection verifies the result. The audit has helped create a bounded task without promising more traffic.
Choose the next action by consequence
Work on a confirmed failure in an important visitor journey before a cosmetic score improvement. A working homepage should not distract from a broken booking link. Conversely, do not make an untested server-wide policy change only to gain a few points.
If a scanner cannot fetch the page, investigate that failure separately. Keep the last usable report, but display its age. Treat a repeat scan as new evidence, not as permission to erase an unresolved finding.
Take a snapshot, then close one loop
Run a free PageVital scan on an authorized public URL. Choose one finding, confirm it, and recheck after the change. If the job repeats across client sites, the weekly review checklist provides a routine for keeping open questions visible.