Most local service businesses need somewhere between four and ten dedicated service pages, one for each distinct thing they actually do well, not one for every service-times-city combination a keyword tool spits out. A locksmith with a lockout, rekey, and commercial installation offering needs three real pages. The same locksmith trying to rank a separate page for “locksmith in Elmwood,” “locksmith in Fairview,” and nine other neighborhoods usually ends up with ten thin pages that all say the same thing with the city name swapped, which is exactly the pattern Google has been pushing back against. The right number isn’t a fixed count. It’s however many services can each support a genuinely different page.
That distinction matters more than the page count itself, and it’s where most local service sites go wrong in one of two directions: too few pages crammed onto a single “Services” list, or too many pages built off a spreadsheet of service-and-location keyword combinations that nobody would ever read past the first paragraph.
Why a Single Services Page Usually Falls Short
A one-page services list works fine as a menu. It doesn’t work as a way to actually rank or convert, because it can’t answer the specific question someone typed. Someone searching “panel upgrade cost” or “emergency ceiling fan installation” wants a page that speaks directly to that job: what’s involved, roughly what it costs, how fast you can get there, and what to expect. A shared paragraph buried in a longer list answers none of that well.
This was the exact problem behind RJ & Son Electric’s old site. Homeowners with an urgent electrical issue couldn’t tell from the homepage whether the company actually handled panel upgrades versus just basic repairs, and there was no clear path to request a quote for a specific job. We rebuilt it in one week on WordPress with custom UI/UX and no theme template, splitting the work into dedicated landing pages for repairs, installations, and panel upgrades, each with its own quote request path. Nothing about that build was about adding more pages for their own sake. It was about matching the page structure to the three actual decisions a homeowner needed to make.
Where Extra Pages Start Costing You Instead of Helping
The failure mode on the other end is more common with businesses that have already been burned by generic SEO advice: build a page for every service, then multiply that by every neighborhood, suburb, or nearby town, because “more pages means more keywords.” It doesn’t work that way anymore, and honestly it barely worked that way before. Google has been explicit that quality signals now matter more than sheer page volume for service businesses, and that a handful of pages with real differentiation outperforms dozens of near-identical ones stuffed with a swapped city name.
There’s also a practical ceiling worth knowing: Google’s own service-area guidance recommends defining your service area by real cities or postal codes, kept within roughly a two-hour drive of your base, rather than an inflated radius. A business that tries to rank pages for towns it can’t realistically service well ends up diluting the pages that matter for its actual core area, and the duplicate-content risk from ten pages that differ only by a placeholder is real: search engines increasingly treat that pattern as thin content rather than ten separate answers.
What Southport Auto Repair Did Differently
Southport Auto Repair needed the opposite fix from RJ & Son. Local customers could find the shop, but the site gave them no reason to trust it over the next search result and no fast way to book anything. We built a two-week WordPress and Elementor site around a service-oriented homepage that leads with the three things the shop is actually known for: oil changes, diagnostics, and brake repair, paired with an integrated booking form and Google Maps directions baked directly into the page rather than buried in a contact page. A blog section handles the longer-tail, less commercial questions (things like “how often should I really change my oil”), which keeps the core service pages focused purely on conversion instead of trying to double as content marketing.
That split is worth calling out on its own: the core service pages exist to get someone to book, and they should read that way, short, specific, and easy to act on. Informational content that ranks for research-stage questions belongs somewhere else on the site, not wedged into the same page that’s supposed to close the job.
A Simple Test for Whether a Page Earns Its Own Existence
Before adding a page, ask whether it can say something the other pages on the site genuinely don’t. That usually comes down to three things:
- A different process. Panel upgrades and ceiling fan installation involve different steps, different permits in some areas, and different timelines, so they can each fill a real page.
- A different price range or decision. If two services cost roughly the same and get booked the same way, splitting them into separate pages usually just duplicates content.
- A different urgency level. An emergency service (burst pipe, no power, locked out) reads and converts differently than a scheduled one, even if the underlying skill overlaps.
If a proposed page fails all three tests, it’s a section on an existing page, not a new URL.
| Structure | When it fits | Where it breaks down |
|---|---|---|
| Single combined services page | Very small operation, 2-3 closely related services, early-stage site | Can’t rank for specific service searches; no room to answer job-specific questions |
| One page per distinct service | Most local service businesses with 3-10 genuinely different offerings | Requires real content per page; a rushed page is worse than no page |
| Service x location matrix | Multi-location businesses with staffed branches in each city | Thin, duplicate-feeling pages for a single-location business chasing search volume rather than reach |
Notice that the service-x-location matrix isn’t wrong in every case, it’s wrong for the business that doesn’t actually have separate branches or crews in each of those locations. A regional company with real staffed offices in three cities has a legitimate reason for three sets of pages. A single-location electrician trying to rank in eleven neighboring towns doesn’t, and building that structure usually produces pages Google treats as duplicates of each other anyway.
Photos matter here too, and it’s a mistake worth flagging separately: a page structured perfectly around real services still reads as generic if every image on it is stock photography of someone else’s van and someone else’s crew. We’ve written before about why real job photos outperform stock photography for local service sites, and the same logic applies once you’ve settled on the right page structure: the structure gets someone to the right page, the photos are what convince them it’s a real, local operation once they’re there.
Frequently Asked Questions
Should I combine similar services onto one page to save time?
Only if they’re genuinely similar in process, price, and urgency. Combining an emergency repair with a scheduled installation on one page usually hurts both, because the page can’t speak clearly to either visitor.
Do I need a separate page for every city I serve?
No, not unless you have a real staffed location or crew based there. Google’s own guidance favors a defined, realistic service area over a long list of thin location pages built purely for search volume.
How long should each service page be?
Long enough to answer the actual questions a customer has before booking: what’s involved, rough pricing or a pricing range, timeline, and what happens next. That’s often 300-600 words plus a clear call to action, not a fixed target.
What if I only offer two or three services total?
A single combined page can be the right call at that scale. Splitting two closely related services into separate thin pages usually does more harm than keeping them together with clear subheadings.
Can I add more service pages later as the business grows?
Yes, and that’s usually the healthier order of operations: launch with pages for what you actually do now, and add a new page only once a new service line is established enough to write something specific about it.
