Page updated October 8, 2026.
If your contractor website is not producing inquiries, find the failed step before buying another website. Check whether suitable local customers reach the right page, can understand your offer, can contact you on a phone, and receive a useful response. A visible phone button does not prove that a call connected. A tracking event does not prove that an inquiry became a job.
The checks below are KKS recommendations for diagnosing that path. Product and search guidance was checked October 8, 2026. They are not a promise of more calls, a ranking forecast, or evidence that your current provider caused a revenue loss.
Start with the evidence you already have
Compare website activity with the records your office uses to run the business. Keep the dates and definitions consistent. Look at the most recent complete reporting period and a comparable earlier period, noting seasonal changes and changes in tracking.
| Observation | What to inspect next | What it does not establish |
|---|---|---|
| Few relevant search visits | Search queries, landing pages and actual service coverage | That the design needs replacing |
| Visits but few contact actions | Mobile placement, service clarity and working links | That every visitor was a qualified buyer |
| Phone taps but few recorded calls | Dialed destination, tracking configuration and call records | That taps were completed calls |
| Calls but few estimates | Job fit, response handling and estimate process | That the website caused the sales problem |
| Estimates but few sold jobs | Matched estimate outcomes, scope, price and follow-up | That more traffic will fix the constraint |
Count unknown outcomes as unknown. If nobody records how callers found you, a blank attribution field is not proof that the website brought no work. If analytics counts the same action twice, the dashboard is not proof of demand either.
1. Check whether the right customers can find the right page
Review the pages that describe the services you want to sell in the places you actually serve. Compare those pages with the queries and landing pages in your own Search Console reporting. Separate branded searches from searches by people who do not already know your name.
Use a public search as a spot check, not a definitive ranking report. Save the query, date and location context. A result seen on one device is not a complete account of the market, and absence from that result does not diagnose a specific technical fault.
Ask your website manager to check indexability, canonical URLs, working internal links and accurate page titles before recommending more content. If a page cannot be accessed or is unintentionally excluded from indexing, resolve that specific problem first. For the broader architecture, see our contractor website design guide.
2. Test mobile usability without treating a score as a sales result
Open the homepage and the service page a prospective customer would actually visit. Can you read the service and location, find the contact action, open the menu, and reach the form without a banner covering them?
Google says Core Web Vitals are used by its ranking systems, but good scores do not guarantee top rankings. It also cautions that chasing a perfect score only for SEO may not be the best use of time.[14]
KKS recommends prioritizing a failure that prevents contact over a small laboratory-score improvement with no visible effect on the customer journey. Record performance measurements separately from inquiries. A faster page can be a useful improvement without proving that it generated an additional job.
Check mobile navigation when closed, open and closed again. Inspect sticky headers and bottom bars after scrolling. A contact button that exists in the HTML but sits behind a cookie panel has not passed a usability test.
3. Replace vague copy with answers a customer needs
A service page should help a visitor decide whether to contact you. Explain the work you perform, where you perform it, what the first appointment involves, and what information you need to assess the job. State exclusions where they prevent unsuitable inquiries.
Do not add paragraphs simply to reach a word target. Google's people-first content guidance explicitly says it has no preferred word count and asks whether content supplies original, useful information rather than merely summarizing other sources.[16]
Use real project evidence where you have authority to publish it. Describe what the images show and avoid inventing a customer, result or location. A specific explanation of how your business handles a repair request is more useful than repeating a claim about quality throughout the page.
4. Organize pages around different customer decisions
A replacement installation, a diagnostic visit and a maintenance agreement may require different explanations. Separate them when customers need materially different answers. Keep related information together when a new page would only repeat the same copy with another city or keyword.
Before adding a service-area page, establish that the company serves that place and has something useful to explain about serving it. A location label alone is not evidence of a local office, completed project or available appointment.
Preserve useful existing URLs during changes. Map the pages customers use now before consolidating or moving them. A redesign is not permission to discard a working service page or break its contact path.
5. Make business evidence clear and accurate
Review the business name, contact details, service area, project descriptions and credentials visible on the page. Check what each claim actually supports. A personal qualification is not automatically a company-wide credential; a license number should identify the relevant holder and work rather than operate as a decorative badge.
Use reviews honestly. Do not infer that a particular review count will produce a particular number of inquiries. Keep photographs connected to the correct business and project. If an appointment, warranty or financing statement has conditions, put the conditions where the reader makes the decision.
The useful question is whether a customer can understand who will do the work and what happens next. Adding more badges cannot resolve contradictory business details.
6. Make the phone path usable, then verify what it measures
For a contractor who accepts calls, KKS recommends a plainly labeled call action near the top of important service pages, with a contact alternative for visitors who cannot or do not want to speak. Keep the number discoverable without opening the mobile menu. Repeat it at a relevant decision point rather than filling the page with competing buttons.
Placement is a test, not a universal layout rule
A fixed bottom call bar can keep the action available while a visitor reads, but it can also cover content or form controls. Test the actual layout instead of assuming that a sticky bar always helps.
Check the control's clickable area, spacing, label and contrast. WCAG 2.2's Level AA target-size criterion specifies at least 24 by 24 CSS pixels, with defined exceptions including spacing and inline links. That is a minimum accessibility criterion with exceptions, not a claim that a small call button is commercially effective.[9]
Use honest action text. "Call to discuss your repair" is suitable when a person can discuss the job. Do not add "24/7," "same-day service" or "dispatch within the hour" unless the business can support that specific promise. An answering service taking a message is not the same as an available technician.
Check the number shown and the destination behind it
Have the developer inspect the telephone link as well as the number a visitor sees. Include the header, service-page buttons, footer and any mobile bar. When tracking swaps a number, verify the replacement in each relevant location.
Google's website-call tracking instructions specifically say to replace both the displayed number and the number called when a mobile link is clicked.[7] Changing the label alone is not an adequate tracking test.
Arrange an authorized test call with the person responsible for answering. Confirm the business reached, routing, voicemail behavior and any after-hours message. Inspect a desktop calling-app prompt separately from a real call on a phone. Do not place unsolicited test calls or assume that opening a dialer proves the office answered.
Keep taps, calls and jobs separate
Google Ads documentation says its mobile phone-number-click measurement tracks clicks, not actual phone calls.[6] Label that event as a phone-link click in your own reporting rather than presenting it as a booked lead.
Google also documents a different website-call tracking setup that uses forwarding numbers and a call-duration threshold.[7] A duration threshold is still not a sale. Reconcile the available call record with the customer's request and subsequent outcome.
A useful operating record distinguishes a phone tap, a recorded inbound call, an answered conversation, a qualified request, an estimate and a sold job. Not every system observes every step. Keep the missing connections visible instead of using a dashboard label to imply certainty.
Decide what happens when nobody answers
Assign responsibility for missed calls and define a response window the business can meet. Make the after-hours message match that process. If the company does not provide emergency service, say so rather than attracting urgent requests it cannot fulfill.
Offer a short request form as an alternative, and explain when someone will review it. A request is not an appointment unless the booking process actually confirms one. Our contractor form guide explains how to choose fields and check that a request reaches the receiving workflow.
7. Maintain the entire contact path
After a theme, plugin, telephone-provider or booking change, recheck the affected customer journey. Confirm that a valid request reaches the intended recipient and that the person responsible can act on it. A confirmation screen alone is not enough.
Keep backups and a recovery path for site changes. Record who owns domain, hosting, analytics and telephone accounts, and how another authorized operator can maintain them. Use website management scope to discuss continuing responsibilities rather than assuming that a launch fee covers every future change.
Choose the smallest correction that addresses the evidence
A broken telephone destination calls for a repair and verification, not automatically a rebuild. Missing service information calls for better content. A system that cannot support required ownership, maintenance or customer workflows may justify a larger migration, but document that constraint before buying it.
Estimate commercial value from your own records where possible. Distinguish additional qualified inquiries from existing inquiries, use matched inquiry-to-sale outcomes, and state the assumptions behind average job value. Gross sales are not profit. Do not treat a hypothetical revenue calculation as money already lost to competitors.
Get an independent assessment of the weak step
The KKS free contractor audit includes a manually reviewed 15-factor website and lead-path scorecard, comparison with up to three relevant local competitors, and a sequenced action plan. The published process allows a repair, management, rebuild or no-engagement recommendation.[13]
Use it when you need an outside view of where the path is failing and what to address first. A managed-website discussion should follow demonstrated fit, not a preselected conclusion that every owner needs a new site.
Frequently asked questions
Does a phone-button click prove that someone called?
No. Google Ads distinguishes mobile phone-number clicks from actual phone calls. Treat a click as an interaction and reconcile calls and customer outcomes separately.[6]
Should every contractor use a sticky call bar?
No single layout is the right answer for every site. Test whether the bar remains readable, reaches the intended number and avoids covering navigation, content or forms. Keep another contact option for visitors who cannot call.
Can tracking change the displayed number but leave the old dialing destination?
That is a configuration issue worth checking. Google's mobile website-call instructions require both the displayed number and the clicked destination to be replaced.[7]
Will a perfect speed score fix a lack of leads?
A speed score does not prove that the right visitors arrived, contacted the company or became customers. Google also says good Core Web Vitals results do not guarantee top rankings.[14]
Do I need a new website if calls are not coming through?
First establish whether relevant visitors are reaching the site and whether the contact path works. A repair can be enough for a specific fault. Consider rebuilding only when the verified constraints justify the cost and disruption.
Sources
- [6] https://support.google.com/google-ads/answer/6095878?hl=en
- [7] https://support.google.com/google-ads/answer/6095883?hl=en
- [9] https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html
- [13] https://korekomfortsolutions.com/free-contractor-audit/
- [14] https://developers.google.com/search/docs/appearance/page-experience
- [16] https://developers.google.com/search/docs/fundamentals/creating-helpful-content