For SEO agencies, web studios and freelancers
Programmatic SEO for agencies, with each client’s own facts
Sell the same service-and-town page structure to every client without copying a word between sites. Collect each client’s facts in an intake sheet, build the layout in their builder, and send drafts for approval before a single page goes live.
- Free on WordPress.org
- Pending Review drafts for sign-off
- Block editor, Elementor, Divi, Avada
How client campaigns go wrong
The structure is reusable. The copy is not.
Most agencies already sell location pages. The trouble starts when the pages built for one roofer become the starting point for the next, and 120 near-identical pages go live before the client has read one of them.
The usual agency workflow
- Duplicate the last client’s Tampa page, swap the logo and the town, and hope nobody compares the two sites
- Facts arrive by email over three weeks: a warranty here, a phone number there, none of it signed off
- The client reads the pages after they are live and sends back 30 corrections
- A branch number changes and someone spends a day editing pages one at a time
With PageForge
- One intake sheet per client, one row per service and town, approved before generation
- Pages created as Pending Review, so the client approves them inside their own WordPress
- Check and preview shows the counts, the first title and the first URL before anything is written
- Edit the sheet, run update mode, and pages the client edited by hand are skipped
The data
One row per page, every detail that changes
One hypothetical client, a roofer around Tampa Bay. Service, City and State build each URL, SEO title and Service schema, Phone sends each town’s callers to the right office, and Warranty, TypicalJob and Inspection are the facts a homeowner checks before picking up the phone.
| Service | City | State | Phone | Warranty | TypicalJob | Inspection | |
|---|---|---|---|---|---|---|---|
| 2 | Roof Replacement | Tampa | FL | (813) 555-0110 | 10-year workmanship warranty | 2 to 3 days | Free inspection with photos |
| 3 | Roof Repair | Tampa | FL | (813) 555-0110 | 2-year repair warranty | Same day for most leaks | Free inspection with photos |
| 4 | Roof Replacement | St. Petersburg | FL | (727) 555-0122 | 10-year workmanship warranty | 2 to 4 days | Free inspection with photos |
| 5 | Storm Damage Repair | Clearwater | FL | (727) 555-0135 | 2-year repair warranty | Tarping within 24 hours | Photo report for your insurer |
| 6 | Roof Inspection | Brandon | FL | (813) 555-0147 | Not applicable | About 1 hour | Written report the same day |
| 7 | Gutter Installation | Wesley Chapel | FL | (813) 555-0153 | 5-year leak-free guarantee | 1 day | Free measuring visit |
| 8 | Roof Repair | Largo | FL | (727) 555-0168 | 2-year repair warranty | Next day | Free inspection with photos |
Placeholders
{Service} {City} {State} {Phone} {Warranty} {TypicalJob} {Inspection}
Patterns
Title{Service} in {City}, {State}
URL/{service}-{city}-{state}/
Campaign size
5 clients × 6 services × 20 towns = 600 pages across 5 sites
Pages this creates
- Roof Replacement in Tampa, FL
- Storm Damage Repair in Clearwater, FL
- Roof Inspection in Brandon, FL
- Gutter Installation in Wesley Chapel, FL
- Roof Repair in Largo, FL
How it works
Run each client campaign in four steps
01
Collect and sign off the intake sheet
One row per service and town. Ask the client for what only they know: warranty terms, job times, what an inspection includes, which number rings in which office. Get the sheet approved in writing.
02
Build the template in their builder
Design the page in the block editor, Elementor, Divi or Avada, whichever the client’s site already runs. Type {Warranty}, {TypicalJob} and the other column names where values change, and choose the page as Base Layout to Clone.
03
Check, then send five drafts
Check and preview reports new, updated and skipped rows and shows the first title and URL. Generate five rows as Pending Review and send them to the client before you build the rest.
04
Generate the set, then keep it current
Generate the approved rows. When the client changes a warranty or a phone line, edit the sheet and run Update it from the CSV and current template. Free runs up to 100 rows per run. Pro has no row limit.
Built for client work
What an agency needs from a page generator, client by client
Each client keeps their own data, design and approval. PageForge handles the URLs, metadata, schema and updates, so your team’s hours go into the intake and the review.
The generated page
What a homeowner sees on Roof Replacement in Tampa, FL
The first row becomes a page that answers what a homeowner asks before calling a roofer: how long the work is covered, how long the crew will be on the roof, and what the first visit involves. Those answers come from the client, so they are specific enough to act on. The Tampa number, (813) 555-0110, sits near the top and on the call button, so the call reaches the right office.
- A 10-year workmanship warranty stated up front
- 2 to 3 days on site, so the homeowner can plan
- A free inspection with photos as the next step
Before the client sees it
Catch a broken page before it reaches the client’s inbox
Check and preview reads the CSV and template and writes nothing. A title or slug placeholder with no matching column stops the run, and a content placeholder such as a misspelled {Warrenty} is listed as a warning, so you fix it before the client opens a draft.
- New, update and skipped counts before any write
- The first page’s real title and URL
- Every skipped row listed with its reason
After launch
When the client changes a warranty, update the pages, not a to-do list
Edit the row in the sheet, upload it and run the same template with Update it from the CSV and current template. Only pages this template generated are changed, their status, URL and parent stay put, and pages the client edited by hand are skipped.
- Updated pages keep their published status
- Rows with no change are reported as unchanged
- Hand edits are overwritten only if you tick the option
Compared
PageForge versus copying the last client’s pages
The deliverable can look similar on launch day. The difference shows when the client asks for changes.
| PageForge | Copying the last client’s pages | |
|---|---|---|
| Facts specific to the client | From the approved intake sheet | Whatever survives find and replace |
| Client review before launch | Pending Review pages in WordPress | Screenshots or a staging link |
| Duplicate URL check before writing | Yes | No |
| SEO title and meta description per page | Built from patterns | Typed by hand, often skipped |
| Service schema naming the town | Yes | Added by hand, if at all |
| Changing one warranty across 20 pages | One update run | 20 separate edits |
| Client’s own edits protected on updates | Yes | No |
Programmatic SEO for agencies: what you are selling
Programmatic SEO for agencies is one page structure sold many times: a page for each service a client offers in each town it covers, built from a row of facts the client has approved. The structure carries over from client to client. The facts, the design and the sign-off do not.
PageForge does the mechanical part. One CSV row and one WordPress template become one page, with its own title, URL, meta description and schema. The work you bill for is everything a plugin cannot do: choosing the towns worth a page, getting facts out of a busy client, writing a template that reads well for the thinnest row, and running the approval.
This guide follows one hypothetical client, a roofing company around Tampa Bay, from the intake sheet to the first update run. The same structure sits behind the local SEO location page generator page, which covers the single-business version.
Clients this works for
- Home services with several services and a wide service area: roofers, HVAC, plumbers, pest control
- Practices with several offices: dentists, physiotherapists, law firms
- Franchise and dealer networks where each territory has its own phone line
- Any client whose customers search for a service plus a town and call one of the first few results
It works badly for a client with one service in one town, or a client who cannot tell you anything different about the places it serves.
The search pattern behind every client
Look at what a roofing client’s customers type: “roof replacement tampa”, “roof repair largo fl”, “storm damage roof repair clearwater”, “roof inspection brandon”, “gutter installation wesley chapel”. Swap the trade and the shape holds for a dentist or an electrician. That shape, {Service} in {City}, {State}, is why one template structure can serve every client on your books.
What each searcher needs differs by job:
- A homeowner with a leak wants to know how fast a crew can come.
- A homeowner pricing a new roof wants the warranty and how long the crew will be on site.
- A homeowner after a storm needs a photo report the insurer will accept.
Your columns should answer those questions. That is why the sample has Warranty, TypicalJob and Inspection columns, and why a template copied from last month’s dentist would not.
Scope the campaign before you quote it
Pages per client are services multiplied by towns. Keep both numbers honest: only towns the client already takes jobs in, and only services it sells there.
| Hypothetical client | Services | Towns | Pages |
|---|---|---|---|
| Roofer, Tampa Bay | 6 | 20 | 120 |
| Dental group with 4 offices | 5 | 4 | 20 |
| HVAC company, one metro area | 4 | 15 | 60 |
| Five clients sized like the roofer | 6 each | 20 each | 600 across 5 sites |
Two things follow. First, one client can pass 100 pages quickly. The free plugin runs up to 100 rows per run, and Pro has no row limit. Second, 120 pages is more than any client will read in one sitting. Launch a market at a time so every batch gets a real review.
Tip: Price the intake and the review, not the page count. Generating 120 pages takes minutes. Getting 120 rows of approved facts out of a roofer in storm season is the job.
The intake sheet: what to ask the client
Send the client a sheet with the columns already named, one row per service and town. Draft what you can from their site and ask them to correct it. Then get written sign-off before you generate anything.
| Column | What to ask the client | Value in row 1 |
|---|---|---|
| Service | Which services do you sell in this town? | Roof Replacement |
| City, State | Which towns do you take jobs in today? | Tampa, FL |
| Phone | Which number should a caller from this town reach? | (813) 555-0110 |
| Warranty | What do you guarantee, in your own words? | 10-year workmanship warranty |
| TypicalJob | How long does this job usually take? | 2 to 3 days |
| Inspection | What happens on the first visit? | Free inspection with photos |
Once the basics are in, add the columns that make each town different: the neighborhoods each office covers, a recent job in that town the client is happy to describe, a customer quote they have permission to use. Prepare your CSV covers formats, quoting and the Excel export setting.
Why copied copy fails
Do not carry paragraphs from one client to the next and change the business name. Google’s spam policies describe two patterns that careless location campaigns fall into: doorway pages, built to catch similar searches and pass people on to somewhere less useful, and scaled content produced mainly to rank, with little added value. The defense against both is the same. Every page needs facts that only this client, in this town, can state. Doorway pages versus location pages shows where the line sits, and Google’s guide to helpful, people-first content is worth sending to a client who wants 300 towns on day one.
A worked example: a roofer around Tampa Bay
This is the client’s sheet after the first intake call. The company, numbers and terms are hypothetical.
Service,City,State,Phone,Warranty,TypicalJob,Inspection
Roof Replacement,Tampa,FL,(813) 555-0110,10-year workmanship warranty,2 to 3 days,Free inspection with photos
Roof Repair,Tampa,FL,(813) 555-0110,2-year repair warranty,Same day for most leaks,Free inspection with photos
Roof Replacement,St. Petersburg,FL,(727) 555-0122,10-year workmanship warranty,2 to 4 days,Free inspection with photos
Storm Damage Repair,Clearwater,FL,(727) 555-0135,2-year repair warranty,Tarping within 24 hours,Photo report for your insurer
Roof Inspection,Brandon,FL,(813) 555-0147,Not applicable,About 1 hour,Written report the same day
Gutter Installation,Wesley Chapel,FL,(813) 555-0153,5-year leak-free guarantee,1 day,Free measuring visit
Roof Repair,Largo,FL,(727) 555-0168,2-year repair warranty,Next day,Free inspection with photos
The template’s patterns:
| Field | Pattern |
|---|---|
| Title Pattern | {Service} in {City}, {State} |
| Slug Pattern | {service}-{city}-{state} |
| Meta Description Pattern | {Service} in {City}, {State}: {Inspection}. Typical job: {TypicalJob}. Call {Phone}. |
What the seven rows produce:
| Row | Page title | URL |
|---|---|---|
| 1 | Roof Replacement in Tampa, FL | /roof-replacement-tampa-fl/ |
| 2 | Roof Repair in Tampa, FL | /roof-repair-tampa-fl/ |
| 3 | Roof Replacement in St. Petersburg, FL | /roof-replacement-st-petersburg-fl/ |
| 4 | Storm Damage Repair in Clearwater, FL | /storm-damage-repair-clearwater-fl/ |
| 5 | Roof Inspection in Brandon, FL | /roof-inspection-brandon-fl/ |
| 6 | Gutter Installation in Wesley Chapel, FL | /gutter-installation-wesley-chapel-fl/ |
| 7 | Roof Repair in Largo, FL | /roof-repair-largo-fl/ |
Seven rows give seven pages and no duplicate URLs: five services, six towns and six phone numbers. Tampa appears twice with the same number because both services run from one office. The period in St. Petersburg is cleaned out of the slug. Check and preview would report Ready: 7 new, 0 to update, 0 skipped.
Row 1’s meta description comes out as “Roof Replacement in Tampa, FL: Free inspection with photos. Typical job: 2 to 3 days. Call (813) 555-0110.” That is 106 characters, and the longest of the seven, Clearwater, is 128. All of them sit inside the roughly 155 characters that search results tend to show.
Because the sheet has Service, City and State columns, each page also gets an SEO title such as “Roof Replacement in Tampa, FL”, the Service value as its focus keyphrase, and a Service item in its schema naming the service and the town. The rules are in Title, URL and meta description patterns.
Rows that need work before launch
Read the sheet the way a homeowner would and three problems show up:
- Row 5 says “Not applicable”. An inspection carries no warranty, but the template prints whatever the cell holds. With
{Warranty}in the meta pattern, the Brandon snippet would say “Not applicable” to every searcher. That is why the pattern above uses Inspection, which every row fills, and why the warranty belongs in a body sentence of its own. Empty the cell and use[pageforge var="Warranty" fallback="Inspection only, no repair work"]there. - Rows 1 and 3, and rows 2 and 7, are near twins. Roof Replacement in Tampa and in St. Petersburg share the warranty and the inspection offer, and differ only by town, number and “2 to 3 days” against “2 to 4 days”. Roof Repair in Tampa and in Largo have the same problem. Add a local column to these four rows before launch: neighborhoods covered, or a recent job in that town.
- TypicalJob values start with a capital. “Same day for most leaks” and “About 1 hour” read well after a label such as “Typical job:” and badly mid-sentence. Write the template around the data, or ask the client to change the cells.
Rows 4 and 6 are ready as they stand. Storm damage has its own promise, tarping within 24 hours and a photo report for the insurer, and gutters have their own guarantee and a measuring visit.
What to put on every page
For a client’s service-in-town page, check each draft for:
- The service and town in the title, the main heading and the first sentence
- The number for the office that serves that town, near the top and on the call button
- What the work is covered by, in the client’s own words
- How long the job usually takes, so the customer can plan around it
- What the first visit includes and whether it costs anything
- The neighborhoods or nearby towns the same crew covers
- One piece of local proof: a recent job, photos from that town or a quote the client may use
- License or registration details, where the client’s trade shows them
- A link to the hub page, and back from the hub to the page
- No hint of an office in a town where the client has none
Getting client sign-off
- Get the sheet approved in writing before you build anything.
- Generate five rows as Pending Review. Include the longest title (Gutter Installation in Wesley Chapel, FL), the thinnest row and one row per service type.
- The client reads the drafts in their own WordPress dashboard.
- Corrections go into the sheet, not the page. A page edited by hand is protected on later updates, so it stops following the sheet.
- Run the corrected sheet in update mode, then generate the rest and publish them together.
How to run it in PageForge
On each client site, with PageForge Free:
- Open PageForge > Settings. Set Business Type (Schema) to RoofingContractor and Target Country (Schema) to US. Left blank with no AI provider connected, the country falls back to AU.
- Open PageForge > Data Sources, choose the sheet under CSV Upload and click Upload CSV.
- Open PageForge > Templates and click Add New Template. Choose the layout you built in the client’s builder as Base Layout to Clone, then fill in the patterns above in PageForge Template Settings. Set Target Post Type to Page and Generated Post Status to Pending Review.
- On the Generate screen, choose 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 and send the drafts for review.
- Add the PageForge Sitemap block to an “Areas we serve” page, grouped by service or city. See Hub pages with the sitemap block.
- When the client changes a warranty or a phone line, edit the sheet and run it with Update it from the CSV and current template. Pages the client edited by hand are skipped. See Update pages you already generated.
Common mistakes agencies make
- Leaving the default content type. On a fresh install, pages go to the PageForge content type with a
/pageforge/prefix. Set Target Post Type to Page for clean URLs. - Leaving Target Country blank. A Florida roofer gets schema saying it serves Australia.
- Two SEO plugins on one client site. A site inherited from another agency can end up with Yoast SEO and Rank Math both active. Keep one active.
- Publishing straight away. Generate as Pending Review or Draft, every time, for every client.
- Fixing facts on the page. The sheet is the record. Fix it there and run an update.
- Renaming a town after launch. A new value in the slug makes a new URL. The old page stays until you delete or redirect it.
- Leaving access open. Revoke the client’s personal access tokens when the engagement ends.
Programmatic SEO for agencies across several client sites
Install the plugin on each client’s own WordPress site and keep each client’s sheet, template and approvals separate. For audits, turn on the read-only connection in PageForge > Connections and ask ChatGPT or Claude to audit SEO across the generated pages and list the ones missing a meta description. In Free it can read and preview, and it cannot change anything.
Pro On the Professional and Enterprise plans, each client can keep their own Google Sheet. A sync creates and updates pages as they edit it, and removes nothing until you have previewed and applied it. Every Pro plan adds no per-run row limit, a queue that publishes up to a daily limit, per-row images and parent pages, AI content per page, bulk AI meta, and assistant write tools that show a preview before risky changes and keep an activity log.
The same client mix shows up in our local service businesses and multi-location franchises use cases. Compare editions on Free vs Pro, and check how many sites each plan covers on pricing.
Use cases
Blueprints with a sample CSV included
{Service} in {City}, {State}One page per service and suburb for plumbers, electricians, cleaners and other trades.6 services × 40 suburbs = 240 pagesSee the blueprintMulti-location brands and franchisesLarkfield 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 blueprintClinics and healthcare practices{Service} in {City}, {State}Treatment pages for each clinic location, reviewed by the practice before they go live.8 treatments × 4 clinic locations = 32 pagesSee the blueprintWill Google see client location pages as doorway pages?
It can, if the pages only swap the town name. Google’s spam policies describe doorways as near-identical pages built to catch similar searches and send people somewhere less useful. Each page needs facts that belong to that client in that town: a local number, job times, warranty terms, a recent project. Publish only towns the client really serves, and keep thin rows as drafts until the client gives you more.
How many towns should a new client start with?
Start with the towns the client already takes jobs in, usually five to ten, not every town on the map. Generate three to five pages as Pending Review, agree the wording and facts, then add the rest of that market. A client with 6 services and 20 towns is 120 pages, so launch in stages the client can actually read.
Can each location page have its own phone number?
Yes. Add a Phone column and type {Phone} wherever the number appears, including buttons and the meta description. In the sample, Tampa and Brandon ring different 813 numbers and the three Pinellas towns ring their own 727 numbers. If a builder field strips curly-brace text, put the shortcode [pageforge var=”Phone”] in a Shortcode widget instead.
Can clients approve pages before they go live?
Yes. Set the template’s Generated Post Status to Pending Review or Draft, and every generated page waits in the client’s WordPress dashboard until someone publishes it. Send the client five pages first. Once they sign off, publish the set from Pages > All Pages with Bulk actions, or keep publishing in groups.
What happens if a client edits a generated page by hand?
That page is protected on the next update. PageForge stores a fingerprint of each page it writes, and when the fingerprint no longer matches, update mode skips the page and lists it in Check and preview. Tick Also overwrite pages that were edited by hand after generation only after you and the client agree which edits to replace.
Can I reuse one template across client sites?
Reuse the structure, not the words. Each client site has its own templates, and the Export button on the Templates screen downloads a template’s settings as a JSON file for your records. Rebuild the layout in each client’s own builder and theme, and write the body copy from that client’s intake sheet so no paragraph repeats across sites.
Does an agency need PageForge Pro?
Not to start. Free covers CSV upload, templates, Check and preview, update mode, schema and SEO plugin fields, up to 100 rows per run. Pro has no row limit and adds a background queue with drip publishing, per-row images and parent pages, AI content per page and bulk AI meta. Google Sheets sync is on Professional and Enterprise. Site counts per plan are on the pricing page.
Can an AI assistant audit a client site without changing anything?
Yes. In PageForge Free, an administrator turns on the connection under PageForge > Connections, and ChatGPT, Claude or a token-based client can read templates, generated pages and SEO status but cannot write. Ask it to audit SEO and list the pages missing a meta description. Create one token per client site and revoke it when the engagement ends.
Give every client pages they can sign off
Install the free plugin on one client site, upload a five-row intake sheet and generate the pages as Pending Review. The client approves real pages, not screenshots.
