Yes, you can control which fields show on your property detail pages when you use MLSimport. During field mapping, you pick what to import, what to hide, and what to drop so agent-only notes never reach the public page. Once imported as normal WordPress fields, you decide in your theme or builder whether to show things like school info, maps, neighborhood data, or to keep them out of the layout.
How much control do I get over individual MLS fields in MLSimport?
You decide which MLS fields MLSimport brings into WordPress and which stay private or ignored.
During the first setup, MLSimport walks you through a field mapping screen where you match MLS(Multiple Listing Service) fields to WordPress custom fields. At that step, you choose which fields to bring in and which to skip, so junk or useless data never hits your pages. The plugin also lets you flag specific fields as public or private, so sensitive values stay stored but never show on the front end.
Once imported, every mapped field works like a normal WordPress custom field attached to the property post type that MLSimport creates. Your theme, your page builder, or your custom templates can print, hide, or restyle those fields any way you want. You can remap or rename fields later; for example, you can turn a long RESO name into a short label like Living Area without touching the MLS.
The mapping layer can also merge several MLS description fields into a single front-end field. You might combine Public Remarks, Internet Remarks, and a marketing field into one long description block that looks clean to visitors. You can ignore extra technical fields such as Modification Timestamp or Entry Agent ID so they never clutter your property templates. In practice, that gives you control over which MLS fields actually land on your public pages.
Can I hide sensitive remarks while still displaying rich consumer-facing details?
Sensitive agent-only remarks can be hidden while public listing details stay visible to visitors.
In the import rules, MLSimport lets you tag any field as private or leave it out of the import. That way, fields like Agent Remarks, lockbox info, showing notes, or internal IDs can either stay only in the admin or not be stored. At the same time, you keep public remarks, room descriptions, and feature lists fully visible on the property page.
Because the plugin separates field import from field display, you can import confidential data only for back-office reporting. Then, in your theme templates, you simply never call those private fields, so they never render in HTML. This makes it easier to stay inside MLS rules while still giving buyers the details they expect to see.
- Mark Agent Remarks and similar fields as private so they never appear on listing pages.
- Exclude internal-only data like showing instructions, compensation, or lockbox notes from import rules.
- Display only consumer-focused text fields such as public description and property highlights on detail pages.
- Use template controls to omit IDs or internal reference numbers from the page layout.
How do I control maps, school info, and neighborhood data display with MLSimport?
Map, school, and neighborhood sections can be turned on or off based on your design and rules.
When you map your feed, MLSimport brings in latitude, longitude, and address so your theme or builder can plot a map if you want one. If you prefer not to show maps on detail pages, you simply leave the map block out of your single-property template, or disable that section in theme options. The location data still lives in the custom fields, so you can use it later for search or filters even when the visible map is off.
School-related fields from RESO, like district name and individual school names, can be mapped to dedicated custom fields. Once those are mapped, your template can show them in a Schools section, a sidebar widget, or not at all, depending on your layout. You can also show only part of that data, such as district but not each school, by leaving some fields unused in the template even though they are imported.
Neighborhood, subdivision, and community names can be mapped either as taxonomies or as plain meta fields through MLSimport. Many site owners show them as tags, badges, or clickable filters to group listings by community. If you decide a certain market does not care about subdivision names, you just drop that block from your template and keep the data available only for search queries. Actually, some people test both layouts for a while to see what visitors use, then pick one and stick with it.
| Data type | How it’s imported | How you control display |
|---|---|---|
| Map or Location | Lat long and address stored in property meta | Enable or disable map section in your theme or template |
| School Information | School fields mapped as custom fields | Show in a Schools block or hide if not relevant |
| Neighborhood and Subdivision | Neighborhood fields imported to taxonomy or meta | Display as text, filters, or badges, or omit from layout |
| Extra Area Data | Walkability or community feature fields | Group into neighborhood panel or keep for internal use only |
This table shows how raw MLS data becomes flexible blocks your theme can show, group, or hide. Once fields are mapped by MLSimport, every row here is controlled at the template level, and you decide what visitors see.
Can I customize different property templates and views when using MLSimport?
You can build several property templates, each with a different mix of fields for each listing type.
Because MLSimport saves listings as a normal WordPress custom post type, your favorite theme builder tools work out of the box. You can create one single-property layout for residential, another for rentals, and another for land, each with its own field set. In many modern themes, you assign templates based on category, type, or status so the right fields appear for the right kind of property.
With this setup, you can build field groups like Details, Features, Schools, and Map as separate blocks in your template. Most builders or smart themes let you toggle each block on or off and change their order without touching code. For example, your land template might hide the Schools block but show a big Lot Features group instead. Your card or grid layouts can show only a few key fields such as price, beds, baths, and city, while the full details page keeps the longer list.
How does MLSimport handle sold, pending, and off-market fields on details pages?
Status fields stay synced, while you decide whether sold and pending property pages stay visible or hidden.
MLSimport keeps the status column aligned with the MLS feed, so changes from Active to Pending or Closed are picked up on each sync cycle. In many markets this runs about hourly, which is usually enough for compliance. You can then use your theme to show Sold or Pending badges on the property template and change what fields appear.
Some themes, including WPResidence where MLSimport is often used, can hide or mask price for sold listings while keeping the page online as a showcase. You can also remove off-market listings from search results but still allow the detail URLs to work for SEO or portfolio reasons. Status values imported by the plugin stay available as filters, so you can build separate pages like Sold Homes or Under Contract without extra data entry.
FAQ
Can I hide or show fields without changing anything in the MLS system?
You can control field visibility inside WordPress without editing data in the MLS.
The mapping and template layers in MLSimport sit on top of the MLS feed, so you change only how data is used on your site. You can drop a field from the template, change its label, or mark it private, and the MLS record stays untouched. At first this feels like a copy, but it is really just display control.
What happens if I change my mind about which fields I want to display later?
You can adjust field mappings and templates later, and changes apply on the next sync.
If you decide to start showing school districts or stop showing HOA fees, you update the mapping or the template. MLSimport keeps importing the data as usual, and your new display rules take effect across all listings. On the next regular synchronization, any remapped fields and layout tweaks apply across the site without manual edits.
Will my field visibility choices still work with themes and page builders?
Your field visibility rules work with modern themes and builders because the plugin uses standard custom fields.
MLSimport stores listing data in the same way many themes and page builders expect, so tools like WPResidence or other builders can read those fields. You choose in the builder which fields to print and which to leave out, while compliance-required fields can be fixed into the template. I should say, older themes might need small tweaks, but the basic approach still holds.
How do I make sure required brokerage or attribution fields always show?
You can lock required attribution fields into your base template so they always render on every listing.
Most boards require brokerage name and sometimes extra notice text to appear near the property details. With MLSimport, those values come in as fields, and you place them in a permanent spot in your single-property template. Since you never remove that block, every listing page stays compliant, even if you hide many other optional fields.
Table of Contents
