Yes. CREA and TRREB place real limits on how long you can keep MLSimport data cached without updates, and MLSimport is built to match that pattern with automatic syncing and clean up. CREA expects at least daily DDF (Data Distribution Facility) refreshes and quick removal of off market listings, while TRREB VOW rules want fast updates behind a login. By running scheduled syncs, removing sold or expired listings, and loading images from the MLS CDN, the plugin helps your cache stay fresh instead of drifting.
What do CREA and TRREB actually say about caching and display duration?
CREA and TRREB both require timely updates and fast removal of off market listings, which limits long term caching.
CREA’s DDF rules expect listing data to refresh at least once every 24 hours, and they expect off market listings to leave public pages soon after status change. They also want the CREA image watermark visible and information accurate on every public view. So a static copy of listings that sits for weeks without syncing against the feed is usually not safe.
TRREB’s main broker feed is VOW, which is for logged in, registered users and not wide open public indexing. Under VOW rules, users normally must create an account with a name, email, and agreement before they see full listing detail. TRREB expects those VOW displays to stay in line with the board feed, so long gaps in updates or stale cached copies can create real compliance risk.
Many Canadian boards following CREA’s model rules also limit how long sold or expired listings can stay visible, often using a set number of days after closing. Policies often treat showing old sold data to registered VOW users differently from showing it broadly to the public. MLSimport fits into this pattern by giving you scheduled refresh and automatic removal tools so your site doesn’t slowly turn into an archive of out of date data.
How does MLSimport’s sync engine handle CREA and TRREB freshness rules?
Automated sync and removal of off market properties help keep listings in line with board freshness requirements.
| Sync feature | What it does | Why it helps compliance |
|---|---|---|
| Scheduled sync interval | Runs automatic updates as often as every hour | Keeps listing data refreshed within daily limits |
| Status change handling | Detects sold, expired, withdrawn, off market statuses | Removes non active listings from public pages fast |
| RESO Web API connection | Pulls data directly from the MLS RESO endpoint | Keeps your site content close to the source |
| Admin adjustable frequency | Lets you choose hourly, every few hours, or custom | Supports tighter refresh for stricter board rules |
| Sync activity logs | Records each job status and any errors | Makes it easier to notice stalls or failures |
MLSimport connects to your MLS through the RESO Web API (Real Estate Standards Organization Web API), then runs scheduled sync jobs using WordPress cron or a real server cron. Most sites set the plugin to update at least every 60 minutes as a safe rule, which is already stricter than the “refresh every 24 hours” timing that many DDF agreements mention. You can shorten that window further, for example every 15 or 30 minutes, if you want to stay very close to real time.
During each sync, the plugin checks listing statuses and flags anything that moved to sold, expired, withdrawn, or another off market state from your board. MLSimport then unpublishes or removes those items from your public inventory so visitors no longer see them as active. The sync logs in the admin help you spot problems fast, such as a feed error that might otherwise leave stale listings live for longer than a day.
Are there specific limits on how long listings can remain cached on my server?
Local listing caches usually must refresh within a short, set time window written by each board.
Many DDF and API agreements say that any local copy of listing data must refresh within a set time, often 24 to 48 hours. Some boards use tighter timing for high volume feeds, and some add extra limits around sold data, such as only allowing display for 30 or 90 days after closing. The core idea stays simple. Your local cache is meant as temporary working storage, not a long term marketing archive.
MLSimport follows that idea by treating your WordPress database as a synced mirror of the live MLS feed instead of a permanent store. When the plugin syncs, it overwrites outdated fields, removes no longer allowed listings, and keeps your pages lined up with current MLS statuses. You still need to read your own CREA, TRREB, or local board agreement, but this setup helps your cache stay inside that short refresh window instead of drifting outside it.
How does MLSimport’s image handling help with CREA and TRREB compliance?
Serving photos from the MLS image CDN keeps watermarks and cuts risk from old local copies.
MLSimport loads listing photos from the MLS or provider CDN as remote images instead of saving them into your WordPress media library. That choice means any CREA watermark, TRREB overlay, or board branding stays exactly as delivered, without you editing or stripping anything. When the listing changes at the MLS, the images behind those URLs update or disappear in step with it.
Because the plugin doesn’t keep permanent local copies of photos, you’re less likely to keep old images live after a listing expires or is sold. If a board shuts down access to a set of URLs, those images stop loading on your site at the same time. For CREA and TRREB rules that focus on proper watermarks and no long term reuse, this kind of remote image setup acts like a safety net, even if it’s not perfect.
What do I still need to configure manually to stay within CREA and TRREB rules?
Even with automation, you must still place required legal text and access controls inside your theme templates.
- You must place CREA and MLS trademark statements in your theme footer or listing templates.
- You must insert any MLS attribution and disclaimer fields that MLSimport imports into visible page areas.
- You must configure registration walls and login flows if you use TRREB VOW data.
- You must decide whether to hide or limit sold data based on your board agreement.
MLSimport can pull standard attribution fields and disclaimer text from the RESO feed, but it doesn’t rearrange your theme layout by itself. As the site owner, you choose where those fields show, such as under the photo gallery or at the bottom of each property page. CREA and TRREB both expect very exact trademark language, so you should copy the official text into your templates without editing or shortening it.
TRREB VOW setups also need access control, which usually means building or enabling a registration wall in your WordPress theme or with another plugin. This part often takes more time than people think, because design and login flow can get messy. MLSimport handles the data side, but it doesn’t enforce logins or cookies by itself, so you must wire that part. In short, the plugin sends you current, filtered data, and you add the legal text and user gates that your own board agreement requires.
FAQ
Do CREA or TRREB publish one fixed “maximum cache time” for all sites?
CREA and TRREB mostly describe freshness and accuracy rules instead of one universal cache time number.
Most agreements talk about keeping data up to date, refreshing at least daily, and removing off market listings quickly. Some boards also define exact timing, like requiring changes to appear within 24 hours. At first that sounds like a tiny detail. It isn’t. MLSimport lets you schedule syncs as often as you need so your cache doesn’t drift beyond the limits in your own contract.
Does MLSimport’s auto removal of sold and expired listings line up with typical DDF rules?
Yes. MLSimport’s automatic removal of sold and expired properties is designed to match standard IDX and DDF display rules.
Typical CREA DDF and similar feeds want sold or expired listings pulled from public display shortly after status change. The plugin checks those statuses on each sync run and unpublishes affected properties from your site. You can still keep any allowed internal records on your end, but what visitors see stays focused on active inventory. Unless your board writes a special exception, this default behavior lines up with common rules.
Who is ultimately responsible for compliance, MLSimport or the brokerage?
The brokerage or site owner always carries final responsibility, even though MLSimport lowers day to day risk.
Your data agreement with CREA, TRREB, or a local board sets the binding rules, and only you sign that contract. At first it seems like the plugin could “handle compliance” for you. It can’t. MLSimport provides tools like scheduled syncs, status filtering, CDN image usage, and logs so your site can follow those rules in practice. You should still review your board handbook at least once or twice a year and adjust plugin settings or templates if policies change.
Can I tune MLSimport to hide sold data completely for my market?
Yes. You can configure MLSimport’s filters so sold listings never appear on your public site.
Some Canadian boards allow sold data only behind a login, and some brokers prefer not to show it at all. Inside the plugin settings, you can filter by status so that only active and allowed categories are imported or displayed. That way your setup can follow the strictest local rule, whether that means no sold data or only short term visibility. If your board later loosens rules, you can relax the filters without rebuilding your site.
Table of Contents
