How a multi-office real estate website runs on one WordPress install: teams, roles, regional pages, IDX, and franchise licensing explained.
Last updated: September 25, 2026
By Cris Bean
A multi-office real estate website runs on one WordPress install with a single shared property database. Every listing is stored once, and each office is an Agency account that holds its Agent accounts. Office pages and agent pages are filtered views of that one central listing pool, so a property you add once can appear on the main site, its office page, and its agent page at the same time. This setup fits brokerages with several branches, franchises onboarding new offices, and teams that started with one agent and keep adding people.
If each office needs its own WordPress dashboard, domain or isolated data, use WordPress Multisite instead. For heavy multi-office inventory, plan for a VPS or managed WordPress host.
On this page:
Every listing is stored once, in one property database on a single WordPress install. Office pages and agent pages draw from that database and show only the listings assigned to them.
WPResidence is a real estate WordPress theme with Agency and Agent roles. An Agency account represents an office or team and holds any number of Agent accounts. Each listing is assigned to an agent and an agency, and both profile pages show it automatically.
Every Agency gets an automatic profile page that lists only that office's properties and its team members. Every Agent gets a profile page too, showing only their own listings. You set the assignment once, and the theme keeps the connection in every place that listing appears.
A brokerage with 10 offices keeps one clean record per listing instead of 10 copies that all drift out of sync. Change a price, a photo, or a status once, and every view of that property updates together.
The same logic covers a single-office team and a franchise-style operation spread across many cities. You add branches by adding Agency and Agent accounts, and the structure stays the same. To see it running, open the brokerage demos and the city portal demos.
WPResidence gives you four user types that matter for real estate work: Agent, Agency, Developer, and Standard User.
Each Agent profile ships with built-in fields: photo, short bio, phone, email, social links, job position, and specialties. A new hire's page is complete on day one.
The profile also fills itself. When an agent adds or updates a property from their dashboard, it appears automatically in the agent's listings section on their page.
For grouping people, the List Agents shortcode and widget show agents in a grid or list, filtered by category, city or area. A Featured Agent widget pins one person in a large block.
An Agency can own listings directly and assign them to agents in the same office. Each listing shows the agent, agency or developer assigned to it, so a head office can publish a property under its own brand or under one of its agents.
Agencies have their own categories, cities, areas and states, so visitors can filter the office directory by location.
All of this runs from front-end dashboards. Agents add, edit, and archive listings, update their profile, and read their leads. The same structure covers a solo agent, a five-person team, and a multi-agency portal. See the agent and agency role features before you map your own team onto them.
Four front-end real estate roles (Agent, Agency, Developer, and Standard User) sit alongside the normal WordPress admin-side roles, and each one has a clear lane.
Agents edit only their own listings and their own profile. Global settings stay with the site admin. Agency accounts sit one level up and manage their own team's agents and listings.
The front-end dashboard is where day-to-day work happens. It splits into sections like Add Property, My Properties, Profile, Favorites and Invoices. Global options (Theme Options, header and footer, search templates, payments and membership) stay locked to WordPress Administrator-level accounts. Agency accounts also get Add Agent and Agents List tabs, so each office creates its agents' accounts and edits their profiles from the front end.
In practice, you map staff onto WordPress roles that already exist. An office admin gets a backend Editor role so they can help with pages and property content. Marketing staff get Editor or Author for pages and posts only, nowhere near listings or design.
Because WPResidence follows the standard WordPress capability system, it works cleanly with role and capability plugins. If you need a photographer, an assistant, or a transaction coordinator on a narrow custom role, you build it with a role editor plugin and the theme respects it.
Listing quotas add one more control layer. Membership rules set how many active and featured listings each account can publish.
For partner or external offices, the admin-approval flow is the key switch. In Theme Options, you can require admin approval for every listing submitted from the front end, so outside offices can contribute while you keep control of the site.
WPResidence Studio, paired with Elementor, lets you design custom templates for Agent and Agency pages: layout, colors, extra blocks, the lot. Per-page branding covers the logo, banner image, bio, and contact details, and dynamic widgets pull in only that agent's or office's listings.
A Studio template can apply to every agency or only to one agency category, city or area, so each office type gets its own page design.
The result is that each team page reads like a standalone microsite, with its own lead forms and highlight sections. In practice, a franchise standardizes the header, footer, menus, and search once, then lets each office differentiate only its own page.
The admin keeps global navigation and branding, so the site design stays consistent while agents edit their own pages.
Assign a bold full-width hero template to a top-producing team and a compact sidebar layout to a smaller office, all from the same install. To see how the templates are built, the WPResidence Studio design templates page walks through the agent and agency options.
Yes. WPResidence works with the free WPEstate Translate plugin, WPML, Polylang and Weglot, so an office in one region can present its page in two or three languages while reading from the same property entries as everyone else. You can translate properties, locations, agents, agencies, taxonomies and dashboard text, and the design is RTL-ready, so grids, ribbons, and agent cards mirror direction for Arabic or Hebrew.
An MLSImport task can import only the listings of one MLS office, by its office ID, and assign them to that office's agent, so each branch shows its own inventory. That ties straight back to the shared-database model: one pool, filtered per office, whatever language the front end runs in.
Underneath, the location taxonomy is built for multi-market work (a State to City to Area hierarchy plus radius "near me" search), so city and area pages get their own URLs from one install.
Each property contact form sends the lead to:
Every lead is also saved in the built-in WPEstate CRM. There, agents keep each contact with their buyer preferences and the properties they viewed, match listings to those preferences and email the matches to the contact. Leads, deals, tasks and notes are managed in the same place. Each agent sees their own leads and messages, and the agency sees all leads and messages from its agents.
For custom forms, the Elementor lead form builder adds your own fields, per-form CC and BCC, and webhooks to Zapier or Make. For round-robin or regional assignment, connect HubSpot: leads sync into its pipelines while the assigned agent is still notified.
Each stage of growth is a settings change on the same WPResidence site:
Listings, URLs and design stay the same at every stage, so search rankings carry forward. MLS listings can be added at any stage through MLSImport.
You do. Properties, agent and agency profiles, and leads all live in your own WordPress database. Because they're stored as standard WordPress content, that data survives a theme change and moves with you across hosts.
The WordPress REST API exposes properties, agents, agencies and developers, so a developer can sync the listings to a CRM, a mobile app, or an internal dashboard.
For moving an existing brokerage in, the WP All Import add-on for WPResidence maps the columns of a CSV or XML file to WPResidence property fields, including custom fields.
For live MLS feeds, MLSImport is the default path. MLSImport is an in-house WPResidence product built on the RESO standard. It connects to 800+ MLS sources and turns imported listings into native property posts.
Native posts matter for two reasons. Imported listings show up in WPResidence search, use your Studio templates, and index cleanly for SEO. And because the import job respects the built-in taxonomies (Status, Type, City) and keeps agent and office assignment intact, it ties straight back to the office-codes mechanism from the regional section. A feed-based listing routes its leads to the right person the same way a hand-entered one does.
If you plan to charge for listings, the tools are already in the theme. WPResidence includes built-in membership packages plus pay-per-listing, pay-per-feature, and recurring billing, and those run directly through Stripe and PayPal.
WooCommerce is optional: add it for extra payment gateways or complex tax rules.
Membership packages are how you sell visibility. Each plan sets quotas for total and featured listings. You can set listing and package expiration in days, so paid placement ends on its own.
For a franchise, use packages to charge partner or affiliate offices for featured placement. The WPResidence pricing and licensing page covers how the theme itself is licensed, which is separate from the packages you sell to your own members.
For a multi-office site, the load that matters is concurrent agent dashboards and per-office filtered queries. Both look up listings by their assigned agent or office, so an office page or a lead route loads only its own records.
The theme ships a native cache for property "units," the cards and rows on search and archive pages. Layer it with a page-caching plugin: the theme cache for listing units, a page-cache plugin for full pages, plus Gzip.
The server needs WordPress 6.7+, PHP 8.0+, MySQL 5.6+ and HTTPS. For large inventories, use a VPS or managed WordPress host.
Support runs through private tickets at care.wpestate.org, and each license includes a year of support and theme updates. WPResidence has 32,000+ buyers.
For onboarding at scale, theme option export and import clones a master config into a new install, the lever a franchise uses to standardize many office sites.
The main points of this page.
WPResidence runs a multi-office real estate website on one WordPress install and one shared property database, with no WordPress Multisite required.
The Agency role acts as an office container, and every Agent gets an auto-generated profile page showing only their own listings.
Leads go to the listing's agent, agency or developer by email and dashboard inbox, secondary agents get a copy, and every lead is saved in the WPEstate CRM.
MLSImport is WPResidence's default IDX and MLS path, built on the RESO standard and preserving agent and office assignment on import.
A brokerage can grow from a solo agent to a multi-office franchise portal, keeping its content, URLs and theme.
WPResidence Studio templates give each agent and agency page its own design, all inside one install.
One WPResidence install with a shared property database handles multiple offices on its own. Each office and agent gets an automatic profile page that filters the same central pool. You only need WordPress Multisite when offices require fully separate dashboards, separate domains, or completely isolated data per branch.
One install holds every office, agent and listing in one database, so the practical limit is your hosting. For thousands of listings, use a VPS or managed WordPress host with page caching.
Each property contact form sends the lead to the agent, agency or developer assigned to the listing, by email and in their dashboard inbox. Secondary agents on the listing get a copy, and a listing with no agent sends it to the user who published it. The admin can add addresses in the Duplicate Email field in Theme Options to get a copy of every contact email.
Yes. WPResidence works with the free WPEstate Translate plugin, WPML, Polylang and Weglot, so you can translate properties, agents, agencies, taxonomies, and dashboard text. Each office page can run in several languages using the same property entries. The RTL-ready design mirrors grids, ribbons, and agent cards for Arabic and Hebrew.
Yes. The Agency and Agent roles are scoped so a partner office manages only its own team and listings, while global settings stay with the admin. You can also require admin approval, which holds every listing submitted from the front end until the admin publishes it. In WPResidence, partners do all of this from the front-end dashboard.
WooCommerce is optional. WPResidence includes built-in membership packages plus pay-per-listing, pay-per-feature, and recurring billing that work directly with Stripe and PayPal. You only need WooCommerce for extra payment gateways or more complex tax rules. For a franchise charging partner offices for featured placement, the native tools usually handle the entire flow.
Yes. Start with one agent profile and user registration off, then add Agent and Agency accounts, open registration and turn on membership packages as branches join. Your listings, URLs, and design stay in place. WPResidence keeps properties as standard WordPress posts, which is why your SEO carries forward.
Each site needs a license tied to its domain: $49 a year for one site, $99 for three or $249 for ten, each with a year of theme updates and support. A franchise with many office sites can cover up to ten of them with one 10-site license. Keeping a clear record of which license key maps to which domain keeps renewals and host moves straightforward across a multi-office real estate website portfolio.
