The way you structure your location pages determines how Google distributes authority across them, how quickly new pages rank, and how painful any future restructuring will be. Get this decision wrong at the start and you are looking at months of recovery after a migration.
Three options exist. One is almost always right. One is occasionally justified. One is a trap that sounds strategic but usually is not.
The Three Structural Options and What Each Signals to Google
Subfolders (/locations/macon/): Consolidated Authority
A subfolder structure keeps all location pages under your main domain: example.com/locations/macon/, example.com/locations/atlanta/, example.com/locations/savannah/.
Every backlink to any page on your domain benefits the entire domain. Authority flows freely between your homepage, service pages, blog posts, and location pages because they share the same root domain.
Google crawls subfolders as part of a single website. One robots.txt file, one XML sitemap, one Google Search Console property. Management is straightforward.
This is the default recommendation for local businesses. Unless you have a specific, documented reason to do otherwise, use subfolders.
Subdomains (macon.yourdomain.com): Semi-Separate Entities
A subdomain creates what Google treats as a semi-separate entity: macon.example.com exists alongside www.example.com but does not automatically inherit its authority.
Google’s John Mueller has acknowledged that Google’s algorithms have improved at understanding subdomain-to-domain relationships, but he has also said that connection is not guaranteed. The safer assumption is that subdomains require independent authority building.
Each subdomain needs its own Google Search Console property. Backlinks to the subdomain do not automatically benefit the main domain in the same way subfolder links do. Internal linking between subdomains passes less concentrated authority than internal linking within a single domain’s subfolders.
Subdomains make sense when a third-party platform hosts your location pages and you cannot use subfolders. If your booking system or franchise platform requires a subdomain architecture, treat each subdomain as a distinct website with its own SEO strategy, link building, and XML sitemap.
Microsites (maconplumber.com): Full Independence, Full Isolation
A microsite is a completely separate domain for each location: maconplumber.com, atlantaplumber.com, savannahplumber.com.
Each microsite starts at zero domain authority. Every link, every piece of content, and every trust signal must be built independently for each domain. The authority from your main brand website provides zero benefit to these separate domains.
Microsites multiply every cost: hosting, SSL certificates, content creation, technical maintenance, link building, and monitoring. For a 5-location business, you are managing 6 separate websites.
How Google Treats Authority Across Each Structure
Link Equity Flow: Where Backlinks Actually Land
In a subfolder structure, a backlink to example.com/blog/plumbing-tips/ passes authority to the entire example.com domain, including your /locations/macon/ page. The authority pool is shared.
In a subdomain structure, a backlink to blog.example.com passes authority to the blog subdomain. How much of that authority transfers to macon.example.com is unclear and inconsistent. Google’s algorithms may recognize the relationship, or they may not.
In a microsite structure, a backlink to maconplumber.com gives zero authority to atlantaplumber.com. They are completely separate domains with no relationship in Google’s eyes.
The practical impact: subfolder sites compound authority faster because every marketing effort, every press mention, every directory listing benefits every page on the domain. Microsites divide your link building effort across multiple domains, diluting the impact of each effort.
Domain Authority Inheritance vs Dilution
A subfolder location page inherits the domain authority of the parent domain from day one. If example.com has been building authority for five years, a new /locations/savannah/ page immediately benefits from that accumulated trust.
A new subdomain starts with minimal inherited authority. A new microsite starts with none.
This inheritance effect is why subfolders rank faster. A new location page on an established domain can begin ranking within weeks. A new microsite for the same location may take months to build enough authority to compete, even with identical content.
Index Coverage Implications for Each Model
One domain means one Search Console property to monitor, one index to manage, and one set of coverage reports to review. Problems are centralized and visible.
Multiple subdomains or microsites mean multiple Search Console properties. An indexing error on one subdomain might go unnoticed for weeks if you are not actively monitoring each property. The management overhead scales linearly with the number of separate entities.
For multi-location businesses, this operational burden is a real consideration. Five locations with five microsites means five times the monitoring effort and five times the probability of an undetected technical issue.
Decision Framework: Which Structure Fits Which Business
Single-Location Business with Service Area Pages
Use subfolders. There is no debate here.
Your service area pages live at example.com/services/plumbing-macon/, example.com/services/plumbing-warner-robins/, etc. They inherit full domain authority, they are easy to maintain, and they consolidate all your SEO investment into one property.
Multi-Location Brand with 5-20 Locations
Use subfolders. Each location gets example.com/locations/city-name/ with unique content for each page.
Build a location hub page at example.com/locations/ that links to every individual location page. This hub serves as a crawl entry point and distributes internal link equity across all locations.
Each location page needs genuinely unique content. Swapping city names on otherwise identical templates is worse than having no location pages at all. Google identifies templated content and either deindexes the duplicates or ranks none of them.
Differentiate with: local testimonials, staff photos and bios specific to that location, driving directions from nearby landmarks, community involvement details, location-specific FAQs, and neighborhood descriptions.
Franchise or Dealer Network with 50+ Locations
Subfolders remain the preferred model even at scale. The single-domain approach consolidates authority and simplifies management, which matters more as location count increases.
The structure scales to: example.com/locations/state/city/ or example.com/locations/city-name/. Use geographic hierarchy in URLs for large networks to maintain organizational clarity.
At 50+ locations, invest in a template system that enforces brand consistency while requiring minimum unique content per page. Set a floor: at least 300 to 500 words of content unique to each location, plus location-specific images, testimonials, and staff information.
Franchise systems that give each franchisee a separate website face the worst possible scenario: dozens of thin, low-authority domains competing against each other and against the parent brand. Consolidation onto the corporate domain with location subfolders is almost always the right strategic move.
When a Microsite Makes Strategic Sense (and When It’s a Trap)
A microsite is occasionally justified when: the location serves a completely different market segment that would confuse the main brand (a luxury brand testing a budget offering in a new market), regulatory requirements demand separate legal entities with separate web presences, or a merger or acquisition brings an established domain with existing authority that should not be abandoned.
The trap: microsites sound strategic in a conference room. They promise “focused branding” and “market-specific messaging.” But the SEO cost is severe. Every month a microsite exists, you are building authority for a domain that could have been a subfolder benefiting from your existing authority. The focused branding can be achieved with subfolder pages that have their own visual template.
If the answer to “why not a subfolder” is anything other than a concrete technical or legal constraint, use a subfolder.
Technical Execution Essentials
URL Naming Conventions for Scalable Location Pages
URL structure should be predictable, descriptive, and scalable.
Good patterns:
- example.com/locations/macon-ga/
- example.com/locations/atlanta-ga/plumbing/
- example.com/services/plumbing/macon-ga/
Bad patterns:
- example.com/loc123/
- example.com/?location=macon
- example.com/locations/macon-georgia-best-plumber-near-me/
Include the city and state abbreviation in the slug. Avoid keyword stuffing in URLs. Keep slugs short and consistent across all locations.
For businesses with both location pages and service pages, decide on a hierarchy: location first (/locations/macon/plumbing/) or service first (/services/plumbing/macon/). Either works. Pick one and apply it consistently. Switching later requires redirect mapping.
Breadcrumb Schema and Geographic Hierarchy Signals
Breadcrumb navigation and breadcrumb schema reinforce your site’s geographic hierarchy to both users and Google.
A breadcrumb trail like Home > Locations > Georgia > Macon tells Google this page sits within a geographic hierarchy. When combined with BreadcrumbList schema markup, this creates a clear structural signal.
{
"@type": "BreadcrumbList",
"itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/"},
{"@type": "ListItem", "position": 2, "name": "Locations", "item": "https://example.com/locations/"},
{"@type": "ListItem", "position": 3, "name": "Georgia", "item": "https://example.com/locations/georgia/"},
{"@type": "ListItem", "position": 4, "name": "Macon", "item": "https://example.com/locations/macon-ga/"}
]
}Breadcrumbs also improve internal linking by creating bidirectional paths between parent and child pages in your location hierarchy.
Migration Risks: Changing Structure After Launch
301 Redirect Mapping for Structure Changes
If you are migrating from microsites to subfolders or from subdomains to subfolders, 301 redirect mapping is the critical step that determines whether you retain your existing authority or lose it.
Every URL on the old structure must map to a specific URL on the new structure. Old: maconplumber.com/services/ redirects to new: example.com/locations/macon-ga/services/. Old: maconplumber.com/about/ redirects to new: example.com/locations/macon-ga/about/.
Map every page. Broken redirects or missing mappings mean lost authority and broken user bookmarks. Use Screaming Frog or a similar crawler to generate a complete URL list from the old structure before beginning the migration.
Test redirects before going live. Verify each redirect resolves in one hop, not through a chain. A redirect chain (old URL > intermediate URL > final URL) loses more authority at each hop and slows the crawl.
Timeline for Authority Recovery After Migration
Even with perfect redirect mapping, expect a temporary ranking dip after migration. This is normal. Google needs time to recrawl all redirected URLs, process the authority transfer, and recalculate rankings.
Typical recovery timeline: 3 to 4 months to recover full authority after a structural migration with clean 301 redirects. Fresh backlinks to the new URL structure accelerate recovery.
During the recovery period, do not make additional major changes. No redesigns, no content restructuring, no hosting changes. Stack too many changes and you cannot diagnose whether a ranking issue comes from the migration or from something else.
Monitor recovery through Google Search Console: track indexing status of new URLs, check for crawl errors on redirected URLs, and compare organic traffic levels to pre-migration baselines on a weekly basis.
This guide covers URL architecture decisions. For content strategy on location pages (what to write, how to differentiate), see our hyperlocal content hubs guide. For thin content avoidance on location pages, that discussion lives exclusively in the hyperlocal content guide to prevent overlap.