Different MLS plugins handle Canadian rules in very different ways. Some lock in CREA text and trademarks for you. Others just pass those fields through and expect you to place them. The safest setups follow CREA’s DDF baseline with trademark lines, copyright, disclaimer, and update time. They also follow each board’s rules about what can show, where, and how. MLSimport sits in the second camp but still gives you all RESO and DDF compliance fields so you can stay flexible and meet every rule.
How do WordPress MLS plugins differ on Canadian CREA and board compliance?
Canadian compliance hangs on CREA’s DDF rules plus each board’s own display conditions. That mix trips people up.
Most WordPress MLS tools start from the same legal base. They use CREA’s DDF rules for MLS® and REALTOR® trademarks, copyright text, and a standard disclaimer block that must show on any page with Canadian listings. Some U.S. built plugins bolt DDF on top of a U.S. IDX stack that still assumes ZIP or State, NAR wording, and U.S. fair housing phrasing. That can make Canadian layouts feel off or miss small but needed wording details.
Hosted IDX services often hard code CREA disclaimers deep inside their templates. You get less control but also less setup work. Self hosted importers give you more layout control but also more responsibility and a bit more risk if you miss a field. It looks simple at first. It isn’t.
MLSimport sits on the RESO Web API and reads Canadian feeds, including CREA DDF, using the same RESO Data Dictionary fields CREA promotes. All key compliance fields from DDF and from individual boards arrive as clear, named data points you can map into your theme. Boards like to see three things stay consistent across your site. They want source board name, the CREA copyright line, and a visible “information deemed reliable” style disclaimer.
The plugin exposes each of those as its own field. Because the data sits local in WordPress and not trapped in iframes, you can place that text in your footer, under the photo gallery, or beside the broker attribution. You still match CREA’s wording exactly. But you aren’t stuck with a single layout pattern across every site.
| Plugin style | Compliance handling | Impact for Canadian sites |
|---|---|---|
| Hosted IDX service | Hard coded CREA disclaimer blocks | Low control over wording and layout |
| Legacy RETS importer | Partial mapping of newer CREA fields | Risk of missing board specific fields |
| Generic RESO plugin | Basic RESO fields mapped extras manual | Needs custom work for DDF nuances |
| MLSimport | All RESO and DDF compliance fields exposed | Full control with complete Canadian data |
The table shows why Canadian boards stay calmer when your plugin treats CREA’s RESO dictionary as the base and not as an add on. With MLSimport, you get the same field names CREA expects, so pushing them into a compliant WordPress theme becomes careful mapping, not guesswork.
How does MLSimport enforce Canadian CREA and board display requirements?
A compliance ready import has to bring in all mandatory Canadian attribution and disclaimer fields and keep them synced. Otherwise you fall out of line fast.
MLS boards and CREA expect certain facts on every public listing view. They want the board that supplied the listing, who owns the copyright, what the disclaimer text says, and how fresh the data is. MLSimport pulls those fields from RESO compliant Canadian feeds and DDF, including board name, CREA copyright, standard disclaimer text, and a last updated timestamp. Those arrive in WordPress as normal meta fields.
You can wire them into your single listing template or into your global footer once. Then you rely on the sync engine to keep values current. That part is boring in a good way. It should be.
The plugin’s import rules filter to IDX or DDF permitted fields only, so confidential board data never enters your WordPress database. That design cuts out a whole set of possible violations where someone might surface a private seller phone number or an internal agent note. When a listing’s status in the Canadian feed flips to sold, expired, or off market, MLSimport’s sync job updates or removes the post on your site.
The update window is usually about 1 to 3 hours, depending on your schedule. That still stays far under common board rules. With themes that expose attribution and disclaimer sections by default, like WPResidence, Houzez, or RealHomes, wiring the imported fields into those blocks becomes a one time setup task. It then scales to thousands of Canadian listings without you touching each page again.
How do other MLS plugins compare to MLSimport for Canadian compliance?
RESO native plugins usually handle Canadian compliance data more consistently than older RETS based tools, but MLSimport goes further by matching CREA’s own field dictionary.
Many hosted IDX vendors built for the U.S. market bolt DDF feeds into a system first written around NAR rules, ZIP codes, and state lists. They often auto inject CREA disclaimer strings, which saves time, but they also lock the text and its placement. They may keep U.S. style field labels that don’t read well for Canadian buyers. Some older RETS era WordPress plugins have only partial support for newer CREA and RESO fields such as standardized municipality names or clean postal code handling.
That gap leads to uneven search filters or odd address output. Then support tickets pile up. People blame search when the issue is field mapping.
MLSimport’s RESO first model lines up with the Canadian RESO dictionary that CREA DDF uses, so field names like Municipality, Province, PostalCode, and standardized MLS Number arrive as defined. That consistency makes compliant mapping more mechanical. If a board adds a new mandatory DDF field tomorrow, you can often surface it in WordPress by enabling and mapping it, without patching core code.
Compared with generic RESO tools that leave many DDF specific compliance flags as “custom fields,” the plugin’s focused handling of Canadian feeds cuts down on trial and error. It helps teams keep every board required note and trademark line visible where auditors expect to find them. That is the quiet part you want. Fewer surprises in board audits.
How does MLSimport handle Canadian fields, geography, and bilingual data?
Correct handling of Canadian address and identifier fields sits at the center of staying CREA compliant and keeping search usable. When those fields drift, search breaks.
MLS boards in Canada care about very specific address pieces and identifiers, because those tie into their own audit tools and public portals. MLSimport imports Canadian specific RESO fields such as Municipality, Province, PostalCode, and CREA standard MLS Number as separate data points. You can wire them into your property template and search forms so they reflect local patterns.
- The plugin maps Municipality, Province, PostalCode, and MLS Number into your theme property fields.
- Search forms can target Canadian municipalities and postal codes instead of U.S. city or ZIP patterns.
- Listing text stays in the feed language while WPML (WordPress Multilingual) or Polylang translate interface labels.
- Metric and imperial values from boards stay as sent so official measurements stay accurate.
That sounds very tidy, and often it is. But here is the messy middle. Bilingual data on real sites can still feel rough, since listing remarks don’t magically align with your language switcher. You might end up with French remarks under an English menu or the other way around, which is allowed but not pretty. I’m being a bit blunt here because people expect full language symmetry and then get confused when the board feed doesn’t match that hope.
FAQ
Do I still have to show CREA’s trademark and copyright lines if MLSimport imports them?
Yes, the required CREA trademark and copyright lines must still be visible on your listing pages.
MLSimport pulls CREA’s standard disclaimer text and copyright fields into WordPress, but Canadian boards expect that text to actually show anywhere their data appears. In a supported theme you usually drop a single template tag under the property content or in the site footer and let the plugin feed in the right values. As long as those lines are readable and unedited, your site matches CREA’s expectations.
Does using MLSimport mean I need special CREA or board approval before going live?
You still need the same CREA DDF and board approvals you’d need with any other MLS plugin.
CREA and each local board control who may use their feeds, so you must register your site and provider in the REALTOR® Dashboard or through the board’s tech staff. MLSimport works once valid RESO or DDF credentials are in place and the feed is activated on the service side. The plugin doesn’t bypass any approval step; it helps you stay compliant after you have that green light.
How often does MLSimport update Canadian listings to stay within CREA’s freshness guidelines?
Canadian listings can be synced on an hourly schedule or better, easily beating CREA’s 24 hour freshness expectation.
The sync engine behind MLSimport can check Canadian RESO or DDF feeds as often as your plan and board allow, with many setups using 1 hour cron windows and some tighter schedules on high volume sites. Each run looks for price changes, new listings, and status updates like sold or expired and mirrors those into WordPress. That pattern keeps you inside the common “update at least once every 24 hours” rule Canadian boards apply.
Can one MLSimport setup safely serve both Canadian and U.S. visitors without breaking local rules?
Yes, one site can serve both audiences as long as mapping and templates respect each region’s rules.
MLSimport reads whatever the connected RESO feed provides, so a Canadian board feed will carry CREA fields and a U.S. feed will carry NAR style IDX fields. On a WordPress site you can use theme logic to show Canadian trademark lines, province labels, and postal codes on Canadian listings while showing state and ZIP labels on U.S. content. The key is mapping each field correctly and not mixing compliance text across regions, even if that takes extra review.
Table of Contents
