City by service pages for a client without a developer: how to pick the cells, fill them and ship them
Short answer: A city by service page is a page for one service in one place, such as "water heater repair in Mesa". With 5 services and 9 cities you have 45 possible pages, and most should not exist. Score each pair by real jobs done, a fact that differs by place and client sign-off, then build only the pairs that pass, from a table, in batches. Ploy, an AI platform that builds and hosts websites, is one tool for the table-to-pages step, and it is one option among several.
Your local client wants every service in every town, and there is no developer on your team. Here is how to decide which pages to build and how to ship them safely.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The short answer: lay the client's services across the top and its towns down the side, then give each cell a score before you build anything. A cell gets its own page only if the client really did that job in that place and you can put one fact on the page that is true only there. Most cells fail. Cells that fail get a line on a parent page instead. This keeps a 45-cell grid down to a dozen pages a client can defend.
This guide is for agencies and freelancers who look after local business sites (plumbing, roofing, dental, cleaning and similar) and do not have a developer on call. It does not repeat Google's rules on doorway pages and the full page template; those are in service-area pages for local clients, which I suggest reading first. This page is about the grid: choosing cells, the data sheet, client sign-off, tool options with prices, and a test plan. It is information, not legal advice.
This page may contain affiliate links from which Blur Studio earns commissions.
Start with the grid, not the pages
Write the client's services in columns and its towns or neighborhoods in rows. A small plumber with 5 services and 9 towns has 45 cells. A dentist with 8 treatments and 4 towns has 32. If you built every cell, you would have a pile of near-identical pages, which is the pattern Google's spam policy calls doorway abuse when it exists to catch similar searches and funnel people to something else. See doorway pages and thin content at scale.
Instead, make three layers:
- Service pages (one per service, for the whole business). These are the backbone. Every client needs them first.
- Area pages (one per town or group of towns). These say where the crew works, how fast it can come and who to call.
- City by service pages (one per qualifying cell). These are the exception, not the rule.
Link them in a clear hierarchy: service page to area page to the matching cell page, and back. Google's policy text names "substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy" as a problem, so a clear structure is part of the answer.
Score each cell before you build it
Use a four-point score. One point for each yes. Build a cell page at 3 or 4. At 2, put the town on the area page. At 0 or 1, leave it off.
| Question | Where the answer comes from | Yes if |
|---|---|---|
| Did the client do this job here? | Job records, invoices, the booking system | At least 2 jobs in the last two years (my rule of thumb, not Google's) |
| Is there a fact true only for this pair? | Price range from real jobs, local permit or inspection rule, building age, a photo | You can name it in one sentence |
| Is there proof? | A photo with a date, a review from that area with the customer's consent | At least one real item |
| Will the client confirm it in writing? | Sign-off email (template below) | Yes, and it is dated |
Google's own pages say local results come from relevance, distance and prominence, and that there is "no way to request or pay for a better local ranking". A cell page cannot change distance. What it can do is give a real customer in that town a reason to trust and call. So score on usefulness to a person, not on what you hope a search engine does. Check the client's Google Business Profile (the listing on Google Maps and search) first, because Google's guidelines expect an accurate address or service area. See local SEO pages for near me searches.
A worked example with made-up numbers
The business and figures below are invented to show the method. "Northline Plumbing" has 5 services (water heater repair, drain cleaning, leak detection, repiping, fixture install) and 9 towns. That is 45 cells.
| Result | Cells | What happens |
|---|---|---|
| Score 4 (job, local fact, proof, sign-off) | 7 | Own cell page |
| Score 3 | 5 | Own cell page after the client supplies the missing item |
| Score 2 | 14 | A line on the area page: "We also do drain cleaning here" |
| Score 0 or 1 | 19 | Nothing. Towns outside the real driving range are not listed at all |
The agency builds 5 service pages, 7 area pages (the 9 towns become 7 because the 3 smallest share one page) and 12 cell pages, so 24 pages in place of 45 near-copies and no filler. The pilot is the first 10: 5 service pages and 5 of the strongest cell pages. After four weeks the agency checks calls and form leads by page and decides the next batch. No result is promised.
The data sheet for a cell page
A cell page is built from one row. Use a spreadsheet or table with these columns. If a row has fewer than five real facts, set status to "not ready".
| Column | Example |
|---|---|
| Service, town, cell score | Water heater repair, Mesa, 4 |
| Jobs done (count, date range) | 6 jobs since March 2025 |
| Typical price range from those jobs | Made-up: $180 to $420 for repairs, quote for replacement |
| Local fact | Which permit or inspection rule applies, or the water or building issue common there |
| Photo and date | Job photo taken with the customer's permission |
| Review quote and source | Copied exactly, with consent |
| Crew base and drive time | Depot in Tempe, about 20 minutes |
| Next step | Call number, booking link, hours |
| Client sign-off date, reviewer | 12 Nov, A. Smith |
| Status | Ready, not ready, published |
Fill the sheet from the client's job records, not from an AI prompt. AI is useful for a first draft of sentences around real facts, but Google's guidance on AI content says to review it for accuracy, and mass-producing pages without added value can fall under its scaled content rule. Read whether Google penalizes AI-written pages. Use your agency's client approval process for AI-written pages for the sign-off step.
A client sign-off template you can paste
Send this per batch, with the pages attached as a preview link or PDF:
Subject: Please confirm facts for 5 new service pages. Below is each claim we will publish: job counts, price ranges, photos, review quotes, rules and drive times. Reply "approved" for each line, or mark what to change. We will not publish a line you have not confirmed. Please also confirm you have permission to show each photo and review. Pages go live on [date] after your reply.
Keep the replies. If a claim is challenged later, the dated approval protects both of you.
Tool options without a developer, from least to most effort
Prices are as vendors show them in November 2026. Check each vendor's page, because plans and billing terms change.
| Route | Price shown | Fits when | Watch for |
|---|---|---|---|
| No tool: build 10 pages by hand in the client's current site | Free (your time) | You want to see whether any cell pages get visits before investing | Copy-and-paste drift and slow edits |
| Webflow, a visual website builder with a built-in content database | Starter free; Basic $15 a month billed yearly; Premium $25 a month billed yearly | The client's site is already on it, or a designer builds one template | Webflow's pricing page says Basic is for sites that do not need a CMS (a content database) and Premium adds the CMS. Check the page for item limits. Cell pages from a table need the CMS. Agency workspaces are priced separately, so check the page |
| WordPress, the most widely used website system | Software free; hosting and upkeep extra | The client already runs it and someone maintains it | A table-driven setup usually needs a plugin or custom fields, which is developer territory |
| Freelancer or developer | Quote or hourly | You need a feed from the client's job software | Ask for the total over three years |
| Ploy, one option of several | Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote | You want chat-built templates filled from a table | Page limits are not published. Generation uses credits (Ploy's unit for AI work) that do not roll over |
Where Ploy fits
Ploy has a built-in spreadsheet-style database called PloyDB. Per its docs, the Agent (Ploy's built-in AI assistant) builds one template that turns every row into a page, adding a record publishes a page, and edits usually reach visitors within about a minute. Limits listed include 97 columns per table and 128 KB per text value, plenty for the sheet above. For agencies, Ploy's docs describe one organization per agency with one workspace per client, and a choice of "You pay" or "Client pays" billing. Ploy's pages do not describe white-labeling, so ask before you promise a client a branded setup. See Ploy for agencies and Ploy's database explained.
As of November 2026, Ploy's pricing page shows Free at $0 (500 AI credits a day up to 2,000, a ploy.build address), Starter at $50 a month and Pro at $300 a month. A custom domain starts at Starter. Ploy's CMS docs warn "Always review before publishing". The docs describe no duplicate-page check, no uniqueness check and no per-row noindex setting (a tag that asks search engines to leave one page out), so your score and review steps do that job. Ploy's own comparison with Webflow lists heavy programmatic SEO at scale as a reason to pick Webflow, and Ploy's pages do not describe a feed from job-management software.
The quality control is yours with any tool. Whichever route you pick, the quality gate is: would the page exist if search engines did not; can the client name the jobs; does a person read it before it goes live.
Running it week to week
- Batches of 5 to 10. Publish, wait several weeks, check, then add.
- One log. Date published, who approved, and the sheet row for each page, so you can undo anything.
- Tracking. Use a different tracking phone number or a form field "which page" per page type if the client agrees, and check Google Search Console (Google's free tool that shows how a site appears in search) for impressions and index status. "Crawled - currently not indexed" is a common status and a sign to add facts, not pages.
- Merge rule. A page with no calls, no clicks and nothing unique after a few months is merged into the area page or removed with a redirect.
- A page after each job. The best source of new cells is new jobs. Add a row when a job finishes and the customer agrees to a photo.
Test plan with pass and fail rules
| Check | Pass | Fail |
|---|---|---|
| Two cell pages side by side | Price, rule, photo and review all differ for real reasons | Same text with a swapped town |
| Client sign-off | Every claim approved in writing | Any unapproved claim |
| Phone check | Call and booking buttons work and the page loads fast | Broken button or slow load |
| URL Inspection in Search Console | Page is eligible, or the reason is clear | Blocked by robots.txt (a file that tells search engines which pages to skip) or a stray noindex you did not intend |
| After 4 to 8 weeks | Some pages produce calls or forms | No activity: merge or remove |
Who should skip this, and who should skip Ploy
- The client has fewer than three towns. A good areas page and the service pages are enough.
- The client has no job records. Fix that first. No tool supplies local proof.
- Skip Ploy if the client's site already runs well on a system you know, or if you need per-page noindex and redirect-map controls that Ploy's docs do not describe.
- Skip bulk pages if the client wants 100 towns it has never served. A page that claims service in a place the business does not cover is a trust problem, not only an SEO one.
How I'd approach this
I would sell the grid as a fixed first project: build the service and area pages, score every cell, and publish 10 pages with sign-off. Then a small retainer to add a page after each real job. I would put the score and the sign-off in the contract so the client understands why 45 cells became 24 pages. I would tell the client the true thing: more pages is not the goal, more proof is.
For the table-to-pages step you can try Ploy on its free plan with a copy of the sheet for one client, and ask Ploy how many pages your plan allows and how to keep a page out of search before you rely on it. If the client needs the custom version, such as pulling job photos and prices straight from its job software, or ongoing care of many pages, Blur Studio builds that with CRM and calendar connections and ongoing care. For the field-business view of the same idea, see landing pages for every service and suburb, and for faster agency delivery see building client websites faster with AI.
First-week plan. Day 1: build the grid with the client's job list. Day 2: score every cell. Day 3: fill sheet rows for the top 5 cells. Day 4: build the 5 service pages and 5 cell pages in the tool you picked. Day 5: send the sign-off email. Day 6 to 7: fix, check on a phone, and publish only what is approved.
You may also want franchise and multi-location websites.
You may also want making hundreds of pages from a spreadsheet.
Questions people ask
How many city by service pages should a client have?
As many as pass the score, usually far fewer than the grid. In the made-up example above, 45 possible pairs became 12 cell pages. Start with 5 and add after you see calls. For the full rule set see service-area pages for local clients.
Does Google ban location pages?
Google's spam policies name doorway abuse and scaled content abuse, and they are about purpose and value rather than a ban on pages for places. A page that serves a real place with real facts is different from near-copies built to catch searches. See doorway pages and thin content at scale.
Can I do this without a developer?
Yes, if the site tool can build one template from a table. Webflow (on plans with its CMS) and Ploy both can, per their docs. WordPress usually needs a plugin or custom fields. A developer helps most when data must come from the client's job software.
Can AI write the pages?
It can draft sentences around facts you supply, but a person must read and the client must approve every claim. Google says to review AI-written content for accuracy. See does Google penalize AI-written pages.
How many pages can Ploy make for one client?
Ploy does not publish a page limit. Its docs show limits of 97 columns per table and 128 KB per text value, and generation uses credits that do not roll over. Ask Ploy about your page count before you commit. See Ploy pricing.
What do I tell the client about results?
Tell them no ranking or lead number is promised. Local results depend on relevance, distance and prominence, and Google says you cannot pay for a better local ranking. Report on calls, forms and Search Console by page instead.
When should a weak page be removed?
If a page has no calls, no clicks and nothing unique after a few months, merge it into the area page or take it down and redirect it. Do not leave thin pages up in case they help.
Do I need the client's permission for photos and reviews?
Yes. Get written permission for any photo of a customer's home or property and for any review you quote. Never write or buy reviews. Google's review policy bans incentives for reviews.
More in this topic: Websites: local, property and Dubai pages (4 guides) →
Sources
- Ploy CMS docs: review before publishing (Ploy)
- Reviews policy (Google Business Profile Help)
- Spam policies for Google web search (Google Search Central)
- Using generative AI content on your website (Google Search Central)
- Improve your local ranking on Google (Google Business Profile Help)
- Guidelines for representing your business on Google (Google Business Profile Help)
- Page indexing report statuses (Google Search Console Help)
- Ploy Database (PloyDB) docs, updated November 18, 2026 (Ploy)
- Ploy pricing page (Ploy)
- Webflow pricing (Webflow)