Everything we build, in the order it has to happen.

Before anything is proposed, we establish what is actually true about your visibility, your site, and your market.

• Live 100-point scan. The same audit you can run yourself on this page, plus the interior pages and the technical detail a ten-second scan cannot cover

• Local surface read. Google Business Profile completeness, category strategy, review volume and recency, citation consistency, and map pack rank across a grid of points around you rather than one check from your own office

• AI visibility baseline. Whether ChatGPT, Perplexity, Gemini, and AI Overviews name you today, and which competitor they name instead

• Competitive gap analysis. The services, questions, and towns your competitors answer and you do not

• Call path teardown. Every step between a customer landing and your phone ringing, counted, including what happens after hours

Named priorities and named numbers, agreed before work starts. Not a package with your logo on it.

• Priority sequence. What gets fixed first, second, and third, ordered by what changes call volume rather than what is easiest to put in a report

• The numbers we are judged on. Agreed before we start, so nobody redefines success in month six

• Service and territory scope. Which services and which towns the campaign targets, based on verified demand rather than a keyword list

• What we are not doing. Named explicitly, so the plan has edges and the budget is not spread thin across everything at once

Custom-built around the call, with speed, trust, and accessibility as constraints rather than later fixes.

• Custom architecture. Server-rendered so your content is in the HTML on first fetch, which is the only version AI crawlers ever read

• The phone as the spine. A tappable number on every screen, a quote form for the people who will not call, and online booking wired to your field service software where you run one

• Trust in the first five seconds. Licensed, bonded, insured, years in business, real photos of real crews. The things a homeowner checks before letting a stranger in

• Service page system. One page per service, structured to answer what it costs, how long it takes, and what happens on the day

• Town page system. A real page per town you actually serve, each with its own substance, rather than one page listing forty place names, which Google treats as spam

• Accessibility built in. WCAG 2.2 AA in the markup itself. No overlay widget, which plaintiff firms now treat as a signal worth investigating rather than a defence

The machine-readable version of your business, generated from one source of truth so it cannot drift.

• Your actual trade type. HVACBusiness, Plumber, RoofingContractor, Electrician, AutoRepair, not a generic LocalBusiness that puts you in the same bucket as a nail salon

• Complete location data. Address, coordinates, hours including after-hours availability, phone, and service area, on every location

• Services as structured offerings. Your service list declared as data rather than prose a machine has to interpret

• One source of truth. Every schema field generated from the same data as the visible page, so the two can never disagree

Being the source an AI answer quotes, which is a different job from ranking and increasingly the one that happens first.

• Crawler access, agent by agent. The AI citation agents explicitly allowed, the training agents set to whatever you decide. Most sites confuse the two and lose the citations while trying to protect the content

• Answer-first structure. Every service page opens with the citable answer, then earns the rest of the read

• Question architecture. The cost, timing, and what-happens-next questions customers actually ask, marked up and visible on the page rather than hidden behind a script

• Corroboration. The same facts stated consistently across your site, your profile, and your listings, because agreement across sources is what an engine treats as confidence

The searches people speak, which are longer, more urgent, and much closer to a booked job.

• Emergency and after-hours intent. If you take 2am calls, the site says so in plain words and your structured data backs it up, so an assistant can answer who is open right now

• One-tap calling. Every number a tel link, because a voice search that ends in a memorised phone number ends

• Conversational content. Written the way a customer talks, naming the towns and landmarks people actually use

• Consistent listings. Name, address, and phone identical everywhere, because a near match still counts as a mismatch

Three results above the fold on a phone. For a business customers need to physically reach, this is the most valuable real estate in search.

• Profile optimization. Primary and secondary categories, services, attributes, booking link, and the storefront or service-area configuration that matches how you actually operate

• Site to profile parity. Name, address, phone, and hours verified identical across your site, your schema, and your profile. Drift here is the most common cause of a stalled map pack

• Citation consistency. The directories that matter for your trade, corrected and kept consistent

• Review systems. Compliant velocity with no gating and no incentives, response templates, and a recovery process for the legitimate negatives

• Geo-grid measurement. Rank across a grid of points around you, so you can see which neighbourhoods you are invisible in rather than one flattering number from your own desk

Service and town content written to answer completely, and to be the page a machine quotes.

• Pillar and cluster architecture. A page per service, supported by the question and problem pages that feed it, linked programmatically rather than by hand

• Demand-gated town pages. Pages exist where there is real demand and something specific to say about that town. We do not fan out empty pages, because Google names that as spam

• Substantiated claims. Superlatives and guarantees checked against what you can actually stand behind, because the FTC judges the overall impression, not the fine print

• Freshness cycles. Scheduled re-verification, because a service page nobody has read in two years is a liability

Traffic that does not call is a cost. This phase is the distance between arriving and your phone ringing.

• Call path engineering. Taps from landing to dialling, measured and reduced. Every extra step is a share of customers who do not finish

• Speed to lead. Form and call routing so an enquiry reaches a person fast, because in the trades the company that answers first usually gets the job

• Objection handling on the page. Price ranges, financing, warranty, and what happens on the day, answered before the call rather than during it

• Call tracking and attribution. Calls attributed to source so cost per booked job is a measured number rather than a feeling

• Testing. Structured tests on the paths carrying the most traffic, measured in calls, not bounce rate

The campaign is not finished at launch. It is finished when the numbers move, and the numbers are yours.

• Calls by source. Reported monthly in your numbers. Not impressions, not sessions, not a dashboard screenshot

• Geo-grid heatmaps. Map pack position across your service area, tracked window over window

• Search Console and rank tracking. Clicks, impressions, and page-level movement, with competitor overlays

• Profile actions. Calls, direction requests, and website clicks originating from your Google Business Profile

• AI visibility tracking. Whether the assistants name you, tracked as it changes

• Scheduled reviews. Checkpoints at 30, 60, and 90 days against the numbers agreed in phase 01, not against goalposts moved afterwards