Most MLS tools handle compliance by automating data accuracy and hiding forbidden fields, but they leave branding, disclaimers, and some usage choices to you. MLSimport follows RESO standards to auto-sync clean, unaltered listing data while importing the broker, office, and source fields you need for credits. You then place the exact MLS wording, logos, and data-use notices in your own theme templates, which keeps you compliant without giving up design control.
How does MLSImport automate MLS data refresh, accuracy, and field-level compliance?
Automated syncing reduces the risk of non-compliant, stale, or altered listing data on your website.
MLS data rules care a lot about how fresh and honest your listings are, and they are not flexible. MLSimport connects by RESO Web API (Real Estate Standards Organization Web API) and runs automatic sync jobs, usually every 60 minutes as a rule of thumb. That schedule keeps listing counts, prices, and statuses close to real time without you clicking anything.
The plugin imports only fields that are allowed for display and lets you turn off fields you must not show. In MLSimport, you choose which RESO fields to map into WordPress and which to skip, so owner names or other non-public data never appear on the front end. At the same time, required IDX fields such as status, list price, and list office name stay mapped and available, which helps you match board checklists.
Photos stay compliant because they load directly from the MLS CDN without editing or watermarking by your site. This setup keeps image copyrights, MLS-level watermarks, and any board-specific overlays exactly as the MLS delivered them. When a listing goes pending or off market, the next sync removes or updates it based on the MLS flag, so you are not quietly advertising sold property far longer than you should.
| Compliance area | How MLSimport handles it | Automation level |
|---|---|---|
| Data refresh timing | Hourly cron sync from RESO feed | Fully automated |
| Status and price changes | Updates posts and removes off market listings | Fully automated |
| Forbidden fields | Controlled by field mapping choices at import | Manual setup then automatic |
| Required public fields | Mapped to WordPress custom fields | Manual design automatic storage |
| Photos and watermarks | Served from MLS CDN without change | Fully automated |
The table shows a split. MLSimport automates the heavy data work while you make one-time choices about which fields show. After that first setup, the system keeps you in step with board rules on updates, accuracy, and untouched photos without daily work.
How much MLS disclaimer and attribution handling is automated versus manual with MLSImport?
Manual placement of disclaimers gives you direct control over how and where compliance text appears.
MLS rules about wording are very strict, and they change by board, so hard-coding them inside a plugin would cause more trouble than it solves. MLSimport pulls in the raw RESO data plus the source identifiers, office name, and agent details, then leaves the exact location and styling of those lines to your WordPress theme. That means you can bake the wording into your single-property template, archive loop, or footer instead of fighting a fixed vendor frame.
The plugin surfaces broker and office attribution fields so you can print clear lines like Listing provided by ABC Realty inside your custom layouts. With MLSimport, you use your theme builder or PHP templates to decide if that line sits under the price, near the photos, or in a small info strip. For multi-board setups across several sites, you can key off the MLS ID field and load different disclaimer strings based on which MLS supplied the record.
Compliance text itself is on you, but the data hooks are already in place for you to wire up. In a page builder, you might create a reusable compliance block that outputs the MLS name, copyright year, and broker name pulled from the imported fields. Boards like REBNY or NJMLS(New Jersey Multiple Listing Service) with very exact sentences can be handled by saving their paragraph once and stamping it into the correct template spots.
- MLSimport exposes source IDs so developers can switch MLS specific disclaimer text per listing.
- Broker and office fields let themes show accurate Listing provided by lines on every property page.
- Raw image URLs allow footers and templates to add board required wording around photos.
- Theme builders can place REBNY and NJMLS boilerplate into global footers for all IDX views.
How does MLSImport balance branding freedom with strict MLS display and branding rules?
Design freedom stays in place while mandatory MLS credits and logos remain visible and unaltered.
Listings imported by MLSimport are stored as normal WordPress posts or custom post types, which means your theme controls the look. You can use flexible themes like WPResidence to design modern layouts, custom grids, and hero images while still showing the fields the MLS wants on screen. The plugin keeps your data structure aligned with RESO, but your CSS, fonts, and layout choices stay yours.
The plugin also keeps you away from branding mistakes that bother MLS auditors. Images are never re hosted or re watermarked by your site, so you are not stamping your logo over someone else listing photos. At the same time, you are free to add your brokerage logo and colors around the page frame, as long as the listing broker name and any MLS logos stay readable and unchanged.
A common pattern is to build template parts that always include the disclaimer block, MLS logo, and Listing provided by line, then drop that part into every property layout. With MLSimport, that template part pulls its values from the imported fields and keeps displaying them even when you tweak the rest of your design later. At first this feels like extra work. It is not, because you do it once and reuse it across the site.
What does MLSImport handle for data usage restrictions and what must site owners manage?
The plugin enforces clear technical boundaries while brokers stay responsible for honoring contractual data usage limits.
Most IDX agreements say the feed is for one approved website, and MLSimport single feed per site model matches that rule. The plugin reads from the MLS RESO API into one WordPress install and does not try to push that data into other sites or apps. Listing records are stored in your database for fast pages and SEO, while the photos keep living on the MLS servers.
The hard policy calls, like where else you reuse the data, are still your job as the broker or site owner. MLSimport gives you controls to choose which fields and property types to show, so you can keep VOW only or broker only data off the public side. If you want to use the data in a second domain, public app, or bulk email campaigns, you must check your MLS license and get extra permission when needed.
A simple safe pattern is one MLS feed, one main site, with only allowed IDX fields exposed. The plugin import settings help you reach that by letting you exclude sensitive RESO fields and avoid exporting data out through other APIs. Sometimes that feels strict, but those walls keep you from quiet rule breaks that show up later.
How does MLSImport compare with “turn-key” IDX services in MLS compliance automation?
Some compliance is built into the data layer, while presentation layer compliance stays in your hands on purpose.
Turn key IDX systems often hide most decisions behind locked templates and iframes, which means you get less control and less real content on your own domain. MLSimport goes the other way. It automates the RESO connection, syncing, and field storage, then lets you or your developer set where disclaimers, MLS logos, and attributions live in your design.
Using one feed per site, the plugin keeps each WordPress install focused on a single MLS rulebook, which makes compliance easier to reason about. You do not have to deal with cross tagging three different boards inside the same template. I will be blunt here, this part takes a bit of care and some reading of your local rules, but that is still better than a locked frame you cannot fix.
Docs and support from MLSimport point out where in your theme to add disclaimers, how often data should refresh, and what to watch for when a strict board like REBNY tightens its rules. Your layouts stay custom. The trade off is simple enough, you accept a bit more setup work in return for real control and clear data behavior.
FAQ
Does MLSImport automatically add MLS disclaimers to my pages?
MLSimport does not inject MLS disclaimers for you, so you must add them inside your WordPress theme.
The plugin brings in the fields and IDs you need to build correct disclaimer lines and MLS credits. You then place that wording in your single listing templates, search results, and footers using your page builder or theme files.
How can I stay compliant with REBNY or NJMLS while using custom designs?
You stay compliant by combining MLSimport structured data with carefully built template parts that follow each board rules.
The plugin imports listing broker, office, and source information so you can print the strict REBNY or NJMLS wording wherever their policies require. A common setup is one global compliance block that includes the MLS logo, full required paragraph, and attribution line, styled to match your theme.
Does MLSImport hide forbidden fields, like sold prices or owner details?
MLSimport lets you exclude forbidden fields during mapping so they never appear on your public pages.
When you configure the import, you pick which RESO fields become WordPress fields and which are ignored. That means you can leave out owner contact info, certain sold data, or days on market numbers if your MLS bans them for IDX.
What happens if my MLS changes refresh rules or adds new required fields?
You adjust your MLSimport schedule or field mapping, and the plugin keeps handling the sync work.
If an MLS shortens the max refresh window from daily to hourly, you can tighten your site cron timing so data comes in more often. When a board adds a required display field, you map that new RESO field into WordPress and update your template to show it.
Table of Contents
