Multi-facility senior living website architecture: one site or many

The website architecture decision for a multi-facility senior living operator is the second-most-consequential digital decision after the platform choice. Get it right and the system scales gracefully across 8 or 15 or 30 facilities. Get it wrong and the operator is rebuilding within three years.

There are three legitimate approaches. Each has clear use cases and clear failure modes. This is how to choose between them.

The three architectures

Approach 1: Single site with facility pages

One website at the parent domain. Each facility has its own page (or set of pages) within the single site. Architecture: parentdomain.com/communities/westchester, parentdomain.com/communities/riverdale, etc.

When this works:

• Smaller portfolios (3-7 facilities)
• Tight geographic concentration (one state or one major metro)
• Highly consistent brand and care model across facilities
• Limited facility-level marketing budget or capability
• Strong central marketing function with operational ownership

When it doesn’t:

• Larger portfolios where facility pages get lost in the navigation
• Geographic distribution across states or distinct markets
• Facilities with meaningful local equity or brand differences
• Strong local SEO competition where each facility needs its own domain authority
• Facilities competing in different price tiers or care types

Operational implications:

• Single CMS to maintain
• Single SEO investment that benefits all facilities through internal linking
• Local SEO is harder; the parent domain ranks for “senior living [city]” queries but each facility-specific page has to fight for local search results
• Centralized analytics and lead tracking
• Lower total cost than multi-site
• Less flexibility per facility

This is typically the right architecture for small multi-facility operators with concentrated geography. It stops scaling well around 8-10 facilities.

Approach 2: Hub-and-spoke (parent site plus facility sites)

A parent site at the operator’s domain serves as the brand hub. Each facility has its own dedicated site (often on its own subdomain or domain) that’s part of the larger system but functions independently.

Architecture options:

• westchestercommunity.com (independent domains per facility) plus parentbrand.com
• westchester.parentbrand.com (subdomains per facility) plus parentbrand.com
• parentbrand.com/westchester (path-based subsites within parent domain) plus the parent home page

When this works:

• Mid-to-large portfolios (8-25 facilities)
• Geographic distribution across multiple markets
• Mix of facility types (independent, assisted, memory care, skilled nursing)
• Local SEO matters significantly per facility
• Operator wants central brand strength plus local distinctiveness
• Each facility has enough scale to support its own digital presence

When it doesn’t:

• Very small portfolios where each facility doesn’t need its own site
• Very large portfolios where 30+ separate sites become unmanageable
• Operators without the central design system to keep facilities feeling unified
• Limited budget for ongoing maintenance across multiple sites

Operational implications:

• Stronger local SEO per facility (each facility has its own domain authority and local signals)
• Higher initial build cost (each facility site has to be built)
• Higher ongoing maintenance cost (each site needs updates)
• Brand consistency requires explicit design system enforcement
• Lead routing and analytics get more complex across multiple properties
• Most flexibility per facility while preserving brand connection

This is the architecture most multi-facility healthcare operators end up with. The hub-and-spoke balances local relevance with central brand investment, and scales reasonably from 8 to 25 facilities.

Approach 3: Distinct facility sites without a unifying parent

Each facility has its own site, with no central operator brand visible. The operator’s identity is back-office; families never encounter it.

When this works:

• Operators with very different facility brands across the portfolio (e.g., luxury memory care at one price tier and standard skilled nursing at another)
• Facilities that the operator has acquired and explicitly wants to keep distinct
• Cases where the operator’s name carries no useful equity for families (rare in senior living)

When it doesn’t:

• Most multi-facility operators (the operational cost of maintaining truly separate brands is significant and rarely justifies the benefit)
• Operators who want to extend brand investment across facilities
• Most senior living operating contexts

Operational implications:

• Each facility is essentially its own marketing operation
• Highest cost architecture by significant margin
• No efficiency gains from shared brand investment across facilities
• Most flexible at the facility level, but most expensive overall

This architecture is rare and almost always reflects a specific strategic choice rather than a default. Most senior living operators evaluating this option benefit from a hub-and-spoke instead.

How to choose between the three

Three operational questions, in order of importance:

Question 1: What’s the geographic distribution?

If all facilities are within one state or one major metro, a single site can work. If facilities span multiple states or distinct markets, hub-and-spoke is usually correct because each market has its own competitive set, its own search behavior, and its own local SEO requirements.

The breakpoint isn’t strictly geographic; it’s competitive. If a single Google search for “senior living near me” produces a different competitive set in each market, each facility benefits from its own domain authority.

Question 2: How many facilities, and how distinct are they?

Under 5 facilities, a single site usually wins.

5-10 facilities, the choice depends on geographic distribution and facility distinctiveness. If the facilities are similar and concentrated geographically, single site can scale. If they’re distributed or distinct, hub-and-spoke is better.

10+ facilities, hub-and-spoke is almost always the right architecture. A single site with 10+ facility pages becomes navigationally awkward, dilutes the brand of each individual facility, and makes local SEO harder for every facility.

25+ facilities, the architecture needs careful design to remain manageable. Some very large operators end up with regional hubs plus local sites, or with a strict hub-and-spoke disciplined by a tight design system.

Question 3: What’s the operational capacity?

Hub-and-spoke architectures require sustained investment in each site. Local content updates, local photography refreshes, local SEO work, local review management. If the operator has a strong central marketing function with facility-level support, this is feasible. If marketing is thin, hub-and-spoke can become a maintenance burden that produces inconsistent quality across facilities.

The honest evaluation: can the operator maintain 12 sites at quality, or only 3? Pick the architecture that matches the operational capacity, not the architecture that looks ambitious on paper.

The local SEO question

For multi-facility senior living operators, local SEO is one of the most impactful aspects of the architecture decision.

Each Google Business Profile is tied to a physical address. Each facility’s address generates local search visibility for “senior living [city]” queries. The architecture decision affects how much domain authority that local visibility ties into.

Single site: All local SEO benefit accrues to the parent domain. The parent domain becomes very strong locally for the markets it serves. Individual facility pages benefit from internal linking but compete with each other for the parent domain’s authority budget.

Hub-and-spoke (subdomains): Each subdomain inherits some authority from the parent domain. Each can rank locally without competing with siblings. Strong configuration if the parent domain has authority worth distributing.

Hub-and-spoke (separate domains): Each domain stands on its own. Each builds its own authority over time. Slower initial ramp but stronger long-term local positioning if the operator invests in each site properly.

Distinct facility sites without parent: Same as separate domains, with no central brand benefit.

For operators where local SEO drives a significant portion of inquiries, the architecture choice has compounding effects over years. Most multi-facility senior living operators benefit from architectures that produce strong local presence per facility, which usually means some form of hub-and-spoke.

The design system that makes hub-and-spoke work

Hub-and-spoke architectures fail most often because the central operator can’t maintain brand consistency across the spokes. Each facility’s site drifts. Three years later, the portfolio of sites looks like fifteen different operators rather than one.

What prevents drift:

A documented design system. Components, typography, color, photographic style, voice and tone, layout patterns. Documented in a real document or design tokens, not just in the head of the original designer.

Centralized templates. Each facility site uses the same component library. New facilities adopt the components when they’re built; existing facilities are updated when the system evolves.

Centralized brand stewardship. A single team or person responsible for maintaining the system across facilities. Not a committee. Not divided across vendors. One owner.

Periodic audits. Quarterly or semi-annual reviews of all facility sites against the design system. Drift is identified and corrected before it accumulates.

Locked components vs flexible content. The design system locks the structure (header, footer, navigation, page templates, photography style) while allowing content (copy, photography, specific information) to vary per facility.

Without these systems, hub-and-spoke architectures degrade. With them, they scale.

The CMS implications

Multi-site architectures have CMS implications.

Single CMS, multiple sites: Most modern platforms (Webflow, WordPress multisite, Astro with content collections) can serve multiple facility sites from a single content management backend. This makes maintenance more efficient.

Multiple CMSes, multiple sites: Each facility runs its own CMS install. More flexibility, more operational complexity. Usually only justified for operators with very different requirements per facility.

For most multi-facility senior living operators, single-CMS architectures serving multiple sites or sub-sites are the right answer. The maintenance efficiency outweighs the flexibility benefit of separate installs.

We covered platform-specific considerations in Webflow vs WordPress for senior living websites.

What lead routing looks like in each architecture

Lead routing is operationally important and architecture-dependent.

Single site: All leads route through one form. Routing logic determines which facility (or facilities) receive each lead. Simpler initially, but routing logic becomes complex as the portfolio grows and lead types proliferate (different forms for different inquiry types).

Hub-and-spoke: Each facility site has its own form, routing directly to that facility’s admissions team. Simpler per-facility routing. The trade-off is that prospects who browse multiple facilities don’t have a unified experience; their inquiries fragment across facilities.

For most operators, per-facility routing in hub-and-spoke architectures produces better admissions response times because the inquiries land directly with the team that needs them. We covered the response-time importance in family communications during senior living admissions.

The migration path

For operators on a single-site architecture who’ve grown past it, the migration to hub-and-spoke is non-trivial.

Typical migration sequence:

1. Audit current site traffic, conversions, and SEO authority by facility
2. Plan the new architecture with redirect mapping for every existing URL
3. Build the new system on the new architecture
4. Migrate content with redirects in place from day one
5. Monitor SEO performance for 3-6 months post-launch, addressing any traffic drops

The migration is typically a 4-8 month project for a 10-facility operator, with planning alone taking 6-8 weeks. It’s not a project to undertake casually, but for operators who’ve outgrown a single-site architecture, the migration cost is recovered in 12-18 months through better local SEO and conversion performance.

What to do next

If you’re commissioning a new multi-facility website system or considering migrating from an existing architecture, the decisions to make first are around architecture before design. Design follows architecture, not the other way around.

We work with multi-facility healthcare operators on website architecture and build engagements as part of broader brand work. If you’re at the architecture decision point, send a note. The architecture conversation is the most important early conversation; it’s where the long-term operational implications get set.

Related reading:

• Senior living website design: a guide for operators
• Webflow vs WordPress for senior living websites
• What a senior living website needs in the first five seconds
• Senior living website conversion benchmarks
• Multi-location operator branding guide
• Brand consistency across multi-facility healthcare