Local service website: Ankora Pest Control

The challenge

Local pest control is searched on two axes at once: the pest and the place. People do not search for “pest control services”; they search for wasp removal in Edina, or mice in the wall in Bloomington. A single services page and a list of towns competes on neither axis, and the visitor leaves for a competitor whose page names the thing they typed.

What we built

A matrix rather than a brochure. Eight service pages and twenty-three service-area pages, built so that the intersection a searcher actually typed has a page that confirms both halves of it. Somebody looking for wasp removal in Edina reaches a page about wasps that confirms Edina, rather than a general services page that mentions neither.

Conversion was designed into the same screen. The booking form sits in the hero and the phone number sits beside it as an equal action, because in an urgent category a meaningful share of visitors would rather call. Licensing, free inspection, same-day availability and pet-safe treatment are stated above the fold, since those are the four things that decide whether a stranger will let you into their house.

What changed

The site can now be found for the specific job in the specific suburb, and the page that ranks is the page that answers. A pest identification library and a seasonal blog give the site something to rank for out of season, when the urgent searches stop.

The project in detail

The summary above is what changed. What follows is how: what local service search actually looks like, why a matrix beats a brochure, and what another local service business should take from it.

Two axes, searched at once

Local service demand is not one query with a location attached. It is a pest and a place, typed together, by somebody who has just found something in their kitchen. “Wasp nest removal Edina” is a different search from “pest control Minneapolis”, and it is the one that converts, because the person typing it has already decided what the problem is and only needs to know who will come.

A brochure site answers neither half well. It has one services page that mentions eight pests without owning any of them, and a coverage list that names twenty-three towns without saying anything about any of them. It reads as relevant to everything and specific to nothing, which is exactly how it ranks.

Why a matrix rather than a list of towns

Eight services and twenty-three areas is a matrix, and the pages are built so that the intersection a searcher typed has a page that confirms both halves of it. Somebody searching for wasps in Edina lands on a page about wasps that confirms Edina, rather than on a general page that mentions neither.

The obvious failure mode here is well known and was designed against: generating every combination as a page with the town name swapped in. That is a doorway estate, it reads as one to a person, and it is treated as one. What makes the difference is that each page has to carry something true that only applies to it — what the pest does in this climate, what a treatment involves in housing of this type, what the seasonal pattern is locally. If a page has nothing of its own to say, it should not exist, and the area belongs on a page that covers the region honestly.

Designing for somebody deciding in ninety seconds

In an urgent category the visitor is not researching. They are deciding whether to let a stranger into the house, and they are doing it fast.

• The booking form is in the hero, and the phone number is beside it as an equal action. A meaningful share of people in an urgent category will not fill in a form, and burying the number below the fold loses them silently.
• Licensing, free inspection, same-day availability and pet-safe treatment are stated above the fold. Those four are what the decision actually turns on; everything else is detail for somebody who has already decided.
• Nothing between the intent and the action. No interstitial, no newsletter prompt, no chat window opening over the form.

What keeps the site working out of season

A pest control site has a demand curve with deep troughs. A pest identification library and a blog structured around the seasonal pattern give the site something to be found for when the urgent searches stop — and the person who identified their insect in March is the person who books a treatment in June.

How it ran

1. Demand mapping. Which pests, which suburbs, and which intersections carry enough real demand to deserve their own page.
2. Matrix design. The page set, and the rule for what each page has to say that no other page says.
3. Build and conversion design. Templates, booking form, call path and the trust block, tested on a phone first.
4. Handover. The client can add a service or an area without a developer, which is what stops the matrix going stale.

What another local service business should take from this

Build for the intersection, not the category

The query that converts names both the job and the place. If no page owns that pair, the enquiry goes to whoever does.

Put the phone number where the form is

In an urgent trade the call is not a fallback, it is the preference for a large share of buyers. Treating it as secondary loses those people without recording that it happened.

Only create a page you can say something on

The line between a service-area page and a doorway page is whether the page carries anything true that only applies to it. If it does not, cover the area honestly on a page that does.

Local service website questions