Houzez property data in WordPress is highly structured. The theme does much more than style real estate listings: it expects prices, bedrooms, locations, map coordinates, media, property types, statuses and agent relationships to be stored in specific WordPress fields and taxonomies.
That structure matters when Agentbox is your real estate CRM. A basic import can create a property post, but a listing that looks complete in the WordPress admin may still be invisible to Houzez search, missing from the map or disconnected from its gallery and agent profile.
This guide explains how Houzez stores property listings, why generic CRM imports often fall short and how WP AgentBox Sync maps Agentbox data into the structure Houzez can use. It is written for real estate agencies, WordPress developers and site owners planning an Agentbox to Houzez integration.
What you will learn
Use this guide to understand the Houzez data model, diagnose incomplete property imports and plan a reliable Agentbox-to-WordPress sync.
- Data structureWhere Houzez expects property fields, taxonomies, media and relationships.
- Failure pointsWhy a listing can appear in WordPress but fail in search, maps or galleries.
- Reliable syncingHow WP AgentBox Sync translates Agentbox records into Houzez-ready listings.
The short answer: how does Houzez store property data?
Houzez stores each listing as a WordPress property custom post type. It then combines several types of data around that post:
- Core post data for the listing title, description, excerpt, author and publication status.
- Post meta for values such as price, bedrooms, bathrooms, garages, property size and map coordinates.
- Custom taxonomies for reusable classifications such as property type, property status, features, labels and locations.
- WordPress media attachments for the featured image, property gallery, floor plans and documents.
- Relationships that connect the listing to an agent, agency or WordPress user.
This follows the wider WordPress model of combining post types, taxonomies and custom fields, but Houzez adds its own field names, relationships and frontend expectations.
The main parts of the Houzez property data structure
| Property information | How Houzez commonly uses it | What can break when mapped incorrectly |
|---|---|---|
| Title and description | WordPress post title and content | Incomplete property pages and poor search snippets |
| Price and property details | Houzez post meta fields | Sorting, range filters and display formatting |
| Type, status and features | Houzez property taxonomies | Filter results and taxonomy archive pages |
| Suburb, area, state and country | Location fields and hierarchical taxonomies | Location search, archives and breadcrumb context |
| Latitude and longitude | Geolocation and map fields | Missing or incorrectly positioned map pins |
| Photos and floor plans | Media attachments plus Houzez gallery data | Empty galleries, wrong image order and missing floor plans |
| Agent and agency | Houzez record relationships | Broken profile links and inconsistent contact details |
Core post data
The property post holds information WordPress understands natively: the title, main description, excerpt, slug, status and featured image. This makes a Houzez listing visible in WordPress, but it is only the outer shell. Most real estate-specific information lives elsewhere.
Houzez custom fields and post meta
On a typical Houzez installation, values such as price, bedrooms and bathrooms are stored as post meta. Common Houzez meta keys include fave_property_price, fave_property_bedrooms, fave_property_bathrooms and fave_property_map_address. Geolocation commonly uses dedicated latitude and longitude values as well.
Those names are useful when diagnosing an import, but they should not be treated as a universal spreadsheet template. The installed Houzez version, enabled modules and fields created through the theme’s field builder can all affect the final mapping. Houzez confirms that its custom fields can be connected to listing forms, property pages and search filters, which is exactly why importing a value into an unrelated meta key is not enough.
Houzez property taxonomies
Repeated classifications belong in taxonomies rather than plain text. Houzez commonly uses taxonomies for property type, status, features, labels and location levels such as country, state, city and area. A value such as “Apartment”, “For Sale” or “Surry Hills” should be attached as the correct taxonomy term if it is expected to power filters and archive pages.
This is also why spelling, capitalisation and hierarchy need a clear policy. “NSW”, “New South Wales” and “N.S.W.” can become three separate terms unless the sync normalises them. Parent and child locations must also be created and connected in the correct order.
Why incorrect Houzez property data breaks search and maps
A generic importer usually answers one question: can this source value be copied into a WordPress field? A reliable Houzez integration must answer a more important question: where does Houzez expect the value, in what format and what other relationships need to be updated?
- A display price such as “Contact Agent” cannot replace the numeric value needed for price sorting and range filters.
- A suburb saved as ordinary text does not automatically become a searchable Houzez location term.
- An image URL does not automatically become a WordPress attachment, featured image or ordered Houzez gallery item.
- A latitude and longitude pair in the wrong fields will not reliably create a Houzez map marker.
- An agent name saved in a paragraph does not create a relationship with a Houzez agent profile.
- A changed CRM record may create a duplicate property if the importer cannot match it to the existing WordPress post.
Houzez’s advanced property search can filter by price, bedrooms, bathrooms, garages, amenities, locations and custom fields. That functionality depends on consistently structured data, not simply on text being visible on the page.
How to sync Houzez property data from Agentbox
A theme-aware sync acts as a translation layer between the Agentbox data model and the Houzez data model. It needs to understand the meaning of a source field, transform it where necessary and write it to every Houzez structure that relies on it.
1. Match each listing by a stable identifier
The Agentbox property ID should be retained so later updates modify the existing property instead of creating another post. Reliable matching is the foundation for price changes, status transitions, media refreshes and property withdrawals.
2. Preserve numeric and display prices
Real estate pricing is not always a single number. A sales listing might show a fixed price, a guide, an auction message or “Contact Agent”. A rental can have a numeric amount, period and public label. Houzez search may require a clean numeric value while the property page needs the wording supplied by the agency.
A good field mapping preserves both purposes where the CRM data allows it: machine-readable data for filtering and human-readable data for display.
3. Build location data for search and maps
A full address is useful to visitors, but Houzez also benefits from separate street, suburb, postcode, state and country values. The location taxonomy hierarchy supports navigation and filtering, while latitude and longitude power map search and property markers.
Address visibility also needs attention. Some campaigns require the full street address; others should show only a suburb or a masked address. The public label and the geocoding data should be handled separately so privacy choices do not break the map.
4. Import images as WordPress media
Property photography should normally be downloaded or otherwise registered as WordPress media, connected to the property and placed into the expected gallery order. The first image may also need to become the featured image used by cards, search results and social previews.
Floor plans, brochures and other documents require their own mapping. Treating every file as a normal gallery photograph can place important media in the wrong section or omit it entirely.
5. Link agents and agencies as records
Agent information is reused across multiple listings. Matching a property to the correct Houzez agent or agency record gives the site consistent contact details, profile pages and listing relationships. The sync also needs a strategy for new staff, name changes, duplicate email addresses and agents who leave an office.
How WP AgentBox Sync integrates Agentbox with Houzez
WP AgentBox Sync is our Agentbox WordPress plugin. We built it around the practical difference between importing a listing and creating a listing that works correctly with the selected WordPress real estate theme.
For Houzez websites, the plugin maps Agentbox listing data into Houzez-compatible post fields, taxonomies, media and relationships. Depending on the configured Agentbox connection, listing data can be retrieved through supported feed or API workflows, while webhook support can deliver updates when CRM data changes.
- Connect Agentbox: add the credentials and connection details supplied for the agency account.
- Choose the sync scope: configure which listings and fields should be brought into WordPress.
- Map the Houzez structure: write property details to the appropriate post data, meta fields, taxonomies and relationship fields.
- Process media: connect photos, featured images and floor-plan data to the property.
- Keep listings current: match future Agentbox updates to the same WordPress property instead of requiring duplicate manual entry.
Agentbox remains the source of truth, while WordPress becomes the correctly structured publishing layer. If a particular property needs a protected manual change, the plugin also provides a listing lock workflow described in the WP AgentBox Sync documentation.
The integration is not limited to displaying listings. Agencies using Elementor can also connect website enquiries to Agentbox. See our guide to setting up Elementor forms with WP AgentBox Sync.
Common Houzez property data problems and what they mean
| Symptom | Likely mapping issue |
|---|---|
| Property exists in WordPress but not in Houzez search | Wrong post type, status, taxonomy or searchable meta field |
| Price displays but cannot be filtered or sorted | Numeric and display price were not separated correctly |
| Map pin is missing | Incomplete address, geolocation or Houzez map fields |
| Gallery is empty | Remote URLs were saved without media attachment and gallery mapping |
| Suburb filter returns no results | Suburb stored as text instead of the relevant location taxonomy |
| Agent name appears without a profile link | Text imported without matching a Houzez agent record |
| Duplicate properties appear after every sync | No stable Agentbox ID match or update strategy |
Houzez and Agentbox integration checklist
- Confirm the installed Houzez version, child-theme customisations and enabled custom fields.
- Document which Agentbox value is the permanent listing identifier.
- Separate public display values from numeric search values.
- Map property type, status, features and locations to taxonomies.
- Normalise state, suburb and property-type names before creating terms.
- Test map coordinates and address visibility rules.
- Verify featured image, gallery order, floor plans and document handling.
- Match agent and agency records instead of importing names as plain text.
- Test new, updated, sold, leased, withdrawn and deleted listings.
- Check that manual exceptions can be protected from later syncs.
Frequently asked questions
Does Houzez store properties as normal WordPress posts?
Houzez properties use a custom post type rather than the standard blog post type. Each property still uses WordPress core data, but Houzez adds custom meta, taxonomies, media and relationships for real estate functionality.
Can Agentbox listings be synced to the Houzez theme?
Yes. WP AgentBox Sync supports Houzez-aware mapping so Agentbox listings can be created and updated inside the property structure expected by the theme.
Why is my imported Houzez property missing from the map?
The most common cause is incomplete or incorrectly mapped geolocation data. Houzez needs the relevant address and coordinate fields, and the property must also be configured for map display.
Why do generic XML or CSV imports cause problems with Houzez?
XML and CSV are transport formats, not theme mappings. An import only works fully when every source value is transformed into the correct Houzez field, taxonomy, attachment or relationship.
Will a sync overwrite manual property edits?
Synced properties normally need to follow Agentbox as the source of truth. WP AgentBox Sync provides a lock option for listings that should be protected from subsequent updates, as covered in the plugin documentation.
Need a reliable Agentbox to Houzez integration?
We have worked extensively with WordPress real estate data, Agentbox and the Houzez property model. WP AgentBox Sync keeps listings current without forcing your team to maintain a fragile custom import or duplicate property data manually.
Custom Houzez fields, child-theme changes and unusual listing workflows can be reviewed as part of the mapping plan.