Building a real estate website involves more than creating attractive property cards and adding photographs to individual pages. As a property catalogue grows, managing prices, locations, property specifications, availability and other listing information manually becomes increasingly difficult. A website that relies on individually designed pages for every property can quickly become cumbersome to maintain, particularly when information needs to be updated across multiple listings.
A more sustainable approach is to separate property information from its visual presentation. WordPress supports this through custom post types, taxonomies and custom fields, while Advanced Custom Fields (ACF) provides a convenient interface for managing structured property metadata. When connected to Elementor Pro’s dynamic content functionality, these structures can power reusable listing cards, individual property templates and archive layouts.
This approach is particularly useful for estate agencies, property developers and businesses managing multiple residential or commercial listings. However, there is an important distinction between displaying dynamic information and building a fully functional property discovery platform. While Elementor provides the visual tools for creating reusable layouts, more sophisticated requirements such as custom-field filtering, interactive maps and automated enquiry routing may require additional development.
In this guide, we’ll walk through the underlying architecture, explain how to connect ACF to Elementor, and examine how these concepts extend into real-world implementations developed by Cr8v Stacks.
Prerequisites and System Requirements for Dynamic Property Grids
Before designing property listing templates, you need to establish the underlying content structure. Each component has a distinct responsibility: WordPress manages the content records, custom post types separate properties from ordinary posts, ACF stores additional property information, and Elementor controls how that information appears on the frontend.
The following table outlines the main components required for a conventional ACF and Elementor property directory.
| Component | Required Role / Configuration | Stack Responsibility |
|---|---|---|
| WordPress Core | Current supported installation with appropriate permalink settings | Provides content management, database storage and the underlying application framework. |
| Advanced Custom Fields | Compatible ACF installation | Stores structured property metadata such as prices, addresses, bedrooms and availability. |
| Elementor Pro | Active installation with Dynamic Tags and Loop Grid functionality | Provides the visual editing environment, reusable templates and dynamic content integration. |
| Custom Post Type | For example, property | Separates real estate listings from standard posts and pages. |
| Custom Taxonomies | Property type, location and listing status | Organizes listings into meaningful categories and supports taxonomy-based queries. |
| Loop Item Template | Reusable Elementor Loop Item | Defines the visual structure used to display individual property records in a grid. |
One important consideration is that ACF and Elementor do not automatically provide every feature associated with a professional real estate directory. Their native integration handles structured data and visual presentation, but advanced filtering, property comparisons and specialized search behaviour may require additional plugins or custom development.
What Plugins Are Required for Elementor ACF Dynamic Content?
For the implementation covered in this tutorial, the primary requirements are Advanced Custom Fields and Elementor Pro. ACF provides the custom metadata fields, while Elementor Pro exposes supported ACF values through its Dynamic Tags interface and provides the Loop Grid functionality used to display reusable property cards.
ACF’s free version is sufficient for many basic property attributes, including text, number, image and select fields. More advanced requirements, such as repeater fields and galleries, may require ACF PRO. The appropriate configuration ultimately depends on the information your property directory needs to manage.
Step 1: Registering the Real Estate Custom Post Type and Taxonomies
The first step is creating a dedicated content type for property listings. Although WordPress allows you to publish property information using standard posts or pages, a custom post type provides a more organized structure for managing a growing inventory.
You can register a custom post type using PHP or a suitable WordPress administration tool. ACF also provides post type registration functionality, allowing you to establish the structure without writing the registration code yourself.
Configure Core Post Type Settings
Create a post type with the name Property and a suitable URL slug, such as property. Enable public visibility and public querying if listings are intended to appear on the frontend. You can also enable archive functionality if you want WordPress to provide a dedicated property archive endpoint.
Enable the appropriate native WordPress features, including titles, featured images, excerpts and the content editor, depending on how the listings will be managed. The exact configuration should reflect the website’s content requirements rather than enabling every available option by default.
Add Custom Taxonomies for Property Organization
Custom taxonomies provide another important layer of organization. For example, a real estate directory might use Property Type, Location and Listing Status to classify its inventory. A hierarchical location taxonomy can accommodate geographical structures such as countries, cities and neighbourhoods, while non-hierarchical taxonomies can be used for independent labels.
It is important to distinguish taxonomies from custom fields. A location category used to organize multiple properties is better suited to a taxonomy, whereas a specific street address or building number is usually better stored as an individual field. Making this distinction early helps establish a more consistent data structure and makes subsequent query configuration easier.
After registering new post types or changing rewrite settings, visit Settings > Permalinks and save the settings if necessary to refresh WordPress rewrite rules. This is particularly useful when newly registered listing URLs return unexpected 404 errors.
Step 2: Structuring Property Metadata with Advanced Custom Fields
With the property post type established, the next stage is defining the information each listing needs to store. Advanced Custom Fields allows you to create structured inputs for property attributes, ensuring that information is entered consistently rather than being embedded entirely within the standard post editor.
A typical property record might include its asking price, address, floor area, number of bedrooms, number of bathrooms, property status and photographs. Depending on the type of real estate being managed, you may also need fields for parking spaces, plot dimensions, development information, rental terms and floor plans.
Create a Dedicated ACF Field Group
Open your WordPress admin dashboard and navigate to ACF > Field Groups. Click Add New to create a collection of custom fields specifically for your property records.
Give the group a descriptive name, such as Property Information. You can then begin adding individual fields using suitable field types. The following configuration provides a basic starting point.
| Field Label | Field Name | Field Type |
|---|---|---|
| Property Price | property_price | Number |
| Property Address | property_address | Text |
| Bedrooms | bedrooms | Number |
| Bathrooms | bathrooms | Number |
| Floor Area | floor_area | Number |
| Property Status | property_status | Select |
| Property Description | property_description | Text Area |
| Property Gallery | property_gallery | Gallery (ACF PRO) |
Configure Location Rules and Field Types
Scroll down to the Location Rules section to determine where the fields should appear in your WordPress dashboard. Set the rule to display the field group if Post Type is equal to Property. This ensures that the property-specific inputs appear when creating or editing property records rather than appearing on unrelated pages or blog posts.
Choose field types according to the information being collected. For example, a numerical price should generally be stored in a Number field rather than unrestricted text, while listing status is better managed through predefined Select options. Image and file fields should also use appropriate return formats for the way their values will be displayed later.
Once the configuration is complete, publish the field group and open an existing Property record. You should now see the additional inputs in the editing interface, allowing administrators to populate the structured information associated with each listing.
Step 3: Designing the Loop Item Template with Elementor ACF Dynamic Content
After establishing the content structure, you can begin connecting the stored information to the frontend. Elementor Pro’s Dynamic Tags functionality allows supported widgets to retrieve values from the current property record rather than relying on manually entered content.
This is particularly useful when building reusable property cards. Instead of designing a separate card for every listing, you create one template and allow Elementor to populate its elements using the corresponding post title, featured image and ACF values.
Create a New Loop Item Template
Navigate to Templates in your WordPress dashboard and open Theme Builder. Create a new Loop Item template and launch the Elementor editor.
Configure the preview settings to use an existing property record. Previewing actual listing information makes it easier to evaluate text wrapping, image dimensions, spacing and other layout details while building the template.
Bind Custom Fields to Layout Widgets
Add the necessary Heading, Image and Text Editor widgets to your layout. Select a widget and locate the Dynamic Tags icon beside its content field. Choose ACF Field and configure the field settings to retrieve the appropriate property attribute.
For example, you can connect a Heading widget to the property_price field, while another text element retrieves the bedroom count. The property title can use Elementor’s native Post Title dynamic tag, and the primary listing photograph can use the featured image or a compatible ACF image field.
Pay attention to field return formats, particularly when working with images, galleries and file fields. ACF can return different data formats depending on the field configuration, and not every format is compatible with every Elementor widget. Check the field settings and use the appropriate dynamic tag or custom rendering method where necessary.
Configure Hover Effects and Card Constraints
Once the dynamic connections are working, you can refine the appearance of your property cards. Add suitable hover transitions to image containers, configure consistent image aspect ratios and establish spacing rules that work across different listing records.
If you want to explore more advanced visual presentation strategies, see our tutorial on creating hover image reveal lists in Elementor. It provides another example of how carefully designed interactions can improve the presentation of visual content.
Also consider what happens when a property has missing information or an unusually long title. A reusable template should accommodate these variations without producing empty labels, broken layouts or inconsistent card heights. Where necessary, configure fallback values or use conditional display logic to hide elements that have no corresponding data.
Step 4: Querying and Displaying Listings with the Elementor Loop Grid Widget
With the Loop Item template complete, you can use Elementor Pro’s Loop Grid widget to display multiple property records on a page or archive. This provides a reusable listing interface without having to manually place individual property cards throughout the website.
Open the page or template where you want the listings to appear and drag the Loop Grid widget onto the canvas. Select the property card template you created earlier so the widget knows how each record should be displayed.
Configure the Property Query
Open the Query settings and select the Property post type as the content source. You can then configure the available query conditions to control which listings appear. For example, taxonomy conditions can be used to show apartments in a particular location or display only properties assigned to a specific listing category.
Other query settings allow you to control the number of records displayed, ordering, exclusions and pagination. This is useful when building separate sections for recently published properties, featured developments or listings belonging to a particular property category.
Understand the Limitations of Native Property Filtering
There is an important technical distinction between querying property records and filtering them using arbitrary custom-field values. Elementor’s native query controls support several useful conditions, including post types and taxonomies, but displaying an ACF price field inside a card does not automatically make that field available as a functional minimum-and-maximum price filter.
For more sophisticated property searches, developers may need to introduce custom query logic using WordPress metadata queries, a compatible filtering plugin or bespoke PHP functionality. AJAX can then be used to update the results without requiring visitors to reload the entire page after changing their search criteria.
This distinction becomes increasingly important as a property directory grows. Visitors may expect to search by price range, property type, availability and geographical location simultaneously. Delivering that experience requires the underlying data structure, query logic and frontend controls to work together rather than simply connecting more dynamic tags to Elementor widgets.
Configure Grid Layout and Pagination
After configuring the query, adjust the Loop Grid layout to establish the number of columns, gaps and responsive behaviour. Enable suitable pagination when displaying larger property inventories so visitors can navigate the available listings without loading every record simultaneously.
Test the finished layout using multiple property records and viewport sizes. Check image proportions, title lengths, missing metadata and pagination behaviour. A property grid should remain consistent even when the underlying listings contain different information.
Step 5: Extending a Dynamic Property Directory into a Professional Real Estate Platform
The architecture covered so far provides a solid foundation for managing and displaying property information. However, a professional real estate platform often requires considerably more than a collection of dynamic cards and individual listing pages.
Depending on the business model, additional functionality may include multi-criteria property searches, interactive maps, agent assignment, property comparison, saved searches, enquiry routing and integrations with external property management systems. These requirements introduce additional architectural considerations that cannot always be addressed through standard Elementor widgets.
This is where custom WordPress development becomes particularly valuable. A bespoke implementation can combine structured post types, ACF metadata, custom PHP query routines, frontend JavaScript and AJAX endpoints to create functionality that is designed around the actual requirements of the property business.
Mkenny Properties: Building a Bespoke Real Estate Directory
At Cr8v Stacks, we applied this broader approach while developing the real estate platform for Mkenny Properties, a commercial property business operating in Manchester, United Kingdom.
The project involved transforming a basic corporate presence into a more comprehensive property catalogue. Rather than relying on a conventional collection of manually maintained pages, we developed a structured WordPress architecture with dedicated property post types, taxonomy systems and custom listing components.
The implementation included bespoke PHP-powered widgets and dynamic property listing functionality, giving the editorial team greater control over how individual developments and commercial properties were presented. We also developed filtering functionality that allowed visitors to narrow listings using relevant property criteria.
The result was a more purposeful property discovery experience, supported by a content architecture designed around the client’s actual requirements rather than the limitations of a generic real estate template.
This is an important distinction when evaluating the capabilities of Elementor and ACF. These tools provide useful building blocks, but a more sophisticated property platform may require custom components and query functionality to deliver the expected experience.
See what we built: Explore the Mkenny Properties case study in the Cr8v Stacks portfolio.
The Duch Apartments: Extending Property Website Engineering Beyond Listings
Another relevant example of our work is The Duch Apartments, a luxury serviced apartment business in Lagos, Nigeria. Although hospitality platforms have different operational requirements from conventional real estate directories, they share several underlying considerations, including structured property information, user-friendly discovery, availability management and conversion-focused website architecture.
For The Duch Apartments, Cr8v Stacks developed a bespoke digital platform with a strong emphasis on direct bookings and search visibility. Rather than treating the website as a static collection of accommodation pages, the implementation incorporated a dedicated booking experience designed to support the business’s reservation process.
The platform demonstrates how a property-related website can extend beyond displaying information to supporting an actual business operation. Its design and technical architecture were developed around the needs of the hospitality operator, with an emphasis on creating a direct customer journey rather than relying entirely on third-party booking platforms.
While this project is not a conventional ACF and Elementor property directory, it provides another example of our approach to building bespoke digital platforms for property and accommodation businesses.
Explore the project: View The Duch Apartments case study in our portfolio.
Both projects illustrate an important principle: the right website architecture should reflect the operational requirements of the business. A simple property catalogue may work perfectly well with standard WordPress components, while a more advanced platform may require bespoke functionality to support search, enquiries, reservations and other customer interactions.
Performance, Maintenance and Scalability Considerations
A dynamic property directory should be designed with long-term maintenance in mind. As the number of listings increases, the underlying data structure, image delivery strategy and query implementation can have a significant impact on the website’s performance and usability.
Maintain Consistent Property Data
Use appropriate field types and predefined options wherever possible. For example, storing listing availability through a Select field helps prevent inconsistencies caused by administrators entering different variations of the same status. Similarly, numerical information should be stored in numerical fields when it needs to support sorting or filtering.
Optimize Property Images
Property websites are particularly dependent on photographs and image galleries. Large, unoptimized images can increase page weight and affect loading performance. Use appropriately sized images, modern formats where supported, responsive image delivery and lazy loading where appropriate.
Be Careful with Complex Queries
Advanced filtering can introduce additional database queries, particularly when several custom fields are involved. Query logic should be designed around the expected listing volume, with appropriate caching and database optimization where necessary.
Test Templates with Real Property Records
Do not rely exclusively on placeholder information when evaluating your templates. Test listings with different numbers of photographs, missing specifications, longer titles and varying availability statuses. This helps identify rendering issues before they affect the live website.
Build Your Custom Real Estate Directory with Cr8v Stacks
Combining Advanced Custom Fields with Elementor Pro provides a practical foundation for building dynamic property listings in WordPress. Custom post types establish a dedicated content structure, ACF manages property metadata, taxonomies organize the inventory, and Elementor provides the visual tools for displaying that information through reusable templates.
However, the requirements of a professional real estate website often extend beyond displaying property information. Advanced search, custom filtering, interactive maps, lead routing and other business-specific functionality may require a more sophisticated development approach.
Our work on Mkenny Properties demonstrates how a structured WordPress foundation can be extended into a bespoke property directory, while The Duch Apartments illustrates how custom website engineering can support a more complete digital experience for a property-related business.
At Cr8v Stacks, we build WordPress platforms around the actual requirements of the businesses using them. Whether you need a property directory, a custom development catalogue or a more advanced digital platform, our approach combines thoughtful architecture, purposeful design and functionality built to support your operations.
If you’re planning a real estate website or considering an upgrade to an existing property platform, explore our WordPress development capabilities and discover how we can help turn your requirements into a scalable digital solution.
Frequently Asked Questions
What plugins are required for Elementor ACF dynamic content?
You need Advanced Custom Fields and Elementor Pro for the standard integration described in this tutorial. Elementor Pro provides Dynamic Tags and Loop Grid functionality, while ACF manages the structured property metadata.
How do I create a custom post type for real estate listings?
You can register a Property custom post type using PHP, ACF’s post type registration functionality or another suitable WordPress tool. Configure the post type with the appropriate public visibility, supported features and archive settings for your website.
Can Elementor Loop Grid display custom post types?
Yes. Elementor Pro’s Loop Grid can retrieve supported WordPress custom post types. You can connect a reusable Loop Item template to the grid and configure its query to display the required property records.
Does ACF automatically create property search filters?
No. ACF stores structured property information, but advanced filtering requires additional functionality. Depending on the search requirements, you may need taxonomy queries, custom-field query logic, a compatible filtering plugin or bespoke PHP and AJAX development.
Can I filter real estate listings by price and location?
Yes. Location filtering can be implemented using custom taxonomies, while price filtering can use numerical custom-field values and appropriate query logic. More advanced search interfaces may require additional development to combine multiple filtering conditions efficiently.
Why should property listings use a Loop Item template?
A Loop Item template provides a reusable design for displaying individual property records. Instead of manually designing every card, you create one template that retrieves the appropriate information from each listing, making it easier to maintain a consistent frontend presentation.
