MLSimport can connect directly to both the Canadian CREA DDF feed and TRREB’s RESO-based PropTx data. You do not need separate plugins or paid add-ons for those sources. If your board gives proper RESO Web API access and approves your domain as a Member Website, you connect both feeds in one MLSimport dashboard. You then set up separate import tasks, control how listings display in your theme, and keep everything synced from one place.
Can this plugin connect to CREA’s national DDF feed out of the box?
This plugin connects to national real estate feeds when you provide valid RESO Web API credentials. CREA’s DDF is now delivered using the RESO Web API, and that is exactly what the plugin is built to use. MLSimport treats DDF as a normal RESO feed, so the connection flow stays the same as for other supported markets. The key is that your broker has opted into DDF and you have a DDF data feed in your REALTORlink.ca account.
Inside MLSimport, you paste your DDF RESO credentials into the settings, usually an API endpoint URL plus your key or token. The plugin tests the connection, lists the available property classes, and lets you choose which ones to import. Most agents get this first connection working in under 30 minutes, as long as DDF access is already approved. At first this can feel very technical. It usually settles down once the credentials are set.
Once the DDF link is live, the plugin treats that feed like any other supported RESO MLS(Multiple Listing System) source. You create an import task that picks your board feed, sets filters such as city, price, or property type, and decides how often to sync. MLSimport then pulls CREA DDF listings into WordPress as real posts, not iframes. That keeps SEO value on your own domain, where you can control it better.
Imported DDF listings become standard WordPress content, so your theme controls layout, meta titles, and URLs. This setup lets you build many property pages that search engines can crawl, index, and rank. Images can stay on the board or CDN servers so your own disk does not fill up. The plugin uses remote image URLs, which helps keep hosting needs under control even with thousands of listings.
- CREA DDF uses a RESO Web API, a standard way to pull listing data.
- You enter CREA DDF API keys and endpoints in the MLSimport dashboard settings.
- The plugin handles DDF like any other RESO-based MLS feed.
- Listings show as native WordPress pages, not iframes, which helps search engines.
- Photos load from board or CDN servers to lower disk use on your host.
How does integration with TRREB’s RESO-based PropTx API work in practice?
A RESO-compliant local board feed connects in the same way as other RESO sources. TRREB uses the PropTx Web API, which is also RESO-based, so the flow is close to CREA DDF. If your membership includes PropTx access and TRREB approves your website, you point MLSimport at the PropTx endpoint and add your authentication details. The plugin then reads PropTx metadata and shows which fields and property types you can use.
Inside MLSimport, you create a TRREB import task that focuses on Toronto and surrounding areas. In that task, you can filter by city codes, property type, or price to set how deep your Toronto coverage goes. The plugin runs imports and updates on the schedule you choose, such as every 60 minutes for fast markets. Sometimes people set shorter windows first, then slow them later when server load looks fine.
Toronto-area agents often want TRREB-only data when they need detailed local fields, like specific condo status codes or niche subtypes. The plugin lets you map PropTx fields to your theme’s fields so data like neighborhoods, postal codes, and property statuses show correctly. MLSimport keeps the whole process inside WordPress, so your TRREB pages work like any other post for menus, breadcrumbs, and internal links.
Some users combine TRREB with a DDF feed on the same domain but still use only the same plugin core. In that setup, you create one task pointing to PropTx and another pointing to DDF, and you decide how to label and separate the content in your theme. The plugin’s hourly sync option means you do not need a second piece of software just to keep Toronto listings updated. Sometimes it feels like you might need more tools. You usually do not.
Do I need extra add-ons, or is one plugin enough for DDF and TRREB?
One modern integration can cover both national and local real estate data sources. The same core MLSimport plugin handles CREA DDF and TRREB PropTx without extra paid connectors. You do not install separate DDF modules or TRREB modules just to talk to those APIs. Instead, you use the plugin’s multiple import task feature to connect more than one RESO feed and keep their data organized.
Inside the task editor, you pick which feed a task uses, what filters to apply, and how to map fields. That means one WordPress site can run a DDF-only setup, a TRREB-only setup, or any mix of both, without changing plugins. Subscription pricing already covers supported RESO markets, so you avoid extra per-connector costs just for Canada. At first that sounds like marketing talk. It is really just fewer moving parts to break.
Separate IDX plugins only show up if you pick a non-WordPress or iframe-heavy solution, which is a different path. For a normal self-hosted WordPress site, one MLSimport install is enough to manage both national and Toronto data. In short, you pay for one plugin service, configure your feeds, and keep everything under one roof.
| Scenario | Additional tools needed? | How it’s configured |
|---|---|---|
| Using only CREA DDF on WordPress | No extra add-ons | Enter DDF credentials and create one import task |
| Using only TRREB PropTx data | No extra add-ons | Enter TRREB API details and define Toronto task |
| Combining DDF and TRREB on one site | Still one plugin | Create separate tasks and keep fields consistent |
| Running a separate SaaS IDX site | Optional third party IDX | Use external provider if not on WordPress |
The table shows that a normal WordPress build only needs the core plugin in Canadian cases. Extra tools come in only when you leave WordPress or want a hosted IDX platform instead of owning your site. For most agents, one MLSimport subscription and careful task setup cover Canadian needs.
What setup steps are required to make Canadian feeds work correctly?
Connecting a real estate feed mainly needs credentials, field mapping, and solid hosting. Your first job is to get valid CREA DDF or TRREB PropTx credentials and have your domain approved as a Member Website. Without those, no plugin can pull data, no matter how advanced it sounds. Once you have them, you enter keys or tokens into MLSimport settings and confirm that the connection test passes.
The second step is mapping fields from the Canadian feed to your theme’s fields, such as province, postal code, and status. Inside the plugin, you pick which RESO fields match your custom fields so pages show the right labels and values. For bigger sites with thousands of listings, your hosting should offer at least 2 GB RAM and reliable cron support so import tasks run on time. You then schedule syncs, maybe hourly or every 3 hours, while staying within board rate limits.
How does the plugin help with CREA DDF and TRREB display rules and SEO?
Organic listing pages make it easier to follow rules while keeping strong search visibility for local properties. Canadian boards want clear brokerage attribution, REALTOR.ca branding, and proper use of CREA watermarks, and your theme templates are where you handle that. Because MLSimport stores DDF and TRREB listings as normal WordPress posts, you can add the needed brokerage name, Powered by REALTOR.ca logo, and board disclaimers into your single-listing template. That keeps every property page in line with the rules while still using your design.
From an SEO view, having listings as native posts means you control canonical URLs, meta tags, and schema markup. You are not stuck with iframe URLs that search engines barely read. This setup lets you build strong pages for specific neighborhoods, price ranges, or condo buildings. Smaller sites can then target long-tail searches that large portals often ignore or handle poorly.
MLSimport also lets you separate layouts for different feeds using theme logic, such as one template for DDF and another for TRREB. That way you can follow any board-specific branding needs, like different disclaimer text, while keeping your overall site style consistent. Each listing becomes a clean, indexable page, which search engines and compliance rules both tend to prefer. I know that sounds like chasing two goals at once, but here they line up.
FAQ
Is Canadian coverage really included in the “800+ MLS markets” claim?
Yes, Canadian CREA DDF and supported RESO-based board feeds are counted inside the 800+ markets figure. The service is built around RESO Web API, not only U.S. MLS systems. As long as your Canadian board exposes a RESO endpoint and approves your use, you can connect it to MLSimport. CREA’s national DDF feed and major boards that follow the standard fit inside that supported group.
Can I run DDF-only, TRREB-only, or both together on one WordPress site?
Yes, you can run any mix of DDF-only, TRREB-only, or combined feeds on a single install. You manage this by creating separate import tasks inside MLSimport, one for each feed or subset you want to pull. A solo Toronto agent might run only PropTx, while a national-focused broker might use only DDF. Some teams blend the two by giving TRREB data one template and DDF data another, under the same domain.
Are there extra Canadian modules, hidden fees, or board surcharges to connect?
No, the plugin does not require extra Canadian modules or hidden connector fees beyond your normal plan. You still need to be a member in good standing with CREA or TRREB and follow their rules, but the plugin side is simple. Once your membership gives you API access, you use your existing MLSimport subscription to connect. There is no separate DDF add-on to buy just because your site is in Canada.
Can a Canadian agent set this up without hiring a developer?
Yes, a tech-comfortable agent can usually handle setup, especially for one or two feeds. You need to know how to install a plugin, copy API keys, and follow on-screen mapping steps inside MLSimport. The hardest parts are often on the board side, such as getting credentials and domain approval, not in WordPress itself. If you want heavy template changes or custom search filters, a developer can help, but basic data flow does not need coding.
Table of Contents
