This Forsan Pools case study answers one question: how does a single site serve customers who search by city and by service at the same time? The answer was a library of 183 pool-service pages, mapped before a single screen was drawn, and every count can be checked on the project page itself.
What the Forsan Pools case study covers
The client is a pool company in Riyadh whose customers search by city and by service together. Everything in the table below is published on the project page.
| Item | What it is | Verification |
|---|---|---|
| Page library | 183 pool-service pages | Published, countable |
| Coverage weighting | Riyadh alone carries 136 of them | Published |
| Home page | Services, coverage, three pricing tiers, a four-step process, a before-and-after gallery, eight FAQ answers and contact, on one scroll with in-page navigation | Published |
| Pricing | Three tiers with what each includes, published rather than held back for a phone call | Published |
| Contact path | Every call to action opens WhatsApp with the message already typed | Published |
| Technical setup | Schema for Organization, WebSite, WebPage and Article, canonical tags throughout, and four sitemaps covering posts, pages, categories and video | Published |
| Language | Built in Arabic with full right-to-left layout from the start | Published |
Every line is on the Forsan Pools project page, and the pages can be counted on the live site. What you will not find in the Forsan Pools case study is a ranking position or a traffic figure. The last section explains why.
Why one general page per country stops working
Before anything was decided, we recorded what the competing sites did and did not do. The pattern was one general page and a phone number, a page that matches nobody exactly. Somebody typing a service and a city asks a narrow question; a national page answers a wider one.
The gap is not keywords. It is four things a buyer wants settled fast: do you cover my area, how soon, what does it cost, and what happens after I message you.
When is a service times city architecture the right call?
- You genuinely serve that city. Without a crew there, the page is a promise you cannot keep.
- Demand is phrased with both terms, service and place in one query, not service alone.
- Something real changes per city: response time, price band, access constraints, nearby work you can point to, the pool type that dominates locally.
- Proximity drives conversion. In field services, distance is the first question, not the fifth.
- You can maintain the count. A large library needs review or it decays into abandoned pages.
Where does this cross into doorway pages?
Doorway pages are built to catch near-identical queries and push everyone to one destination, with no value of their own. Google files them under its spam policies and demotes them rather than ignoring them. The definition is published in Google’s spam policies documentation.
The practical test takes a second. Delete the city name: is anything left that belongs to that city? If not, it is a doorway page whatever your intent was. The Forsan Pools case study puts the same standard plainly, describing each page as a real page for a real search rather than a template with the city name swapped into the title.
How do you build the template so the pages are not clones?
Templates are not the problem. Thin templates are. The direct lesson from the Forsan Pools case study is that the varying fields get settled before any copy is written:
- Decide what really changes: city, price band, response time, neighbourhoods covered, the questions that recur in that area.
- Write one local section per page that could not be generated: a situation common in that area and how the crew handled it.
- Put the price, or its range, on the page. Hiding it asks for extra effort at the moment someone is comparing suppliers.
- Vary the FAQ by city instead of repeating the same five answers. Real questions come from sales calls.
- Use real job photos where they exist, and do not repeat one image across a hundred pages.
- Have a person read every page before it ships. If five in a row feel like one page to you, they will to a reader.
Shipping in batches beats shipping everything at once: the first batch tells you whether the template holds up.
How do internal links work at this size?
Past a hundred pages, internal linking decides which pages get found and which sit isolated. The pattern that holds: a hub per service collecting its cities, a hub per city collecting its services, and every leaf page linking to both hubs plus a few geographic neighbours.
What we avoid is a footer stuffed with the whole library on every page. Sitemaps carry the rest: this project runs four, covering posts, pages, categories and video.
What the Forsan Pools case study says about sequencing
The order was: read the competition, settle the page map before drawing a screen, approve the design, build and fill, then keep the search work running. Structure decided the design rather than the other way round. Schema and sitemaps went in during the build, and search work carried on from launch day because it was part of the build.
The client is in Riyadh and the work was delivered remotely from our office in Sheikh Zayed, Giza. We have no office in Riyadh. A long relationship with this client on home services in Saudi Arabia, across design, development and search, is why the brief needed little translating.
Why the Forsan Pools case study publishes no rankings
The project page says so outright: no positions and no traffic figures, because rankings move and a number that was true when it was written would not be true when you read it. What is published is what was built, and every count can be checked.
If you are weighing a similar architecture, look through our project work and the types of websites, then our website design and development service.
Frequently asked questions
How many service pages does the Forsan Pools site have?
183 pool-service pages, with Riyadh alone carrying 136 of them, as stated in the Forsan Pools case study on the project page. Both counts can be checked on the live site. The library was not published in one day; it grew as the work extended into more cities.
Can a large page count get a site penalised?
Volume is not the trigger. The trigger is pages that are substantively identical and exist only to catch queries. When each page carries different real content and the service is genuinely offered in that city, a large count is architecture, not a violation.
Why was WhatsApp the contact path instead of a form?
Because it is the channel this market actually uses. Every call to action opens WhatsApp with the message already typed, which cuts what the visitor has to do down to one tap. Forms earn their place when you need detail before quoting, which was not the case here.
Is publishing prices always a good idea?
Not always, but it helps when the service splits into clear tiers. Here three tiers were published with what each includes, because a first visit is mostly a comparison between suppliers, and a page that withholds price drops out of it early.
Where should I start if I want this architecture?
Start with the page map, not the design: which pages exist, how a city page relates to a service page, and where a visitor lands from a search naming both. Then publish a small batch, measure it, and correct the template before scaling.
Is this architecture right for your business?
Send your service list and the cities you genuinely cover, and we will come back with a proposed page map and a straight opinion on whether a large count helps you.
Request a quote · Message us on WhatsApp · Call us
Arqam Web
44 Central Axis, Al Saraya Mall, Lower Ground, Entrance 2, Sheikh Zayed, Giza, Egypt
Phone and WhatsApp: +20 111 872 1404 · Email: info@arqamweb.com
