Yes, you can import only the property types, price ranges, and areas you care about and keep your site focused and fast. With MLSimport, you define narrow import rules at the feed level, so WordPress only receives listings that match your niche. That means fewer useless posts in your database, quicker pages, and a site that looks built for your exact market instead of the whole MLS(Multiple Listing System) universe.
How does MLSimport let me limit imports by property type and status?
You can limit MLSimport feeds to only the property types and statuses that match your business focus.
The plugin connects to your MLS through the RESO Web API and pulls listings in as normal WordPress properties, such as the “property” post type used by themes like WPResidence. MLSimport lets you define one feed at a time, and each feed can include or exclude specific PropertyType and PropertySubType values from the MLS. You can keep Residential and Condo, skip Land and Commercial, and keep your content clean.
Inside the MLSimport feed settings, you choose which listing statuses to allow, using the exact values exposed by your MLS. A common setup is to import only Active and Coming Soon listings, while ignoring Sold, Expired, Canceled, or Withdrawn records that add noise. Because the plugin is built around targeted imports instead of “grab everything,” your WordPress database stays smaller even if your MLS has 50,000 or more current records.
This setup also helps when you want a tight niche, such as condos only or new-construction homes only. You tick the PropertyType and PropertySubType combinations that match that niche and leave the rest off. At first this seems minor. It is not. MLSimport then syncs only those matching listings on every run, so you avoid wasting queries, disk space, or indexing time on property types your visitors never care about.
Can I use MLSimport to focus on specific price ranges or niches?
Price filters let you import only the value ranges that match your target market or niche.
Each feed in MLSimport can have a minimum and maximum ListPrice, using the ListPrice field from the RESO feed as a hard gate. You might set one feed from 250000 to 600000 for first-time buyers and another feed from 1500000 to 5000000 for luxury, and the plugin will only create posts for listings that land inside those bands. This keeps your WordPress property archive in line with the kind of inventory you actually sell.
You can also create separate feeds for different price-driven segments and map them to different sections of your site. For example, an “entry-level homes” section could attach to a feed capped at 500000, while a “luxury estates” section uses a feed with a minimum price of 2000000 plus other filters. MLSimport respects whatever ListPrice limits you set, so your higher-end pages do not get cluttered with low-price rentals or starter condos.
Luxury agents often stack price filters with other fields that the MLS exposes, such as waterfront flags or minimum bedroom counts. While the interface focuses on core RESO fields like ListPrice, you can mix that with your city and property-type filters to produce very tight luxury-only feeds. Because the plugin queries the MLS by price before importing, your WordPress database holds fewer rows, which usually improves performance once you reach a few thousand properties.
| Feed goal | Example price band | Typical MLSimport filters |
|---|---|---|
| Starter homes | $250,000 to $600,000 | Residential, selected cities, Active only |
| Move-up buyers | $600,000 to $1,200,000 | Residential, 3+ bedrooms, main suburbs |
| Luxury waterfront | $2,000,000 to $10,000,000 | High min price, waterfront flag |
| Investment condos | $200,000 to $450,000 | Condo subtype, specific ZIP codes |
This kind of feed layout lines up your site structure with real price bands. Instead of one bloated import covering every dollar amount, you use several tight feeds that match how buyers search and how your brand is positioned. It looks like extra work at first. But long term, managing content gets easier, not harder.
How precisely can MLSimport target cities, ZIP codes, and hyperlocal areas?
City and area filters let you run a hyperlocal site without importing irrelevant locations.
The plugin reads location fields straight from the RESO Web API feed your MLS provides and then lets you pick which places to include in each feed. With MLSimport you can select a single city, several cities, or specific postal codes and have the import skip everything else. For a tight farm area, that often means only pulling a few ZIP codes or municipalities instead of the full metro region covered by the MLS.
In broad national feeds like CREA DDF(Data Distribution Facility), where one pool may cover all of Canada, the hyperlocal controls become vital. MLSimport lets you focus that large dataset down to one province, a handful of municipalities, or similar supported regions so your WordPress site is not buried under thousands of out-of-area posts. By filtering on city and region fields at import time, the plugin keeps your site honest to the places you actually serve.
Once the listings are imported as regular WordPress posts, you can build landing pages for each target city or neighborhood using your theme tools. Those pages then only show the properties that match your feed filters, such as “Downtown Toronto condos” or “Eastside single-family homes.” Because the off-area locations never got imported in the first place, your city archives and search results stay focused instead of mixing in random towns from 100 miles away.
Will selective importing with MLSimport keep my WordPress site faster and lighter?
Limiting imported listings to what you truly need helps your real estate site stay fast.
Every listing is a WordPress post, so importing fewer but more relevant properties usually means a smaller database and quicker queries. Instead of dragging in every record from an MLS with 80,000 active listings, you might pull 2,000 to 5,000 that match your property type, status, price, and area filters. MLSimport is built around this idea of targeted feeds so your server does not waste time rendering pages for junk inventory.
The plugin also keeps image storage lean by using MLS or CDN image URLs rather than copying every photo into your media library. That alone can prevent tens of gigabytes of disk use when you work with thousands of properties, which helps backups and file scans run faster. You can split your imports into multiple smaller feeds with different filters and schedules, which spreads the processing load instead of hammering your server in one giant sync job.
Can I run multiple MLSimport feeds for different segments or agents?
Multiple feeds let you segment imports by agent, area, or property niche on the same site.
You can define several independent feeds inside MLSimport, with each feed using its own rules for city, price, property type, and status. One feed might cover downtown condos, another suburban single-family homes, and a third just listings for a specific team member. The plugin treats these as separate pipelines, which gives you clear control over how listings get into each section of your site.
For office or team setups, you can also base feeds on agent or broker identifiers when your MLS exposes those fields over RESO. That way a brokerage site can have one feed that pulls only office listings, while area-focused feeds still show full IDX-style coverage for consumers. Each feed can run on its own schedule and with its own maximum listing count, so you can give a high-traffic niche more frequent updates than a small, slow-moving segment.
- Use one feed per city cluster so each area page stays lean and focused.
- Assign a dedicated feed to each top producer using their listing agent ID.
- Create separate feeds for rentals and sales to keep searches easy.
- Limit each feed to a safe maximum count based on hosting power.
FAQ
Can I combine filters like city, price, and property type in one MLSimport feed?
Yes, you can stack city, price, and property-type filters together in a single feed.
In the feed settings you choose your allowed cities, add a minimum and maximum ListPrice, and then pick PropertyType and PropertySubType values. MLSimport sends those combined filters to the RESO Web API so only listings that match all your choices are imported. That lets you do things like “only residential homes between $500,000 and $900,000 in three target suburbs” with one feed.
What happens if I change my filters after I already imported listings?
When you change feed filters, future syncs adjust your inventory to match the new rules.
If you tighten an MLSimport feed, listings that no longer match will be cleaned out on later runs, and new matching ones will be added. You do not need to start from scratch or wipe the whole site; you just update the feed criteria and let the next sync bring things back in line. I should say this though. You still want regular WordPress backups, especially when making big changes to import scope.
Can I start with a broad MLSimport feed and later narrow it down?
You can begin with a broad import and narrow it over time without reinstalling anything.
Many site owners start with wide filters to see what kind of inventory appears in each city and price band. After a few weeks they review performance and then cut the feed to focus on the segments that bring leads or match their brand. With MLSimport this is just a matter of editing feed settings, saving, and letting the scheduled sync cycle update the posts.
Are the same filters available in every MLS that works with MLSimport?
Most core filters are available everywhere, but some fields depend on what your MLS exposes.
City, ListPrice, PropertyType, PropertySubType, and Status are standard RESO fields, so you can count on those across supported U.S. and Canadian MLSs. Agent or office ID filters, and more niche fields, are only available if your specific MLS includes them in its RESO or CREA DDF payload. MLSimport reads whatever fields are present and exposes the useful ones in the feed configuration screens.
Table of Contents
