A listing exists once on your site. MLSImport identifies every listing by its unique MLS identifier, so a listing that is already a property is updated rather than imported a second time, no matter how many import tasks match it.
That single rule decides how to build a company listings page alongside individual agent pages. Plan which task owns which listings, and both pages stay accurate through every sync.
Before you start
- An agent profile exists for each agent, created in your theme or under Real Estate Agents in standalone mode.
- You know which identifier your feed populates for agents and offices, which the article on importing by agent or office explains how to find.
- Sync is running, because these pages are only as current as the last successful sync.
Why the first task wins
When an import runs, each incoming listing is looked up by its MLS identifier. A match means the existing property is updated. No match means a new property is created, and the task that created it is recorded as the one it came from.
On WpResidence, Houzez and Real Homes the agent is attached at that moment of creation. A later agent task that matches the same listing finds it already there, updates its price and status, and leaves the original agent in place. This is why an agent page can sit at forty listings when the agent has sixty: twenty of them were created by an earlier office-wide or market-wide task.
Standalone mode rewrites the agent link on every run, so the last task to touch a listing owns its agent. That removes the cleanup work and adds a different requirement: two tasks that both match a listing will hand it back and forth, so exactly one task should still match each listing.
The structure that holds up
Make agent tasks the source of your own inventory, and keep general tasks for everything else.
- One import task per agent, filtered on that agent’s identifier. Select the statuses you want to keep visible, typically Active, Pending and Closed.
- Set that agent in Select Agent on the same task, so the properties arrive attached to the right profile.
- Add Active, Pending and Closed to Protected Statuses if the page is a portfolio. Without that, the daily reconciliation removes closed listings once the MLS drops them.
- Exclude your own office from every general task, using Exclude listings with ListOfficeMlsId or Exclude listings with ListOfficeKey. That is what stops a broad market task from claiming your agents’ listings first.
Expected result: every listing your agents hold is created by exactly one agent task, and your general market tasks cover everything else without overlapping them.
Run the agent tasks before the general tasks the first time, then add the office exclusion. Order matters only on that first run, because after it every listing already has an owner and later runs are updates.
Build the pages from what is imported
Neither page is another import task. Both read properties that are already on the site.
Agent pages. Your theme’s agent page lists the properties attached to that agent with no configuration. In standalone mode each agent’s own page carries a Listings section that does the same.
The company page. Use a listings widget or page block and point it at several agents at once. In standalone mode the property list and slider blocks take an agent, and the Team Directory block gives visitors the roster with a link through to each agent’s own page. If you want the page to read as company inventory rather than personal branding, most themes can hide agent names on the property cards.
Adding an agent later
- Create and publish the agent profile.
- Create the import task filtered on that agent’s identifier, and pick the profile in Select Agent.
- Run the first import and enable sync on the task.
- Add the agent to the company page’s widget or block.
New listings from that agent arrive attached correctly. Listings the agent already had on the site, imported earlier by another task, are the ones to check, because on the three supported themes they keep their original agent.
Moving from one office task to per-agent tasks
This is the case that needs real cleanup, and only on WpResidence, Houzez and Real Homes. The listings exist, so the new agent tasks import nothing and change nothing.
- Build and save the agent tasks first, each with its filter and its agent.
- Stop the old office task so it cannot claim the listings again.
- Either bulk edit the existing properties to the correct agent, or delete them from the Tools tab and let the agent tasks import them fresh.
- Confirm your general tasks exclude the office, then run the agent tasks.
Bulk editing is faster than deleting and re-importing, and it keeps the properties’ addresses and any editorial labels you added. Delete and re-import only when the properties are also wrong in other ways, for example imported before you fixed the field selection.
Frequently asked questions
Can I have the same listing appear on two agents’ pages?
No. One property carries one agent, and a listing becomes one property. A listing where two of your agents were involved has to be presented some other way, for example a manual mention on the page.
If I delete an import task, do its properties disappear?
No. The properties stay on the site and stop being updated. Deleting properties is a separate action from the Tools tab.
How do I tell which task a property came from?
The Import History screen records the import task alongside each listing it handled, over the last thirty days. For older properties, the task that owns a listing is the one whose filter still matches it.
Do closed listings count against my listing allowance?
Yes. A closed listing kept as a portfolio piece is a property on your site like any other, so a large sold archive is worth planning for rather than discovering.
Related
- Importing one agent’s or one office’s listings
- Avoiding overlapping import tasks
- Importing agents and showing listings by agent
- Protected statuses
- Closed and off-market listings
Send us your agent list and the tasks you have now and we will map out which task should own what.