Audit a General Contractor Website Before You Add More SEO Spend

This audit is for general contractors that already have a website and need to determine why search visibility, qualified enquiries, or both are weaker than expected. It is also useful when you need to verify whether existing SEO work is holding up before approving more spend. The objective is diagnosis: identify what is observable, decide how serious it is, assign ownership, fix the root cause, and verify the result.

Start with evidence you can inspect directly. Google Search Console can show indexing and query data, browser testing can expose broken mobile experiences, and page-level review can reveal weak service coverage. Several first-pass checks can be completed in under 30 minutes, while backlink data may require a specialist tool if you need a fuller comparison.

Run this audit when the evidence gives you a reason:

• Relevant organic traffic has dropped or remained flat over the past 90 days and you need to isolate whether the cause is technical, content-related, local, competitive, or measurement-related.
• A redesigned or migrated site may have changed URLs, templates, internal links, metadata, or indexability.
• The company added services or genuine service locations and the public site no longer reflects current operations.
• An agency or internal team is producing activity reports but the business cannot connect that work to observable improvements in crawl health, search coverage, or qualified enquiries.
• Competitors are becoming more visible for priority services and you need a page-by-page and signal-by-signal comparison rather than a generic strategy discussion.

If you are still building the initial foundation, use the contractor setup checklist first. This audit assumes there is an existing site, profile history, and search evidence to inspect. Work through the stages in order so later recommendations are not built on unresolved foundation problems.

Audit objective: prove that important contractor pages can be discovered, rendered, indexed where appropriate, and used on the devices customers actually use. Evidence: Search Console indexing reports, live URL inspection, browser testing, crawl output, redirect behavior, and page templates. Severity: critical when revenue-driving pages are unavailable or excluded unintentionally; high when recurring template faults affect many pages; lower when the issue is isolated and does not block discovery or use. Owner: developer or technical site owner, with SEO defining the affected URLs and expected behavior. Validation: rerun the same checks after deployment and confirm that the corrected URLs return the intended status, render correctly, and can be indexed when appropriate.

What to Check and How to Validate It

• Page performance: Test the homepage and representative service pages with PageSpeed Insights and real-device checks. If an internal benchmark uses a mobile score above 70 and flags scores below 50 for investigation, treat those values as operating thresholds rather than Google ranking guarantees. Diagnose the actual cause, such as oversized images, unnecessary scripts, layout instability, or slow server response, then retest the same templates after changes.
• Mobile usability: Open key pages on common viewport sizes and complete the actions a homeowner would take: read the service summary, view project evidence, tap the phone link, submit the form, and navigate back to another service. Record any obstruction as evidence. The corrective action belongs to design or development, and validation means repeating the same journey after the fix.
• Indexing and crawlability: Use Search Console and live URL inspection to identify important pages that are excluded unexpectedly, blocked, canonicalized elsewhere, or returning the wrong response. Do not treat every excluded URL as an error; classify whether the exclusion matches the intended indexation plan.
• HTTPS and mixed content: Verify that important pages and assets load securely and that redirects consistently resolve to the preferred secure version. Correct insecure asset calls or conflicting protocol behavior at the template, application, or server layer, then validate across representative pages.
• Broken internal links: Crawl the site with an appropriate tool. A free crawler limit of 500 URLs can be enough for a small contractor site. Prioritize internal 404 destinations that sit in navigation, service hubs, project pages, or high-traffic templates. Fix the source link or restore the intended destination, then rerun the crawl and confirm those 404 references are gone.
• Duplicate URL handling: Check preferred host, trailing-slash behavior, parameters, redirects, and canonicals. If multiple URL variants expose substantially the same page, define the intended version and align internal links, redirects, and canonical signals. Validation is not merely seeing a canonical tag; it is confirming that the site's internal architecture consistently points to the preferred URL.

A technical finding is complete only when the audit records affected URLs, observable evidence, business impact, severity, owner, corrective action, and the exact retest. Avoid repairing content first when a template-level technical defect would continue to undermine every page built on that template.

Audit objective: determine whether each important contractor page has a clear search purpose, sufficient decision-useful information, and a distinct role in the site architecture. Evidence: page copy, title and heading structure, internal links, Search Console queries, landing-page traffic, project evidence, and overlap between competing URLs. Severity: high when a priority service has no useful dedicated page or multiple pages compete for the same intent; medium when metadata or supporting sections are weak; lower when the problem is cosmetic. Owner: SEO or content lead for page strategy, with operations or estimating validating technical and commercial claims. Validation: compare the revised page against the mapped intent, confirm internal links point to the intended URL, and monitor whether relevant query coverage improves without creating new cannibalization.

What to Check and How to Validate It

• Service-page separation: Confirm that major services with materially different customer intent have their own useful pages rather than being compressed into a generic list. A dedicated page should explain scope, project fit, process, evidence, and next steps without duplicating another service page.
• Title tags and descriptions: Inspect the rendered metadata and page source. The title should identify the page topic clearly and naturally. Do not force a city into every title when location is not central to the page's intent. Rewrite vague or duplicated metadata, then validate that the correct title is rendered after deployment.
• H1 structure: Review the visible primary heading and source markup. Use one clear H1 when the template supports that pattern, and avoid treating heading count as a magical ranking rule. A missing H1 or a repeated H1 can indicate a template or hierarchy problem worth reviewing, but the validation question is whether the page has an obvious primary topic and a coherent structure.
• Content depth: A page under 300 words is not automatically weak, and a long page is not automatically useful. Audit whether the page answers the real decisions a homeowner or project owner needs to make, including scope, fit, process, limitations, evidence, and contact path. Add information because it closes a decision gap, not merely to increase length.
• Intent overlap: Compare pages targeting similar services and locations. If several URLs answer the same query with substantially similar information, decide whether to consolidate, differentiate, or change internal linking so the intended page is unambiguous.
• Image accessibility and context: Project images should use meaningful alt text when an image conveys relevant information. Avoid empty descriptive opportunities and opaque filenames such as IMG_4821.jpg in asset management, but do not present filenames or hidden metadata as undocumented ranking shortcuts.

Score each priority page on evidence, not aesthetics. The core question is whether a prospective client can understand the service, see why the contractor may be a fit, verify relevant proof, and take the next step without encountering duplicated or contradictory information.

Audit objective: verify that the contractor's website and local business presence describe the same real company, services, and operating footprint. Evidence: the live Google Business Profile, website contact information, category and service settings, important directory listings, customer feedback, and genuine location pages. Severity: critical when the profile is inaccessible, suspended, or represents incorrect business identity; high when contact or location data conflicts across prominent sources; medium when service coverage or page detail is incomplete. Owner: business owner or profile administrator for identity and access, with marketing maintaining public information. Validation: compare the live profile and key listings against an internal source of truth after corrections, then verify that customers encounter consistent information.

What to Check

Google Business Profile

• Confirm the profile is claimed, accessible to the correct owner, and represents the real business.
• Compare the business name, address where applicable, phone number, hours, website, and services with current operations and the website.
• Review the primary category for accuracy rather than choosing a broader or unrelated category simply to chase visibility.
• If an internal audit uses at least 10 recent reviews with an average above 4.0 as a comparison point, label that as an internal benchmark requiring source reconciliation, not a Google threshold. More important, verify that review requests are made consistently to eligible customers without incentives or gating.
• Check that service-area settings reflect places the contractor genuinely serves and do not imply locations the business does not operate in.

Business Data Consistency

Compare the contractor's core business information across the website, profile, and important third-party listings. Focus on discrepancies that can confuse customers or materially misstate the business. Minor formatting variations are not automatically a ranking defect. Record the source, incorrect value, correct value, owner, and date corrected so the same error does not reappear later.

Service-Area Pages

Create or retain a dedicated location page only when the contractor genuinely serves that market and can provide useful location-specific information. Do not duplicate one template across nominal areas and change only the place name. During the audit, flag pages that lack distinct local value, consolidate where appropriate, and validate that retained pages accurately represent current service coverage.

For deeper profile-level checks, use the dedicated Google Business Profile guidance in this cluster. The audit stage should end with a clean record of what is accurate, what is unsupported, what changed, who owns each correction, and how the live result will be verified.

Audit objective: determine whether the contractor has enough legitimate external evidence to compete for the searches that matter, without confusing third-party SEO scores with Google metrics. Evidence: referring domains, link destinations, source relevance, mentions, competitor link patterns, and proprietary comparison metrics where useful. Severity: high when priority pages have little credible external support relative to competitors; critical only when manipulative or harmful link activity creates a clear risk; medium when the main issue is a gradual competitive gap. Owner: SEO or digital PR lead, with the business approving relationships and claims. Validation: confirm that new references are live, relevant, correctly attributed, and connected to pages that deserve support rather than measuring success by raw volume alone.

What to Check and How to Validate It

Third-party authority scores can help organize research, but they are not Google metrics and should not be presented as direct ranking inputs. If a comparison shows one contractor site at a score of 5 and another at 30, treat that as a tool-specific indicator that warrants deeper link inspection, not proof that the score itself causes the ranking difference.

• Referring domains: inspect the number and quality of distinct sites linking to the contractor. If an existing internal benchmark cites 20-40 referring domains as a common range for visible local sites, preserve it as an observational planning reference that still needs source reconciliation. Compare the actual sources, not just the count.
• Source quality and relevance: identify links from legitimate local publications, trade organizations, suppliers, partners, project references, or other relevant sites. Separate those from low-quality directories, scraped pages, and unrelated networks. A smaller set of credible references can be more useful than a larger collection of weak ones.
• Link destination: check whether useful links point only to the homepage or also support relevant service, project, or resource pages. Corrective work should strengthen pages that merit citation instead of forcing anchors toward commercial keywords.
• Anchor patterns: look for unnatural repetition or obviously manipulated commercial anchors. Natural profiles usually contain a mix of brand, URL, topical, and contextual wording. If a pattern looks engineered, review acquisition history before adding more links.
• Competitor comparison: compare the backlink profiles of the most relevant visible competitors for the same service and market. Do not assume the top 3 or 5 results are comparable if they are directories, marketplaces, or businesses with different models. Use the comparison to identify legitimate source types and content gaps, not to copy links mechanically.

The corrective action may be digital PR, supplier or association references, reclaiming legitimate unlinked mentions, improving assets that deserve citation, or simply stopping low-quality acquisition. The validation step is to verify the source and context of each earned reference and then observe whether the supported pages gain relevant visibility over time.

After the audit, convert findings into a prioritized remediation queue. A useful scorecard records evidence, affected pages or profiles, severity, owner, corrective action, dependency, and validation method. Do not collapse the result into a single vanity grade if that hides the difference between a blocked service page and a minor metadata issue.

Self-Score the Audit Stages

• Technical health: pass when priority pages can be crawled, rendered, loaded securely, and indexed as intended. Needs work when material crawl, redirect, mobile, or template problems remain unresolved.
• On-page content: pass when priority services have clear, differentiated pages that answer real customer questions and fit the site architecture. Needs work when pages are generic, duplicated, contradictory, or poorly mapped to search intent.
• Local signals: pass when the profile is accessible, business data is accurate, important listings agree on core facts, and location pages represent genuine operating markets. Needs work when identity, contact information, eligibility, or location coverage is misleading or inconsistent.
• Authority: if an internal scorecard uses 20+ quality referring domains and a competitive gap under 15 proprietary DR points as a reference, keep those figures labeled as internal comparison criteria, not Google thresholds. A site with a weak set of low-quality referring domains may still have a meaningful authority gap if relevant competitors have stronger legitimate references.

When to Handle It Yourself

Handle isolated issues internally when the evidence is clear, the corrective action is low risk, and the team has the access needed to validate the result. Examples include correcting a stale directory listing, fixing a broken internal link, rewriting weak metadata, or updating a service description. Use the General Contractor SEO Checklist to turn straightforward findings into assigned tasks.

When to Hire a Professional

Escalate when several audit stages are failing at once, when a migration or template problem affects many pages, when access or server work is required, when traffic losses cannot be explained from available evidence, or when authority work requires sustained outreach and editorial judgment. The professional's job should be to diagnose the root cause, prioritize by impact and dependency, document the work, and define how success will be checked.

A deeper engagement can add full crawl data, query and page segmentation, competitor analysis, link review, local profile checks, and a remediation backlog. If that level of diagnosis is needed, contractor SEO experts who can diagnose your site can be evaluated against the same evidence-first standard used in this guide.