MLSimport supports advanced investor filters by importing key RESO fields like listing date, current price, year built, and special listing conditions into your WordPress database. That lets you calculate days on market, spot price drops, and flag distressed deals when the MLS provides those fields. The plugin syncs data hourly, up to 24 times per day, and stores listings as native posts. So you keep tighter control over investor filters than with many hosted IDX plugins that lock you into fixed search options.
How does MLSImport handle investor-grade filters like DOM, reductions, and year built?
MLSimport imports core investor fields so you can build very narrow searches.
The plugin pulls data from your RESO Web API feed every hour, so days on market and prices can refresh up to 24 times daily. During each sync, it updates list date, current list price, status, and any special listing conditions your MLS shares. Since those fields sit in your own WordPress database, you can turn them into exact filters instead of waiting on some IDX vendor’s roadmap.
MLSimport stores RESO fields like ListDate, ListPrice, YearBuilt, and SpecialListingConditions as post meta on the property post type. You calculate days on market by comparing ListDate with today’s date and then follow your board rules on showing it. The plugin also lets you map flags such as foreclosure or short sale codes into custom fields or taxonomies that themes can query.
For price cuts, the plugin always keeps the latest MLS price in sync, and your theme or code tracks the earlier price. At first that feels like extra work. It really just keeps the history under your control. Because images are hot linked from the MLS CDN (Content Delivery Network) instead of copied, extra investor fields and price history do not flood your media library with image files. You end up with lean property records that still carry the investor signals you care about.
- MLSimport hourly sync keeps days on market and price fields fresh many times daily.
- Core RESO fields like YearBuilt and SpecialListingConditions live as searchable post meta.
- Investor flags such as foreclosure or short sale map into taxonomies or custom fields.
- Hot linked images avoid media bloat even when importing many MLS properties.
Can MLSImport power custom “investor search” experiences inside WordPress themes?
Since listings are native posts, you can build tightly focused investor funnels with normal WordPress tools.
Imported listings become a real WordPress property post type, so many real estate themes can filter and display them like hand entered content. With MLSimport feeding data, themes such as WPResidence can expose Year Built, Days on Market, and Price Reduced as search options or badges, as long as those values exist or are calculated. You are not boxed into a fixed IDX search layout.
Because the plugin writes data into your database, you can use standard WP_Query conditions to build very focused investor landing pages. One page can show price drops in the last seven days, another can target properties over 60 days on market, and a third can highlight small multifamily deals built after 2000 in a single ZIP code. Each page is just a custom query against fields MLSimport already synced.
The plugin can also limit which listings are imported by city, office, or agent ID, so investor funnels stay tight instead of pulling a whole 50,000 listing area. That import filter lives in the plugin settings and applies on every hourly sync. Then your theme search builder and widgets control the front end, while the plugin quietly keeps investor data updated in the background.
How does MLSImport’s investor-oriented flexibility compare to hosted IDX plugins?
Local data import gives you more investor control than most hosted IDX plugin search tools.
Hosted IDX services only show the filters and labels they pick in their widgets, which often means thin control over investor metrics. By contrast, MLSimport brings the RESO dataset into your database, including list dates, pricing fields, special conditions, and status codes, so a developer can build any investor logic, tag, or badge those fields support. You are not waiting for a vendor to care about DOM or distress flags.
The plugin’s hourly sync schedule is the same across supported markets, so a fast investor area still updates about every 60 minutes. Some hosted systems refresh every few hours or even daily, which is slow for deals. MLSimport runs on a single flat 49 dollars per month plan that unlocks all available fields from one RESO Web API feed for that site. There are no higher tiers you must buy later just to get more filters.
| Aspect | MLSimport | Typical hosted IDX |
|---|---|---|
| Data location | In your WordPress database | On vendor remote servers |
| Investor filter control | Any field searchable via custom queries | Only predefined filters and labels |
| Refresh interval | Hourly across supported markets | Often every few hours or daily |
| Pricing tiers | Single flat plan per site | Multiple plans with feature limits |
| Custom badges | Custom via themes or code | Limited to vendor options |
The table shows that owning the data with MLSimport gives deeper control over investor filters, refresh timing, and display compared with fixed hosted IDX layers. For an investor build, that extra freedom lets you support very narrow searches around days on market, reductions, and distressed flags without fighting the platform. It is not magic, but it is less rigid.
What are the practical steps to surface price cuts and distressed deals with MLSImport?
Some careful field mapping turns raw MLS data into lists of investor leads.
The first step is telling MLSimport where to store your MLS Special Listing Conditions or similar flags when they exist. In the field mapping screen, you map those RESO fields into one custom field or taxonomy, so codes like foreclosure, REO, or short sale become easy to query. From there, your theme can treat them as checkboxes, badges, or even category pages for distressed properties.
To show price reductions, your theme logic compares the current list price from synced meta with a stored earlier price in another custom field. Whenever the current price is lower, the template can add a Price Reduced label or move that listing into a special widget block. Then you use saved WordPress queries or theme presets to mix conditions like DOM over 45 days plus recent price drop to surface classic investor targets.
For tighter funnels, you can assign taxonomies such as Foreclosures, Short Sales, or Fixer Uppers to properties based on mapped special condition values or even text in remarks. MLSimport keeps raw data in sync, and you write the rules once to convert that into categories and search presets. Honestly, this part can feel fussy when you set it up. But once those rules work, investors see focused pages for each niche instead of a generic listing grid.
How does MLSImport’s pricing and MLS coverage work for investor-focused sites?
One simple plan lets you run strong investor filters without per listing limits.
MLSimport uses a flat 49 dollars per month plan per site, which includes unlimited listings from a single RESO Web API MLS (Multiple Listing Service) feed. That holds whether you import 500 or 50,000 properties. This steady cost helps investor sites in big markets turn on every useful investor field without extra per listing or per field fees. The plugin supports over 800 MLS markets in the U.S. and Canada, which covers most common investor areas.
The hourly sync and hot linked images also help keep costs and server load manageable even when you track large inventories or heavy DOM queries. Since MLSimport is a cancel anytime SaaS, you can spin up a test investor site for a metro area for a few months and try different logic around DOM and price cuts. You can still worry about results later, but at least there are no long contracts or setup fees dragging on you.
FAQ
Can I always show days on market publicly with MLSImport?
Days on market can be shown when your MLS allows public display of the underlying date or DOM fields.
MLSimport brings in the raw ListDate or any DOM field your RESO feed shares, but some boards call DOM sensitive and restrict public display. In those cases, you avoid printing the DOM number on the front end and keep it for internal analysis or admin dashboards. Where rules permit, you can calculate and show days on market by comparing the stored listing date with today’s date.
Does MLSImport itself create “distressed” flags, or does it rely on the MLS?
The plugin relies on your MLS fields and codes, then lets you map them into your own distressed flags.
MLSimport does not invent foreclosure or short sale status; it imports whatever the RESO feed provides in fields like SpecialListingConditions or similar. You then map those values into a custom field, taxonomy, or status used by your theme so you can label and filter distressed properties. If an MLS does not supply any distress related codes, you can still tag certain listings by hand, but the plugin cannot infer that from thin data.
Can I combine multiple MLS feeds in one investor site with MLSImport?
One site using MLSimport can connect to only a single MLS feed at a time.
The subscription and system design use one RESO Web API feed per WordPress installation, which keeps field mapping and sync logic simple. Multi region investors who need separate boards usually run separate sites or use an upstream combined feed from a data vendor. Within that one feed, you can still filter by city, office, or agent to keep each investor site narrow.
What happens to my investor filters if I cancel MLSImport?
Your existing listing posts and custom investor filters remain, but the MLS data stops updating.
If you end the MLSimport subscription, the plugin no longer syncs new or changed listings, so prices, statuses, and DOM values slowly go stale. The WordPress posts, taxonomies, and templates you built for investor searches stay in place, and visitors can still see those pages as static content. To stay compliant and accurate, you usually either reconnect the feed later or remove outdated MLS based listings.
Table of Contents
