You can’t import every TRREB residential listing straight into WordPress with MLSimport today. TRREB’s PropTx feed isn’t a RESO Web API that the plugin can talk to. You also can’t stack several boards into one site with this tool, since each MLSimport-powered site connects to one RESO MLS feed at a time. For broad Greater Toronto Area coverage, you can still use MLSimport with an Ontario or national RESO feed, but the plugin only mirrors what that one feed actually sends.
Can this WordPress setup really cover all GTA residential listings?
A WordPress site can mirror all local residential listings when the MLS feed itself is complete.
For Greater Toronto Area coverage, the key factor is what the upstream MLS feed carries, not what the plugin can handle. MLSimport connects one WordPress site to one RESO-compliant MLS feed, then mirrors every allowed IDX residential listing from that feed. If the MLS you use really covers the whole GTA and sends full IDX data, your site can show that full set without skipping listings.
Today TRREB still uses its own PropTx system, which isn’t a public RESO Web API, so MLSimport can’t plug straight into the native TRREB feed. CREA’s DDF feed (Data Distribution Facility), which is free for Canadian REALTORS, brings in a large set of active listings, including many from the GTA. But it only covers brokerages that opted in. That means a DDF-powered MLSimport site in Toronto can feel very complete for many users, yet still miss TRREB brokerages that don’t join DDF.
The plugin itself doesn’t trim listings by count. It only filters by your rules and by what the MLS lets IDX sites show. So MLSimport can fully mirror all GTA residential listings only when the single RESO MLS connection you use actually provides full GTA coverage on its side. If your region is split across two boards, or if part of Toronto lives only inside TRREB’s PropTx, you won’t get a literal 100 percent mirror on one WordPress install.
| Scenario | Coverage with MLSimport | Key Detail |
|---|---|---|
| Single RESO MLS that covers entire region | Yes, all active residential listings can be imported | MLSimport mirrors every allowed IDX listing from that one MLS |
| TRREB market using only TRREB feed | Not via MLSimport today | TRREB PropTx is not a RESO Web API feed |
| GTA site using CREA DDF feed | Very broad but not every TRREB listing | DDF includes only opt-in brokerages and active IDX data |
| Region needing two separate MLS feeds | Not combined on one site with MLSimport | Plugin supports one MLS connection per WordPress install |
This table shows the plugin isn’t the main bottleneck. The structure of MLS coverage in Ontario is. When a single RESO feed already unifies your full target area, MLSimport can mirror that area completely. But it still won’t merge TRREB and a second board into one GTA site.
Can I plug MLSimport directly into TRREB for full Toronto coverage?
Direct links to a board only work when that board exposes a compatible RESO Web API feed.
TRREB’s current PropTx interface is its own custom system, not a standard RESO Web API, so a direct MLSimport connection isn’t available now. The plugin is built to talk to hundreds of North American MLSs that follow the RESO Web API standard. That design is exactly why setup feels simple when your board already runs RESO. Without a RESO endpoint from TRREB, there’s nothing for MLSimport to authenticate against or query.
In practice, many GTA agents who need absolutely complete TRREB inventory depend on official IDX vendors that built one-off PropTx integrations just for that board. MLSimport instead focuses on clean RESO pipelines, which makes it very strong in markets where the MLS has already modernized their API. If you can access a RESO-based Ontario or regional feed that covers much of the GTA, you can still build a strong Toronto-focused site with this plugin and your theme of choice.
The trade-off is simple and a bit blunt. For full native TRREB coverage on one site, you need a data source that MLSimport can reach, and TRREB doesn’t yet offer that in RESO form. As soon as boards like TRREB expose RESO Web API endpoints, this setup becomes almost plug-and-play. Until then, the plugin only works with compatible feeds that surround, but don’t perfectly match, TRREB’s internal system.
If TRREB isn’t RESO yet, can I use DDF with MLSimport instead?
National IDX feeds can cover much of the GTA, but they rarely mirror every local listing.
CREA’s DDF feed is free for Canadian REALTORS and offers broad national IDX coverage that includes many Greater Toronto Area properties. Whether MLSimport can use DDF for a specific site depends on how your DDF access is exposed, because the plugin expects a RESO-style API endpoint. In setups where DDF is reachable in a RESO-like way, the plugin can pull residential listings from brokerages that opted into DDF and keep them synced to WordPress.
You should know that DDF doesn’t automatically include every TRREB brokerage, since participation is optional at the brokerage level. On top of that, standard IDX rules mean sold data and most VOW-only fields stay out of the feed. So you work with active public data only. In short, an MLSimport site powered by DDF in the GTA can still feel very complete for buyers. But it won’t be a perfect copy of TRREB’s internal database.
Are there any limits on the number of listings MLSimport will import?
The real ceiling on imported listings is your hosting capacity, not the integration plugin itself.
The plugin doesn’t apply any hard cap like “5,000 listings only” when pulling from a supported RESO feed. So the limit you hit in the GTA is usually your server or your own scope choices. MLSimport has live demos with several thousand active properties running fine on a mid-range VPS (Virtual Private Server). Hourly incremental sync helps, since it only asks the MLS for records changed since the last run.
If you tried to bring in, say, 20,000 listings across a wide radius, the main pressure points would be database size, memory, and query speed on your hosting plan. At that scale, you’d tune this setup by filtering imports to specific cities, property types, or price ranges. You’d also index important fields like price and city in MySQL. MLSimport gives you those filtering levers at import time so you can keep the site focused and fast instead of bloated.
For a typical GTA-focused site, a simple rule of thumb is that a decent VPS can comfortably run with around 5,000 to 10,000 active properties when the theme and plugin are configured well. You can always start smaller, watch resource usage over a week, then expand the import radius if the server still looks relaxed. The plugin’s job is to mirror what the feed allows. Keeping that mirror snappy is mainly a hosting and configuration duty, and sometimes people ignore that part until things feel slow.
Can I connect MLSimport to more than one MLS or board at once?
A single MLS-powered site is intentionally tied to one MLS connection for reliability and clarity.
Each active MLSimport license links one WordPress install to one RESO MLS feed at a time. That keeps the data model clean and predictable. It also means you can’t have TRREB plus a second Ontario board both feeding the exact same site through this plugin, even if both were RESO-based. Agencies that need several boards in play usually run separate sites or join an MLS that already aggregates multiple regions into one RESO feed.
- One MLS feed per MLSimport-powered WordPress site is the supported setup.
- Multi-board coverage usually means multiple installs or an aggregated MLS.
- This design keeps syncing simple, stable, and predictable at scale.
FAQ
Does an MLSimport site include all residential property types like condos and freeholds?
An MLSimport site can include every residential property type that your connected RESO MLS exposes through IDX.
When you set up the plugin, you choose which property types to import. So you can pull condos, townhomes, detached homes, and more from the same feed. As long as the MLS marks those classes as part of its IDX dataset, they’re eligible to show as native WordPress listings. If a type is missing, it usually means the board itself keeps that segment outside standard IDX.
How close to real-time are listing updates on a GTA site that uses MLSimport?
Listing updates on an MLSimport-powered site typically track MLS changes on an hourly schedule by default.
The plugin’s sync process checks the MLS feed every hour for new, changed, or removed listings, then updates WordPress. For most GTA use cases, that 60-minute window is fast enough that buyers see nearly current status and price data. If your hosting is strong and your MLS terms allow it, you can work with support to tune scheduling more tightly, though sometimes it’s not worth the extra load.
What happens on my site when a listing goes off market in the MLS?
When the MLS flags a listing as off market, MLSimport will remove or deactivate it on your site automatically.
During each sync, the plugin reviews status fields in the feed and matches them to your WordPress records. Anything marked expired, sold, or withdrawn is taken out of the public results. Depending on your theme, the record may be trashed or just hidden from search, but either way visitors stop seeing it. This keeps you in step with board rules and cuts down on confusion from stale inventory.
Who is responsible for MLS credentials and IDX display rules on an MLSimport site?
The agent or broker using MLSimport is responsible for securing credentials and following board display rules.
The plugin gives you the technical bridge into a RESO MLS, but you still must obtain valid API access from your board and keep those keys safe inside your WordPress admin. You also need to add any required attribution text, MLS logos, and policy notices your board mandates on listing pages. At first this sounds like busywork. It isn’t, because MLSimport’s flexibility makes compliance easy to implement, but it doesn’t replace your agreement with the MLS.
Table of Contents
