SEO audit cost: how to evaluate scope and price

There is no responsible universal price for an SEO audit. Cost depends on the site and the decision the audit must support: number of distinct templates, rendering complexity, markets, business risk, data access, evidence depth, stakeholder involvement, and whether implementation or retesting is included. A five-page professional-services site and a multilingual SaaS platform should not receive the same analysis simply because both have a domain name.

That does not mean buyers must accept vague pricing. You can compare proposals by forcing every provider to declare scope, evidence, deliverables, exclusions, and handoff requirements. Price becomes interpretable once the unit of work is visible.

Start with the decision the audit needs to support

An audit purchased without a defined decision tends to become a long list of possible improvements. Write the decision in one sentence before contacting providers. Examples include:

• identify why priority service pages are not consistently discoverable;
• assess technical risk before a redesign or migration;
• consolidate overlapping content without damaging important routes;
• establish an SEO and answer-engine baseline for a new category position;
• turn known crawl warnings into an engineering-ready backlog;
• verify whether measurement supports investment in organic acquisition.

The decision changes the work. A migration-risk review may need redirect mapping, staging access, launch controls, and post-launch monitoring. A content architecture review may need stakeholder interviews, page ownership, search intent, and consolidation planning. An AEO baseline needs a disclosed prompt panel, preserved responses, source review, and careful limitations.

If you are not sure which kind of audit you need, Leaf’s combined SEO and AEO audit guide separates technical access, content quality, answer testing, and business outcomes.

Site complexity changes effort more than raw URL count

Providers often ask how many pages a site has because crawl volume affects processing and review. Raw count is only a rough proxy. A site with 20,000 consistent product URLs may be easier to diagnose at the template level than a site with 500 pages across several content systems, markets, and JavaScript states.

Scope variables that can materially change effort include:

• number of distinct page templates and content systems;
• JavaScript rendering and client-side routing;
• parameters, faceted navigation, and duplicate URL patterns;
• subdomains, documentation, help centers, or separate applications;
• countries, languages, and international targeting;
• migrations, redirects, or legacy domain history;
• access to Search Console, analytics, log files, and a staging environment;
• regulated, legal, security, or credential claims requiring owner review;
• stakeholder interviews and internal approval cycles;
• backlinks, reputation, or digital PR analysis beyond on-site work;
• implementation support and retesting.

Ask whether every URL will be reviewed or whether the provider will crawl broadly and inspect representative templates. For most patterned sites, template-based diagnosis plus exact affected URL exports is sensible. The provider should still state the sampling method and any areas excluded from manual review.

Evidence depth determines whether the report is usable

A low-effort audit may export crawler warnings and add generic recommendations. A deeper audit validates material issues, connects them to affected pages and business routes, and explains how to verify the fix. Those are different deliverables even when both are called “technical SEO audits.”

For each finding, look for:

• the observed evidence and collection date;
• the affected URL, template, or pattern;
• the intended state and why it matters;
• severity, confidence, effort, and dependencies;
• a named or suggested owner;
• an implementation note;
• a deterministic retest or a clearly labeled experiment.

Google’s official documentation illustrates why interpretation matters. Its robots.txt guidance distinguishes blocking a crawler from preventing a URL’s appearance in search. A report that calls every blocked URL “deindexed” may be quick to produce but expensive for your team to correct and reinterpret.

The same applies to performance. The Core Web Vitals documentation distinguishes user-centered metrics and data sources. A useful audit labels field data and lab diagnostics instead of presenting one test run as universal user experience.

AEO scope adds sampling and claim work, not certainty

If an audit includes answer-engine optimization, ask exactly what that means. Some providers only inspect crawler controls and page structure. Others add a prompt baseline, citations, factual accuracy, competitor sources, and recommendations. These scopes are not comparable until the components are named.

A defensible AEO component should disclose:

• answer products and interfaces tested;
• markets, language, and date;
• prompt-selection method and exact prompt count;
• neutral discovery versus branded accuracy prompts;
• repetitions, if any;
• saved answers, citations, and cited URLs;
• separate fields for mention, citation, and recommendation;
• how inaccurate claims are escalated;
• retest method and limitations.

Google says its core SEO practices apply to AI features. That is a platform fact, not a guaranteed optimization recipe. Any provider pricing “guaranteed AI rankings” is selling control it does not possess.

AEO can increase audit effort because responses must be collected and interpreted, and company claims may need cross-functional validation. It should not add a mystical premium justified only by a proprietary score.

Normalize proposals with a scope table

Send the same brief to every provider and require an included, excluded, or optional answer for each row. Add quantities rather than accepting broad labels.

Do not assign invented dollar values to missing rows. Ask the provider to revise or price options. Your team’s capacity also matters: a technically excellent report can be poor value if no one can implement it.

The hidden cost is usually ambiguity

The invoice is only one part of audit cost. Internal teams spend time granting access, explaining the business, validating claims, translating findings, creating tickets, resolving conflicts, and retesting changes. A cheap report can become expensive if each recommendation restarts discovery.

Watch for phrases such as:

• “improve content quality” with no page, audience, or missing information;
• “fix crawlability” with no directive or affected pattern;
• “add schema” with no type, visible fact, or eligibility rationale;
• “build authority” with no source gap or ethical method;
• “optimize for AI” with no prompt evidence or acceptance condition;
• “increase conversion” when analytics events were never validated.

An implementation-ready finding reduces translation work. It does not have to contain production code or final copy unless implementation is part of scope. It does need enough detail for the responsible owner to confirm the problem and estimate the change.

Fixed price, project price, or ongoing engagement?

A fixed-price audit works best when the site, templates, markets, data access, and deliverable are bounded. It gives buyers a clear fee and forces the provider to define inclusions. It works less well when discovery may reveal unknown systems or when the site is actively changing.

A custom project is more appropriate for migrations, large international estates, penalty or security-adjacent investigations, complex marketplaces, and engagements requiring many stakeholder reviews. The proposal should still state assumptions and a process for scope changes.

Ongoing support makes sense when implementation, release QA, content production, digital PR, or repeated monitoring is required. Do not pay an ongoing fee merely because answer products change. Pay for named recurring work, a cadence, ownership, and useful outputs.

Leaf’s fixed SEO and AEO audit costs $875 and is designed for established B2B sites that fit the stated boundaries. It includes a prioritized diagnostic and handoff; implementation is not included, and rankings or AI citations are not guaranteed. That is a Leaf offer fact, not an industry benchmark.

Use a total-cost decision worksheet

Before approving a proposal, estimate effort using your own internal rates and capacity. Do not borrow generic benchmarks. Complete this worksheet with team-specific numbers:

Then assess value against the decision you defined at the start. If the audit does not reduce uncertainty around that decision, its price is difficult to justify. If it prevents a high-risk launch mistake or turns months of warnings into a clear backlog, a higher fee may be rational—but that is a company-specific judgment, not a promised return.

Ask these questions before signing

A final buyer check should cover:

1. What exact properties, templates, markets, and data sources are in scope?
2. What will be sampled, and how will the sample be selected?
3. What evidence accompanies each material finding?
4. Are content, backlinks, analytics, and AEO included or excluded?
5. Which work is a verified fix versus an external-outcome experiment?
6. What access and stakeholder time must the client provide?
7. Who owns implementation, and what handoff format is delivered?
8. Is a readout or questions period included?
9. What is retested, by whom, and when?
10. What happens if discovery changes scope?

For a more granular view of the report itself, compare the proposal with Leaf’s SEO audit deliverables checklist. If you only need a first-pass homepage check, the free AEO assessment may be enough to identify the next investigation.

A fair SEO audit price is not the lowest number or the longest report. It is the cost of a clearly bounded investigation that produces evidence your team can understand, prioritize, implement, and verify.