LOCAL SEO · CITY PAGES
Separate city pages can be useful when a location creates a genuinely different search intent, commercial context or user need. They become risky when the only change is replacing one city name with another.
Short answer
A business does not need a separate page for every city it can theoretically serve. Create a city page when there is real search demand, the business genuinely serves that market and you can add unique local value. Do not build dozens of near-identical pages only to capture “service + city” phrases.
First distinguish three things: location, service area and SEO landing page
1. Physical business location
A real office, shop, clinic or service point where the company operates and, where relevant, customers can visit.
2. Service area
The geographic area a company actually serves. A service-area business can work across several towns without having a physical office in each one.
3. SEO landing page
A page created to answer a specific local search intent. It can describe service in a city even when collaboration is remote, provided the claim is truthful and the page does not invent an office or address.
When does a separate city page make sense?
1. People genuinely search for service + city
Validate local demand instead of assuming every city deserves a page. Search volume, Search Console data and the current SERP can show whether local intent exists.
2. Search Console already shows a local signal
If the domain receives impressions for a city-related query, a dedicated page can help organize that demand more clearly—especially when the current traffic is concentrated on a general page.
3. The local SERP differs from the general SERP
If Google shows local businesses, maps, city-specific directories or local landing pages for the query, the intent is different from a national generic query.
4. A customer in that city needs different information
Local proof, relevant projects, how cooperation works, typical industries, travel or remote-service details and city-specific FAQ can justify a separate page.
When should you NOT create a separate city page?
1. When the only difference is the city name
Pages for Gdańsk, Gdynia and Tczew should not be copies with one word changed. That adds little value to users and creates a scaled-content risk.
2. When every page points to one “real” location
If all city pages create the impression of separate offices but the company has only one location, the architecture becomes misleading.
3. When the company does not actually serve the market
Do not create a location page for a city simply because the keyword looks attractive if the business cannot realistically serve customers there.
4. When location does not affect the decision
Some services are effectively location-independent. A city page may add nothing if buyers do not care where the supplier is based.
5. When there are no resources to maintain the pages
Local pages need updates, links, proof and measurement. Ten strong pages are usually more useful than one hundred abandoned copies.
Doorway pages: where is the line?
A risky model is a large group of pages created mainly to rank for different locations while offering almost identical content and leading to the same destination. A better model gives each location a real reason to exist: distinct local context, relevant examples, different questions, real service availability and a useful conversion path.
Scaled content abuse matters in the AI era
The fact that AI can produce hundreds of city pages quickly does not make that architecture valuable. Automation can help with drafting, but it does not create real experience, local proof or a business reason for a page.
How many city pages should a business have?
There is no correct number. Prioritize locations using four signals:
- Demand: do people search for the service in that city?
- Historical domain signal: does GSC already show impressions or clicks?
- Business importance: can the company genuinely win and serve customers there?
- Ability to create local value: can the page contain something more useful than a changed city name?
What should a good city page include?
- Clear H1 and offer: service + city where that matches real intent.
- Direct answer: confirm whether and how the business serves the city.
- Service scope: what exactly is included.
- Local context: market, customer type or relevant practical context.
- Real work: projects or examples where available.
- Proof: reviews, case studies or verified evidence.
- Local FAQ: questions that differ from the main service page.
- CTA: a clear next step.
How much text should a city page have?
There is no useful word-count target. The page should be long enough to answer the local intent without padding. A shorter page with real local information can be stronger than a long generic article that repeats the city name.
Do you need a local address on every city page?
No. An organic landing page is not the same thing as a Google Business Profile location. You can truthfully explain that the company works remotely or serves customers in the area without claiming a physical office that does not exist.
Should every city page use LocalBusiness schema?
No. Structured data should describe a real entity and real location. Do not generate a fictional LocalBusiness for every city landing page if there is no business location there.
What URL structure should you use?
Keep it simple and consistent. Examples include:
/gdansk/for one broad local landing page/gdansk/web-development/and/gdansk/seo/when separate service intent is justified
A location hub such as /locations/ can organize active city pages and explain the remote/local cooperation model.
Should a city page canonicalize to the main service page?
If the city page is genuinely unique and intended to rank, it normally needs its own canonical. Canonicalizing it to the main service page tells search engines that the local page is not the preferred version. If a city page is effectively a duplicate, the better solution may be to merge or remove it rather than trying to fix duplication with canonicals.
How should you internally link city pages?
Link them from relevant service pages, the locations hub, case studies and useful local content. Avoid creating a footer with hundreds of city links only for search engines.
Should local pages link to one another?
Only when that helps the user. A “Nearby locations” section can make sense, but a circular link network between every city page is not automatically useful.
Can one “areas served” page replace many local landings?
Yes, especially when demand is low or the offer is simple. One strong locations page can be a better choice until GSC or market research justifies dedicated city pages.
One city page or separate service + city pages?
Model A: one city page
Works when the company has a small number of services and local intent is broad.
Model B: separate local service pages
Works when different services have meaningful independent demand and each page can contain unique local value.
How should FreenetPro approach local pages?
The approved FreenetPro strategy is selective rather than mass-generated. Historical signals and business potential should decide the rollout. Priority markets can be developed first, while larger cities are added only after fresh GSC, keyword and SERP validation.
Should you create pages for districts?
Only if users genuinely search at district level and the business can add specific local value. Creating dozens of district pages automatically is usually unnecessary.
Should you create pages for regions or provinces?
Sometimes. A regional page can make sense when the service is bought at that geographic level and the SERP confirms the intent. It should not exist only to create another keyword variation.
Can one city page target several services?
Yes, when the services are closely related and the city intent is broad. If one service dominates demand or deserves substantially different content, a dedicated landing page may be clearer.
How do you avoid cannibalization between the main service page and a city page?
Give them different roles. The main service page should explain the service broadly. The local page should answer how that service works in a specific market. Titles, H1s, internal links and content should reinforce those distinct intents.
Does every local page need to be in the main menu?
No. Important local pages should be discoverable through logical internal linking, but the primary navigation should remain useful to users rather than becoming a list of locations.
What should be unique on every local page?
Changing the city name is not enough. Useful uniqueness can come from local demand, examples, relevant industries, collaboration details, local questions, proof, projects and market context.
Can AI help create city pages?
AI can help organize research, drafts and repetitive formatting, but it should not be used to invent offices, case studies, customer claims or local facts. Human verification and real business evidence remain essential.
How do you measure whether a city page works?
Search Console
Monitor impressions, clicks, queries and which page Google associates with the city intent.
GA4
Measure visits, engagement and conversions by landing page.
CRM or lead data
Track whether the page generates real enquiries from the intended market, not only impressions.
When should you remove or merge a city page?
Consider consolidation when the page has no unique value, receives no meaningful visibility over time, competes with another page for the same intent, represents a market the company no longer serves or cannot be maintained accurately.
From FreenetPro practice: treat local pages as investments, not a keyword list
A useful local page needs a reason to exist, a clear role in the architecture and a measurement plan. The goal is not to publish the maximum number of URLs; it is to build the smallest set of pages that can genuinely help users and search engines understand where the business operates.
Checklist before creating a city page
- Demand: validated local queries
- Business: real ability to serve the market
- SERP: confirmed local intent
- Content: unique local value
- Technical: clean URL, canonical and indexability
- UX: clear service, proof and CTA
- Monitoring: GSC, analytics and lead data
FAQ
Should a business create a page for every city?
No. Create separate pages only for locations with real demand, business relevance and enough unique value to justify a page.
What is a doorway page?
It is a page or group of pages created mainly to rank for similar queries or locations while providing little distinct value and often funneling users to the same destination.
Are service + city pages forbidden?
No. They can be useful when they represent real local intent and contain genuinely useful information. The risk comes from large sets of thin, duplicated pages.
Do you need an office in a city to create an organic city landing page?
No, but you must not imply a physical office if none exists. Clearly explain the real service model.
Can a remote company create city pages?
Yes, if it genuinely serves those markets and the page is truthful and useful.
Does every city page need LocalBusiness schema?
No. LocalBusiness structured data should represent a real business entity and location.
Should a city page canonicalize to the main service page?
Not if the local page is intended to be a unique indexable landing page. If it is a duplicate, consider merging or removing it instead.
Can one locations hub be enough?
Yes. A single strong locations page can be the right starting point before there is evidence to justify separate city landings.
Can AI create 100 city pages?
It can generate text, but mass creation does not create real local value. Publishing hundreds of similar pages increases quality and maintenance risks.
What matters more: number of pages or quality?
Quality and clear intent. A small set of strong pages with real local relevance is more useful than a large set of duplicated location URLs.
The most important rule
A city page should exist because it helps a real user make a local decision—not because a spreadsheet contains another city name.
