WPResidence handles agent profiles, listing management, lead routing, and role controls on WordPress.
Last updated: September 25, 2026
An agent’s page on a brokerage site or on Zillow belongs to the platform: the domain, the lead data and the search rankings stay there when the agent switches firms.
WPResidence is a real estate agent portal WordPress theme that gives agencies and brokers the whole portal. Each agent gets a public profile page, a front-end dashboard to manage their own listings, and automatic email routing for every inquiry on their properties. The same install runs a solo agent today and a firm with hundreds of agents later.
As an agency website theme, it bundles profiles, listing management, lead routing, memberships, and role controls, into one license.
Every Agent, Agency, or Developer account in WPResidence automatically generates a public profile page that lists that user's active and sold properties. Registering as an agent spins up a profile and links every property assigned to them.
Each profile stores a photo, bio, specialties and service areas, languages spoken, phone, email, social links, and a built-in contact form. The agent's listings render in a grid below the bio, so a single page works as both a "hire me" pitch and a live inventory feed.
Styling stays consistent across the team: profile pages are built with WPResidence Studio templates or Elementor, so the global header, footer, and typography hold the brand together while each agent differs by photo, bio, and specialties. Shortcodes and widgets render team grids, agent or agency directories, and blocks like "Listings by John Smith." You can preview the options across the 50 one-click demo sites of this real estate WordPress theme first.
The Agents List page offers 5 agent card styles, and profile pages come in 2 layouts. For a custom design, build a Single Agent, Single Agency or Single Developer template in WPResidence Studio and apply it to all profiles or only to one agency category, city or area. The template's widgets cover the name, photo, contact form, call, WhatsApp and email buttons, listings, reviews, specialties and custom fields.
When an agent leaves and you reassign their listings, the property URLs and content stay exactly the same, so links and rankings stay with the site.
There are five account types in total: three professional roles (Agent, Agency, and Developer), plus a Regular User role and the WordPress Admin. The Developer role is built for builders showing projects and units.
Agency is its own account type. It gets its own profile page showing the company logo, a description, office contact details, a team roster, and the combined inventory of every linked agent. A form on the agency page routes leads to the agency email and the linked agents, and one agency can run 5 or 50 agents under one umbrella, each keeping their own profile.
Agents, agencies and developers each have their own categories, cities, areas and states, so visitors can filter the directory by what and where each one sells.
The same property can be assigned to more than one agent and shows correctly on each agent's profile, which matters for co-listed deals. On multilingual sites, each property's language versions are linked, so a price update syncs to all languages.
Agents and owners log into the front end of the site and manage their entire workflow (listings, profile, messages, invoices) from a dashboard built out of ordinary WordPress pages. Each tab is an optional template page and appears once its page exists.
The core tabs are My Profile, My Properties, Add or Submit Property, Favorites, Saved Searches, Messages, Invoices, and CRM, laid out as either a top bar or a side menu (agencies tend to favor the side menu, solo agents the top bar).
Agency and developer accounts also get Add Agent and Agents List tabs, so the agency creates its agents' accounts and edits their profiles from the front end. An Analytics tab shows views and inquiries per listing.
The Submit Property form carries most of the daily work. Admins control which fields show, whether each is required, and their order.
A drag-and-drop uploader handles photos, PDFs, floor plans, virtual tour links, and video URLs, and agents reorder the gallery and set the featured image from the form. The form uses a tabbed layout (Details, Media, Location, Price) and saves drafts. The image limit is an admin setting, commonly 20 to 30 and configurable up to 40, with uploads restricted to JPG, PNG, and PDF.
The My Properties tab is the management table: agents edit, duplicate, or delete listings and flip a status to Sold, Featured, Expired, or Active in one click, with per-listing analytics showing views and inquiries. Guest submission is supported too, but a visitor must register right before saving, and the listing stays Pending until an admin approves it.
The Custom Fields Builder lets you add unlimited custom fields (text, number, date, dropdown) through a visual builder, and they flow into the submit form, the single-property template, the property cards, and advanced search at once.
You can even build different submission forms per property type, so a rental asks for deposit and minimum stay while a sale asks for year built and HOA fee. Compared with Houzez and RealHomes, WPResidence gives you more control over submission logic: Houzez ties field behavior to its CRM, and RealHomes uses a fixed tabbed wizard. Our WPResidence vs Houzez and WPResidence vs RealHomes comparisons cover the differences.
You can test it before buying. WPResidence's demos include agent logins, so you can publish a sample listing yourself and time it. The dashboard keeps "Add Property" and the edit controls a click or two from the front page.
A realistic submission runs in a predictable order: title and price, then location, then features, then media. Location follows a strict State, then City, then Area hierarchy, with address auto-complete through Google Places or OpenStreetMap. Listings sort into seven default taxonomies: Category, Type, City, Area, State, Status, and Features, so buyers can filter precisely.
Brokerages that add listings centrally can disable front-end submission by unpublishing the Submit Property page and turning off open registration. The result is a read-only catalog that office staff fill from wp-admin, while every other dashboard function (profile, messages, CRM) stays available for the agents who still need it.
The user separation toggle is the central permission control. With it on, each agent can see and edit only their own listings; with it off, the broker owns all listings and agents edit only what they're assigned.
WPResidence has five account types: Agent, Agency, Developer, Regular User and Admin.
Agents see and edit only their own listings. Agency accounts see and edit their whole team's inventory. Full admins can edit anything from wp-admin.
Approval runs by risk level. New Agent, Agency, and Developer accounts land as Pending until an admin publishes them, while Regular Users can be set to auto-approve. Admins can lock specific fields, such as the property slug or certain taxonomies, and theme options let you tick which dashboard menu items appear for each role.
For a Property Manager role that edits all properties while theme options and payment gateways stay with the admin, clone the Agent capabilities with a standard WordPress role-editor plugin. The built-in labels (Agent, Agency, Developer) are fixed, though you can rename them in signup text and translation strings; genuinely new roles call for a role plugin.
WPResidence keeps roles simple by design. RealHomes and Houzez expose finer-grained capability checkboxes and permission matrices, so if you need surgical control over dozens of individual capabilities out of the box, those themes give you more switches. WPResidence covers the common brokerage cases with sensible defaults and leans on a role plugin for the edge cases.
Every listing inquiry in WPResidence routes to the email of the agent assigned to that listing; if no agent is set, a site-wide fallback admin email fires instead.
Built-in inquiry forms sit on every listing page, every agent profile, and every agency page, plus a Schedule-a-Tour form. The theme auto-injects the property title and link into each message, so the agent always knows which property the lead is about. The routing path runs like this:
Agency-page forms route to the agency address and notify both the agency and its linked agents, and developer forms route to the developer. For listings imported through MLSImport, office-code mapping sends each one to the correct branch or agent. For rotation across a team, use HubSpot's assignment rules.
Schedule-a-Tour adds a date and time picker; the request is stored and emailed with the chosen slot and the listing ID. For a calendar with availability and booking limits, embed a tool like Calendly, Amelia or Bookly.
Forms drop into the sidebar, below the listing details, or inside the gallery lightbox without code, and WhatsApp and click-to-call buttons can sit beside them. Email templates are editable per role and per event (new lead, new listing, approved listing, expired membership), and subject-line tokens like city, type, and property ID let you build mail-filter rules.
The built-in WPEstate CRM stores every form submission as a lead, capturing name, email, phone, property context, and moves through editable stages from New Lead to Closed Won. Each agent sees only their own leads; the admin sees all and can export them. Because leads live in the database, they survive a bounced notification email. Agents work the leads from 8 front-end CRM pages: Contacts, Leads, Enquiries, Deals, Tasks, Activity, Automations and Stats. 27 ready-made automation rules handle assignment and follow-up reminders, deals move across a board view, and SMS goes out through Twilio.
Native HubSpot integration pushes form data through an API key, with a separate key per agent, and other CRMs (Salesforce, Zoho, Pipedrive, Google Sheets) connect through Contact Form 7, Gravity Forms, or WPForms plus Zapier. Our Elementor lead form sends to Zapier or Make through webhook URLs.
WPResidence supports recurring membership packages, pay-per-listing, or a mix of both, plus one-time fees. Each plan specifies a price, how many listings it allows, how many days they stay active, and how many featured slots the account receives. When an account hits its cap, new published listings are blocked until it upgrades.
Payments work out of the box with built-in PayPal and Stripe, and bank or wire transfer is supported offline. WooCommerce is optional: you only need it for extra gateways, complex tax, or a different checkout.
The My Invoices front-end page lists every purchase (memberships, paid listings, featured boosts) with IDs, amounts, and dates, and WooCommerce orders surface there too. You can also tie auto-publishing to packages: hold all new listings as Pending globally, then let paid tiers publish instantly.
If you plan to open registration to the public, fake agents and junk listings are the first thing you'll worry about. WPResidence handles both with moderation at two levels, plus spam defenses on every front-end form.
New Agent, Agency, and Developer accounts stay Pending until an admin publishes them, and a global option can hold every new listing for review before it goes live. Email alerts fire on new signups and listings.
The spam defenses stack up. WordPress nonces protect all front-end forms, Google reCAPTCHA plugs in through theme options, and a required Terms and Conditions checkbox, optional social login, and forced account creation on guest submissions raise the bar further. If you run paid or pay-per-listing models, each fake listing costs money to post, which is a natural deterrent, and per-listing analytics make abnormal spikes easy to spot.
To mark verified agents, add a custom field or label with an icon after you check an agent's ID or license offline, and store those documents outside WordPress.
A single WPResidence install can run as a solo-agent brochure site today and grow into a multi-agency portal later, by toggling roles, dashboards, and payments in theme settings rather than migrating to a different theme. You start with only the Agent role, registration hidden, and payments off, then flip on the Agency and Developer roles, the front-end dashboards, memberships, and payment gateways as the business grows. Enabling a role auto-adds its menus; disabling it cleans them up.
For thousands of listings, plan for a VPS or managed WordPress host with page caching. WPResidence needs WordPress 6.7 or higher, PHP 8.0 or higher and MySQL 5.6 or higher; our server requirements article lists the recommended PHP limits.
For social proof, WPResidence's ThemeForest listing reports 32,000+ buyers and 1,600+ reviews averaging 4.85/5.
If your inventory spans more than one language, this part is straightforward. The free WPEstate Translate plugin creates the languages, and WPML, Polylang and Weglot are also supported.
Listings, taxonomies, and profiles become linked translations, so you enter a property once and translate on top, with per-language URLs, menus, and search that returns only active-language listings. For a deeper walkthrough, see our multilingual real estate website guide.
Renaming labels is just as direct. Using Loco Translate or WPML String Translation, you can change "Property" to "Listing," "Agent" to "Broker," or "Price" to "Rent per month" in under an hour, with no file edits, and the change applies globally.
The theme includes RTL support for Arabic and Hebrew, ships in 40+ languages, and offers a multi-currency switcher with scheduled exchange-rate updates. Roles and ownership stay stable across every language.
WPResidence includes a native star-and-text review module for agent, agency, and developer profile pages.
On the professional side, the review module is native. Visitors leave a star score plus written text on an agent, agency, or developer profile, an admin moderates it before display, and the profile builds a visible history over time. Those reviews tie to a user account and can power "Top rated agents" widgets and badge logic.
Property listings use WordPress comments; add a rating plugin for per-listing stars. For comparison, RealHomes focuses its ratings on individual properties, while Houzez and MyHome also include professional ratings.
WPResidence is built around native WordPress listings but integrates with MLS and IDX feeds, and MLSImport is the default path (an in-house product, and this article is published on wpresidence.net). It uses the RESO Web API to pull MLS listings into WordPress as native property posts, each with its own indexable URL and the same templates and search as your manual listings. Imported listings behave like any other property, gaining reviews, favorites, and saved-search support, and office codes map them to the correct agent or agency.
WPResidence also coexists with hosted IDX plugins such as iHomefinder, dsIDXpress, and Realtyna for board search, while your native listings stay branded and indexable. Iframe-style IDX listings load from the provider's server, so they use the provider's templates and the SEO goes to the provider.
On data ownership, properties are a standard custom post type, while users and leads sit in normal WordPress tables, all exportable via CSV, XML, or REST. Switching hosts or themes keeps your content intact, and Elementor and Studio layouts are the one part you rebuild. A REST API at the path /wp-json/wpresidence/v1/properties, with matching endpoints for agents, agencies, and developers, supports full create, read, update, and delete operations for external CRM sync.
The main points of this page.
WPResidence includes five account types (Agent, Agency, Developer, Regular User, and Admin), with each professional role getting a public profile page and front-end dashboard.
Every listing inquiry routes automatically to the assigned agent's email, with a site-wide admin fallback if no agent is set and an optional CC to a broker.
The user separation toggle controls whether each agent owns only their own listings or whether a broker owns all and assigns them.
Agent and agency profiles include a native star-and-text review module, while individual property listings use WordPress comments rather than star ratings.
A WPResidence license costs $49 a year for one site, $99 for three and $249 for ten, so agencies can cover several client sites with one purchase.
Agents add and manage listings, messages and invoices from a front-end dashboard.
Yes. Each Agent signup in WPResidence creates a public profile page with a photo, bio, contact form, and a live inventory feed of that agent's listings. An Agency account groups multiple agents under one brand and combines their listings on a single agency page. One install supports five or five hundred agents.
Yes. The WPResidence front-end dashboard is built from WordPress pages using a User Dashboard template. Agents log in to add, edit, or delete listings, update their profile, read messages, check invoices, and view per-listing view and inquiry analytics. The user separation setting walls front-end accounts off from the WordPress back end entirely.
Yes. In WPResidence, unpublish the Submit Property template page and turn off open registration. The site becomes a staff-managed catalog filled from wp-admin, while any dashboard tabs your agents still need, such as profile, messages, and CRM, keep working.
WPResidence gives you the most control over submission logic of the three: Houzez ties its dashboard to its CRM, and RealHomes uses a fixed tabbed wizard. The theme lets admins control which fields appear, their order, and their requirement status per property type. It also supports guest submission and unlimited custom fields through a visual builder.
WPResidence builds in four front-end account types (Agent, Agency, Developer, and Regular User), plus the WordPress Admin role, for five in total. The user separation toggle controls whether agents own their own listings or a broker owns all of them. Admins can lock specific fields, choose which dashboard tabs each role sees, and require manual approval for Agent, Agency, and Developer accounts. A standard WordPress role-editor plugin extends this for a Property Manager pattern.
Yes, at two levels. New Agent, Agency, and Developer accounts in WPResidence land as Pending until the admin publishes them. A separate global setting holds every new listing for review before it goes live, even from existing verified accounts. Regular Users can be set to auto-approve, so you moderate exactly as tightly as your portal needs.
Each listing form in WPResidence routes to the assigned agent's email and logs the lead in that agent's CRM inbox. If no agent is assigned, a site-wide fallback admin email fires instead. A global CC or BCC option copies an office manager or broker on every lead. Agency-page forms notify the agency address, and MLSImport listings route by office code to the correct branch or agent.
Yes. A single-site WPResidence license ($49 a year) covers one live domain. For several client sites there are 3-site ($99 a year) and 10-site ($249 a year) licenses. Each license includes a year of theme updates and support; the sites keep working after the license year ends.
Agent, agency, and developer profile pages in WPResidence include a native star-and-text review module. Visitors leave a star score plus written text, and an admin moderates it before display. Individual property listings are different: they use WordPress comments for feedback, and a separate rating plugin is needed if you want per-listing star ratings.
Yes. One WPResidence install covers the full range. You start with a single Agent account, registration disabled, and payments off. As the business grows, you enable the Agency and Developer roles, front-end dashboards, memberships, and payment gateways from theme settings. The theme, content and URLs stay the same.
Yes. WPResidence pairs with the free WPEstate Translate plugin, WPML, Polylang or Weglot. Listings, taxonomies, and agent profiles become linked translations, so a property is entered once and translated on top. The theme ships in 40+ languages, built-in RTL support for Arabic and Hebrew, and a multi-currency switcher with scheduled exchange-rate updates.
