Search Traffic Is Down. Are Contractor Leads Down Too?

A lower traffic number can point to a real problem. It can also hide a healthier mix of buyers, a seasonal slowdown, a tracking gap, fewer low value visits, or a change on one page that has little to do with the jobs your company wants. Contractors need to trace the whole path before making a big marketing decision.

Start with one question: did the loss happen before the click, after the click, or after the phone rang? Search Console, Analytics, call records, estimates, and job costing each cover a different part of that answer. One dashboard cannot replace the others.

Do not borrow a publisher benchmark

Recent traffic reports have focused on news and media sites. Chartbeat's 2026 report found weaker search referral traffic across its publisher network, but it also showed that total traffic moved far less than the search channel. That research is useful evidence for publishers. It is not a benchmark for a roofer, electrician, remodeler, or plumbing company that needs a smaller number of local buyers with a real service problem.

A publisher may earn revenue from large pageview volume. A contractor earns revenue when the right customer in the service area reaches the office, qualifies for the work, accepts an estimate, and produces a healthy job. The same traffic drop can mean very different things for those two businesses.

Trace the whole contractor funnel

The chart below is a diagnostic path, not a performance benchmark. A healthy review moves from broad visibility toward business evidence. Each step answers a different question and has a different owner.

If impressions fell, the service page may have lost visibility or demand may have changed. If clicks fell while impressions held, the search result, buyer intent, or result page may have changed. If visits held but qualified calls dropped, inspect the service page, form, phone path, coverage facts, and offer. If estimates held but booked work or margin fell, the website may not be the main problem at all.

Keep three ledgers instead of one big dashboard

The simplest useful setup is three small ledgers. They can live in a spreadsheet, reporting tool, or CRM as long as the dates, service lines, local areas, and owners line up. Do not force the totals to match exactly. The tools count different events.

Search ledger

Use Search Console for impressions, clicks, search queries, pages, devices, countries, and search types. Google Search Central, part of Alphabet (GOOGL), recommends checking a long enough date range to see seasonality and comparing the affected period with the previous period or the same period last year. Break the change down by page and query before calling it a sitewide loss.

Website ledger

Use Analytics for sessions, landing pages, phone taps, form starts, form submissions, and other useful actions. If the property sends Google's recommended lead events, the lead acquisition report can also show new, qualified, and converted leads by channel. Google explains that Search Console clicks and Analytics sessions are calculated differently, so the totals will not match exactly. Compare the trend and investigate large gaps instead of trying to make two different systems produce one number.

Office ledger

Keep the records the marketing tools cannot judge on their own: new calls, qualified inquiries, estimate requests, estimates sent, booked work, lost reasons, job value, gross margin, and service area fit. The office should note how the buyer says they found the company, but that answer is supporting evidence, not perfect attribution. A homeowner may see a truck, read reviews, ask an AI assistant, search the company name, and call from the website.

Read the pattern before the total

Four common patterns lead to four different repair jobs. Looking only at total traffic can send the team after the wrong one.

Impressions down on the priority service page

Check whether the loss is tied to the service, location, device, or a wider seasonal change. Review indexing, crawl access, recent page edits, internal links, local coverage, and whether the page still answers the work buyers are searching for. Do not rewrite every page because one service lane changed.

Impressions steady, clicks down

The page may still appear while fewer people choose it. Inspect the visible title and description, the search results around it, queries tied to the company name, other discovery queries, and whether the result still matches the job. Google says a small position change can create a noticeable click change even when impressions remain steady.

Visits down, qualified calls steady

This may be a smaller but more useful audience. Confirm that the office is recording sources consistently and that important form and phone actions still fire. If qualified inquiries, estimates, booked jobs, and margin remain healthy, do not chase empty pageviews to make the chart look better.

Traffic steady, good jobs down

Inspect the buyer handoff. The service page may attract research traffic but fail to explain scope, coverage, proof, estimate conditions, response time, or the right contact path. The office may also be slow to return calls or may be qualifying against old service facts. More traffic will not fix a broken handoff.

Use this diagnostic table before you change the site

Choose the row that matches the evidence. Assign the first check to one owner and write down what would confirm or reject the suspected cause.

A useful diagnosis can end with no website change. If seasonality explains the drop and the company is still booking the intended work at a healthy margin, the right move may be to keep monitoring. If a technical fault or broken form is confirmed, fix it quickly and record the date so the team can judge recovery.

AI search makes attribution harder, not less important

Google says links from AI Overviews and AI Mode are included in overall Search Console web traffic. It also recommends using Analytics to review conversions and time on site. That means a contractor should not invent a clean AI search lead number when the available data does not support one.

Keep a dated prompt and citation log as an observation layer. Compare it with Search Console visibility, tracked referrals when they are available, branded search changes, landing page actions, and office outcomes. An AI answer that mentions the company may help a buyer learn the name and search for it later. It may also create no business result. Both are possible, so report the observation and the outcome separately.

Search Console's branded query filter can help eligible sites compare people already looking for the company with people discovering it through other queries. Google notes that the classification can be imperfect and that the filter does not affect ranking. Use it as one clue, not a verdict.

Use GEO Smith to find the proof gap behind the traffic line

GEO Smith can help inspect how contractor services, locations, questions, and proof appear across AI search answers. Pair that visibility check with the three ledgers. The point is to find the weak handoff: a service page missing a clear answer, a local claim without proof, an important project trapped in a camera roll, or a buyer path that loses the call before the estimator sees it.

Connect local visibility, service page proof, buyer actions, and office outcomes before deciding what to repair.

Run a 30 minute monthly traffic and lead review

Bring the person who can read Search Console, the person who owns the website, and the person who knows which calls became estimates and jobs. For a small company, that may be one owner wearing three hats. Keep the evidence separate anyway.

End the meeting with one dated decision. For example: repair the heat pump service form, verify call tracking, and review qualified inquiries again on November 7. That is an operating plan. Increase traffic is not.

Follow the GangBoxAI guide that matches the break

A traffic drop can expose a search problem, a proof problem, or an office problem. Use the guide that repairs the confirmed break.

• Build the weekly view around one service page, one area, buyer actions, and office outcomes.
• Separate AI visibility, referred visits, qualified leads, estimates, and booked work.
• Keep crawler activity and technical discovery out of the lead count.
• Set continue, repair, and stop conditions before funding more content.
• Repair the service facts, coverage, proof, estimate boundaries, and next step on the landing page.
• Check whether a ready buyer can confirm fit and reach the right office path.
• See how public proof supports the contractor recommendation layer beyond one click.
• Connect SEO, direct answers, AI visibility, proof, and measurement without chasing one channel metric.
• Use GEO Smith to inspect AI search visibility and locate the next supported proof fix.

Sources

• Chartbeat: Navigating the New Traffic Landscape
• Google Search Central: debugging drops in Google Search traffic
• Google Search Central: using Search Console and Google Analytics data for SEO
• Google Analytics Help: lead acquisition report
• Google Search Central: AI features and your website
• Google Search Central: branded queries filter in Search Console