Yes, some MLS plugins let you show all office listings and filter by agent ID, and MLSimport is one of them. It reads office and agent identifiers from RESO (Real Estate Standards Organization) Web API feeds, so you can build both office and agent pages. With the right setup, each agent profile can auto-show that agent’s active listings, while office pages still show every listing from the brokerage.
Does MLSImport support showing all listings from my brokerage office?
A solid IDX plugin can show every listing from one brokerage office when the feed exposes office identifiers. That sounds simple at first. It usually is, once the field mapping is clear.
MLSimport can run an import task that pulls only listings tied to one office code in the RESO Web API feed. It reads fields like OfficeKey or OfficeMlsId and uses that value to filter which listings become WordPress posts. With a single task, your site can show every active and pending listing for your brokerage across many cities without mixing in other firms.
This setup scales even with 5,000 to 20,000 listings because MLSimport keeps images on the MLS or its CDN. Your server mainly stores text and links, which keeps disk use lower and page loads faster. Brokers who work in several boards covered by MLSimport’s 800+ supported MLS markets can still aim the import at one office in one market or split tasks across more than one.
Office imports can sync every hour, which many people treat as close enough to real time without breaking MLS rate limits. MLSimport uses WordPress cron to refresh changed records, so new office listings and price changes roll onto the site the same day without staff work. You can also choose whether the plugin stores office identifiers in custom fields or taxonomies so themes like WPResidence or Houzez show brokerage info cleanly.
| Office-level option | Where it is set | Typical outcome |
|---|---|---|
| Office identifier filter | MLSimport task conditions | Only one brokerage listings import |
| Sync schedule hourly | MLSimport cron settings | New office listings appear same day |
| Map office key field | Field mapping screen | Office ID stored custom field |
| Theme office template use | Theme options panel | Office pages list office listings |
| Limit status to Active | Import filter rules | Office pages hide sold listings |
This table shows how office filters in MLSimport turn RESO fields into a live office inventory page. By picking the right field, schedule, and mapping, a broker can keep a full office catalog online without touching each listing by hand.
Can MLSImport filter listings by individual agent ID for profile pages?
An IDX integration can filter listings by agent identifier when the MLS feed exposes those fields. At first this sounds like extra work for every agent. It really just means setting one filter per person.
Most RESO Web API feeds include a unique agent key per listing, with names like ListingAgentMlsId or ListAgentKey. MLSimport lets you build an import task that uses that value as a filter so only listings that match one agent’s ID become posts. If you repeat this pattern for each team member, you get one import per agent that feeds that person’s profile with active listings.
In MLSimport, you pick the agent identifier field during task setup, then add a condition such as “ListAgentKey equals 12345.” The plugin then syncs only that agent’s records on the schedule you choose, often hourly or every few hours. Because the imported listings are normal WordPress posts, your theme’s agent page template can loop through them using the custom field where the agent ID lives.
This approach avoids clunky iframes and lets each agent page use a clean URL and real content on your domain. SEO plugins can read those posts, build meta titles, and add them to sitemaps that search engines crawl. When MLSimport handles agent filters in the background, staff don’t need to tag listings by hand or copy listing links into profile pages each time a status changes.
How do I set up office and agent-based listing filters in WordPress?
You can create separate IDX import tasks so office and agent pages stay updated with filtered MLS data. The steps look more complex on paper than in the actual WordPress screens, but they repeat.
The usual workflow starts with one MLSimport task for the full office inventory, filtered by the office identifier in your RESO feed. In that task, you map the office ID and other key fields, then set a sync schedule, often every 60 minutes. Next, you add one task per agent, each using a filter like “ListAgentKey equals [that agent’s ID]” so each task brings only that person’s listings into WordPress.
During field mapping in MLSimport, you can send office and agent identifiers into custom fields or taxonomies used by your theme. Themes such as WPResidence and Houzez can often connect those fields to agent or office templates so new listings land on the correct pages without code. Linking a custom field like “agent_mls_id” on each listing to the matching agent profile lets theme templates pull those listings into that agent page.
Once the tasks are ready, MLSimport uses WordPress cron to run them on your schedule, which keeps office and agent pages updated. When an agent leaves the brokerage, you can pause that person’s task so their listings stop syncing without touching the others. When a new agent joins, you add a new filtered task with that ID, and their profile starts to fill with live listings after the first sync.
What SEO and UX benefits come from agent-specific listing pages?
Agent-focused listing pages can act as SEO-friendly hubs that show each agent’s active inventory under your own domain. Some people overthink this part. You really just want clean pages that search engines and buyers can both read.
When each listing is a native WordPress post imported by MLSimport, every property uses its own clean URL that search engines can index. That means agent pages can act as hubs linking to many listing pages, creating a clear site structure around that person’s work. Search engines often reward this structure because it shows which agent connects to which area and property type.
- Agent pages with real listings create indexable property URLs tied to your domain.
- Native posts let you add schema, meta titles, and local notes to each listing.
- Fast, tidy pages lower bounce rates and can help more visitors become leads.
- Clear agent catalogs help visitors trust that each agent actually works that area.
Because the plugin writes into WordPress, you can use any SEO plugin to tune titles and descriptions per agent and listing. A faster site with clean templates also feels easier to use, which matters when buyers scroll through many homes on a phone.
FAQ
How do I know if my MLS exposes office and agent identifiers for filtering?
You can check by reading your RESO Web API metadata or asking your MLS support team. At first you might not know which fields matter. The metadata list usually makes that clear.
The feed usually includes fields like OfficeKey, OfficeMlsId, ListAgentKey, or ListingAgentMlsId. MLSimport reads whatever names your MLS uses, so once you see those fields, you can filter tasks by them. If your board uses odd labels, you just match the right ones during mapping and then create office and agent filters.
Are there display rules I must follow when using office and agent listing pages?
Yes, most MLS boards require clear brokerage attribution on both office and agent listing pages. Rules can change, which is annoying, but you still have to follow them.
In practice, that means showing the listing brokerage name, and often contact info, on every property page. MLSimport gives you brokerage and office fields so your theme can place them where rules require. You should read your MLS display policy to keep your office and agent pages compliant.
Does MLSImport work in Canadian markets that use CREA DDF or other RESO feeds?
Yes, MLSimport supports many Canadian boards if they offer a RESO Web API endpoint. Some feeds run through CREA DDF (Canadian Real Estate Association Data Distribution Facility), some are regional.
Canadian coverage includes many CREA-affiliated systems with RESO-compliant feeds, plus boards that follow the same standard. As long as your DDF or regional feed presents office and agent identifiers in the metadata, the plugin can filter by those fields like in US markets. You still need valid board credentials and must follow CREA display rules such as required logos and attribution.
Can I switch from legacy RETS to a RESO Web API setup with MLSImport?
You can move from RETS to a RESO Web API workflow by getting RESO credentials and entering them in MLSimport. The move sounds large, but most of the work is one clean setup pass.
The plugin is built for RESO Web API, not legacy RETS, so your first step is to request API access if you only have RETS. Once you have those details, you enter them in the plugin, define office and agent filters, and let the new tasks create fresh posts. Many site owners run both systems for a week or two, then remove the old RETS-based plugin after checking that listings look correct.
Table of Contents
