Roofing & home services · Carlisle
Building a storm-ready search engine for a Carlisle roofer
An illustrative campaign showing how emergency and planned-work pages, postcode-level map tracking and a disciplined review system can turn autumn demand into exclusive enquiries.
+214% enquiry scenario
Primary scenario outcome
9-month model
Campaign horizon
Evidence standard: Illustrative, anonymised campaign scenario. The company identity and figures are not presented as independently verified client results; they show a realistic measurement framework and the type of outcome a well-executed campaign would target.
Starting point
The baseline we would document
- Search structure
- One generic roofing page served every job type
- Map visibility
- Strong near the office, weak across CA2–CA6
- Proof
- Good offline reputation but an irregular review flow
- Measurement
- No call source or postcode-level rank tracking
The commercial problem
The contractor was relying on referrals and shared leads while its website treated an emergency leak, a planned re-roof and a heritage slate repair as the same enquiry. That hid the urgent information storm customers needed and gave Google no focused page to rank for each service.
Carlisle also behaves as several local markets. A business may appear close to the top around the city centre but disappear from a phone in Dalston, Brampton or the northern CA postcodes. The campaign therefore had to improve both relevance and geographic confidence rather than chase one city-wide ranking screenshot.
The strategy
We modelled two journeys. Emergency visitors received a fast page with coverage, availability, insurance guidance and a tap-to-call action. Planned-work visitors received roof-type detail, materials, guarantees, project evidence and a quote pathway. Supporting pages covered flat roofing, slate, leadwork and storm inspections without duplicating the same copy across towns.
The content calendar worked backwards from autumn. Core pages were planned for late summer, followed by inspection guidance and weather-response updates. That gave pages time to be crawled before demand, while paid search remained the contingency for any postcode where organic visibility had not matured.
- Separate emergency and planned-work search intent
- Map-grid tracking across realistic service areas
- Review prompts asking customers to mention job type and town
- Call tracking grouped by landing page and postcode
What was implemented
The homepage stopped carrying the full SEO burden. Internal links directed authority into focused service and Carlisle pages; each page answered cost, response, materials and coverage questions in plain English. Business information was made consistent across the site and key directories, and the Google Business Profile was aligned with the services actually offered.
A simple evidence routine turned every completed job into useful marketing material: permissioned photographs, a short description of the fault and repair, the broad area served, and a review request. This created authentic proof without exposing customer addresses.
How success would be measured
The primary measure was qualified enquiries from organic search, not traffic. Calls had to last long enough to indicate a real job, forms needed a valid postcode, and duplicates were removed. Secondary measures included map visibility by grid cell, non-brand clicks to service pages and review recency.
The headline uplift is intentionally presented as a scenario rather than a verified testimonial. A real engagement should publish the baseline dates, call-tracking export and comparison method before making a public performance claim.
The transferable lesson
Seasonal demand rewards preparation. A roofer cannot wait for wind warnings to begin explaining emergency coverage, just as a hotel cannot wait for a bank holiday to improve its booking journey. The durable advantage is a page system, proof routine and measurement setup that are already working when demand arrives.
Delivery
Campaign timeline
- 1
Months 1–2
Technical baseline, service split, map grid, tracking and profile clean-up.
- 2
Months 3–5
Publish priority pages, build project evidence and establish steady review requests.
- 3
Months 6–9
Strengthen weak postcode cells, publish seasonal guidance and refine conversion paths.
Scenario outcomes
- Top-three map visibility across the highest-priority CA postcode cells
- A modelled 214% increase in tracked organic phone and form enquiries
- A lower blended cost per qualified lead than shared lead-buying platforms