Yes, our MLSimport plugin can import MLS data and map it into WordPress custom fields so you can show highlights like “Architect”, “Gated Community”, “Celebrity Ownership History”, or “Private Screening Room”. As long as your MLS feed has a field, you can point it into any custom meta key your theme uses. For details that aren’t in the MLS at all, you can still add manual custom fields and show them next to the imported data.
How does MLSImport map MLS fields into WordPress custom fields?
The importer can match any MLS field to any WordPress custom meta field you set.
MLSimport connects to your MLS through the RESO Web API (Real Estate Standards Organization Web API) and pulls listings into WordPress as a real “property” post type, not an iframe. Standard RESO fields such as ListPrice, BedroomsTotal, BathroomsFull, and LivingArea are auto-mapped to your theme’s price, beds, baths, and size meta keys. That first pass gives you working listings quickly, often with dozens of core fields mapped right away.
Inside your theme, you open the “Property Custom Fields” or similar panel to see which meta keys the layout expects. There you can make extra keys for anything the MLS exposes, like ArchitecturalStyle, BuilderName, or CommunityFeatures. MLSimport then lets you pair each incoming MLS field to one of those meta keys through its mapping screen, so the data lands where your theme will read it.
Once you save that map, the plugin keeps using those links on every sync, so new and updated listings always write into the same custom fields. If your theme expects a field called “property_architect”, you tell MLSimport to write the RESO ArchitecturalStyle value into that key. At first this sounds rigid. It isn’t, because you can still add new custom fields later without redoing the whole import.
Can we import niche data like ‘Architect’ or ‘Gated Community’ as highlight fields?
Any field present in your MLS feed can become a special highlight on listing pages.
If your board sends fields like ArchitecturalStyle, BuilderName, or CommunityFeatures, you can route them into your own custom meta keys through MLSimport. In your theme options, you create fields named “Architect”, “Gated Community”, or any label you want visitors to see. Then you map the MLS fields to those keys so the values fill in during every sync instead of you typing them each time.
- Use the theme’s custom fields panel to add highlight fields such as Architect or Gated Community.
- In MLSimport mapping, point each RESO field to the matching custom meta key your theme uses.
- Design a highlight box or badge row in the property template pulling from those mapped fields.
- Keep extra facts like celebrity ownership in separate manual fields that MLSimport never overwrites.
Once the data is mapped, your template can show those fields in a “Key Highlights” box, a badge strip, or an icon list. MLSimport keeps updating the values from the MLS while leaving your non-MLS fields, such as “Celebrity Ownership History”, alone because they aren’t tied to any feed column. That split lets you mix strict MLS data with your own notes on the same page, even when you keep adding more.
How does MLSImport handle luxury‑grade fields like private screening rooms or wine cellars?
Luxury amenities from the feed can fill both visual highlights and advanced search filters.
Most high-end features live inside broader RESO fields like InteriorFeatures, ExteriorFeatures, or CommunityFeatures, which MLSimport pulls in with the rest of the data. You can break those long feature strings into structured checkboxes or flags inside your theme, such as “Private Screening Room”, “Climate-controlled Wine Cellar”, or “Gated Driveway”. Then you map the MLS feature list into a single meta field and let your theme logic turn matches into clear on-page labels.
In practice, you extend your theme’s amenities list so it treats those specific items as separate toggles. The plugin feeds the raw RESO features into that meta key, and your layout turns them into strong visual highlights and filter options for serious luxury buyers. At first you might worry about the photos. But MLSimport also reads photo URLs directly from the MLS or CDN (Content Delivery Network), so large galleries load without flooding your own media library.
Will imported custom‑field data work with my theme’s search, badges, and layouts?
After mapping once, all new synchronized listings follow your custom highlight rules.
With a compatible theme like WPResidence, any custom meta key that gets data from MLSimport becomes available to the theme’s search and layout tools. That means if you mapped ArchitecturalStyle or CommunityFeatures into named fields, you can drop those into your front-end search builder as dropdowns, checkboxes, or quick filters. The same meta keys can also drive ribbons, badges, or “Key Facts” blocks on the property page template without extra coding.
| Theme feature | Uses mapped meta | Example highlight |
|---|---|---|
| Advanced search filters | Yes via search builder | Filter by architectural style |
| Property badges | Yes from boolean meta | Gated Community ribbon |
| Highlights box | Reads custom fields | Architect and year built |
| Saved search presets | Based on mapped fields | Only homes with wine cellars |
| Card overlays | Meta-driven labels | Private Screening Room tag |
Once you set the mapping, every sync reuses the same rules for thousands of listings without more work from you. If you later redesign your templates, you still pull the same meta keys, so the “Architect”, “Gated Community”, and other special flags move into the new layout almost by themselves. The tradeoff is that poor mapping choices stay visible too, so you’ll sometimes revisit earlier decisions.
FAQ
Can we mix MLS‑imported fields with manual ones like “Celebrity Ownership History”?
You can safely combine MLS-imported fields with manual custom fields on the same property pages.
MLSimport only controls the fields you actually map to the MLS feed, so it never touches your own extra meta keys. You might map ArchitecturalStyle and CommunityFeatures from the board, then create a “Celebrity Ownership History” field that you fill in by hand. On the front end, your theme can show all of them together even though they come from different places.
Does MLSImport ever change data back in the MLS when we tweak highlights?
No, MLSimport never edits anything inside the MLS; all changes stay only on your WordPress site.
The plugin is a one-way importer that reads from the RESO Web API and writes into your local database. When you adjust highlight logic, add new custom fields, or move badges around, you only affect how your own site looks. The underlying MLS listing in your board’s system stays exactly as entered by the listing agent, even if your labels keep shifting.
What happens to existing listings if we change the custom‑field mapping later?
Changing mapping rules later will update existing listings on the next sync or re-process.
If you rename a field or point an MLS column to a new meta key, MLSimport applies that rule going forward and during the next full update. Many sites run a manual re-process after big mapping changes so all stored posts refresh within a few hours. That way your “Architect” or “Gated Community” data stays aligned across both old and new listings.
Will thousands of listings with many highlight fields slow the site down?
A site with thousands of listings and many meta fields can stay fast if hosting and caching are set up correctly.
Each listing might carry dozens of custom fields, but those are just database rows that WordPress can handle on a decent server. Pair MLSimport with solid hosting, page caching, and a theme tuned for property queries, and even 5,000 to 10,000 listings can stay responsive. The truth is that bad hosting hurts more than the number of highlight fields, while images from the MLS or a CDN avoid extra load.
Table of Contents
