Yes, you can add custom fields and tags to imported listings with MLSimport. The plugin pulls in over a hundred RESO(Real Estate Standards Organization) fields per MLS, stores them as WordPress custom fields, and lets you stack your own taxonomies and tags on top. Your added tags and fields aren’t overwritten by sync, so your custom structure stays safe over time.
How does MLSimport handle custom fields during the MLS import process?
Imported MLS fields are saved as editable custom fields on each property in WordPress.
MLSimport lists more than 100 RESO fields per MLS in its admin screen and lets you turn each one on or off. When you pick a field, the plugin creates a matching WordPress custom field on the property custom post type and fills it on every sync. At first this sounds complex. It isn’t, because you only see fields your board actually exposes.
On import, the plugin stores each selected field as post meta, so every property carries its own data copy inside WordPress. You can rename field labels in the mapping step, like changing “Waterfront Y/N” to “Waterfront Home,” so the front end stays friendly while the raw value still matches the MLS. That label change lives in the plugin settings, not the feed, so it survives updates.
A checkbox in the field list lets you mark a field as private, which means it never appears on the public page. MLSimport uses this for items like “Agent Remarks” or internal notes so those stay only in the dashboard. Because unused MLS fields can be unchecked and skipped, your database stays lean and you avoid filling themes or builders with data you never show.
Can I map MLS data into my own taxonomies, tags, and niche categories?
Custom taxonomies and tags you assign to imported listings stay intact through MLS data updates.
Core location and type fields like city, state, and property type are mapped by MLSimport into the theme’s built-in taxonomies during import. A “City” field from RESO becomes a real “City” term in WordPress, which your theme can use for archives and widgets. You still control the URL and layout, but the data arrives already sorted into the right buckets.
You can also create your own taxonomies such as “Neighborhood,” “Luxury Tier,” or “Student Housing” using standard WordPress tools. After MLSimport creates each listing, you can assign those terms manually, by workflow rules, or with custom code, and the plugin doesn’t touch them on later syncs. At first the split feels odd, since the MLS feed does so much. But this separation lets you run a content plan on top of the raw feed without fighting the automation.
| Data source | Where it lands | How MLS sync treats it |
|---|---|---|
| MLS City field | Theme City taxonomy | Updated on every sync |
| MLS Property Type | Theme Property Type taxonomy | Updated on every sync |
| Custom Neighborhood taxonomy | Terms you assign | Never changed by plugin |
| Custom Luxury Tier taxonomy | Manual or rule based tags | Never changed by plugin |
| Manual WordPress tags | Standard post tags | Never changed by plugin |
This layout means the feed owns core facts like address and status, while your taxonomies carry your niche story. MLSimport refreshes the mapped fields on your schedule, but your “Luxury Tier” or “Neighborhood” terms stay as you set them, so you can build stable category pages and funnels.
How do I add my own non‑MLS fields for niche content and keep them safe?
Custom fields you create for niche data aren’t overwritten by ongoing MLS sync.
You can add extra property fields, like “Cap Rate,” “ROI,” or “Historic Home,” using your theme options or a plugin such as Advanced Custom Fields. MLSimport only syncs fields that are part of its mapping, so your added meta keys are ignored by the importer. That means you can write your own investment notes or special flags and know they’ll still be there next week.
With a theme like WPResidence 5.2 or newer, ACF fields attached to the property post type are auto detected and shown in layouts. The plugin fills the MLS data, and the theme exposes your custom blocks like “Investment Highlights” or “Luxury Features” using those extra fields. I should flip that around, though, because the point is control. By keeping your custom meta separate from mapped MLS keys, this setup gives you freedom to shape messages for niches without babysitting each sync cycle.
Can I use MLS fields and my custom data as powerful search and filter options?
Both imported MLS fields and your custom fields can become front end search and filter options.
When you map a RESO field like Waterfront, HOA Fee, or Year Built into theme fields, they become usable in search forms. MLSimport feeds those values into the database in a clean, repeatable way, so filters behave the same across every board that uses RESO. With a flexible theme, you can drop these mapped fields into search bars, filter sidebars, or map search panels in a few clicks.
The same idea extends to your own fields if your theme supports them in search builders. WPResidence lets you add custom and ACF powered fields directly to search and filter bars, so a field like “School District” or “Lifestyle Tag” can become a real filter. The RESO structure keeps basics like beds, baths, and price acting the same across at least three or four MLS sources, while your custom filters carve out your niche.
- You can expose mapped MLS fields like Waterfront or Year Built as simple checkboxes or dropdowns.
- Custom taxonomies such as Neighborhood can drive local filters in sidebars or map search.
- ACF based fields for things like Cap Rate can appear in advanced search panels.
- Standardized RESO fields mean filters for beds, baths, and price act the same.
How does MLSimport support SEO, content ownership, and long‑term content strategy?
Imported listings become indexable pages on your own domain, which supports a steady SEO plan.
The plugin stores every listing as a native WordPress post, so each property has its own URL under your main domain. Search engines can crawl prices, features, and locations like any other page, and your custom fields or taxonomies show up as normal HTML. Over time, even a few hundred listings can mean hundreds of steady landing pages for long tail searches.
MLS photos are served from the MLS CDN(content delivery network) but rendered as normal image tags with alt text, which helps image search and page quality. MLSimport keeps the last synced data in your database, so if the MLS API has a short outage, the site still serves live pages instead of blank results. Around the imported fields, you can add copy, video, or widgets in templates to build stronger content clusters that match your brand, even if that takes extra work.
FAQ
Do custom tags or taxonomies get erased when MLS data updates run?
Custom tags and taxonomies you add to listings aren’t erased by MLS updates.
The sync process in MLSimport focuses on mapped fields pulled from the MLS feed such as price, status, or beds. Any taxonomies or tags you create directly in WordPress, including niche sets like “Waterfront Luxury” or “Fixer‑Upper,” are left alone. This lets you build long term category pages without worrying that tomorrow’s sync will undo your work.
Can I use the same custom taxonomy plan when importing from several MLS feeds?
You can share one custom taxonomy plan across multiple MLS feeds on the same site.
MLSimport pulls each MLS feed into the same property post type, so your custom taxonomies apply site wide. You can tag listings from three different boards with one “Neighborhood” or “Luxury Tier” structure and keep filters consistent. The only thing that changes per feed is which RESO fields you choose to map into those shared structures.
Will manual edits to MLS-synced fields be overwritten on the next import?
Manual changes to fields that MLSimport manages will be overwritten on the next scheduled sync.
The plugin treats mapped fields like price, beds, and descriptions as read only mirrors of the MLS, so they stay in line with the board. If you need stable custom notes, put them into separate custom fields that the importer doesn’t map. That way you keep clear control: MLS owns the facts, your custom fields carry your story.
Is performance a problem if I use many custom fields and taxonomies with a big MLS?
Performance stays solid if you plan indexing and hosting for scale when using many custom fields.
MLSimport handles feeds cleanly, but WordPress still has to query thousands of listings and meta rows. For sites going past roughly 10,000 active properties, it makes sense to use good hosting, object caching, and proper database indexes on key meta fields. With that in place, even heavy search forms using a dozen filters stay fast enough for normal users, though very complex filters can still need care.
Table of Contents
