Asking for a quote for an SEO audit is like asking for a tailor-made suit: two tailors can give you very different figures and both can be right, because they are measuring different things. The problem is that most of the proposals you will receive do not break down what they include. This checklist is designed so that you can evaluate a freelance SEO audit quote point by point before signing, and so that you can detect when the price responds to real work and when it responds to a template filled in in twenty minutes.
Before looking at the figure: what the quote must specify
A serious SEO audit quote does not start with the number, it starts with the scope. If the proposal you receive only says «complete SEO audit» with an amount, you already have a signal. Use this list to verify that the document covers the following:
- Number of URLs analyzed or sampling criteria. An 80-page site and a 40,000-page site are not audited the same way, and the price should explicitly reflect that.
- Access the freelancer needs. Search Console, Analytics, CMS, server or logs. If they do not ask for them, either they are not going to look at real data or they are going to audit «blind».
- Declared technical depth. Crawling with their own crawler? Server log review? JavaScript rendering tests? Each layer adds hours.
- Concrete deliverables. Document, spreadsheet of prioritized issues, handover video, Q&A session. A 90-page PDF that nobody reads is not the same as a sheet with 40 actions ordered by impact.
- What is left out. Implementation, copywriting, link building and subsequent follow-up are usually excluded. Having it stated in writing avoids misunderstandings.
- Delivery deadline and estimated hours. Although hours are not always broken down, a range helps to compare proposals.
Checklist of line items that justify the price
These are the tasks that really consume time in an audit and that should appear, at least in part, in any proposal above the lowest range. Use it as a checklist: tick the ones that are included and ask about the ones that are missing.
1. Crawling and indexing diagnosis
- Review of robots.txt, meta robots tags and accidental noindex directives.
- Coverage analysis in Search Console: excluded pages, reasons and trend over time.
- Detection of cannibalizations and of URL parameters that generate duplicates.
- Checking sitemaps: whether they are up to date, whether they include URLs that should not be there, whether they exclude the ones that should.
- Crawl budget (on large sites) with log data if the client can provide it.
2. Architecture and internal linking
- Click depth from the home page to the pages that convert.
- Detection of orphan pages and broken internal links.
- Evaluation of the category structure and of whether the silos respond to search intent.
3. On-page and content
- Review of titles, metas and heading hierarchy in the key templates, not page by page.
- Detection of thin or duplicate content by template.
- Correspondence between search intent and page type (product, category, article).
4. Performance and Core Web Vitals
- Field data (CrUX or Search Console) versus lab data. A report that only shows PageSpeed Insights is half done.
- Identification of the three or four elements that cause the high LCP, not a list of 60 generic recommendations.
5. Structured data and rich results
- Validation of existing schema and detection of missing types according to the business.
- Checking that rich results actually appear in the SERP, not only that the code validates.
6. Link profile and authority
- Analysis of toxic links or anomalous patterns, with judgment. It is not enough to export a tool’s list and paint red everything with a low DR.
- Comparison with two or three real competitors in the sector, not with irrelevant giants.
Price ranges and what to expect in each tier
Amounts vary greatly by market, country and project size, so take these ranges as a general industry guide, not as an official rate. What matters is the relationship between price and declared volume of work.
| Tier | What it usually includes | Red flag |
|---|---|---|
| Low-cost | Review with an automated tool, report of basic technical issues, review of titles and metas in a sample | 100-page report generated by software with no prioritization or business context |
| Mid-range | Full crawl, Search Console analysis, on-page review of templates, architecture proposal and prioritization | Does not ask for access to Search Console or the CMS |
| High-end | All of the above plus server logs, rendering analysis, link review with editorial judgment, handover session and phased roadmap | Promises «guaranteed results» or specific positions after the audit |
A detail that almost nobody asks about and that changes the price: whether the website is in JavaScript and the content is rendered on the client side. Auditing an SPA requires checking what the crawler sees versus what the user sees, and that can double the hours compared to a plain HTML site. If your project is like that and the quote does not mention it, either the freelancer has not detected it or is ignoring it.
Judgment errors I have seen in real quotes
There is a pattern that repeats itself when someone asks for their first audit: comparing proposals only by the final number. A typical case is receiving three quotes, choosing the cheapest and discovering at delivery that the report lists 300 404 errors without saying which ones matter, without ordering by impact and without distinguishing between a 404 on a page with traffic and one on an internal resource. The document is technically correct and practically useless. An audit is not paid for counting errors, it is paid for deciding which ones to fix first.
Another frequent error: hiring the audit and not hiring the implementation or the handover. Without a session where the freelancer explains to the technical team what each issue means and in what order to tackle them, many audits end up in a shared folder that nobody opens. Always ask whether the price includes that handover session; if not, negotiate it.
Questions you should ask before accepting the price
- How many hours do you estimate and what part is automated analysis versus manual review?
- What tools do you use for crawling and what limitations do they have on my type of site?
- Have you audited a project with this platform or CMS before? If not, how do you plan to cover that learning curve?
- What happens if during the audit we find a problem that requires urgent development?
- Does the report include a roadmap with estimated effort per task?
- Do you offer subsequent review of the implementations or is that billed separately?
What an audit does not solve (and it is worth knowing)
An SEO audit detects problems and proposes solutions, but it does not generate traffic on its own. If the business has no search demand for its services, if the website competes in a saturated niche with a minimal budget or if the internal team cannot implement the changes, the best report in the world will not move the rankings. There are also limits in measurement: Search Console data has delays and privacy thresholds that hide low-volume queries, and third-party tools estimate traffic with models, not with certainties. Any freelancer who presents those estimates as exact data is oversimplifying.
And a warning about guarantees: nobody serious can promise you specific positions or a percentage of growth after an audit. What can be committed to is the scope of the work, the delivery deadline and the quality of the deliverable. Evaluate the quote on that, not on promises.
How to use this checklist in practice
Ask for the proposals in writing, sit down with this list and tick what each one includes. If two quotes differ greatly in price, compare line item by line item: one is probably auditing the surface and the other the complete system. And if the most expensive one does not detail more work, ask why. A fair freelance SEO audit price is one that you can break down into concrete tasks, with reasonable hours and verifiable deliverables. Anything that does not fit that logic deserves, at the very least, a second question before signing.