Multi-location SEO for construction firms: architecture that scales.

The duplicate-content trap that kills multi-location SEO

Most contractor sites with multiple service areas get this exactly wrong: they create city pages by swapping the city name into otherwise-identical content. Google's algorithm spots this in seconds and either picks one canonical version (only one of your cities ranks) or deindexes them all. Either way, you've built dead pages.

The fix isn't to avoid per-city pages - they're essential. The fix is to make each one genuinely city-specific.

URL architecture options (and the right one)

Three patterns to choose between:

1. Subdirectory: yoursite.com/austin/kitchen-remodel. Recommended for most firms. Inherits domain authority, easy to manage.
2. Subdomain: austin.yoursite.com. Useful for franchises with independent local marketing teams. Each subdomain ranks somewhat independently.
3. Separate domains: austin-yourbrand.com. Almost always wrong for construction. Splits authority, multiplies maintenance, confuses GBP.

Default to subdirectory. Use subdomain only if there's a real organizational reason. Avoid separate domains.

Multi-location Google Business Profiles

Each physical location gets its own GBP. Service-area-only markets (where you serve but don't have an office) cannot have a GBP - Google enforces this. So:

• Real office in Austin → GBP for Austin location.
• Service to Round Rock from Austin office → no GBP for Round Rock; instead, a strong city page on the website.

Manage multiple GBPs through Google Business Profile Manager (the bulk tool). Each location: distinct address, distinct phone (use call tracking), distinct hours, distinct photos, distinct posts. Google detects duplication.

What city-specific content actually looks like

For each city page, include genuinely local content:

• Local neighborhoods/zip codes served, listed by name
• Recent local projects - at least 3, with photos and addresses (with permission)
• Local code/permit specifics ("In Austin, kitchen remodels over $X require permitting through...")
• Local testimonials from clients in that city, with neighborhood mentioned
• Local team if you have local crew/dispatchers
• Local business mentions - supply chain partners, local materials providers
• Driving distance/time from your office to common neighborhoods

If a page has 800+ words of genuinely local content, Google treats it as distinctly local. If it has 300 words of templated boilerplate, Google treats it as duplicate spam.

Multi-location schema

Each city page gets its own LocalBusiness schema with the right geo coordinates and area-served polygon. Plus a parent Organization schema on the homepage with each location listed via hasMember. This signals to search engines (and AI assistants) that you're one organization with multiple verified physical or service-area presences.

Scaling beyond 5 cities

Below 5 cities, you can hand-author city pages. Above 5-10, you need a content system:

1. Define a city-page template with required fields (neighborhoods, projects, code notes, testimonials, team).
2. Each new city expansion requires populating those fields with real data - not autogenerated.
3. CMS or static-site setup so updates can be made without dev involvement.
4. Quarterly review: which city pages have stale projects? Refresh them.

Done well, a 30-city operation can rank in all 30 with 60-80 hours of content effort spread across the build and 4-6 hours/quarter of maintenance.