How to run a local SEO audit for a contractor
Verify business identity, service and area pages, contact paths, crawl signals, local proof, and conversion tracking. Rank defects by customer and search impact.
Written for a contractor, agency, or freelancer reviewing a local-service website before investing in new pages or listings.
Key facts
- A local audit should connect search visibility with the customer's booking decision.
- Business names, contact details, service areas, and public profiles should describe the same entity.
- Technical access, useful service copy, local proof, and working contact paths require separate checks.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
The direct answer
Start with the public business name, contact details, service area, primary categories, and booking route. Check whether the homepage and service pages state who serves which jobs and locations. Verify crawl access, canonicals, titles, headings, organization data, links, and mobile forms. Review local projects, credentials, reviews, and policies for support. Rank fixes that block contact or confuse business identity before publishing new location content. The finished work should let a reader or reviewer identify the subject, the intended result, the evidence behind the recommendation, and the next action without reconstructing your reasoning. Keep material conditions in the same passage as the claim they limit. Use the canonical public page as the source of truth, since search engines and answer systems retrieve pages rather than private briefs. Google describes useful, reliable, people-first content and ordinary search eligibility as the foundation for both search results and its AI features. No heading pattern or schema type can compensate for a page that gives a vague answer, hides its evidence, or serves a different intent from its title. Complete the task for one named reader first, then check how the result appears to crawlers and extraction tools.
- A local audit should connect search visibility with the customer's booking decision.
- Business names, contact details, service areas, and public profiles should describe the same entity.
- Technical access, useful service copy, local proof, and working contact paths require separate checks.
Prepare the page and evidence before editing
Collect the business's legal and public names, phone numbers, address or service-area model, hours, core services, served locations, credentials, profiles, and lead destinations. Choose the homepage, two main services, and one location page as the first sample. Save a baseline before you change anything: the public URL, response status, canonical, visible title, main heading, opening answer, source links, and the date you checked them. Record the target question in the reader's words and write one sentence describing the decision the page supports. This baseline prevents a common measurement error where several edits ship together and nobody can tell which one improved the result. It also gives editors a compact source ledger. A reviewer can compare each material statement with the cited page, its jurisdiction or product version, and its checked date. If the task affects a generated template, inspect several representative URLs rather than assuming one record proves the template works for every content shape.
- Call or submit the public contact path and record the result.
- Compare business identity across page copy, metadata, organization markup, and linked profiles.
- Gather real project and qualification records for content review.
Complete the process in five controlled steps
Work through the five steps in order and keep one output from each step. The order protects you from polishing copy while a crawl, canonical, intent, or evidence problem still blocks the page. Each output should be small enough for another person to verify from the public URL. Use plain labels and stable entity names throughout the page. When a changing fact controls the answer, cite the primary source beside that fact and include the relevant date or version. After each step, compare the output with the primary question. Remove any section that serves a different reader decision, and link to a separate guide when the adjacent task deserves its own page. This creates a focused answer instead of a broad page assembled from loosely related keywords.
- 1. Verify identity: Compare the business name, contact details, service area, and profile links across public surfaces. Evidence of completion: Customers encounter one consistent entity.
- 2. Verify service fit: Read core pages for job scope, exclusions, location, process, price factors, and next action. Evidence of completion: Each page qualifies a specific customer need.
- 3. Verify access: Check response, robots, canonical, sitemap, mobile rendering, and crawlable navigation. Evidence of completion: The intended canonical pages are available to users and crawlers.
- 4. Verify proof: Review projects, reviews, licences, insurance, warranties, and author or business ownership. Evidence of completion: Trust claims have names, context, dates, and records.
- 5. Verify conversion: Test phone, form, booking, analytics, and confirmation on representative devices. Evidence of completion: A qualified visitor can complete the promised contact action.
A worked example
A plumber's site lists two phone numbers, uses a former trading name in schema, and sends mobile quote forms to an unmonitored inbox. Its pages are indexable, but the drain page serves five cities with no service boundary or project detail. The audit ranks the broken lead path first, entity cleanup second, and service-page evidence third. Creating ten city pages does not enter the plan. The owner fixes the customer path and identity before expanding content. Treat the example as a model of the reasoning, not as a universal benchmark. The useful part is the chain from question to evidence to action. Preserve the exact entity names, scope, and conditions that a reader would need if an answer engine quoted the passage outside the page. If a number comes from a report, state the reporting window. If a result comes from a test, state the URL type, device or crawler, and date. A compact example earns its space when it helps the reader make the same decision on another page. Remove invented precision, anonymous authority, and conclusions that reach beyond the recorded evidence.
- A broken form can waste current demand before ranking work begins.
- Entity consistency supports both trust and technical interpretation.
- More local URLs cannot repair missing service evidence.
Avoid the mistakes that weaken the result
Local audits become listing inventories or score reports when reviewers ignore the website's service and booking experience. The business needs a ranked repair list tied to real customers. Fix the first mistake that changes eligibility or meaning before editing smaller presentation details. Keep source boundaries visible: one citation should support the nearby claim, while a separate claim should receive its own source. Do not repeat the target phrase to manufacture relevance. Search systems can use titles, headings, visible text, links, structured data, and other signals, so those elements should agree on the subject without copying one sentence across the page. Check the public result after deployment because a correct content record can still produce the wrong page through caching, layout inheritance, JavaScript failure, or a stale build.
- Counting directory mentions without checking accuracy hides identity conflicts. Correction: Verify the public entity and fix owned sources first.
- Auditing desktop pages alone misses mobile contact failures. Correction: Complete calls and forms on a phone.
- Recommending content volume before fixing proof creates weak pages. Correction: Use documented service facts and projects to set the publishing pace.
Verify the result and choose the next action
Retest each priority defect on the public site, then track qualified calls, forms, service and area fit, and landing pages. Monitor crawl and query evidence for core services. Keep business-detail changes in a dated record. Use a fixed observation window and compare like with like. Record the query set, country, device, page version, and publication or change date. Search impressions can show discovery and query matching; clicks and useful sessions show whether the result attracted the intended reader. Observed AI citations add a separate retrieval signal, but a citation count does not prove traffic or revenue. Review the cited passage when you can and check whether the answer preserved its subject, scope, conditions, and source. Keep the page stable long enough to collect evidence unless you find a factual error, broken route, security problem, or misleading claim. The next edit should respond to the strongest observed failure instead of a generic scoring recommendation.
- Require working phone and form paths on representative devices.
- Re-crawl the sample pages after identity and access fixes.
- Review lead quality with the dispatcher or estimator.
Put it to work
Find the highest-impact fix on your site.
Inspect business identity, services, local proof, contact paths, and search signals.
Run the contractor auditSources
- 1.Google Search Central: SEO Starter GuideChecked 2026-07-26
- 2.Google Search Central: Creating helpful, reliable, people-first contentChecked 2026-07-26
- 3.Google Search Central: Organization structured dataChecked 2026-07-26