What is the difference between city, suburb and service pages?

A city page targets a whole metro ("web design Cape Town"), a suburb page targets a smaller area inside it ("web design Sea Point"), and a service page targets the work itself ("e-commerce website development"), with location secondary.

The split matters because each carries a different competition level and a different risk. City pages have real search volume and warrant deep, genuine pages. Suburb pages have thin volume and the highest doorway-page risk, because they are the easiest to spin from a template. Service pages often have the strongest commercial intent of the three, since someone searching "POPIA-compliant website build" knows exactly what they want. Google rewards the page that best answers the query, so the question for every page is: does a distinct search exist for this, and can I write something genuinely useful and specific to it? If not, fold it into a parent page.

When should you build a city page?

Build a city page when you genuinely serve that metro and can fill it with real local substance. A "web design Johannesburg" or "plumber Durban" page is justified when you have clients there, can name real projects, and can speak to local context rather than swapping one place name into a template.

City pages are usually the safest location pages to build because the search volume is real and the page has room to be substantial. Give each one unique copy: named local clients, area-specific case studies, local pricing context, and an embedded map of the area you cover. Aim for genuine depth rather than a word count, and link to it from your service pages and a locations hub. The trap is publishing a city page for every metro in SA when you only really work in two. If you cannot write something true and specific about serving Bloemfontein, do not publish a Bloemfontein page.

When should you build a suburb page?

Build a suburb page only when you have real, demonstrable proof in that suburb and a genuine search exists for it. A Sandton or Umhlanga page earns its place when you have multiple clients there, local projects to show, and enough volume to justify the page.

Suburb pages are where most SA businesses go wrong. The instinct is to create a page for every suburb in Gauteng, each one identical except the name. That is the exact pattern Google’s scaled-content-abuse policy targets, and it puts your whole site at risk, not just the thin pages. A useful test: if you can regenerate the page by find-and-replacing the suburb name, it is spam. Most businesses are better served by one strong city page that mentions the suburbs they cover than by twenty hollow suburb pages. Build the suburb page only when the local proof is real and the page would stand on its own, the same bar we set in our guide to building location pages without thin content.

When should you build a service page instead?

Build a service page when the service is what people actually search for and location is secondary. Queries like "e-commerce website development" or "website redesign" are about the work, not the place, and a service page targeting them often converts better than any location page.

Service pages are frequently the most underbuilt asset in an SA business’s site. They carry strong commercial intent, they are easier to make genuinely unique because you are describing real work rather than a place, and they avoid doorway-page risk entirely. Give each core service its own page with a clear scope, your process, real examples, and pricing context. Then let your city pages and service pages cross-link: the city page covers who we serve and where, the service page covers what we do and how. This keeps each page to a single intent, which is exactly what Google wants.

How do you decide which page a query needs?

Map the query to the page type by asking what the searcher actually wants:

• "[service] [city]" with real volume and you serve there: city page with genuine local proof
• "[service] [suburb]" and you have demonstrable local clients there: suburb page, only if it can stand alone
• "[service]" with location secondary: service page; mention areas served, do not split by suburb
• "[service] near me": strong Google Business Profile plus your best city or service page; no new page needed
• A suburb with no clients and no proof: mention it on the parent city page; do not build a standalone page
• Many similar suburbs: one city page listing the suburbs beats many thin suburb pages

When in doubt, build fewer, deeper pages. One page that fully answers a query outranks five that half-answer it. A useful sequencing rule for SA businesses: get your core service pages right first, add city pages for the metros you genuinely serve next, and treat suburb pages as the rare exception you only reach for when the local proof is undeniable. Most sites never need to reach the suburb tier at all.

How many location pages is too many?

Too many is the point where you can no longer write something genuinely distinct for each page. There is no magic number, but once you are templating pages and swapping only the place name, you have crossed into scaled-content-abuse territory regardless of how many pages there are.

A practical approach for SA businesses: start with your real service areas only, ship a small set, and watch whether those pages get indexed and earn impressions over a few weeks before adding more. As hard limits, treat more than 500 templated pages, or less than roughly a third unique content per page, as the scaled-content zone. For a typical SA service business the honest number of justified location pages is small: the handful of metros where you genuinely work and can prove it with real clients and projects.

Frequently asked questions