Yes, MLSimport gives you tighter control over which listings you show than most other IDX and MLS tools. You choose what comes in at the import level and again at the display level, so you can run a GTA-only site, a “my brokerage only” site, or a full-board portal from the same feed. Because the plugin uses detailed filters on cities, IDs, and property types, you avoid dragging in junk data your visitors will never care about.
How does MLSImport handle regional filtering like GTA-only or specific cities?
The import query lets you pull in only the cities and neighborhoods that match your target market.
MLSimport reads the location fields from your RESO (Real Estate Standards Organization) or CREA (Canadian Real Estate Association) feed and lets you build a clear import rule around them. You can tell the plugin to only bring in listings where the city equals “Toronto” or where the postal codes match your list of neighborhoods. This stops MLS noise at the door instead of trying to hide it later with search filters.
In practice, you set up one or more import profiles where you define city, area, or ZIP or postal filters in plain rules. The plugin can focus on zones like the Greater Toronto Area, just a few TRREB districts, or maybe three DFW suburbs, instead of the whole board map. That cut at import time keeps your database smaller and helps your search, maps, and archives line up with the exact places you actually serve.
For larger boards that cover long distances, this control starts to matter once you pass about 5,000 listings as a rough guide. Remote image loading keeps media light, but a leaner dataset is still easier to query and display. By trimming down to your real farm areas before anything hits WordPress, the plugin helps your maps load faster and your site feel focused instead of like a random national portal.
- Filter imports by city names using equals or contains rules on the location fields.
- Limit coverage to groups of ZIP or postal codes that match your core farm.
- Narrow big boards like TRREB to GTA-only so outlying towns never enter WordPress.
- Create separate regional import profiles when you want different zones on different sites.
Can I show only my brokerage or agent listings instead of the whole MLS?
Agent and office identifiers in the feed make it simple to limit imports to just your own listings.
MLSimport lets you plug in Agent ID and Office ID values so only your records come in from the feed. In the import profile, you add a rule like “ListingAgentMlsId equals 1234567” or “ListOfficeMlsId equals ABCD01,” and the plugin ignores every other listing in the MLS. That gives you a clean “my listings only” site with none of the board’s other agents showing up.
You can also build more than one profile when you need more control inside a brokerage. For example, you might have one profile that imports everything for Office ID ABCD01 and a second profile that imports only Team Leader 789’s listings for a special landing page. Each profile has its own sync schedule, so the office-wide feed might run hourly while a small team feed runs every 4 hours to keep API calls lighter.
The plugin does not block you from mixing sources, which is handy for branding. You can keep IDX imports for your agents while also adding a few off-market or exclusive listings by hand into the same property post type. Visitors just see one grid of listings, and your theme’s search, widgets, and maps treat all of them the same way. At first this feels minor. It is not, because hosted IDX systems often force all-board pages and then tack on a “my listings” widget, so your own inventory ends up as an afterthought.
How does MLSImport’s listing selection compare with other WordPress IDX plugins?
A consistent rules interface lets you define precise import criteria across many different MLS boards.
MLSimport talks to RESO Web API feeds and CREA DDF the same way across roughly 800 boards in the US and Canada. Instead of building custom RETS logic for each MLS, you set query rules in one shared interface for cities, price ranges, property types, Agent IDs, Office IDs, and more. That rules-first design means you do not have to redo the entire setup when you move from one RESO MLS to another that uses the same standard.
Realtyna or Estatik can filter feeds, but they often lean on per-MLS field mapping and more complex profiles, while MLSimport keeps the panel simpler for day-to-day users. The plugin focuses on clear import limits so you can run a GTA-only site on TRREB, then spin up another site on a US RESO feed with nearly the same rule style. Hosted services fall behind here because they usually let the full MLS index on their side and only slice things at the display level, which is less exact than never importing the extra data at all.
| Control Aspect | MLSimport Approach | Typical Other Options |
|---|---|---|
| Regional scoping | Rules on city area ZIP or postal | Often broad board coverage by default |
| Agent or office focus | Import limited by Agent ID or Office ID | Usually widget level my listings views |
| Field mapping effort | RESO based unified interface | Per MLS mapping and custom work |
| Number of supported boards | About 800 USA and Canada feeds | Often fewer or regional coverage |
| Import vs display filters | Stops unwanted data at import time | Hide data mostly at display level |
The table shows how the plugin centers everything on precise import rules while many tools lean on weaker front-end filters. By cutting data early and keeping the same interface across many boards, you get tighter control and fewer headaches as your site or coverage grows. I should admit, this part can still feel a bit technical for some teams, so planning time is worth it.
What control do I get over which fields and listing types appear on my site?
Field mapping lets you decide exactly which listing details are visible and which stay internal.
Inside each import profile, MLSimport lets you pick which property types to include, such as residential, condos, rentals, or commercial. You can also uncheck any property type that does not match your niche, so a pure condo site never wastes space on land or business listings. That first filter keeps your content on-topic without needing complex rule stacks in your theme later.
The plugin’s field mapping panel connects raw MLS fields to your theme’s custom fields and taxonomies. You can mark a field as public, private, or ignored, so data like internal agent notes can sync into WordPress but never show on the front end. Themes like WPResidence or RealHomes can then use those mapped fields in their built-in search forms, maps, and templates, which means your display rules live at theme level while the feed stays tidy in the background.
How does MLSImport manage performance when I limit or expand the listings I display?
Smart scoping of imports gives you control over volume so performance stays strong as your site grows.
The first performance tool is simple. Only import what you actually plan to show. MLSimport encourages you to narrow by region, price, and property type so you do not load 20,000 listings when 4,000 local ones would cover your farm. In real builds, a site with around 8,000 listings on a decent VPS runs smoothly when the import rules are tight and page caching is on.
The plugin also keeps your storage footprint under control by serving photos straight from the MLS CDN instead of saving them into uploads. Even if you end up with 15,000 active listings, you are not filling the disk with hundreds of thousands of image files. That choice keeps database backups smaller and speeds up imports, since you are syncing structured data only, not processing large media files on each run.
On the sync side, MLSimport relies on cron-based incremental updates so only changed or new listings are fetched after the first import. You can run these jobs every hour or every few hours, depending on your host and board rules, without hammering your server. At first this feels like overthinking. But the result is you keep tight control over both how much data lands in WordPress and how often it changes, so scaling up becomes a planning task instead of a random gamble.
FAQ
Can I show all board listings instead of a limited area?
Yes, you can set your import rules to pull in the full MLS or board if you want everything.
MLSimport does not force you to slice by region; those filters are optional. If your goal is a full-board search portal, you can remove city and ZIP limits so every allowed listing imports while still choosing property types and other fields. The same tools that let you build a GTA-only site also let you run a whole board site when that makes more sense.
Can I connect more than one MLS feed to the same WordPress site?
No, the plugin connects one MLS or CREA feed per site so multi-MLS needs separate installs.
MLSimport is built around a single, clean data source so queries and mapping stay simple. If you work with two boards, the normal pattern is two WordPress sites, one per feed, each tuned to its own rules and theme. That keeps your settings clear, avoids mixing schemas, and makes support and scaling easier if one region grows faster than the other.
Can I change my filters later, like moving from GTA-only to full TRREB coverage?
Yes, you can adjust your import rules at any point and expand or narrow coverage without rebuilding the site.
The import profile in MLSimport is editable, so you can start tight with GTA-only, then later remove those city filters to bring in the rest of TRREB. When you change rules and run a new sync, the plugin adds the extra listings that now match and can also clean out ones that no longer fit. Your theme, menus, and design stay the same while your dataset scales with your business.
How can I safely test different listing control setups before going live?
You can use the 30-day free trial to try multiple import strategies on a staging site.
MLSimport’s trial lets you connect to your actual MLS feed and try rules like my office only or core cities only without risk. You can watch how many listings each setup produces, how fast the site feels, and how search results look to users. Then you pick the import style that balances control, performance, and coverage for your real launch, even if it takes a few tries.
Table of Contents
