SEO audit pricing spreads wider than almost any other line item an agency sells, and the spread is not mostly about quality. It is about scope. The same phrase covers a crawler export with a cover page, a two-week diagnostic on a large site involving log files and a development team, and everything in between. Because the deliverable is not standardised, quotes are not comparable until you specify what the audit has to answer. This page sets out the variables that move the number, what a serious audit contains, and how to write a short brief that turns four incomparable proposals into four comparable ones.
The five variables that move the price
First is site size and complexity: auditing a two hundred page brochure site and auditing a faceted ecommerce catalogue with millions of crawlable combinations are different jobs, and Google's own crawl budget guidance notes that crawl management only becomes a real concern on large or frequently changing sites. Second is depth of data access: an audit that includes Search Console, analytics and server log files costs more and finds more than one done from the outside. Third is scope of discipline, since technical, content, and authority audits are three separate exercises often sold under one word. Fourth is whether recommendations are prioritised and specified for developers, or simply listed. Fifth is what happens after delivery: a debrief, a prioritisation session and follow-up questions are labour, and a quote that excludes them is cheaper because it is smaller.
What separates an audit from a tool export
Every SEO tool will produce a list of issues. That list is an input, not an audit. The work that carries the value is judgement: deciding which of the thousands of flagged items actually affect how this site is crawled, indexed and ranked, tracing symptoms to causes, and estimating the business impact of fixing each one so that a development team can sequence the work. A useful audit tells you what to do first and why, what to ignore and why, and what evidence would prove the diagnosis wrong. A weak audit hands you a severity-colour spreadsheet and leaves the prioritising to you, which is the part you were paying for. When comparing quotes, ask each candidate to show a redacted sample deliverable, and read it for reasoning rather than length.
What a serious audit actually examines
The technical pass covers crawling and indexing, whether important pages are reachable and returning correct status codes, duplicate and near-duplicate handling, canonical and hreflang correctness, structured data validity, and page experience signals including the Core Web Vitals metrics Google documents as part of page experience. The content pass reviews whether pages answer the queries they target, whether coverage matches demand, and whether thin or overlapping pages compete with each other. The authority pass looks at link profile composition and any pattern that touches Google's spam policies, since buying links or scaled low-value content can cost a site more visibility than any technical fix will recover. The reporting pass checks that Search Console and analytics are configured well enough that anyone can tell later whether the work worked.
How to specify an audit so quotes are comparable
Write half a page before you request quotes. State the site's page count and platform. State the question you need answered, for example why organic traffic fell in a specific month, or whether the site can support a planned expansion. State what data access you will grant, including read-only Search Console, analytics and whether log files are available. State the deliverable you expect: written findings, a prioritised action list specified clearly enough for a developer to act on, and a live debrief. State the deadline. Send that same brief to every candidate and ask each to quote against it with an hour estimate. The quotes then differ on rate and approach rather than on hidden scope, and the exercise usually reveals which candidate has done this on a site like yours before.
Questions people ask about seo audit pricing
Why do SEO audit quotes vary so much for the same site?
Because the word audit is not standardised. One quote may cover a crawler run and a summary, another a multi-week diagnostic with log file analysis, developer-ready specifications and a debrief. Quotes only become comparable once you write a brief stating scope, data access, deliverable and deadline, and send the same brief to everyone.
Is a free SEO audit worth taking?
It is a sales document, and worth reading as one. Free audits are usually automated tool output framed to justify a retainer, so read them for whether the issues are real and correctly explained rather than for a plan. If the free audit reasons well about your specific site, that is a genuine signal about the provider.
Should an audit include implementation?
Usually not in the same fee, and it is cleaner if it does not. Keeping diagnosis separate from implementation lets you take the findings to your own developers or to a different supplier. If the auditor also wants the build work, ask for the audit fee and the implementation quote separately so you can judge each on its own.
How often does a site need a full audit?
A full technical audit is worth repeating after a migration, a redesign, a platform change or an unexplained traffic drop. Between those events, ongoing monitoring in Search Console covers most of what a repeat audit would find, at a fraction of the cost.