Client case study · Foundation / basement services · New Hampshire
Google organic clicks rose 140% year over year.
From June 3 through August 21, 2026, 603 Basement Solutions recorded 1,060 organic web clicks, compared with 442 during the same dates in 2025. Search impressions rose 135% over the same year-over-year window.
Visible non-brand query clicks and GA4 Organic Search sessions also increased across the preceding equal 80-day comparison. The measurements are associated with the engagement window, not proof that one tactic caused every increment.
442 to 1,060Organic clicks, year over yearGoogle Search Console · web search June 3-August 21, 2025 vs June 3-August 21, 2026
47,312 to 111,119Search impressions, year over yearGoogle Search Console · web search June 3-August 21, 2025 vs June 3-August 21, 2026
53 to 81Visible non-brand query clicksGoogle Search Console · visible query dimension Preceding equal 80-day period vs June 3-August 21, 2026
3,268 to 4,639Organic website sessionsGoogle Analytics 4 · Organic Search Preceding equal 80-day period vs June 3-August 21, 2026
DemandSearch, local and AI discovery→
CaptureCalls, forms, estimates and follow-up→
OperateSoftware, data and accountable workflows→
CompoundBrands, locations and acquisitions
How demand moves into follow-up, delivery and repeatable operations.
The business, and where it started
A basement and foundation contractor working across three states.
603 Basement Solutions sells basement waterproofing, crawl-space work and structural foundation repair to homeowners across New Hampshire, Maine and Massachusetts. It is a local-service business: the work is sold by inspection, the demand is seasonal, and the buying decision starts with a problem a homeowner can see.
Caldrin started on June 1, 2026. The headline Search comparison uses the same June 3 to August 21 dates in 2025 and 2026. Visible non-brand queries and GA4 use the preceding equal 80-day period. Those windows answer different questions and stay separate.
Baseline windows match the comparison windows exactly. Where a window is partial, it says so.
Observable at the start
June 2026
Google Search clicks
442
Google Search impressions
47,312
Clicks from visible non-brand queries
53
GA4 Organic Search sessions
3,268
Q&A Search impressions
No rows surfaced
The measured scoreboardfour evidence lines, kept separate
Organic clicks, year over year+140%
442 to 1,060
Google Search Console · web search June 3-August 21, 2025 vs June 3-August 21, 2026
Search impressions, year over year+135%
47,312 to 111,119
Google Search Console · web search June 3-August 21, 2025 vs June 3-August 21, 2026
Visible non-brand query clicks+53%
53 to 81
Google Search Console · visible query dimension Preceding equal 80-day period vs June 3-August 21, 2026
Organic website sessions+42%
3,268 to 4,639
Google Analytics 4 · Organic Search Preceding equal 80-day period vs June 3-August 21, 2026
Supporting evidence
Before
After
Change
Source / window
GA4 Organic Search engaged sessions
1,883
2,764
+46.8%
Google Analytics 4 · Organic Search · Preceding equal 80-day period vs June 3-August 21, 2026
Q&A Search impressions
No rows surfaced
4,662
New visibility
Google Search Console · Search Appearance export · June 2026 vs August 1-26, 2026
Local URLs surfacing
69
120
+51
Protected local-inventory Search Console analysis · June 2026 vs August 1-26, 2026
Weighted local position
25.97
18.25
7.72 positions better
Protected local-inventory Search Console analysis · June 2026 vs August 1-26, 2026
Eligible inventory also grew, from 178 URLs to 228. A percentage across a changed denominator would compare two different things, so the absolute move is shown instead.
What changed in Search
The measurements moved across more than one Search surface.
Visibility expanded across commercial decision content, Answer-style results, local pages and structural/Foundation topics. The evidence shows the combined movement. It does not assign sitewide growth to one release or tactic.
Audited town and service-page indexation URL by URL rather than relying on sitemap totals.
Rebuilt priority town and service pages and strengthened the internal link architecture.
Corrected technical, structured-data and entity inconsistencies that made the business harder for search systems to interpret.
Built a dated measurement layer across Search Console, GA4, local-pack grids and repeated AI-answer captures.
Protected established organic winners while testing new content and service-area cohorts separately.
Answer / AI Search expansion
Google Answer visibility and AI recommendations are different proof types.
Search Console records Answer and Q&A presentation inside Google Search. AI recommendation captures document individual model responses. We do not merge the two.
Google Answer / Q&A Search
Answer-style impressions reached 4,662
0 → 4,662
June
No rows surfaced
July
846
Aug 1-26
4,662
This is Google Search presentation evidence. It does not establish ChatGPT visibility.
Google Search Console · Search Appearance · June through August 26, 2026
Mentions
not publishedNo repeated, comparable mention rate has been published for this account. Historical runs exist but are not like-for-like.
Citations
not publishedCaul is the only source permitted for a citation figure, and no comparable June baseline exists for the current prompt set.
Recommendations
dated examples onlyIndividual model responses that named 603 can be shown as dated captures, each with its exact prompt and capture date. One response is not a rank and does not generalise.
The available AI cohorts, provider modes and grounded denominators are not comparable. The evidence supports dated snapshots, not a June-to-August AI trend, so none is shown.
Local-pack baseline · not an improvement claim
Eight service queries across 61 towns.
The August 14 grid is a point-in-time diagnosis. It does not establish a citywide rank, a permanent position or movement from an earlier grid.
603 service-area baseline8 services × 61 towns
Finishing
Waterproofing
Bowing wall
Crawl space
Crack repair
Foundation
Radon
Sump pump
603 held a positionLocal pack, 603 absentNo local pack
603 Basement Solutions local-pack baseline by service.
Basement finishing: 61 measured points; local pack available at 61; 603 held a position at 0.
Basement waterproofing: 61 measured points; local pack available at 60; 603 held a position at 1.
Bowing wall repair: 61 measured points; local pack available at 5; 603 held a position at 0.
Crawl space encapsulation: 61 measured points; local pack available at 51; 603 held a position at 22.
Foundation crack repair: 61 measured points; local pack available at 57; 603 held a position at 0.
Foundation repair: 61 measured points; local pack available at 61; 603 held a position at 3.
Radon mitigation: 61 measured points; local pack available at 57; 603 held a position at 0.
Sump pump installation: 61 measured points; local pack available at 61; 603 held a position at 0.
603 Basement Solutions baseline. 8 services × 61 towns = 488 measured points. A local pack appeared at 413 points; 603 held a position at 26. Captured 14 Aug 2026 across NH, MA and ME. This is one dated baseline, not a growth result.
Measurement discipline
The evidence stays in the system that measured it.
Search Console measures search clicks, impressions and visible query rows. GA4 measures website sessions and engagement. Local-pack grids measure specific query-location cells. 603 does not have reliable CRM pipeline logging, so Caldrin does not invent booked-job or revenue attribution.
Search
Google Search Console clicks, impressions and Search presentation.
Website
GA4 Organic Search sessions and engaged sessions.
Local
One dated 488-cell baseline, not a growth reading.
AI
Dated qualitative captures only until a comparable repeated cohort exists.
Unknown
Booked jobs, close rate, revenue and gross profit.
What this page does not show.
Search Console and GA4 are separate measurement systems. Search visibility does not establish qualified leads, booked jobs or revenue.
Search Console anonymizes some query rows, so the non-brand result applies to the visible query dimension rather than every query.
The August 14 local-pack grid is a point-in-time baseline, not a ranking improvement or citywide position.
The available AI cohorts are not comparable over time. Dated screenshots may document individual recommendations but cannot support a permanent ranking or improvement rate.
No single release or tactic is assigned sitewide causation. Several changes shipped during the measured period, and the August 24 Service Areas redesign is a named confound.
What shipped, and when
The work behind the numbers, dated.
Several changes ran in the same window. That is why no single item below is credited with sitewide growth, and why one of them is marked as a confound rather than a win.
June 1, 2026
SEO/AEO engagement began.
June 23-24
20 local service pages published.
July
No precise intervention can be reconstructed.Repository history begins July 31.
August 4
Seven waterproofing town pages published.
August 14
43-city and service-page cohort published.
August 18
Protected helical-cost page wording and FAQ updated.
August 19
20 pages across four towns published.
August 20
95 URLs submitted for discovery and recrawl.
August 23
LocalBusiness schema enrichment.
August 24
Service Areas redesign.Named confound: it changed the local surface mid-measurement.
August 26
Four unsupported services retired with 410.
August 28
Five Foundation Repair town pages completed as drafts only.
The operating side of the engagement
Search growth was not the only system being repaired.
Alongside the Search work, Caldrin has been consolidating customer and project records, building controlled follow-up workflows and reducing avoidable dependency in the operating stack. These are implementation states, not published savings, adoption or revenue results.
603 software transformation states
Before · separate toolsOperating layer · current state
Builder Prime$700/mo
Custom CRMAudited migration
NiceJob$75/mo
Review workflowBuilt, switches off
ArcSite~$1,000/mo
ArcSite integrationKept + integrated
Resend~$20/mo
AWS SESActive paths moved
Prior represented recurring SaaS spend: $1,795/month · $21,540/year. This is represented spend, not verified savings.
Review requests with gates
The leak: Review generation fails when it depends on somebody remembering to ask.
The system: A completed job creates a foreman-readiness request before the customer sequence can begin.
Built · sending controls remain off until activation
Signatures inside the workflow
The leak: A disconnected signing tool creates another handoff and another status to chase.
The system: Reps prepare, send and track a private proposal-signature request inside the CRM.
Implemented · production transaction not claimed here
Required field photos
The leak: Before and completion photos get missed when documentation is optional.
The system: Daily field reports cannot close until the required photo and finish-time gates pass.
Implemented workflow gate
Proposal timing you can see
The leak: Managers cannot fix follow-up they cannot see.
The system: The system records proposal sent time, rep, elapsed time, follow-up activity and overdue state.
Implemented with Gmail read-only evidence
Tasks with an owner and due date
The leak: Critical work disappears when it lives in memory or a private inbox.
The system: Tasks carry an owner, priority, due date, completion state and overdue visibility.
Implemented across project and customer records
Automated completion check-ins
The leak: A manager should not need to chase the field team one person at a time.
The system: Scheduled SMS prompts collect job-completion answers and surface missing or conflicting responses.
Implemented · customer satisfaction uplift not claimed
A 28 August audited migration imported 6,709 source rows into Siteboard, including 6,530 contacts, 6,689 project or lead records and 6,026 notes. This documents an audited import, not completed CRM retirement.
Active Siteboard email delivery moved from Resend to AWS SES on 23 September, with an internal delivered test and a retained rollback path. No cost or reliability uplift is claimed.
ArcSite synchronisation and control capability exists inside the operating system. It is not presented as a full replacement, completed rollout or measured business result.
Sources: Siteboard migration, review campaign, proposal signing, field-photo, proposal monitoring, task, completion-check, SES cutover and ArcSite implementation records · August–September 2026. Workflow capability does not establish adoption or commercial impact.
Next phase
Foundation Repair is the next deliberate growth lane.
The broad Foundation parent moved from 234 to 971 impressions and average position 31.83 to 18.90. It is becoming more eligible, while specific structural problem, method and cost content still carries much of the click demand.
Foundation impressions234 → 971Google Search Console · June vs Aug 1-26, 2026
Period
Clicks
Impressions
Average position
June
0
234
31.83
July
1
551
27.90
Aug 1-26
2
971
18.90
The next sprint
Broad Foundation Repair city pages
City pages for bowing walls, settlement and cracks
Local project proof and stronger internal topic ownership
This is one contractor, in one region, over three months. The numbers are theirs. What generalises is the shape of the problem and the way it was measured, not the size of the movement, and any firm telling you otherwise is selling you an average.
The observed query and page mix included problem, method and cost content. This case does not isolate which page type caused the impressions.
Service-area coverage is an inventory problem before it is a content problem. Eligible URLs and surfacing URLs are two different counts, and only one of them is a result.
Answer-style Search presence and assistant recommendations are separate systems. Google reporting one does not tell you anything about the other.
Keep the instruments apart. Search Console’s visible query dimension does not contain every query, and GA4 engagement does not become a qualified-lead count.
Organic web clicks rose from 442 to 1,060 across the same June 3 to August 21 dates in 2025 and 2026. That is a site-level acquisition reading, not a rank for any one query.
Your market, measured the same way
Want this mapped against your market?
The Growth Engine Diagnostic maps visible demand, capture and operating constraints while keeping each source, period and limitation attached to the finding.