Property Pages and Property Search in the Webflow CMS: Filters, Brochures and Self-Editing

In short: Property pages, property search and brochure download work well in the Webflow CMS if you maintain the properties yourself and the number of simultaneously active properties stays manageable. You need a clean data model with required fields, a filter solution and rules for URLs. If you want to import hundreds of properties automatically from broker software, you should consider WordPress with a real estate plugin or an interface as an alternative.

What a property page has to deliver

A property page is more than a gallery with a price. It has to answer questions before anyone picks up the phone, and at the same time meet the legal disclosure requirements.

• Key data: Property type, location, living or usable area, rooms, year of construction, price or rent, availability.
• Location: Map, surroundings, connections, in words and not just as a pin.
• Images, floor plans, visualizations: For new builds, also construction progress.
• Property brochure: As a download with visible benefit, not just a link for the sake of compliance.
• Inquiry: Form tied to the property, contact person, alternatives (phone, appointment).
• Energy details: Mandatory as soon as an energy certificate exists.

On the mandatory information: if an ad appears in commercial media and an energy certificate exists, Section 87 of the Buildings Modernization Act (Gebäudemodernisierungsgesetz) lists as minimum details the type of energy certificate, the final energy value, the main energy sources and, for residential buildings, the year of construction and the energy efficiency class. For non-residential buildings, heat and electricity must be stated separately. Lawsuits over missing energy details in listings are documented, for example a 2024 lawsuit by Deutsche Umwelthilfe (DUH, statement of claim). Check the current version of the regulation with your legal counsel. Technically, this means: these fields belong in the CMS as required fields, so no property can be published without them.

Data model: how to set up properties in the CMS

In the Webflow CMS, you define a collection with fields. This structure works for real estate websites:

Two field types are decisive for search: number fields (price, area, rooms) allow range filters and sorting, reference fields (location, property type) allow filtering by category. Never enter numbers as text ("approx. 450,000 EUR"), otherwise no filter will work.

Control status instead of deleting pages

A sold or rented property should not simply disappear. A status field (available, reserved, sold) and a separate reference view for completed properties save you 404 errors and provide references. WP-ImmoMakler handles reference properties the same way and shows them without a price (WP-ImmoMakler, features). In the Webflow CMS, you build this with a status field and conditional visibility.

Property search with filters for location, price and area

Webflow collection lists can be filtered and sorted by fields, but you set these filters in the Designer. Visitors cannot operate them. For a search that visitors control themselves, many projects use Finsweet Attributes. The List Filter is free and, according to the documentation, supports checkboxes, radio buttons, select fields and text search, as well as operators such as greater than and less than for numbers and dates. That lets you map price and area ranges. Active filters can be shown as tags, and a counter shows the number of results. The filters do not run in the Designer, so you test them on the published site.

Limits you should know

The Webflow CMS has fixed limits that shape the architecture of the search (Webflow, Dynamic content limits):

Webflow also describes that with pagination enabled, you can display more than 100 items (same help page). Whether a client-side filter then covers all properties is something you have to test with large inventories, because a filter can only work on items that are loaded. For total size, the Webflow pricing page names different limits depending on the plan: Starter 50 CMS items, Premium ($25 per month with annual billing) up to 20,000 items and 40 collections, Enterprise custom (Webflow, Pricing). For a broker with 30 to 300 properties, that is no problem. For portals with thousands of entries, it is a criterion.

Filters, URLs and SEO

Filtered views produce many URL variants. In its documentation on faceted navigation, Google describes two risks: overloading crawling and slower discovery of new content (Google, Faceted navigation). Whether filter URLs should appear in the index is a decision you make deliberately:

• Do not index: Filters without a URL of their own or with parameters blocked via robots.txt. Google ignores fragments (#) anyway.
• Index selectively: A few sensible combinations as pages of their own, for example "Condominiums in Munich". These pages need their own text and real content.
• Empty combinations: According to Google, these should return a 404 status, not a redirect.

For location and property type pages, it is best to create collection pages (locations, property types) that show filtered property lists with their own text. That is more stable than parameter URLs.

Brochure download: file or generated PDF?

The simplest way in the Webflow CMS is a file field per property. Editors upload the finished brochure, and a button links to it. Note the upload limit: Webflow names 10 MB for documents and 4 MB for images (Webflow, Working with assets). A brochure with many photos can exceed this limit. In that case you compress it or host it externally.

Two variants to weigh:

1. Download without a barrier: More reach, less data. Suits properties you want to market broadly.
2. Download after a form: You get a contact, visitors face a barrier. Often sensible for premium properties if the form stays short.

The Webflow CMS does not offer PDFs generated automatically from property data out of the box. That is an assessment from practice, not a statement from the documentation. WP-ImmoMakler, by contrast, generates multi-page PDF brochures with customizable header, footer and number of images (WP-ImmoMakler, features). If you need many brochures, that is a strong argument for this solution, or for generating the PDF in the broker software and bringing the file into the CMS.

Self-editing: how editors maintain properties

The Webflow CMS offers an editor in which editors create properties like form entries: fill in fields, upload images, save, publish. In practice, these rules apply:

• Mark required fields for price, area, location and energy details, so nothing is missing.
• Use draft until all details are checked.
• Specify image formats (aspect ratio, minimum width) so galleries stay consistent.
• Define roles: who may publish, who may only draft?
• Add a short instruction per field, visible directly in the editor.

The guide Maintaining the Webflow CMS yourself covers day-to-day work in the editor.

Importing properties automatically from broker software

Many brokers manage their properties in broker software and do not want to maintain them twice. The industry standard for exchange is OpenImmo, an XML format. WP-ImmoMakler lists compatible software such as onOffice, Propstack, FlowFact, estateOffice and FIO Webmakler, and supports import via OpenImmo over FTP or SFTP as well as direct interfaces to ImmoScout24 and Immowelt (WP-ImmoMakler, broker software).

The Webflow CMS has no OpenImmo import out of the box. You build a connection via the Webflow Data API: a script or an automation service reads the property data and creates entries in the CMS. The API allows up to 100 items per create request, with each language variant counting toward the total (Webflow, Create items). Rate limits are 60 requests per minute on Starter and Basic and 120 on the higher plans (the API documentation still uses the older plan names CMS, Ecommerce and Business for this), and publishing the site is limited to once per minute (Webflow, Rate limits). For a few hundred properties, that is enough. More on connecting systems is in the guide Connecting your website to a CRM.

Webflow CMS or WordPress plugin?

The plugin prices come from the provider's pricing page. BASIC covers up to 30 simultaneous properties, PLUS 50 to 250 depending on the package. WP-ImmoMakler also lists a Webflow integration among its interfaces, which shows that the two worlds can be combined. A hybrid solution is also possible: brand and project pages in Webflow, property list via the broker software or a plugin.

If you want to settle the platform question in principle, the comparison Webflow or WordPress helps.

Map, data protection and structured data

Maps and videos often load third-party services. The TDDDG (German Telecommunications Digital Services Data Protection Act) regulates access to information on the end device and in many cases requires consent (e-recht24, TDDDG). Build maps so that they load only after consent, with a static preview in front. WP-ImmoMakler also loads Google Maps only after consent.

For structured data, Schema.org has the type RealEstateListing, which according to its description represents a listing with one or more real estate offers. The type is still in development status at Schema.org. Google writes that structured data must match the visible content (Google, AI features and your website). So use markup only for details that are also on the page.

Project pages for developers

Project developers often do not need a large property search, but a project page with location, architecture, unit table and sales status. The Webflow CMS is well suited for this: a project collection, a units collection with a reference to the project and a table that shows price, availability, size and floor. A landing page template per project saves time with every new launch and keeps the presence consistent. How brand and project page work together is described on the page Branding and positioning for real estate companies.

When you do not need an agency

If you have few properties, no design goal beyond the portals and broker software with a website module, its standard page is often enough. A WordPress plugin with a ready-made theme is also sufficient if the brand does not play a special role and you handle maintenance yourself. An agency pays off when the site is meant to stage a brand, projects are built individually or data comes together from several sources.

How we implement this

Webwavers builds property pages following the process described on the process page: initial conversation, briefing, strategy conversation, design in Figma with a feedback round per milestone, development in Webflow, Framer or WordPress and launch with personal onboarding, so you can maintain content yourselves. The team advises neutrally between the Webflow CMS and a WordPress plugin. A dedicated project lead and a Slack channel of your own are part of the collaboration.

Two real estate projects for context, each based on the details on the project pages: the website of Palmera Hills was built in Webflow, with nine service pages, seven region pages and three paths to an inquiry, including a property check. A property search with filters is not the topic there, though. For Atoria Immobilien, the project page shows imagery of a website with properties and a map, but the project itself is about the corporate identity. A large property search with broker software integration is not documented among the references on the website. Whether and how that is feasible for you, we clarify in the initial conversation.

Frequently asked questions

Can we add new properties ourselves in the Webflow CMS?

Yes. You create properties in the CMS editor like forms, fill in the fields and publish. Required fields for price, area, location and energy details prevent incomplete entries. Onboarding at the start helps the team work with confidence.

How does a property search with filters for location, price and area work?

Price and area are number fields in the CMS, location and property type are references. A filter script such as the free Finsweet List Filter lets visitors filter by them. Keep the limit of 100 items per list without pagination in mind and test filters on the live site.

Webflow CMS or real estate portal plugin for WordPress, which fits better?

Webflow fits if design and a few, elaborately staged properties come first. A WordPress plugin fits if you have many changing properties and want to import automatically from broker software. The two can be combined.

Can I import properties automatically from onOffice or Propstack?

With WordPress and plugins such as WP-ImmoMakler, yes, via the OpenImmo interface. In the Webflow CMS, this needs a custom connection via the Data API, which you have to factor into planning.

How do I build in a brochure download?

One file field per property in the CMS, with a button linking to it. According to Webflow, documents may be up to 10 MB. Automatically generated brochures need a plugin or the broker software.

What information is mandatory in real estate ads?

If an energy certificate exists, Section 87 requires, among other things, the type of certificate, final energy value, energy sources and, for residential buildings, year of construction and energy efficiency class. Set up these fields as required fields.

Is a single landing page enough for a new-build project?

For the start of sales, yes, with location, visualizations, unit table and brochure download. Once several projects are running, a project collection pays off, so pages stay consistent and can be created faster.

Next step

If you want to maintain properties yourself and want to know whether the Webflow CMS, a WordPress plugin or a mix suits your inventory, talk to us about your property setup.

Sources

• Gesetze im Internet: § 87 Pflichtangaben in Immobilienanzeigen (mandatory information in real estate ads)
• Deutsche Umwelthilfe: Klageschrift 2024 zu fehlenden Energieangaben (2024 statement of claim on missing energy details)
• Webflow: Dynamic content limits
• Webflow: Pricing
• Webflow Developers: Working with assets
• Webflow Developers: Create items
• Webflow Developers: Rate limits
• Finsweet Attributes: CMS Filter
• Google: Faceted navigation
• Google: KI-Funktionen und deine Website (AI features and your website)
• WP-ImmoMakler: Funktionen (features)
• WP-ImmoMakler: Preise (pricing)
• WP-ImmoMakler: Maklersoftware (broker software)
• e-recht24: TDDDG
• Schema.org: RealEstateListing
• Webwavers: Process
• Webwavers: Palmera Hills project
• Webwavers: Atoria Immobilien project