How should a team structure its website?

Default to one strong team domain carrying agent profile pages, and treat separate per-agent websites as the exception that must argue for itself. One domain concentrates SEO equity, gives every marketing dollar a single destination, simplifies lead routing, and keeps admin sane. The exception exists — genuinely distinct personal brands or markets — and it charges real costs in dilution and duplication.

Why one domain is the default

Search equity is the bluntest reason: rankings accrue to domains, and a team splitting its content, links, and sold proof across five small sites is running five weak competitors against every strong one domain in its market. Consolidated, the same effort compounds in one place — the team’s area pages rank on the strength of everything the whole roster contributes. The operational reasons stack on top: one destination on every sign and ad, one database with one routing system behind every form, one site to keep current instead of five going quietly stale. Structure, here, is leverage.

Agent profiles are the release valve

The one-domain default works only if individual agents still get a real presence, and that is what profile pages are for — not a headshot grid, but a genuine page per agent: bio in their voice, their live and sold listings, their reviews, their communities, their contact path. Done properly, the profile wins the agent’s name search — the moment referred clients verify them — while feeding the shared domain’s strength. What separates a profile that recruits and converts from a directory card is detailed in agent bio pages on team websites. This is also the honest answer to a recruit asking “do I get my own site?”: you get a page that ranks for your name on a domain stronger than any site you would start alone.

When separate agent sites earn their keep

Two cases genuinely justify a second site. Distinct market: a team member working a geography or niche the team brand does not credibly cover — a cottage-country specialist on a city team — can justify a focused standalone site. Distinct brand: an agent whose personal brand meaningfully outweighs the team’s in their segment, typically a luxury practice. Note what is not on the list: ego, a recruiting sweetener, or “everyone else does it.” Every additional site divides content effort, link equity, and admin attention, and most teams that scatter across many sites would convert more from one. If you do run the exception, the mechanics of where it lives — a subdomain of the team’s domain versus the agent’s own domain — carry real ownership consequences, weighed in agent subdomains vs separate domains.

Routing and database implications

Structure decides where leads land and who owns the record. On one domain, every inquiry enters one CRM and routing does the fairness: listing inquiries to the listing agent, area leads round-robin or first-to-claim, profile-page leads to that agent. Scattered sites mean scattered databases — some in personal spreadsheets that leave when the agent does. Consolidation is what makes team-level rules enforceable at all, and it is why the structure question is really a database-ownership question wearing a design costume.

The economics, briefly

One platform site with seats is the cheap shape: on BrokerFold, the Team plan includes five seats with extra seats at $70/month, so the whole roster works one site and one database on one subscription — while every additional standalone site is its own build, its own subscription, and its own maintenance burden. Full cost shapes are broken down in real estate team website cost, and what a team site should actually include in real estate team websites. The money, like the SEO, votes for concentration — spend the difference making one domain excellent.