For plumbers, electricians, HVAC and cleaners
Location pages for service businesses, one for every job and suburb
Put every job and suburb you cover in a row: the phone that rings that crew, the call-out fee, the arrival window and the hours. Design one page, and PageForge builds a WordPress page for each row with its own title, URL and schema.
- Free on WordPress.org
- Service schema for each city
- Preview every URL before writing
Why trade sites stall
Ten copied city pages and a footer full of town names is not coverage
Most trade sites stop at a handful of city pages cloned from the first one, because building and maintaining more by hand takes evenings nobody has. The pages that exist say the same thing, so none of them gives a customer a reason to call.
How it usually gets done
- One Services page, plus a list of thirty suburb names pasted into the footer
- Ten city pages copied from Austin with only the town name changed
- Call-out fees on the site that stopped matching what the office quotes last spring
- Every new suburb or price change means opening and editing pages one by one
With PageForge
- One row per job and suburb, carrying that crew’s phone, call-out fee and arrival window
- Title, URL, meta description and Service schema built from the row
- Check and preview flags duplicate URLs and missing columns before anything is written
- Change a fee in the CSV, run update mode, and every page that shows it refreshes
The data
One row per page, every detail that changes
Service and City name each page and its schema. Phone, CallOutFee, ArrivalWindow and Hours answer what someone with water on the floor asks first, and JobNote adds one line on how that crew does the job.
| Service | City | State | Phone | CallOutFee | ArrivalWindow | Hours | JobNote | |
|---|---|---|---|---|---|---|---|---|
| 2 | Drain Cleaning | Austin | TX | (512) 555-0142 | $89 | Same day when booked by 2pm | Mon-Sat 7am-7pm | Camera inspection included on main lines |
| 3 | Water Heater Repair | Austin | TX | (512) 555-0142 | $89 | Within 4 hours | Mon-Sat 7am-7pm | Tank and tankless units serviced |
| 4 | Drain Cleaning | Round Rock | TX | (512) 555-0158 | $99 | Next morning | Mon-Fri 8am-6pm | Crew based on the north side of town |
| 5 | Leak Detection | Cedar Park | TX | (512) 555-0163 | $119 | Within 1 business day | Mon-Fri 8am-5pm | Thermal camera survey before any digging |
| 6 | Water Heater Repair | Pflugerville | TX | (512) 555-0171 | $99 | Same day when booked by noon | Mon-Sat 8am-6pm | Old tank hauled away at no charge |
| 7 | Sewer Line Repair | Georgetown | TX | (512) 555-0186 | $129 | Within 2 business days | Mon-Fri 7am-4pm | Written quote before any work starts |
| 8 | Emergency Plumbing | Austin | TX | (512) 555-0199 | $159 after hours | Within 90 minutes | 24 hours a day | Night and weekend calls answered by staff |
Placeholders
{Service} {City} {State} {Phone} {CallOutFee} {ArrivalWindow} {Hours} {JobNote}
Patterns
Title{Service} in {City}, {State}
URL/{service}-{city}-{state}/
Campaign size
6 services × 40 suburbs = 240 pages
Pages this creates
- Drain Cleaning in Austin, TX
- Water Heater Repair in Pflugerville, TX
- Leak Detection in Cedar Park, TX
- Sewer Line Repair in Georgetown, TX
- Emergency Plumbing in Austin, TX
How it works
From your job list to pages customers book from
01
List the jobs and suburbs you really cover
One row per service per suburb. Add the columns a customer acts on: the number that rings that crew, the call-out fee, the arrival window, the hours and one line on how the job is done. Leave out suburbs you only reach once a month.
02
Build the page once
Design it in the block editor, Elementor, Divi or Avada, with {Service}, {City}, {CallOutFee} and the other columns where values change. Set the Title Pattern to {Service} in {City}, {State} and the Slug Pattern to {service}-{city}-{state}.
03
Check, then draft five
In Settings, set Business Type (Schema) to Plumber, Electrician, HVACBusiness or the type that fits, and Target Country (Schema) to US. Check and preview shows the counts and the first URL. Generate five drafts and read them on your phone.
04
Publish and keep the fees right
Publish the drafts you trust and add the PageForge Sitemap block to your Areas we serve page. When a fee or arrival window changes, edit the CSV and run it with Update it from the CSV and current template.
Built for trade sites
What a suburb page needs, filled in from your job list
The template decides how the page looks. The row decides what is true in that suburb. PageForge joins the two and writes the title, URL, metadata and schema.
One generated page
What a customer with a blocked drain sees on Drain Cleaning in Austin, TX
The heading names the job and the town they typed. Under it sit the three answers they came for: an $89 call-out fee, same-day arrival when booked by 2pm, and a button that dials (512) 555-0142. The job note, camera inspection included on main lines, tells them what the visit covers before they ring.
- Fee, arrival window and phone in the first screen
- That crew’s hours, Mon-Sat 7am-7pm, next to the button
- One line on how the job is done, from JobNote
Hubs, not footers
Link every suburb page from one Areas we serve page
PageForge Free does not link generated pages to each other by itself. Add the PageForge Sitemap block to your Areas we serve page, group it by city, and every published suburb page gets a link from a page your menu already points to.
- Group the list by city, state or service
- Write two lines above it on how far your crews travel
- Link the hub from the main menu or footer
Prices change
Raise the call-out fee once, not on forty pages
Fees, arrival windows and hours drift. Edit the column, upload the file and run it with Update it from the CSV and current template. Status, URL and parent stay as they are, and a page your office manager rewrote by hand is skipped unless you choose to overwrite it.
- Check and preview counts the pages to update first
- Pages edited by hand are listed, not overwritten
- A renamed suburb is a new URL, so redirect the old one
Compared
Generated suburb pages versus copying the first one
The page a customer sees can look the same. What sits behind it, and how far it drifts over a year, does not.
| PageForge | Copied suburb pages | |
|---|---|---|
| Call-out fee and arrival time per suburb | From the CSV | Typed in once, then forgotten |
| Title, URL and meta description | Built from patterns | Edited by hand, often skipped |
| Service schema naming the city | Yes | No |
| Duplicate URL check before writing | Yes | No |
| Changing a fee on 40 pages | One update run | 40 separate edits |
| Areas we serve hub | Sitemap block, grouped by city | Kept up to date by hand |
| Pages per run | Up to 100 in Free, no limit in Pro | One at a time |
Location pages for service businesses: what the search looks like
People who need a trade type the job and the place. “Drain cleaning round rock.” “Water heater repair pflugerville.” “Emergency plumber austin.” Location pages for service businesses exist to answer those searches with a page about that job in that town, instead of sending everyone to one general Services page.
The person searching usually has a problem in front of them: water on the floor, no hot water, a drain backing up into the shower. They want three answers before they pick up the phone:
- Do you cover my area?
- How soon can someone get here?
- What does it cost to show up?
The page that answers those near the top gets the call. The page that opens with four paragraphs of company history does not.
Why most trade sites stop at ten pages
Six services across forty suburbs is 240 pages. Each one needs a title, a URL, a meta description, the right phone number and a fee that matches what the office quotes. Built by hand, that is weeks of evenings, so most sites stop at a few city pages copied from the first one with the town name swapped. Those pages look like coverage and say nothing new.
PageForge takes the copying out. You keep a list with one row per job and suburb, and one template. The plugin builds a WordPress page for every row, with its own title, URL, SEO fields and schema. What it cannot do is know your business. Each page is only as useful as the row behind it.
What a customer checks before calling
Listen to the calls your office takes. The questions repeat, and each one can be a column. Here is the Round Rock row from the sample, lined up against the question it answers:
| Question on the phone | Column | Round Rock row |
|---|---|---|
| Do you come out to Round Rock? | City | Round Rock |
| What number do I call? | Phone | (512) 555-0158 |
| What do you charge to come out? | CallOutFee | $99 |
| How soon can you get here? | ArrivalWindow | Next morning |
| Are you open on Saturday? | Hours | Mon-Fri 8am-6pm |
| Is the crew local? | JobNote | Crew based on the north side of town |
The answers differ from one suburb to the next, and that difference is the reason the page exists. Drain cleaning in Austin is $89 and same day when booked by 2pm. In Round Rock it is $99 and next morning. A customer can act on that. A page that only swaps the town name gives them nothing to act on.
Worked example: the sample CSV
The sample is a hypothetical plumbing company working Austin and the towns north of it. It has eight columns and seven rows:
Service,City,State,Phone,CallOutFee,ArrivalWindow,Hours,JobNote
With the Title Pattern {Service} in {City}, {State}, the Slug Pattern {service}-{city}-{state} and Target Post Type set to Page, the seven rows produce seven pages:
| Row | Page title | URL |
|---|---|---|
| 1 | Drain Cleaning in Austin, TX | /drain-cleaning-austin-tx/ |
| 2 | Water Heater Repair in Austin, TX | /water-heater-repair-austin-tx/ |
| 3 | Drain Cleaning in Round Rock, TX | /drain-cleaning-round-rock-tx/ |
| 4 | Leak Detection in Cedar Park, TX | /leak-detection-cedar-park-tx/ |
| 5 | Water Heater Repair in Pflugerville, TX | /water-heater-repair-pflugerville-tx/ |
| 6 | Sewer Line Repair in Georgetown, TX | /sewer-line-repair-georgetown-tx/ |
| 7 | Emergency Plumbing in Austin, TX | /emergency-plumbing-austin-tx/ |
That is five services across five towns, with Austin carrying three of them. Every slug is different, so Check and preview reports 7 new, 0 to update and 0 skipped, and shows “Drain Cleaning in Austin, TX” at /drain-cleaning-austin-tx/ as the first page. Because the file has Service, City and State columns, every page also gets an SEO title in the same “Service in City, State” form and a Service item in its schema naming the job and the town.
Rows that need more before they go live
Seven rows that parse cleanly are not seven pages ready to publish. Read each one as a customer would:
- Rows 1 and 2 share everything except the job. Austin drain cleaning and Austin water heater repair have the same phone, fee and hours. Only the arrival window and the job note differ. Give those pages a section that really differs, such as what a drain visit involves compared with a water heater visit, through a
ServiceIntrocolumn or a separate template per service. - Row 7 needs a sentence about the fee. “$159 after hours” makes sense at midnight, but a customer reading it at 10am will wonder whether it applies to them. Add the daytime fee, or a
FeeNotecolumn that says when the after-hours rate starts. - Row 6 quotes on site. Sewer work is priced after a look, which is honest. The page should say what the $129 visit covers and whether it is credited if the customer goes ahead.
- No row lists nearby suburbs. The template outline below has an “Areas we cover around {City}” section, and nothing in the sample can fill it. Add a
Nearbycolumn, such as “Hutto, Brushy Creek, Pflugerville” for Round Rock, or drop the section.
That last gap is the common one: a template section that no column fills. The page ships with an empty heading, or with filler that reads the same on every page.
From seven rows to a full campaign
The planning number for this use case is 6 services × 40 suburbs = 240 pages. Before you build all 240, ask how many of those pairs you would actually send a van for. A company with one crew north of the river might take emergency calls in forty suburbs and sewer work in twelve. Build the pairs you sell, at the arrival times you hit.
For the first market, pick ten suburbs you already get work from. Six services across ten suburbs is 60 rows, few enough to read every draft. The free plugin runs up to 100 rows per run. Pro has no row limit and can queue rows so a set number publish each day.
What to put on every page
Use this list on every suburb page, roughly in the order a customer reads it:
- The job and the town in the heading, the way people type them
- The phone number that rings the crew covering that suburb, as a button that dials on a phone
- The call-out fee or starting price, and what it covers
- The arrival window in plain words: “same day when booked by 2pm”, not “fast service”
- The hours that crew works, and what happens outside them
- One line on how the job is done, written by someone who does it
- The neighboring suburbs the same crew covers
- Your license number, where your trade and state issue one, and proof of insurance
- A way to book that is not the phone, such as a form or a booking link
- Photos of your own vans, crews and jobs, never stock images captioned as local work
If a row cannot fill at least three of these with something true for that suburb, keep it out of the run until it can.
Build the template for the thinnest row
Template outline
- {Service} in {City}: what the visit includes
- Call-out fee and arrival times in {City}
- Opening hours, and what happens after hours
- Areas we cover around {City}
- Questions about {Service} in {City}
- Book a visit or call {Phone}
Habits that keep 240 pages readable
- Put the fee, the arrival window and the call button in the first screen on a phone.
- For the call button, a digits-only column such as
PhoneLinkwith 5125550142 is cleaner in atel:link than “(512) 555-0142”. Tap it on a draft before you generate the rest. - Where a builder field strips curly braces, or a value may be empty on some rows, use the shortcode with a fallback:
[pageforge var="ArrivalWindow" fallback="Call for today's arrival times"]. See Use variables as shortcodes. - Write the rest for the row with the least data. If a sentence breaks when a cell is blank, give that detail a sentence of its own.
- Use spintax sparingly. It changes wording, not information, so it never rescues a thin row. See Spintax.
Location pages for service businesses and Google’s spam policies
Google’s spam policies describe two patterns that matter here. Doorway abuse is a set of similar pages made to catch similar searches, often one per city, that send visitors to the same place without giving them anything of their own. Scaled content abuse is producing many pages mainly to rank, with little value for the people who land on them, however the pages were made.
A suburb page earns its place when the row behind it carries facts that are true for that suburb and nowhere else. In practice:
- Only build pages for suburbs you actually serve, with the arrival time you actually hit.
- Make sure no two URLs target the same search. “Plumber Round Rock” and “Plumbers in Round Rock” is one page, not two.
- Link every page from a hub, so it is part of the site and not a page only a crawler can find.
- Keep weak rows as drafts until you can fill them.
For where the line sits, read doorway pages vs location pages and the quality checklist.
SEO fields, schema and the hub page
SEO fields. PageForge writes each page’s SEO title, meta description, canonical and social fields into Yoast SEO, Rank Math, SEOPress or All in One SEO, or prints them itself when none is active. Write a Meta Description Pattern rather than relying on the fallback:
{Service} in {City}, {State}. Call-out fee {CallOutFee}. Arrival: {ArrivalWindow}. Call {Phone}.
Row 3 then reads “Drain Cleaning in Round Rock, TX. Call-out fee $99. Arrival: Next morning. Call (512) 555-0158.” That is 95 characters, and the longest row in the sample, Pflugerville, comes to 118, both inside the roughly 155 that search results usually show.
Schema. Under PageForge > Settings, set Business Type (Schema) to Plumber, or Electrician, HVACBusiness, RoofingContractor or HomeAndConstructionBusiness for other trades. Set Target Country (Schema) to US. Each page then carries your business as a Plumber, a WebPage item and a Service item for that job in that city. PageForge does not put your address, phone or hours into the markup, and it adds no FAQ or Review schema, so show those details on the page itself. More on what is generated in schema markup automation.
The hub. PageForge Free does not link generated pages to each other. Create an “Areas we serve” page, add the PageForge Sitemap block, group it by city, and link that page from your main menu. Every published suburb page then has a link from a page people and crawlers can reach. See hub pages with the sitemap block.
How to run it in PageForge
- Open PageForge > Data Sources, choose the CSV under CSV Upload and click Upload CSV.
- Open PageForge > Templates and click Add New Template. Build the page with placeholders, or design it in Elementor, Divi or Avada and pick it under Base Layout to Clone.
- In the PageForge Template Settings box, enter the Title Pattern, Slug Pattern and Meta Description Pattern above, set Target Post Type to Page and Generated Post Status to Draft.
- Under PageForge > Settings, set Business Type (Schema) and Target Country (Schema).
- On the Generate screen, pick the template and the CSV, leave When a page already exists on Skip it (create new pages only) and click Check and preview.
- Click Generate 7 pages now, then read the drafts under Pages > All Pages on your phone before you publish.
The first campaign walkthrough shows each screen.
Keeping fees and arrival times current
Fees go up, a crew changes its days, a new hire means a suburb gets same-day service. Edit the CSV, upload it and run it again with Update it from the CSV and current template. PageForge refreshes the pages it generated and keeps their status, URL and parent. A page your office manager rewrote by hand is skipped unless you tick the option to overwrite edited pages. See update pages you already generated.
Two things are not updates. A renamed suburb or a changed Slug Pattern produces a new URL, so PageForge creates a new page and leaves the old one where it is: delete or redirect the old page yourself. And a suburb you stop serving needs its page unpublished, not left live with a fee you no longer charge.
Pro Every Pro plan adds a background queue that publishes a set number of pages a day, and a featured image per row, so each suburb page can show a job from that town. Google Sheets sync, on the Professional and Enterprise plans, lets the office edit a shared sheet and updates each page when its row changes.
Common mistakes
- Building every suburb in the county on day one. Start with the ones you get work from, read them, then grow.
- A fee column with the same value on every row. If it never changes, it belongs in the template, and the page needs some other local fact.
- Template sections with no column behind them. “Areas we cover” with nothing to fill it is the usual one.
- A phone number that does not match the Google Business Profile. Customers notice when the page and the listing disagree.
- A blank Target Country. With no AI provider connected, PageForge falls back to AU, so a Texas plumber gets marked as serving Australia.
- Leaving Target Post Type on the default. A fresh install creates PageForge Page content under a /pageforge/ prefix. Choose Page for root URLs like /drain-cleaning-austin-tx/.
- Publishing without reading. Read five drafts top to bottom before generating the rest.
Free or Pro
The free plugin covers this whole workflow: CSV upload, templates, Check and preview, update mode, schema, SEO plugin fields and the Sitemap block, up to 100 rows per run. Pro has no row limit, and adds the queue, drip publishing, per-row images and AI content per page. Compare them on Free vs Pro. For the general method behind location pages of any kind, see the local SEO location page generator.
Use cases
Blueprints with a sample CSV included
Larkfield Fitness {Location}, {City}A page for every location with its own hours, phone, amenities and directions.45 locations × 1 page = 45 pages, refreshed from one spreadsheetSee the blueprintAgencies and freelancers{Service} in {City}, {State}Run a proven page structure for each client, with their own data, design and sign-off.5 clients × 6 services × 20 towns = 600 pages across 5 sitesSee the blueprintDirectories and listing sites{Category} in {City}, {State}Category and city pages for directories, published only where you have real listings.8 categories × 60 cities = 480 possible pages, published only where listings existSee the blueprintWill Google see my suburb pages as doorway pages?
Not if each page is genuinely useful to someone in that suburb. Google’s spam policies describe doorway pages as near-identical pages made for similar searches that funnel people to the same place. A page with that crew’s phone number, fee, arrival window and hours answers a real question. A page where only the town name changes does not, so leave those rows out until you have something specific to say.
How many suburbs should I start with?
Start with the suburbs where you already get work and can reach quickly, often ten to twenty. Generate five of them as drafts, read them on your phone and fix the template before adding the rest. A small set of well-filled pages tells you more about what brings calls than two hundred thin ones. The free plugin runs up to 100 rows per run, and Pro has no row limit.
Can each suburb page show a different phone number?
Yes. Add a Phone column and put {Phone} wherever the number appears, including the call button. Each page shows its own row’s number, so the Round Rock page can ring the north-side crew while Austin rings the main office. Keep each number identical to the one on your Google Business Profile, and tap the button on a draft before you generate the rest.
Should I make a page for a suburb where I have no office?
Yes, if you really send crews there. Describe how you cover the area: the arrival window, the call-out fee and how to book. Do not show a street address or suggest a branch that does not exist. PageForge’s Service schema names the city served, not an office, so the markup stays honest as long as the page copy does too.
Is it a good idea to show prices on these pages?
Usually, yes. A call-out fee or starting price answers the question many people hesitate to ask on the phone, and it filters out calls you would not book anyway. Put it in a column so it can differ by suburb, say what it covers, and keep it current. When the fee changes, edit the CSV and run update mode instead of editing pages.
Which schema business type should a plumber or electrician pick?
Pick the closest match under Business Type (Schema) in PageForge Settings. Plumber, Electrician, HVACBusiness and RoofingContractor are listed, with HomeAndConstructionBusiness or LocalBusiness for other trades. Set Target Country (Schema) too, or a blank field can mark you as serving Australia. PageForge does not put your address, phone or hours into schema, so show those on the page.
Does PageForge link suburb pages to each other?
Not automatically in the free plugin. Use the PageForge Sitemap block or the [pageforge_sitemap] shortcode on an Areas we serve page to list every published generated page, grouped by city or service. For nearby-suburb links on each page, put the neighboring pages’ URLs in columns and write the links into your template, then click each one on a draft.
Can each page show photos from jobs in that suburb?
In the free plugin, images come from the template, so every page shares them. PageForge Pro, on every plan, can set a featured image and its alt text per row from a Featured Image column, so the Georgetown page can show a Georgetown job. Use photos of your own work and crews, never stock images captioned as local jobs.
Give every suburb you cover a page worth calling from
Install the free plugin, upload the sample CSV and generate seven drafts. You see every title, URL and fee before a single page goes live.
