Regional SEO: Why One Site Across 20 Cities Beats 20 Separate Sites
Common myth: a site per city. In reality one site with the right location architecture beats it on traffic and budget. Here's the structure I use across 30+ cities.
On this site I have 39 locations × 18 services = 702 location pages on one domain. A month after launch — 1200+ organic impressions on regional queries. Here's why this model beats “20 separate sites.”
Domain authority is a slow currency
Every new domain starts at zero. Google needs time to trust it. 20 new sites = 20× longer to result. One site = one authority shared across every location page. By month 6 the difference is ×3-5 in traffic.
Scalable architecture
The structure I use: /locations (all-cities hub) → /locations/[city] (city hub) → /locations/[city]/[service] (city × service combo). On this site that's 1 hub + 39 city hubs + 702 combo pages. All unique through a template + city-specific fragments.
Content that doesn't duplicate
Biggest risk = duplicate content. Solved with template + 30% city-specific data: local landmarks, local case studies, climate / business specifics, testimonials from people in that city. If you don't have that depth — start with 5 key cities and do them properly. Don't clone.
Internal linking as a resource
20 separate sites can't link each other without looking spammy. One site links every page naturally: city → service, service → city, hub → all. Boosts crawl rate and authority of each page.
Technical: hreflang and canonicals
Multi-language? On one site it's hreflang in head. On 20 sites it's 20 separate setups and SEO-conflict risk. One site = one control surface.
Budget
20 separate sites: $20–40 hosting × 12 = $4.8–9.6k/year + 20 SSLs + 20 backups. One site: $200–500/month on a real VPS. 5–10× savings.
Local signals
NAP consistency, Google Business Profile per city (mandatory even with one site!), local backlinks, reviews on Maps. That's separate work, parallel to the site. More important than the domain structure.
When you do need separate sites
If the brand is genuinely different across regions (different names, different owners, legally separate companies) — then yes. In 90% of other cases, one site.
How I ship this on projects
1) Pick the top 5 cities by demand → full landing pages for them. 2) Template pages for the rest with 30% localization. 3) Sitemap, hreflang, schema set. 4) Google Business Profile per city. First organic numbers in 4–6 weeks.
More articles
Tilda vs Custom Build: An Honest Comparison (No Agency Whining)
Half the agencies say “custom only.” Half the no-code crowd say “Tilda is enough for everyone.” Reality is in the middle and the choice depends on 5 specific factors.
Mobile App Design: 5 Decisions That Boost Retention by 30%+
What keeps users in your app isn't “pretty design.” It's specific UX choices that feel natural. Here are 5 that consistently move retention in my projects.
CRM vs ERP vs SaaS: Which One Does Your Business Actually Need
I see it constantly: businesses buying expensive ERP when CRM is enough — or the reverse. Here's the difference in plain English plus a checklist for picking the right tool for your stage.
A Landing Page That Converts: My 14-Point Checklist for Every Project
14 hours of redesign vs a 14-point audit — sometimes the gap between the two is 70 conversion points. Here's my checklist. Map it onto your own landing.
MVP in 6 Weeks: When Speed Helps and When It Kills the Product
'MVP in a week' is a great slogan and often a trap. Here's what actually fits in 6 weeks, what doesn't, and the price you pay either way.
How to Cut Homepage Bounce Rate in Half: A Practical Framework
Bounce rate isn't a 'bad metric.' It's an honest signal that your homepage doesn't answer the question your visitor showed up with. Here's how to fix it.