The short version: a scan collects data. An audit interprets it. Both have a place in website maintenance, but they serve different purposes and produce very different outputs.
What a website scan does
A website scan is an automated process that crawls your site and checks specific, measurable things. A scan can detect broken links, missing image alt attributes, slow page load times, missing meta tags, HTTP status errors, and similar technical conditions. It produces a list of what it found.
Scans are fast, cheap, and good at cataloging. Many free tools offer basic scans. The limitation is that a scan tells you what exists — not whether it matters, not how bad it is, and not what to do about it. A scan might flag 200 issues, leaving you with no sense of which three actually need fixing this week.
What a website audit does
An audit uses scan data as a starting point but goes further. It evaluates what the data means in context. A good audit assesses severity, explains impact, and gives you prioritized recommendations written for the person who will act on them.
For example: a scan tells you that your donate page loads in 6.2 seconds. An audit tells you that 6.2 seconds is well above the threshold at which donation rates drop significantly, identifies the two oversized images causing it, and tells you exactly how to fix them.
Audits also cover things that scans can't detect at all — like whether your calls to action are clear, whether your homepage messaging makes sense to a first-time visitor, or whether your contact information is easy to find.
When a scan is enough
If you need a quick snapshot of obvious technical problems — broken links, missing page titles, pages returning errors — a scan is a fast and useful tool. Scans work well for routine monitoring, for checking that a recent update didn't break anything, or for gathering raw data before a more thorough review.
If your team has the technical experience to interpret scan output and knows which numbers matter, a scan can be a sufficient starting point. For many nonprofit staff without a web background, that's where it breaks down.
When you need an audit
You need an audit when you need to understand what to actually fix, in what order, and why. Before a major fundraising campaign. When donors or grants have flagged website concerns. When your site hasn't been formally reviewed in more than a year. When you want to present findings to a board or leadership team that needs context, not just a list of flags.
An audit is also the right choice when you want a complete picture — not just the technical layer, but also accessibility, trust signals, performance, and the visitor experience.
GoodSiteReport audits are built specifically for nonprofits — written in plain language, prioritized by impact, and focused on the things that matter most for your donors and visitors, not just technical scores.
The gap between automated results and actionable guidance
The most common frustration nonprofit staff report with website tools is getting a score or a spreadsheet that doesn't help them do anything. A scan can produce a report that looks thorough but leaves you more confused than when you started.
Actionable guidance means: here is the specific problem, here is why it matters for your organization, and here is what to do. That requires human judgment applied to your site's specific situation — which is what distinguishes a real audit from a scan with a report attached to it.