Service Area Ecommerce Pages
One page per town works when each page holds facts a customer in that town needs. This guide gives you a test for which towns earn a page, the facts each page must carry, and a hub layout for the rest.
Service area pages for ecommerce are pages on a store’s website that tell customers in one town or district how buying works for them: when the van comes, what delivery costs, where to collect, and what stock is held nearby. Built well, they answer the question a shopper in that town really has. Built from one template with the town name swapped in, they are what Google calls doorway abuse, and a site full of them can lose pages from the index.
The decision this page helps you make is narrow: which of the towns you serve deserve a page of their own, and which belong in a section of one shared hub page. Most small stores need far fewer area pages than an SEO quote suggests, and the ones they keep need hard local facts. Here is how to tell the difference.
What does Google count as a doorway page?
Google’s spam policies define doorway abuse as pages created to rank for specific, similar search queries that lead people to intermediate pages less useful than the final destination. Two of the examples Google lists describe the classic local-store mistake almost word for word:
- pages “targeted at specific regions or cities that funnel users to one page”
- near-identical pages that sit “closer to search results than a clearly defined, browseable hierarchy”
The same policy page also covers scaled content abuse: many pages generated mainly to manipulate rankings, with little value for people, no matter how they were produced. Twenty town pages written by an AI tool from one prompt fit that description as neatly as twenty pages written by hand from one template.
Notice what the policy leaves alone. Nothing in it says a store cannot have a page for a town. The problem is a page whose only job is to catch a search and push the visitor elsewhere. A page that tells someone in Oakley that the van comes on Tuesdays and Fridays, costs $6, and that big trees can be collected from the Oakley yard has a job of its own.
When does a town deserve its own page?
Score each town you serve against five questions. Use your own order data and delivery settings, since a keyword tool alone cannot tell you any of this.
| Question | Yes if… | Points |
|---|---|---|
| 1. Are the delivery terms different? | Different days, fee, minimum order or cutoff from the neighboring towns | 2 |
| 2. Is there a place to collect in or near the town? | A shop, yard, locker or partner counter customers can visit | 2 |
| 3. Is the stock or range different? | Items held at a local location, or items you only deliver there | 1 |
| 4. Do real orders come from there? | A meaningful share of last year’s local orders, by your own count | 1 |
| 5. Is there something local to explain? | Access rules, parking at the pickup point, a market-day schedule | 1 |
Decision rule: a town with 4 or more points, including at least one of questions 1 or 2, gets its own page. Everything else gets a section on a hub page. The rule leans on questions 1 and 2 on purpose: those are the facts that change what the customer does, and they are the facts a competitor’s page cannot copy.
Then run the swap test on any draft page: replace the town name with a neighbor’s. If every sentence is still true, the page has no reason to exist alone, and it moves to the hub.
What unique facts must every area page carry?
An area page is a customer service page first. It should answer the five questions a shopper asks before ordering, and each answer should come straight from your store settings so the page and the checkout never disagree.
| Fact | Sample wording | Source of truth |
|---|---|---|
| Delivery days and window | “Our van reaches Oakley on Tuesdays and Fridays between 10:00 and 14:00.” | Delivery schedule |
| Fee and minimum order | “$6 per order, free over $80, minimum order $25.” | Delivery zone settings |
| Order cutoff | “Order by 18:00 on Monday for Tuesday delivery.” | Checkout rules |
| Pickup point | “Collect from our Oakley yard, Station Road, Thursday to Saturday 9:00 to 17:00.” | Pickup settings |
| Local stock | “Trees over 2 meters are held at the Oakley yard and show as available there.” | Location inventory |
| Exact boundary | “We cover postal codes OK1 to OK4. Outer villages: see the hub page.” | Zone postal code list |
| Local practicalities | “Drivers carry to the front door only. Tell us at checkout about steps or gates.” | Driver notes |
Two optional extras earn their place when they are true: the returns arrangement for that town (driver collects on the next run, or drop at the pickup point) and a short note on seasonal changes, such as an extra Saturday run in December. Leave out invented local color. A paragraph about the town’s history or its best cafes tells the buyer nothing about their order.
Worked example: three towns, one page and one hub
Example shop: a garden center in a town we will call Millbrook. It runs its own van and serves three nearby towns. Last year it counted its local delivery orders by postal code.
| Question | Oakley | Ferncombe | Stanton |
|---|---|---|---|
| Delivery terms differ (2) | Yes: Tue and Fri, $6, cutoff 18:00 the day before | No: Wednesday run, $8 | No: same Wednesday run, $8 |
| Place to collect (2) | Yes: second yard on Station Road | No | No |
| Different stock (1) | Yes: large trees held at the yard | No | No |
| Real orders (1) | Yes: 410 orders | Yes: 85 orders | No: 22 orders |
| Local explanation (1) | Yes: yard parking for trailers | No | Yes: narrow lanes, no truck access |
| Score | 7 | 1 | 1 |
Result: Oakley gets its own page, because it scores 7 and passes both of the heavy questions. Ferncombe and Stanton share the same van run on the same terms, so a single hub section titled “Delivery to Ferncombe and Stanton” covers both, with Stanton’s lane note as one extra line. The hub page sits at the top: Local delivery and pickup around Millbrook, with an Oakley summary that links to the Oakley page.
The arithmetic of upkeep matters too. Three separate pages means three places to update when the fee rises from $8 to $9. One page plus one hub section means two edits, and the hub keeps the shared terms in one sentence. The gain grows with every town you add: a shop serving 15 towns on four van runs needs four hub sections, plus pages only for the towns that pass the test.
How should the hub page and area pages fit together?
Google’s doorway examples point at pages that sit closer to search results than to a “clearly defined, browseable hierarchy”. Build the hierarchy and you answer that point directly.
- One hub page for local delivery and pickup, linked from the main menu or the footer under a plain label such as “Delivery and collection”.
- One section per delivery run on the hub, with a heading that names the towns, the days, the fee and the cutoff.
- Area pages only for towns that passed the test, each linked from its summary on the hub and linking back to it.
- Links from area pages into the shop, to the categories that matter locally (large trees at the Oakley yard), so the page leads somewhere useful.
- No town lists in the footer. A block of 40 linked town names on every page is the pattern the policy describes.
Keep URLs short and readable, such as /delivery/ for the hub and /delivery/oakley/ for an area page. If the store has a Google Business Profile, its service areas can list the same towns, up to the 20 that Google allows. Our Business Profile guide explains which profile type fits a store that delivers.
What does a good area page look like, section by section?
An area page for a small store needs 250 to 500 words. Longer than that, and you are padding. Use this outline and fill it only with facts from your settings.
- Heading: “Delivery and collection in Oakley”.
- Answer box (2 to 3 lines): days, fee, free-delivery threshold, cutoff.
- Collecting from the Oakley yard: address, hours, what to bring, where to park.
- What we hold in Oakley: the product groups stocked locally, linked to their category pages.
- Exact area covered: postal codes, plus what happens just outside them.
- Returns and changes: how a customer in that town returns or reschedules.
- Short FAQ: two or three questions customers from that town have asked your staff.
Sample answer box: “We deliver to Oakley (OK1 to OK4) every Tuesday and Friday, 10:00 to 14:00. Delivery costs $6, or nothing on orders over $80. Order by 18:00 the day before. Prefer to collect? The Oakley yard on Station Road is open Thursday to Saturday.”
The FAQ is where real local value hides. Ask the driver and the counter staff which questions they hear from that town. “Can you leave compost by the side gate?” is a better FAQ than anything a keyword tool suggests, because nobody else can write it.
How can you tell an existing area page is a doorway?
If your store already has town pages, audit them before adding more. Any page that fails two of these checks is a candidate for merging.
- Swap test fails: the page stays true with another town’s name.
- Copy overlap: paste two area pages into a free text-compare tool. When most lines match, the pages are duplicates with a name change.
- No settings behind it: the page names a town the checkout does not deliver to, or quotes a fee the checkout does not charge.
- Dead end: the page links only to the homepage or a contact form, with no local category or pickup detail.
- Nobody uses it: twelve months of analytics show almost no visits and no orders from people who landed on it.
- Keyword stuffing: the town name appears in every heading and most sentences.
A provider who proposes “50 location pages” as an SEO package should explain which facts will differ on each page. If the answer is “the town name and a paragraph about the area”, the package is building doorways at your expense. Our guide to hiring ecommerce SEO services lists other questions for that conversation.
How do you merge area pages that fail the test?
Merging is a short job if you do it in this order.
- List every area page with its URL, visits and orders over the last 12 months, and its score from the test above.
- Keep the pages that pass and rewrite them with the facts table.
- Write the hub sections for the rest, grouped by delivery run.
- Redirect each retired page to the hub with a permanent server-side redirect. Google’s redirects documentation recommends permanent server-side redirects (301 or 308) when a page has moved for good.
- Update internal links and menus so nothing points at the old URLs, and remove them from the XML sitemap.
- Check after a month that the hub and the pages you kept are indexed and that the old URLs answer with the redirect.
A redirect from /delivery/stanton/ to the hub works even better if the hub uses an anchor for that section, so a returning customer lands on the Ferncombe and Stanton text directly.
FAQ
How many service area pages does a small store need?
As many as there are towns with different delivery terms or a local pickup point, which for a single-shop business is between none and a handful. Every other town fits in a section of one hub page.
Can I use one template for all my town pages?
Use one outline, never one text. The headings can repeat; the facts under them (days, fee, cutoff, pickup point, local stock) must differ, or the pages fail the swap test and fit Google’s description of doorway pages.
Do I need a page for every postal code I deliver to?
No. Postal codes belong in your delivery zone settings and in the “exact area covered” line of the page or hub section. Customers search for town names, and one page per postal code only multiplies identical pages.
What if two towns have exactly the same delivery terms?
Put them in one hub section with both names in the heading. Same van, same day, same fee means one block of text, and one place to edit when the fee changes.
Should area pages mention nearby landmarks or local history?
Only when it helps the order: “park behind the church hall” for a pickup point earns its place. A history paragraph adds words, gives the customer nothing and makes the page look like filler.
Is it safer to noindex weak area pages than to delete them?
Merging is cleaner. A noindexed page still needs updating every time a fee changes, and customers who reach it from a menu still see thin content. Redirect it to the hub section that replaces it.
Will a hub page section rank for each town name?
Nobody can promise rankings. A section with the town names in a clear heading and real delivery details gives search engines and customers the same answer, which is the most a page can do.
What should you do next?
Export last year’s local orders by postal code, list your delivery runs, and score each town with the five questions. That one table tells you how many area pages to build, which to merge, and what facts each page needs. If you are weighing an SEO quote for location pages, bring the table to the conversation, or send it to us through the MarketPulse contact form and we will help you prepare the questions.