How Many Pages Should a Contractor Website Have?

The short answer

Most contractors need somewhere between 12 and 25 pages, but the number is an output rather than a target. It falls out of three tests applied one page at a time: does anyone search for this, can you say something on it that is true only of it, and will you still maintain it in a year. Pages that pass earn their place at any count. Pages that fail do not become useful because you built a lot of them.

Every answer you have found is a different number

Before the formula, look at what the first page of Google currently tells a contractor asking this question. These are the actual ranking answers as of this week:

That last one is not a typo. In an August 2026 r/localseo thread about structuring a construction company's site, one commenter offered: "For a website with 12 service hubs and 40 services, with around 50 locations, cities and neighborhoods, you will need around 3k pages."

The spread runs from 8 to 3,000. Every one of those sources is confident, and most of them sell the thing they are recommending you buy more of. The reason the numbers disagree is that page count is not a property of your industry. It is a property of your specific service list, your specific geography, the competition in your market, and, more than anyone admits, how much writing you can realistically sustain.

So stop asking for the number. Ask what makes a page worth existing.

Why the count matters at all: Google ranks pages, not sites

The one piece of received wisdom that survives scrutiny is this: search engines rank individual URLs, not businesses.

A local SEO practitioner described the consequence well in a recent r/localseo post about a construction client: a business does ten things, the website has one page called Services with ten accordion dropdowns, and then the owner wonders why they only rank for their own brand name. As they put it, "If plumbing, heating, loft conversions, and kitchen renovations all live on one URL, you have handed Google one page and asked it to rank for ten different search intents. It picks one, usually whichever one has the most text, and the other nine get nothing."

That is the mechanism, and it is the honest argument for more than five pages. It is not that bigger sites rank better. It is that a URL can only be the best answer to a small number of questions, so distinct buying decisions need distinct URLs.

Note the qualifier, though. A commenter on that same thread pushed back sensibly: in a genuinely low competition market, a ten service hub page can rank fine, and building 58 child pages burns budget you may not have. Competition determines how much granularity you actually need. If nobody in your town has a dedicated page for the service, you can win it from a section.

The three tests

Run every candidate page through these in order. A page needs all three.

Test 1: does anybody search for it

Not "is it a thing we do". Does the phrase get typed. A service you perform twice a year, that nobody searches by name, does not need a URL. It needs a paragraph on a page that does get searched.

This is the discipline the better local SEO practitioners keep repeating. In a widely read r/localseo thread on service and city page strategy, the advice was blunt: "CREATE EVERYTHING BASED ON SEARCH KEYWORDS. You don't need to ever guess. You're not here to make decisions for people. You're here to see what people are already doing, and then steer your glove to catch them."

Practically: list your services, list your towns, and check which combinations people actually type before you commit a URL to any of them.

Test 2: can you say something true only of this page

This is the test that kills most city pages, and it is worth being ruthless about. Open a blank document, write down everything you would put on the page, then cross out every sentence that would still be true if you swapped the town name for a different town. If what remains is three sentences and a map embed, the page does not exist yet.

Things that survive the test: named neighbourhoods and streets you actually work, housing stock specific to that area, the drive time and what it means for emergency response, permit or inspection quirks of that municipality, jobs you have completed there with photos, and reviews from customers in that town.

Things that do not survive: "We are proud to serve the residents of your town name here", a paragraph about your commitment to quality, and the same six service blurbs from your homepage.

Test 3: will you maintain it in a year

The forgotten test, and the one that ultimately sets your ceiling. Every page you publish is a page that will need updating when your service list changes, your phone number changes, your pricing model changes, or your service area shifts. A 60 page site maintained by nobody decays into 60 pages of outdated claims.

Be honest about capacity. If you or one person can genuinely refresh eight pages a quarter, a 25 page site is sustainable and an 80 page site is a slow liability.

The pages nearly every contractor actually needs

Start here regardless of trade. Six to eight pages, and most of them exist to convert rather than to rank.

The distinction in that last column matters more than page count does. Roughly half of these pages will never bring you a visitor and are still essential, because they are what a visitor reads between arriving and calling. If your traffic is fine and your phone is not ringing, adding city pages is not the fix, and the causes are covered in why a website gets traffic but no calls.

Service pages: one per buying decision

The rule that works: one page per service that has its own search demand and its own buying decision.

Both halves matter. "Emergency plumbing" and "bathroom installation" are different searches and different decisions, made by different people, in different states of mind, with different urgency. They need separate pages. "Tap replacement" and "tap repair" are usually the same decision and belong on one page, headed by whichever phrase gets searched more.

For most trades this produces four to ten service pages. An electrician might land on panel upgrades, EV charger installation, rewiring, lighting, emergency callouts and inspections. Six pages, each of which a real person searches by name, each of which someone decides to buy separately.

What a real service page contains, beyond the obvious description: who it is for and who it is not for, what the process actually involves step by step, what makes a job cost more or less, how long it takes, what you need from the customer, and photos of that specific work. If your page could describe any contractor in the country performing that service, it will be outranked by one that could not.

Service area pages: where contractors hurt themselves

This is the section that actually determines whether your site works, and it is the section the ranking articles handle worst. Most of them say "yes, build a page for every town you serve" and then add a sentence about making the content unique, which is roughly as useful as telling someone to be interesting.

Start with a distinction almost nobody makes. As SEO practitioner Bill Hartzer put it in an r/localseo thread on this exact question, you should separate location pages from areas-we-serve pages. A location page is somewhere you have a verifiable physical presence, with its own address, hours and people. An areas-we-serve page covers a town you drive to. They are different assets, they deserve different content, and expecting the second to perform like the first is the source of a lot of disappointment. The related question of ranking where you have no premises is covered in how to rank for a city you do not have an office in.

Second, a rule that prevents a common self inflicted wound: do not target the same city twice. In that service and city page strategy thread, the point was made emphatically. If your main service pages already target your primary city, do not also build a city page silo for it. You end up with two pages competing for one query, and Google picks one, often not the one you wanted.

Third, a myth worth retiring. The same practitioner, describing their own testing, wrote: "Out of all the testing I have done on Google Maps, I have never once found that creating some specific page targeting one specific area on the map had an impact specifically on that area." Neighbourhood pages built to move your map pack visibility are a common recommendation with thin evidence behind it. Map pack visibility is largely a Google Business Profile and proximity question, and that is a different discipline covered in how service area businesses should set up a Google Business Profile.

So the working rule for area pages: build one for a town only when people search your service plus that town name, you can write something about working there that is not true elsewhere, and you will keep it current. For most contractors that is three to eight towns, not thirty. Everywhere else goes on a single honest areas-we-serve hub that lists the coverage without pretending each entry is an article.

Google's own test, which is 11 years old and still the standard

Contractors rarely read the primary source, so here it is. In March 2015, Google Search Central published "An update on doorway pages", announcing a ranking adjustment and warning that "sites with large and well-established doorway campaigns might see a broad impact from this change."

The post lists the questions Google says to ask about pages that might be doorways. Read them as a city page checklist:

• "Is the purpose to optimize for search engines and funnel visitors into the actual usable or relevant portion of your site, or are they an integral part of your site's user experience?"
• "Are the pages intended to rank on generic terms yet the content presented on the page is very specific?"
• "Do the pages duplicate useful aggregations of items (locations, products, etc.) that already exist on the site for the purpose of capturing more search traffic?"
• "Do these pages exist as an 'island?' Are they difficult or impossible to navigate to from other parts of your site?"

That third question is the one that catches the standard contractor build. If you already have an areas-we-serve page listing your coverage, and you then generate 40 near identical town pages that duplicate that aggregation to capture more search traffic, you have described Google's own example back to it.

The fourth is the one people fail without noticing. If your 40 town pages are reachable only from a footer link block and from nowhere in your actual navigation, they are islands by Google's definition.

The 2026 change that raised the stakes

For years the practical downside of thin location pages was that they simply did not work. That changed.

On 15 May 2026, Google updated its Spam Policies documentation to clarify that its existing policies apply to AI-generated responses in Search, stating the change was made "to make it clear that the spam policies apply to all of Google Search, including generative AI responses." The prohibited practices explicitly carried into AI Overviews and AI Mode include doorway pages, scaled content abuse, and thin content. Scaled location page generation using templated copy is named as the highest risk pattern for multi-location businesses.

Two practical consequences. First, a site carrying a pile of templated town pages is not merely failing to rank those pages, it is affecting its eligibility to be summarised or cited in the AI answers that increasingly sit above the results. If you are already wondering why AI tools never mention you, that interacts with why your website does not show up in ChatGPT.

Second, and easy to miss: FAQ rich results were deprecated on 7 May 2026. If part of your justification for extra pages was harvesting FAQ rich snippets, that specific return no longer exists.

What actually happens when you publish pages nobody needs

Here is a data point none of the ranking articles can offer, because it requires admitting to your own numbers.

This site has over 350 published pages. Across a recent 90 day window in Search Console, the entire domain earned 30 organic clicks. Twenty three of those went to the homepage. Only five article pages earned a click at all, and four of those earned exactly one. Of roughly 195 pages that had been live long enough to be crawled and considered, about two thirds had picked up at least one impression, and the overwhelming majority of those impressions converted into nothing at all.

That is not an argument against publishing. It is an argument against the belief that publishing is the same event as ranking. Pages get crawled, considered, and quietly filed as not worth surfacing. A page is a lottery ticket with a low expected value, and buying more tickets does not change the odds on any individual one. What changes the odds is picking a query where the existing answers are weak and being obviously better on that one page.

Apply that to a contractor site. Twelve pages that each target a query you can realistically win will beat 60 pages that each target a query someone else already owns comprehensively. If a competitor is currently ahead of you, the reason is rarely their page count, and the actual reasons are worth diagnosing properly, which is the subject of why a competitor outranks you on Google.

Three worked examples

Note what happens in the third row. The business serves 12 towns and publishes 5 town pages, because only five of those towns have enough search demand and enough genuinely distinct content to justify one. The other seven are listed on the hub. That is the discipline the "one page per town" advice removes, and removing it is what gets sites suppressed.

Note also the service plus city combinations. They are the highest converting pages on a contractor site when they are real, and the fastest route to a thin content problem when they are generated. Build three that are excellent before you consider thirty.

The order to build in

Sequence matters more than the eventual total, because the early pages fund the later ones.

1. Home, contact or quote, and one services overview. You need to be credible and contactable before anything else is worth doing.
2. About, work or gallery, and reviews. These convert the traffic you already have. Cheapest possible lift.
3. One service page for your highest margin service. Not your most common. Your most profitable.
4. The remaining service pages, one at a time. Publish each one properly rather than publishing all of them thinly.
5. A single areas-we-serve hub listing every town honestly.
6. Two or three town pages for the areas with the clearest search demand. Wait a full quarter and look at what they actually did.
7. Only then expand, and only into areas where step six actually worked.

Most contractors invert steps three and six, because town pages feel productive and are easy to generate. Then the site has 40 pages, no service depth, and a structural problem that takes a year to unwind. Worth checking, too, that the pages you do have load quickly, since a large site built on a slow platform compounds every other problem: see how to speed up a slow contractor website.

The checklist before you publish any new page

Five questions. Any no means do not publish it yet.

1. Can I name the exact phrase a person types to find this page?
2. Have I checked that phrase is actually searched, rather than assuming?
3. Is there anything on this page that would be false if I swapped the service or town for a different one?
4. Is the page reachable from my real navigation, not only from a footer link block?
5. Will I update this page when something about the business changes?

A contractor site that only ever publishes pages passing all five will end up somewhere near 15 to 25 pages, will keep working through core updates, and will be a far more valuable asset than the 80 page version. The right page count is not the largest number you can justify. It is the largest number you can defend, page by page, to somebody who does not care how hard you worked on it. If lead volume is the actual goal, the structure of the site is only one input, and how the whole system fits together is what we build at Pavado.