SEO audit: how to scope, price and prioritise one

An SEO audit is one of the easiest things to buy in search marketing and one of the easiest to waste. Many audits end as a long PDF that nobody opens twice, because the document lists everything a crawler found instead of answering the question the business actually had. This guide looks at the commercial side of the work: how to scope an SEO audit so it answers a real question, what makes one quote higher than another, and how to turn findings into a ranked backlog that a development and content team can start on the following week.

What an SEO audit should deliver

A useful audit delivers three things. First, a diagnosis: which problems are holding back crawling, indexing, relevance or conversion, with evidence a developer can reproduce. Second, a priority order, so the team knows what to do first and what to ignore. Third, a realistic view of what improvement is plausible if the work is done. Google's own guidance on hiring an SEO describes an audit in similar terms: it should give you realistic estimates of improvement and of the work involved, not a list of alarming numbers.

What an audit should not be is a tool export. Automated checkers are a fine starting point, but they flag every missing alt attribute with the same urgency as a canonical tag that removes half the catalogue from the index. The value an auditor adds is judgement about which of those findings matter for this site, this market and this business model.

Scoping: decide the questions before the crawl

Scope starts with the question, not the tool. "Why did organic leads fall after the redesign?" needs a different audit from "Are we ready to launch three new language versions?" Write the question down, then choose the modules that can answer it. A typical scope is assembled from these building blocks:

• Crawl and indexing: robots rules, sitemaps, canonicals, redirects, status codes, rendering and how many of the important URLs are actually indexed.
• Site architecture and internal linking: how deep key pages sit, which templates receive links and where orphan pages hide.
• Content and intent: whether each important query has one clear page, where pages compete with each other and where content is thin or out of date.
• Performance and page experience: Core Web Vitals from field data, mobile usability and template-level causes.
• Authority and measurement: the link profile, brand signals, and whether analytics and Search Console data can be trusted for decisions.

Agree what is out of scope as clearly as what is in. If international targeting, a migration plan or structured data are excluded, say so in writing. For sites where the technical layer is the main risk, a dedicated technical SEO review usually comes first, because content work on pages that cannot be crawled or indexed is wasted effort. Also agree the sample: on a large site the auditor reviews templates and representative URLs, not every page.

What drives the price of SEO audit services

Quotes for SEO audit services vary widely, and the spread is easier to understand once you see what the hours are spent on. Five variables explain most of the difference. Size and complexity: the number of templates, languages and subdomains matters more than the raw page count. Depth: a health check of a few days is a different product from a forensic review after a traffic drop. Access: an auditor with Search Console, analytics, server logs and a staging environment works faster and finds more than one who only has a crawler. Deliverable: a spreadsheet of issues costs less than a prioritised roadmap with developer tickets and a workshop. Seniority: the person interpreting the data is the product, and experienced people cost more.

When you compare proposals, ask each provider for the same four things: the modules included, the number of days, who will do the work and a sample of a previous deliverable with client details removed. A low price with no named person and no sample is usually an automated report with a cover page. A high price is not proof of quality either; it is fair only if the days and the deliverable justify it.

Prioritising findings: impact, effort, confidence

An audit of a mid-sized site can easily produce a hundred findings. Without a ranking, teams fix whatever is easiest, which is rarely what matters. Score every finding on three dimensions. Impact: how many valuable pages or sessions does it affect, and how close is it to revenue? Effort: how many developer or editor hours, and does it need a release? Confidence: is the cause proven with data, or is it a hypothesis?

Then sort into four groups. Blockers stop pages being crawled or indexed and go first whatever the effort. Quick wins are high impact and low effort, such as fixing a broken canonical rule on one template. Projects are high impact and high effort, such as restructuring category pages, and need a business case. Housekeeping is everything else and can wait or be dropped. A good audit names the top ten actions explicitly and is honest that the remaining ninety may never be worth doing.

From audit to backlog: the hand-over

The audit is finished when the work is scheduled, not when the document is sent. Each priority finding should become a ticket with the affected URLs or template, the evidence, the expected behaviour and an acceptance test. Hold a walk-through with developers and editors so that questions surface before the sprint, and agree one owner on the client side. Set a review date, typically after the first fixes are live and recrawled, to check that the changes were implemented as specified and to re-measure the indicators the audit used.

Red flags when you audit SEO providers

Be careful with a free audit that arrives unrequested and reports dozens of critical errors: its purpose is to sell, not to diagnose. Be equally careful with anyone who promises a fixed position in search results as the outcome of an audit; no auditor controls how search engines rank pages, and a serious one will talk about plausible ranges and conditions instead. Ask for read-only access arrangements, a clear explanation of every recommendation and references you can call. If a recommendation cannot be explained in plain language or checked against official search engine documentation, do not implement it.

If you want to see how an audit fits into a wider programme of technical, content and measurement work, our services overview shows how the pieces connect. We scope every audit around a written question and deliver a ranked backlog, because a finding that is never fixed has no value.

Sources

• Do you need an SEO? — Google Search Central
• SEO Starter Guide — Google Search Central