A franchise group inherits three website patterns after a few years of growth. Corporate locations live at example.com/locations/phoenix. One franchisee uses phoenix.example.com. An acquired operator still owns phoenixplumbing.com.
All three URLs can be crawled. That does not make all three equally maintainable.
The practical decision is not whether Google likes a slash more than a dot. It is whether the URL boundary matches who controls the brand, content, software, analytics, local proof, and future migrations. For most multi-location service brands with shared governance, subfolders are the cleanest default. Subdomains and separate domains are defensible when they represent a real operating boundary.
Important
Google does not publish a ranking rule that says franchise location pages must use subfolders. Choose the structure your team can keep crawlable, internally linked, canonical, locally accurate, and stable through acquisitions and rebrands.
For a 20- to 500-location HVAC, plumbing, pest control, restoration, garage door, med spa, or franchise service brand, the wrong architecture creates slow operational damage. New locations launch on inconsistent templates. Google Business Profiles point to generic or obsolete URLs. Regional teams cannot see the same Search Console data. A later consolidation becomes a portfolio-wide site move.
If the goal is a repeatable branch-page system, multi-location local SEO software should connect the page, profile, review, and measurement owners before the URL format is locked.
The short answer
- Use subfolders by default when locations share one brand, CMS, templates, security team, analytics program, internal-link system, and publishing process.
- Use subdomains for a real boundary when a region or operator has separate software, permissions, releases, or site ownership and can maintain a complete local experience.
- Keep separate domains for distinct operating identities when an acquired or franchised brand remains meaningfully independent and has the resources to run a full website rather than a thin local copy.
This is a governance rule, not a ranking formula. Google recommends simple, descriptive URL structures and consistent organization. Its AI features guidance points back to the same Search fundamentals: crawlable pages, useful text, internal links, structured data that matches visible content, and current Business Profile information. There is no special location-page architecture required for AI Overviews or AI Mode.
Google does not publish a subfolder ranking rule
Claims that subfolders automatically inherit more authority than subdomains are common in agency decks. Google's current documentation does not give franchise brands that guarantee.
Google's URL structure guidance asks for simple, descriptive, logical URLs. Its crawlable link guidance explains that normal links help Google discover pages and understand their relationship. Neither document declares a universal winner between a branch path and a branch subdomain.
There is one visible search distinction worth knowing. Google's site name documentation supports site names at the domain or subdomain level, not at the subdirectory level. A subdomain can therefore present as a separate site in that context. That is useful when it matches reality. It is a reason to avoid subdomains when the location is not supposed to look or operate like a separate website.
The better evaluation is concrete. Can customers and crawlers reach every branch through normal links? Does each location have one stable canonical URL? Can corporate and local owners keep facts current? Will a rebrand require one controlled migration or dozens of separate projects?
Use subfolders when the brand runs one operating system
A shared brand usually benefits from a shared publishing boundary. An HVAC roll-up can keep Dallas at example.com/locations/dallas and Tampa at example.com/locations/tampa while using the same location schema, service taxonomy, accessibility standards, security patches, and analytics events.
This does not mean every page should be identical. The location page checklist for multi-location service brands still requires branch-specific services, coverage, hours, phone routing, reviews, photos, credentials, and local proof. A shared folder structure should make those differences easier to govern, not hide them inside cloned copy.
Subfolders also make the browse path easy to explain. A crawlable directory can link to state or region hubs and then to branch pages. Service pages can link to the locations that actually offer the service. The location finder architecture guide covers how to expose those pages without indexing every map state or ZIP-code result.
For marketing leaders, the benefit is fewer systems to reconcile. One change to the branch template can improve phone labels, schema, breadcrumbs, or conversion tracking across the portfolio. Operations still owns local accuracy, but the software and publishing controls remain visible to the brand.
A subdomain should represent a real boundary
A subdomain can be the right choice when the separation already exists in the operating model. A regional franchisee may run a different CMS, employ its own development team, control releases, and maintain the local service catalog. A hospitality group may operate booking and content systems that cannot safely share the parent site's deployment process.
The test is whether the operator can maintain a site, not just a page. The subdomain needs its own crawlable navigation, local content, canonical controls, sitemap coverage, structured data, security ownership, accessibility review, analytics, and incident response. Corporate still needs a normal link path from the main domain and a clear record of who owns each public fact.
Search Console should follow that boundary. Google's property documentation says a Domain property includes all protocols, subdomains, and paths for a domain. A URL-prefix property can isolate a specific subdomain or folder. Corporate can keep portfolio visibility through the Domain property while granting a regional operator narrower access through a URL-prefix property.
Do not reverse that logic. A reporting preference is not a reason to split the public site. Search Console can report on a folder without moving it to a subdomain.
Keep separate domains only for a distinct identity
Separate domains make sense when an acquired company or franchisee remains a distinct public brand with its own customer promise, leadership, content, and operating responsibility. A home-service roll-up may deliberately preserve a trusted local brand for several years. A med-spa franchisee may own a mature local site that serves more than one business line.
The cost is independence. Each domain needs enough useful content and local proof to stand on its own. It needs security updates, consent and analytics controls, internal links, sitemaps, structured data, profile targets, and an accountable owner. A five-page domain that copies corporate service text and sends every lead to the same national form is not meaningful local independence.
If the brand later consolidates those domains, treat the work as a migration. Google's site move guidance calls for an old-to-new URL map, permanent server-side redirects, updated internal links and canonicals, submitted sitemaps, and monitoring of both properties. Redirecting every old page to the new homepage discards the branch and service relationships customers were using.
The roll-up rebrand workflow extends that migration beyond the website. Google Business Profiles, citations, review destinations, phone routes, booking links, and former-name context need to move by market.
Every structure still needs one canonical branch URL
Subfolders do not rescue a weak location system. Subdomains do not create local relevance. Separate domains do not substitute for proof.
Every real branch needs one URL that the organization treats as primary. The location finder, service pages, XML sitemap, LocalBusiness structured data, and Google Business Profile website field should reinforce that same destination. Alternate campaign or tracking URLs should resolve cleanly to it rather than compete with it.
Google's canonical guidance recommends redirects and canonical link annotations as strong signals, with sitemap inclusion as a weaker signal. Those signals work best when they agree. A page that declares one canonical while the locator, sitemap, and Business Profile point elsewhere creates a preventable conflict.
The branch page should also use the most accurate LocalBusiness structured data that the visible content supports. Schema should confirm the public name, URL, address or service area, hours, phone path, and relationship to the parent organization. It should not invent a storefront for a service-area business or use a parent-company address for every franchisee.
Audit ownership before changing URLs
Before choosing a new pattern, build an inventory that can survive implementation. For every active location, record:
- Current public URL, canonical URL, indexation state, and sitemap source
- Parent brand, local operator, CMS owner, release owner, and security owner
- Google Business Profile website target, booking target, phone route, and primary location ID
- Search Console property, analytics property, consent setup, and conversion events
- Internal links from the location finder, service pages, region pages, and acquisition pages
- Redirect destination and former-name context for any URL that will move
The inventory exposes the real constraint. If corporate owns every template but cannot update local hours, the problem is not subfolders. If franchisees own complete sites but corporate cannot see their crawl or conversion data, the problem is not necessarily separate domains. The missing piece is a responsibility and access model.
Pro Tip
Choose the smallest website boundary that matches real ownership. Then document exceptions instead of letting each new franchisee or acquisition invent another pattern.
A 30-day architecture decision
Week 1: classify the portfolio
Group locations by operating identity, not by current URL. Mark which branches share the parent brand, publishing system, analytics, and customer promise. Flag acquired brands and franchisees with genuine independence. Identify orphaned sites and subdomains with no accountable owner.
Week 2: choose the default and the exception test
Write one default rule for new locations. For most centrally governed service brands, that will be a subfolder under one location directory. Write a stricter exception test for subdomains and separate domains: named owner, complete site duties, durable technical boundary, and a documented handoff if the exception ends.
Week 3: map discovery and measurement
Confirm that every retained location URL is reachable from normal links, appears in the correct sitemap, uses a self-referencing canonical, and has the right profile target. Set up the Domain and URL-prefix Search Console properties the owners need. Do not change URLs just to make a report easier to filter.
Week 4: pilot one migration
If consolidation is needed, move one representative market before changing the portfolio. Validate redirects page by page instead of checking the homepage alone. Update internal links, canonicals, structured data, sitemaps, profile URLs, booking destinations, and analytics. Watch crawl errors, indexation, local leads, and old-brand discovery before setting the next migration wave.
The finished architecture should be boring in the best way. A new location receives one predictable URL. A customer can reach it through the locator and service pages. The branch and brand know who maintains the facts. Search and AI systems can discover the page through the same public relationships customers use.
Sources
- Google Search Central: URL structure best practices. Supports the simple, descriptive, logical URL guidance.
- Google Search Central: links crawlable by Google. Supports the normal-link discovery and anchor guidance.
- Google Search Central: canonical URL guidance. Supports the redirect, canonical, and sitemap signal guidance.
- Google Search Central: site moves with URL changes. Supports the migration, redirect, sitemap, and monitoring workflow.
- Google Search Central: AI features and your website. Supports the use of standard Search fundamentals for AI Overviews and AI Mode.
- Google Search Console Help: property types. Supports Domain and URL-prefix property boundaries.
- Google Search Central: LocalBusiness structured data. Supports branch-level structured data guidance.
- Google Search Central: site names. Supports the domain and subdomain distinction for site names.
- Schema.org: parentOrganization. Supports expressing a branch's relationship to its parent organization.
Amadeus Peterson is the CTO & Co-Founder of Cheers, the local search platform for multi-location service businesses.