Houzez stores its own property data in meta keys that begin with fave_, and it shows imported extras in one grouped block rather than wherever you want them. Mapping is how you put an MLS value into a Houzez field that the theme already knows how to display.
Every setting described below lives on one screen: MLS Import Settings, then the Select Import fields tab.
The three places a field can land
For every field you turn on, MLSImport takes exactly one of three routes, in this order.
- Property Detail Field (post meta) has a value: the MLS value is written into that meta key and nothing else happens with it. This is the route that feeds an existing Houzez field.
- Category has a taxonomy selected: the value becomes a term in that taxonomy. The Front End Label is used as a prefix on the term, so a label of
Roofon a value ofMetalcreates the termRoof Metal. Typenoneas the label to get the bare value. - Neither is set: the field joins the Houzez Additional Features list on the property, using your Front End Label as the row title and the drag order from the field list as its position.
Ticking Hidden from Public? on an unmapped field takes it out of Additional Features and stores it as a plain meta key named after its label in lower case. The value is still imported and stored, and it is not displayed.
Finding the Houzez field ID to map to
You need the meta key Houzez uses for the field you want to fill. Read it off the property editor.
- Open any property in WordPress, in the normal editor.
- Right click the field you want to fill and choose Inspect.
- Read the input’s
idornameattribute. Houzez names them likefave_property_garage,fave_property_yearorfave_property_size. - Go to Select Import fields, find your MLS field, and type that key into Property Detail Field (post meta).
- Run the import task again so the properties are rewritten with the new mapping.
Expected result: the value appears in that Houzez field on the property editor, and wherever the theme prints that field on the front end.
Map into a Houzez field only when the field is genuinely empty of theme data. Both MLSImport and Houzez write to the same key, so pointing an MLS field at one the theme also fills means the last writer wins, and on an imported property that is always the import.
Getting a value into search or a filter
Houzez search dropdowns are built from taxonomy terms, not from meta values. A field left in Additional Features can be read on the page and cannot be searched on.
To make an MLS field searchable, pick a taxonomy in the Category column instead. The value becomes a term, the term gains an archive page, and the theme’s search controls that read that taxonomy can offer it.
If it does not work
- Nothing changed on existing properties. Mapping is applied while a listing is being written, so it only affects imports that run after the change. Run the task again.
- The field is empty everywhere, including wp-admin. The MLS is not sending a value for that field on those listings. Check a listing you know has the value, then ask your MLS which field carries it.
- The value is in the database but not on the page. Houzez has to be told to show it. Check that the details or additional features area is enabled in the theme options, and that no custom CSS is hiding the block.
- You mapped it and it still shows in Additional Features. Only one route runs per field. If both a detail field and a category are filled in, the detail field wins, so clear the one you do not want.
Houzez shows Additional Features as one grouped block. There is no Houzez setting that lifts a single row out of it and places it elsewhere on the page, so when a value must appear in a specific spot, mapping it into an existing theme field is the only route.
Frequently asked questions
Can I map two MLS fields into the same Houzez field?
You can, and you should not. Both write to the same key during the same import and the one processed later overwrites the other, so the result depends on field order rather than on your intent.
Where do beds, baths, price and area get mapped?
They do not need mapping. Those are core fields and MLSImport writes them into the Houzez keys automatically, along with the address, the coordinates and the photo gallery. Mapping is for everything beyond that core.
My mapped key shows on the property editor but not on the listing page. Why?
Houzez only prints the fields its templates ask for. A meta key that Houzez does not have a field definition for is stored and never rendered, so map into a key the theme already displays rather than inventing one.
Does mapping change what is imported from the MLS?
No. Mapping decides where a value is stored once it arrives. What is fetched is decided by Import it? on the field list and by the filters on each import task.
Related
- The Select Import fields screen
- Mapping for WpResidence, WpEstate and Real Homes
- Search fields not populating as expected
- MLSImport with Houzez
Send us the Houzez field you want filled and the MLS field that holds the value, and we will confirm the mapping.