Two dimensions, one grid
A customer searches for a service in a place: "boiler repair Harrow", "patio installers Pinner", "electrician Ruislip". Two dimensions. A trade website that has a page per service and a page per area covers the grid: the service page ranks for "[service]" plus your base town and links to the areas; each area page ranks for "[trade] [town]" and links to the services. Together they catch searches a single Services page and a single Contact page never will.
Here is how to build both as records, so adding the ninth service or the twelfth town is filling in a form.
Service pages
A record per service with fields:
| Field | Purpose | |---|---| | Name | "Boiler repair" | | Category | Heating, Electrical, Plumbing, Building, Outdoor | | Summary | One line for lists | | What it involves | Body content, in customer language | | Pricing approach | Fixed price, "from", typical range, or "quote after photo", with the number where there is one | | Typical duration | Half a day, one day, two to three days | | Credentials relevant | Gas Safe, Part P, NICEIC, and so on, from the credentials list | | Job photos | Tagged to this service | | FAQs | Repeating pairs | | Live booking | The job software's service ID if this is bookable online (annual service, safety certificate) | | Areas | Relationship to area records, or "all" |
The template renders: heading, what it involves, how it is priced, how long, credentials with register links, photos with captions, FAQs, reviews for this service where filterable, Call, Text and Get a quote (with the service pre-filled), Book if live booking exists, and a line "Available across [areas]" linking to area pages.
Eight to fifteen services for most trades. Write each from a five-minute recording of the tradesperson explaining the job to a customer.
Area pages
A record per town with fields:
| Field | Purpose | |---|---| | Town | "Harrow" | | Neighbourhoods | Estates and districts within it | | Intro | Two sentences: how long you have worked there, how far, response time | | Local notes | Housing stock, common jobs, access or council quirks | | Jobs here | Job photos tagged to this town, with a line each | | Reviews here | Google reviews filtered or selected for this town | | Services emphasised | Relationship to service records, optionally weighted | | Travel time | From base |
The template renders: "[Trade] in [Town]", intro, recent jobs with photos, services offered there linking to service pages, local notes, reviews, travel and availability, Call, Text and Get a quote with the town pre-filled, credentials bar.
Five to fifteen towns you genuinely serve. Start where you already have job photos.
Job photos as the connective tissue
A job photo record has: image, caption, service, town, date. One upload from the van populates the service page, the area page and the gallery. This is the content that makes both kinds of page real rather than templated, and it is the content the business already produces daily. The rule: one photo per job, tagged, before leaving site. The manager or the tradesperson does it from the phone.
Avoiding the doorway page problem
Google ignores pages that are the same paragraph with a town name swapped. The area page template avoids this by design: the jobs, the reviews and the local notes are different for every town because they are drawn from records specific to it. An area page with no jobs and no notes should not be published; the template can refuse until at least two job photos exist.
URLs, titles and structured data
- Services:
/services/boiler-repair. Title "Boiler Repair in [Base Town] | [Firm]". - Areas:
/areas/harrow. Title "[Trade] in Harrow | [Firm]". - Both under sixty characters; descriptions under 160 with the service or town, a credential and a response time.
- Structured data: the business as the relevant local service type with
areaServedlisting every area; each service as aServicewithprovider; reviews marked up where genuine; FAQ markup on service pages. - Internal links: services list areas, areas list services, home links to both, footer lists areas.
Adding one
New service: create the record, write or dictate the body, set the pricing approach and credentials, tag existing photos. Twenty minutes plus the writing. New area: create the record, write the intro and local notes, tag two or three job photos, pick the reviews. Twenty minutes. Neither needs a developer.
What to expect
Service pages begin ranking for "[service] [base town]" within weeks. Area pages begin appearing for "[trade] [town]" within weeks to a few months, faster for towns with less competition. Trades that fill the grid report enquiries tagged to towns they previously had none from within the first quarter, and the enquiry form's pre-filled service and town fields tell them which pages produced them.
Where this sits
Service and area records connected by job photos are the content model under every trade website we build. It is what lets a two-van firm have forty pages that are all genuinely about a service in a place, all converting, and all maintained by whoever takes the photo at the end of the job.