An SEO audit should tell you what may prevent the right people from finding your website, which problems deserve attention first, and how to verify the fixes. Ask for a documented scope, page-level evidence, a prioritized action plan, and a clear handoff. A dashboard score can help organize the discussion. It cannot replace those deliverables.
If you are buying SEO services, define what an acceptable audit looks like before you approve the proposal. That makes it easier to compare providers and harder for a long report to stand in for useful work.
Start with the business question and audit scope
Give the auditor one concrete goal: help suitable customers discover a service, understand whether it fits, and make an inquiry. Name the services and locations that matter. Also identify work you do not offer, pages you plan to retire, and any upcoming website changes.
Then agree on the boundaries. A small brochure website, an online store, and a site with thousands of location pages need different investigations. There is no sensible universal promise that every audit will examine every possible issue.
Ask the proposal to specify:
- The domains, subdomains, languages, and page types included.
- Whether the auditor will inspect the entire site or a documented sample.
- Which data sources they can access and which conclusions those sources support.
- Whether local listings, conversion tracking, accessibility, or backlink review are included.
- Whether the price covers diagnosis, implementation, or a later verification pass.
For example, “review the public website and Search Console data” does not automatically include fixing the booking system or auditing every third-party integration. Put those distinctions in writing.
Agree on the subjects the audit will cover
For a typical business website, ask how the review will address the following areas. The depth and relevance of each depend on the site and the agreed engagement:
- Crawling and indexing: whether search engines can reach important pages and whether indexing instructions match your intentions.
- Site structure and internal links: whether important services are easy to find and related pages connect sensibly.
- Page content and search intent: whether each page answers a distinct customer question and accurately describes the service.
- Mobile usability and performance: whether customers can read, navigate, and complete key actions on their devices.
- Local presence or backlinks, where relevant: what will be reviewed, why it matters for this business, and what remains outside scope.
The five deliverables to request
1. A baseline with its limitations
The report should identify the period studied, the pages reviewed, the tools used, and any missing access. Ask the auditor to separate observed results from estimates.
Google Search Console’s Performance report provides search metrics such as clicks, impressions, click-through rate, and average position. Those describe search visibility. They do not by themselves tell you which inquiries became qualified opportunities. Agree on how your business will connect the two, without presenting incomplete attribution as certainty.
2. Evidence tied to affected pages
Each material finding should point to an affected URL or an explicitly defined group of pages. “Improve technical SEO” is too broad to assign. “This service page declares that it should not be indexed” is something a developer can investigate.
Ask how the finding was observed, when it was checked, and whether it is confirmed or suspected. Google’s URL Inspection tool distinguishes information about the indexed version from a live test. A report should say which view supports its conclusion; a live test is not a guarantee that the page will appear in search.
3. A review of the content that serves your buyers
Technical access is only part of the job. The audit should examine whether your important pages answer the questions a prospective customer needs resolved: what you do, whom you help, where you work, what the engagement involves, and what happens next.
Ask for a proposed primary purpose for each important page. Where two pages address substantially the same question, the auditor should explain whether to keep them distinct, improve an existing page, or investigate consolidation. Similar words alone are not enough evidence to remove a page.
Google’s SEO Starter Guide emphasizes clear, useful content, sensible organization, and helping search engines access and understand pages. Use that guidance to challenge recommendations built entirely around a preferred word count or a tool’s score.
4. A prioritized work plan
Every recommended fix should include a reason for its priority, an owner or owner role, dependencies, and a way to test completion. Ask the auditor to distinguish urgent access problems from improvements worth testing later.
A priority label should be explainable. A blocked core service page may deserve immediate investigation. Rewriting an already clear heading may be lower priority. Neither example proves a particular ranking outcome; priority depends on the evidence and the role of that page in your business.
5. A handoff and verification session
Someone needs to turn the findings into work. Request a walkthrough in which the auditor explains the highest-priority items to the people who will make changes. Confirm who can clarify a finding later and whether checking the implemented fixes is included.
Closing a ticket should mean the agreed test passed. It should not mean that rankings immediately improved. Technical completion and subsequent search performance are different observations, often available on different timelines.
A buyer’s acceptance checklist
This is an editorial checklist you can adapt to a proposal. It is not a Google certification or a guarantee of search performance.
| Deliverable | Accept when | Ask for clarification when |
|---|---|---|
| Scope and coverage | Included pages, samples, exclusions, and missing access are named. | The report implies full coverage without explaining what was checked. |
| Findings | Material issues include affected URLs, dated evidence, and an explanation. | Recommendations consist of generic warnings or screenshots without context. |
| Content and page purpose | Recommendations reflect your actual services and distinct customer questions. | New pages are proposed only by changing a keyword or city name. |
| Priorities and ownership | The first actions have a rationale, owner, dependencies, and completion test. | Everything is marked urgent or nobody can explain what happens first. |
| Handoff and follow-up | You know who implements, who verifies, and what follow-up costs or includes. | The audit ends with a report and an undefined offer to “handle everything.” |
Download the editable SEO audit checklist (CSV). Open it in a spreadsheet, add your scope, and record the evidence provided for each deliverable.
What an actionable finding looks like
Illustrative example, not a TOG client result: a fictional service business wants its commercial maintenance page to appear in search. The auditor reports a possible indexing restriction.
- Page: the commercial maintenance service page.
- Observation: a noindex instruction is present in the inspected page response. Record the exact URL, check time, and evidence.
- Business relevance: the owner identifies this as a service customers should be able to discover.
- Decision: confirm that the restriction is accidental before changing it. Some pages are intentionally excluded.
- Owner: the website developer, with the business owner confirming publication intent.
- Acceptance test: verify the unwanted restriction is absent from the deployed page, then use appropriate inspection tools to investigate remaining eligibility issues.
- Follow-up: monitor indexing separately. Removing one restriction does not guarantee indexing or rankings.
This is useful because the team can make a decision, assign the work, and test what changed.
Separate the audit from the implementation offer
Ask for a sample finding and a sample handoff before buying. Confirm that you will receive the actual working records, not only a presentation, and agree on the format you can continue using.
Be cautious about ranking guarantees or unexplained methods. Google’s guide to hiring an SEO recommends asking about experience, methods, expectations, and reporting. It also recommends read-only Search Console access for an initial audit. Grant access appropriate to the work; implementation permissions can be considered separately.
Before committing, name the implementation owner, available capacity, and spending limit. Name who will recheck the affected pages after a material website change.
Once findings are agreed, turn them into a manageable delivery process. TOG’s workflow mapping work starts by clarifying how work moves and who owns each step. Its website and custom software work covers building tools around business needs. Those are useful conversations when the obstacle is turning a finding into an implemented change.
Your next step: send the acceptance checklist with your next audit request. Ask the provider to mark what is included, what is excluded, and what evidence you will receive. If you need help defining the website work and its handoffs, tell The Operations Guide what you are trying to improve.