You have probably received one: a site audit that arrives as a spreadsheet with 180 rows, color-coded red and amber, each row a warning from a crawler. It is thorough. It is also almost impossible to act on, so it does not get acted on.
The problem is not the findings. It is everything around them.
What a working audit adds
Priority based on your goals. Not "severity" from a tool's generic scoring. Which issues actually block your growth, given what you are trying to do this quarter. Most of a 180-row list is noise you can defer indefinitely.
Impact and effort, side by side. A fix that takes an hour and lifts a key template beats a two-week project with a marginal payoff. You cannot sequence work without both numbers.
An owner per item. "The team" is not an owner. Engineering, content, or marketing, named, so the item can move.
A plain-English readout. One page a non-specialist can read and understand what matters and why, before the detailed inventory.
A sequence. A 30/60/90-day plan. What to do first, what depends on what, what to leave until later.
The shape we ship
- Executive readout in plain language
- Evidence-backed issue inventory, every finding with the proof behind it
- Impact and effort estimates
- Ownership recommendations
- A 30/60/90-day action plan
If we implement, that backlog moves straight into delivery. If your team implements, it is written to be handed over and worked without us.
Why "free automated audit" is not the same
Automated tools are useful for the raw inventory. They cannot tell you which twelve of the 180 items matter for your situation, in what order, owned by whom. That judgment is the actual deliverable.
When to run one
Start with a full baseline. Then run focused checks after a migration, a redesign, a tracking change, or a meaningful ranking drop, the moments when something likely broke. Ongoing monitoring covers the recurring technical issues in between.
An audit is only worth what gets fixed because of it.
See what a site audit that becomes a backlog looks like.