What a Website Audit Actually Tells You
Most marketing teams have run a site audit. Far fewer can tell you what changed because of it.
The crawl finishes. A spreadsheet with a few thousand rows lands in someone's inbox. Everyone agrees the site has issues. Then the quarter fills up, and the spreadsheet joins the other good intentions in a shared drive.
I want to explain what an audit is good for, where it falls short, and how to read one so it leads to something.
Why sites drift
Nobody breaks a website on purpose. Developers ship a release. A plugin updates. Three people publish in three different styles. A redesign goes live and a few old URLs quietly disappear. Each change makes sense on its own.
Search engines also keep changing how they evaluate pages, so something that was fine two years ago may be a problem today. An audit is a snapshot. It shows where the site is now compared with where it should be.
What a typical audit covers
The crawl. A crawler walks your site the way a search engine does. It finds broken links, redirect chains, duplicate pages, and pages that are accidentally blocked from being indexed. That last one is more common than you would expect.
Speed and mobile experience. How fast pages load and how they behave on a phone. Visitors notice this, and search engines take it into account.
Content and on-page basics. Page titles, meta descriptions, headings, thin pages, and pages that compete with each other for the same search. Two articles chasing the same query can split their strength.
Security and housekeeping. HTTPS everywhere, no mixed content warnings, no leftover test pages that were never taken down.
Access for search and AI crawlers. Your robots.txt file tells crawlers where they can go. It is worth checking that you are not blocking crawlers you actually want visiting, including the ones that feed AI search. Structured data belongs in this check too.
What an audit cannot tell you
An audit lists what is wrong. It rarely tells you what matters.
Think of a home inspection report that lists every loose nail and cracked outlet cover with the same urgency as the leak in the roof. The report is accurate. It is also hard to act on. A list of 3,000 issues is not a plan.
The useful question is which five of those rows would move traffic if they were fixed this month. In my experience, it is usually a handful. A set of pages blocked by mistake, a redirect problem after a migration, a template that gives every page the same title. The rest is housekeeping you can schedule.
How to prioritize what comes back
I look at three things for each issue.
How many pages does it affect? A problem on one page is a task. A problem in a template that powers 4,000 pages is a project.
How much traffic or revenue do those pages carry? Fixing a page nobody visits can wait.
How hard is the fix? Some of the biggest wins take an hour. Do those first.
That simple filter turns a spreadsheet into an ordered list a developer can work through.
What drives the cost of an audit
I am not going to give you a number here, because any number I give would be wrong for your site. What I can tell you is what moves the price up or down.
Site size matters, since a 40-page site and a 40,000-page site are different jobs. So does the number of page templates. Whether competitors are included changes the scope. And the biggest swing is usually what you receive at the end: a raw export, a prioritized roadmap with explanations, or someone who also helps implement it.
If you are comparing quotes, ask what the deliverable looks like. Two audits with the same price can be very different products.
How often to run one
After a redesign, a migration, or a big content push, definitely. Outside of those, a light check every quarter is probably enough for most sites. Many of the tools make this easy. Google Search Console is free and shows indexing problems directly. Site Audit in Ahrefs can run on a schedule and flag what changed since the last crawl. As with any tool, test it on your own site before you rely on it.
Where this leaves your team
If your last audit is sitting in a shared drive, you probably do not need a bigger audit. You need the five rows from it that would change your traffic, and a date next to each one.