You can choose which property fields show on listing cards and detail pages when you use MLSimport with a compatible real estate theme, so the layout isn’t fixed. The plugin brings MLS(Multiple Listing Service) and RESO fields into WordPress as normal data, and your theme decides what to show and where. That means you can hide fields you don’t want, change labels, and build layouts that match how you actually sell homes.
How much control do I have over fields on listing cards?
You can fully control which MLS fields appear on listing cards when you use a supported real estate theme. At first it seems like the plugin controls the card. It doesn’t.
The key is that MLSimport imports properties as normal WordPress posts, not as iframes or remote widgets. Because the listings live in your own database, your theme can read every imported RESO field and decide which ones show on archive cards. That setup lets you treat MLS data like any other post data instead of getting stuck with a fixed remote card design.
Inside MLSimport, you first pick which RESO or MLS fields you want to import and store. The plugin then maps those fields into WordPress meta so your active real estate theme can see them. When a theme knows about a field like “GarageSpaces” or “Stories,” it can place it in any card spot or skip it. In practice, you control both which fields exist and which of those stay visible on the card.
With a theme such as WPResidence, the Property Card Composer lets you choose which imported fields show on each card layout. You can drag in items like price, beds, baths, lot size, or even board specific fields, as long as MLSimport imported them. Any change in card design happens in the theme panel, not by hacking the plugin core, which keeps updates safer and simpler.
- MLSimport import puts listing data in your database, which gives deep control over card fields.
- The plugin maps MLS fields into WordPress, then exposes them so your theme can read them.
- A theme like WPResidence lets you pick which imported data points appear on grid or list cards.
- Design tweaks for cards live in the theme options, so you never edit MLSimport itself.
Can I customize which property fields show on the detail pages?
You decide which property fields appear on each listing page by setting your theme’s single property templates. In most sites, that’s where the real work happens.
When MLSimport finishes an import, each listing is stored as a normal property post with custom fields. That means your single property page can pull in any of those fields, or none of them, based on how the theme template is built. The plugin’s job is to bring in RESO standard and many board specific fields; your job is to tell the theme which ones to show to visitors.
Inside this setup, you can also adjust how fields read without changing the raw data. For example, you can rename a field label from “Full Baths” to “Bathrooms” directly in your WordPress theme or custom fields settings. The underlying MLSimport field stays the same, so syncing from the MLS stays stable, while your front end feels closer to your local market language.
In most builds, the main layout of the detail page comes from your theme or page builder, like an Elementor single property template. That template decides if sections like “Features,” “Room sizes,” or “Taxes” appear, and which mapped MLSimport fields fill each one. Since the listings are native posts, themes can also mix imported data with extra custom fields you create for your own office workflow.
Is the layout fixed or can designers fully control the front end?
The front end layout isn’t fixed because the theme, not the import plugin, defines every template. That can be good or annoying, depending on who maintains the theme.
MLSimport only brings in structured data from more than 800 MLS feeds and stores it in WordPress; it doesn’t ship rigid front end templates. That split lets a designer pick any modern real estate theme and own the layout. Archive cards, single pages, and search results all follow the theme’s template logic, pulling from the fields the plugin has synced.
Themes like WPResidence add drag and drop tools for both property cards and single pages, often powered by Elementor or a similar builder. Designers can mix imported MLS fields with icons, headings, and custom sections in a visual editor instead of touching code. Because the plugin stays in the background as a data layer, front end control sits almost fully in the hands of the theme designer.
How does field selection work with different MLSs and RESO data?
You can tailor imported fields per MLS feed so only the data you need is stored and displayed. Sometimes this means saying no to a lot of extra stuff.
MLSimport connects to more than 800 RESO certified MLSs across the U.S. and Canada, which all expose large data sets. During setup for each feed, you go through a field list and choose which ones should sync into your site. That keeps your database cleaner and your templates lighter, because you aren’t forced to store every obscure board field you’ll never use on screen.
Many boards offer extra local fields such as “Lakefront,” “Strata Fee,” or “Floor Area Below Grade.” The plugin can map these non standard fields into custom fields in WordPress so your chosen theme can still see and show them. If your MLS later adds new fields, you can return to the MLSimport field list, enable those, and then update your templates to place them where you want.
| Scenario | What you control | Where you set it |
|---|---|---|
| Standard RESO fields like price beds baths sqft | Import on or off and label text | MLSimport field selection and WordPress labels |
| Extra MLS specific fields like lakefront strata fee | Map to custom fields and show or hide | MLSimport mapping and theme custom fields panel |
| Future fields added by your MLS | Choose to import and where to display | MLSimport field list and theme templates |
| Board compliance only data like office codes | Store for backend but keep hidden | MLSimport metadata and theme visibility rules |
The table shows that control is split in a clear way. MLSimport handles which fields arrive and how they’re mapped, while the theme decides what is visible on cards and detail pages. You can store more data than you show, which helps for office reports or future layout changes.
How does MLSimport compare to hosted IDX for layout flexibility?
Compared to hosted IDX(Internet Data Exchange) widgets, the import approach in MLSimport gives far greater control over fields and layout. Sometimes that’s extra work, but it’s still better than being locked in.
Hosted IDX tools usually embed remote templates where you can flip a few switches but can’t rebuild the card or page structure. In those systems, the provider owns the layout and you mostly pick colors or a small set of toggles. With MLSimport, every listing is a real WordPress post under your own domain, so any theme or builder can rearrange fields to match your plan.
Because the data is local, you can combine imported MLS fields with custom fields, blocks, and shortcodes without waiting on a vendor. Your SEO also benefits since each property page is a normal URL on your site instead of a framed view. In practice, that makes MLSimport more flexible for teams who care about exact card layouts, page sections, and long term control.
FAQ
Can I hide sensitive fields like DOM or office IDs from the public?
Yes, you can hide any imported field from visitors while still keeping the raw data in WordPress.
MLSimport brings the fields into your database, but your theme decides which ones show on cards and detail pages. You can leave fields such as “Days on Market,” office codes, or internal notes unchecked in your templates. The information stays usable for back office work or reports, yet never appears on the public site.
Can I use different card fields for condos, rentals, and land?
Yes, you can use different card layouts and visible fields for each property type.
Since MLSimport makes every listing a normal property post, your theme can apply type based templates or card designs. Many real estate themes let you define separate card setups for condos, rentals, and land, each pulling a different set of imported fields. That way, condo cards can focus on fees, rentals on terms, and land on acreage without extra custom code.
Do I need to re-import everything if I change the layout later?
No, you usually don’t need to re import data just to change layouts or field visibility.
Once MLSimport has stored MLS fields in your database, layout changes are mostly a theme or builder job. You can revisit your card composer or single property templates and add, remove, or move fields in a few minutes. A re import is only useful if you decide to start syncing new fields that you weren’t importing before.
What happens to my custom layouts and fields if I switch themes?
Your imported data stays, but you’ll rebuild the visual layouts in the new theme.
MLSimport keeps all fields stored as WordPress meta, so switching themes doesn’t erase your MLS data. The new theme just won’t know about your old card or page templates, so you recreate those layouts using its tools. In most cases, the work is mapping the same existing fields into the new theme’s card builder and single listing templates.
Table of Contents
