Yes, you can selectively hide some MLS fields and highlight others when you use MLSimport with a supported WordPress theme like WPResidence. You choose which imported RESO fields map into visible template spots and which stay stored only in the database. That control lets you push eye-catching items like architectural style, lot size, views, or hand-picked luxury details to the front of the page while hiding boring internal fields from visitors.
How much control do we get over which MLS fields appear on our site?
You can decide exactly which imported listing fields appear publicly and which stay hidden in your database. At first this sounds basic control. It is actually deeper than that in real use.
Each listing imported through MLSimport becomes a normal WordPress property post with many RESO fields saved as meta values. In a theme like WPResidence, you then pick which of those mapped fields show in the single-property layout, archive cards, and search forms. That means items such as MLS ID, internal status codes, or back-end-only flags can live quietly in the database without ever showing on the front end.
The plugin maps standard RESO fields like ArchitecturalStyle, LotSizeArea, and View into WordPress custom fields or meta keys that your theme already understands. In WPResidence you open the Property Custom Fields or Studio layout builder and drop only the fields you care about into the visible layout. If you leave a mapped field out of the layout, visitors never see it, but the value still syncs and stays available for filters or internal logic.
Because data stays in sync even when hidden, you can keep many imported technical fields for reporting or search while showing maybe 10 to 20 user-friendly highlights per page. MLSimport keeps refreshing all mapped values from your MLS(Multiple Listing Service) feed, but your template decides which values are rendered as HTML. That split between data and design is what gives tight control. You store almost everything, but show only what helps a buyer scan and trust the listing.
| Field type | Typical example | Common display choice |
|---|---|---|
| Core public detail | Price beds baths address | Always visible on cards and listing |
| Design focused highlight | ArchitecturalStyle View LotSizeArea | Visible in feature blocks or badges |
| Technical MLS field | MLS ID status code feed source | Hidden from visitors kept in meta |
| Compliance information | Listing brokerage MLS disclaimer | Shown in footer or small text |
| Search only helper | Sub type flags internal tags | Used in filters not printed directly |
The table shows how you can store many field types but only surface the ones that help visitors scan the page. With MLSimport you keep technical and search helper fields available behind the scenes while focusing the design on simple highlights.
Can we highlight key fields like architectural style, lot size, and views for luxury listings?
You can design listing layouts that spotlight your most important property attributes above other details. Some listings really need this focus. Others are fine with a simple stack of facts.
RESO fields like ArchitecturalStyle, LotSizeArea, and View are common in modern MLS feeds and import cleanly into WordPress. MLSimport maps those fields into your theme’s meta keys so they’re ready for high-visibility spots in your templates instead of getting buried in a long generic list. You’re not stuck with one field table that treats a mountain view and a tax ID like they matter the same to a buyer.
In WPResidence, you can use the Studio single-property builder to pull those mapped keys into badges, icon rows, or top-of-page feature strips. For a luxury listing, that might mean a first screen that shows “Modern Architectural Style · 1.2 Acre Lot · City Skyline View” right under the price before any long text. Lower-priority facts like HOA transfer fee or parcel number can move into collapsible “More Details” sections.
You can create at least one layout tuned to luxury where architecture, views, outdoor space, and special amenities get more space than generic bedroom counts. The plugin still feeds the same RESO fields on both entry-level and luxury properties, but your theme layout decides which ones stand out and which ones stay quiet. Because MLSimport keeps those fields updated on every sync, your highlighted badges stay correct even as agents change remarks or measurements in the MLS.
How do we add and map custom fields for unique luxury features not in the MLS?
You can create custom fields for any luxury detail and make them searchable alongside standard MLS data. This is where teams usually get picky, and that is fair.
High-end details like “celebrity ownership” or “private helipad” rarely live in clean MLS fields, so you often need your own spots. MLSimport lets you map all incoming RESO fields to existing theme fields, while WPResidence’s Property Custom Fields screen lets you add new custom fields for extra details that only you know. The result is a mix where some data flows from the feed and some is entered by hand but all appears in one clear layout.
For example, you can add a checkbox field named “Gated Estate” or a text field like “Notable History” and show them only on chosen properties. The plugin keeps importing normal MLS data in the background, and you or your team can fill in those extra boxes on a few showcase listings directly in the WordPress editor. In the advanced search builder you can then include select custom fields, so buyers can filter for “Gated Estate = Yes” alongside price and beds without caring which parts came from MLS and which were typed in.
Can we build different layouts so high-end listings look and read differently?
You can assign custom page designs to selected listings without changing the underlying MLS feed. At first this feels like design sugar. It actually changes how buyers read the page.
Every property MLSimport creates is a standard property post that your theme can route through any template you define. In WPResidence Studio you can build multiple single-property layouts, such as a “Luxury Detail” layout and a “Standard Detail” layout, each using the same mapped meta keys but in very different arrangements. That lets a $5M penthouse read like a magazine spread, while a $350k condo uses a simpler layout with fewer design pieces.
For a high-end template, you might put a full-width hero gallery on top, then bold callouts for architectural style, lot size, and views, followed by sections for spa, gym, and smart-home features. Another leaner template could skip some of those blocks and just show the basics plus a short feature list. MLSimport doesn’t need separate feeds or rules to support this. The plugin simply keeps the property data synced, and the theme decides which layout file to use per listing, per category, or per price band.
What does this selective field control mean for SEO and performance?
You can fine-tune visible fields for visitors without losing SEO or data freshness. Here the tradeoff is between design comfort and technical safety.
Because MLSimport performs an organic import, each listing lives as a normal WordPress post under your main domain, which search engines can crawl like any blog article. Hiding or showing fields only affects what your theme prints on the page; the database still holds the full RESO payload, and sync jobs keep running on schedule, often several times per day as a common pattern. Remote image handling means thousands of MLS photos load from upstream servers instead of filling your disk, which helps keep page generation fast even when your site holds many thousands of properties.
- Visible field choices shape how easy pages are to scan without changing MLS sync.
- Search engines index full listing pages because content lives directly on your domain.
- Remote photos avoid heavy media libraries while still showing high resolution galleries.
- Focused detail blocks around long tail terms can support niche ranking over time.
FAQ
Does hiding a field on the site also remove it from our database?
No, hiding a field in your layout doesn’t delete or stop syncing that data.
When MLSimport pulls a listing, it writes all mapped RESO fields into WordPress meta, even if your theme never prints them. Layout control in WPResidence or another theme only changes which keys are echoed into HTML, not which ones are stored. That means you can later decide to surface a hidden field in search or templates without running a fresh import of all listings.
Do field-mapping or layout changes force us to re-import all MLS listings?
Usually you can change mappings or templates without re-importing existing listings.
MLSimport stores fields under stable meta keys, so adjusting how the theme reads or labels those keys is mainly a front-end task. If you add a new custom field and map an MLS field into it, existing posts often already contain the raw value, and you only need to adjust the template to show it. Only large structural feed changes from the MLS side normally warrant a full re-sync, and that doesn’t happen often.
Does selective field display work the same across all supported MLS feeds?
Yes, the same show or hide logic works across the 800-plus MLS feeds MLSimport supports.
Because the plugin is built around the RESO data dictionary, fields like ArchitecturalStyle, LotSizeArea, and View arrive under consistent names regardless of the specific board. Once you decide in your theme which mapped keys to surface, that design applies across every connected MLS. You still must respect each MLS’s display rules and required disclaimers, but those are added as footer elements, not as forced full-field tables.
Does changing field visibility risk breaking MLS or IDX display rules?
No, adjusting which optional fields show in your templates can still follow normal MLS display rules.
Most MLS policies care that you show required brokerage credits, MLS logos, and standard disclaimers, all of which you can keep fixed in your layout. Fields like architectural style or lot size are rarely mandated in any specific position, so you’re free to emphasize or de-emphasize them as long as the raw data remains accurate. MLSimport keeps the synced values correct in the database, and your theme just arranges them in a user-friendly way that still respects IDX (Internet Data Exchange) rules.
Table of Contents
