New development website: how to build a property project website that generates enquiries?

What a new development website should answer for the buyer

A buyer of a new-build home arrives with a few questions: where the project stands, when it will be completed, which apartments are still available and what the actual terms of purchase are. If the site answers in that order, the path to an enquiry is short. If buyers have to hunt for answers through menus and PDFs, they usually move on to a competing project.

We recommend five levels of content, moving from the general to the specific. Each level has its own purpose, and together they form the path from first interest to contact with the sales team. The structure holds in Slovenia, Croatia and German-speaking markets; what differs is mainly the data buyers expect and the legal notices.

• Project: what you are building, who the developer is, expected move-in date
• Location: distances, surroundings, accessibility
• Building: floors, layout, communal areas, parking
• Units: floor plan, area, status, price or “price on request”
• Enquiry: form, phone call, viewing booking

Project and location: what the buyer checks first

The first screen must tell the visitor within seconds the project name, town, number of units, building type, expected completion date and developer. It should have one main action, such as viewing available units, and one secondary action, the enquiry. A large hero image that hides all the information does not help the buyer.

A location is not a map with a single pin. Buyers care about the nursery, school, shop, public transport and road access, so give distances in minutes on foot or by car and verify them before publishing. In German-speaking markets the energy standard and heating type are also usually important, so include them among the core project facts.

Add the project phase (planning, construction, completion) with the date of the last update. This shows buyers that the site is maintained and makes them more likely to trust the stated deadlines.

Building and units: the core of a property project website

The building is the bridge from a general impression to a specific choice. An interactive building model, in which the buyer selects a floor and then a unit, replaces long tables. Once a unit is selected, it shows the area, number of rooms, orientation, status and floor plan.

Each unit should have its own subpage with a unique address (URL). Buyers can save it, share it with family or find it through a search engine, and you can attribute each enquiry to a specific unit. The enquiry button should already have the unit pre-filled.

Because the apartment does not yet exist, the most informative thing for a buyer is a free-roam 3D walkthrough in the browser, with no installation. ARHIX prepares it from a BIM model or project documentation. It is not a 360° panorama with fixed points, because the buyer moves through the space independently. Place the walkthrough on the unit subpage, not in a hidden menu.

• Area, number of rooms and floor
• Floor plan with dimensions and orientation
• Status: available, reserved, sold
• Price or a clearly stated “price on request”
• Terrace, balcony, storage room, parking space
• Link to the 3D walkthrough or the unit view in the model

Enquiries: the form and the route into your CRM

The form should have as few fields as possible: name, email or phone number, the pre-filled unit and an optional message. Every extra field reduces the number of completed forms, and you can collect the remaining details in the first conversation. Alongside the form, offer a phone call, a viewing booking and a floor plan download, since not every buyer is ready to speak to a salesperson straight away.

An enquiry should reach your CRM automatically, together with the unit, language, traffic source and time of submission. The salesperson receives a notification and the buyer receives confirmation that the message has arrived. Unit statuses on the site should be synchronised with statuses in the CRM, so that the site never offers an apartment that is already reserved.

For privacy, use separate consent for processing the enquiry and for marketing messages. In German-speaking markets also expect to provide an Impressum and a clear data protection notice under the DSGVO, while in Croatia and Slovenia a GDPR notice in the appropriate language is required.

Speed and SEO for a new development website

Most visits come from mobile phones, so the first content must appear quickly. Save images in modern formats such as WebP or AVIF and load them progressively. Load 3D content only when the visitor clicks a button, for example “Open 3D walkthrough”, not when the page opens. Check speed with Lighthouse and PageSpeed Insights, focusing on LCP, INP and CLS.

For search engines you need one page for the project and one for each unit, each with its own title, H1 and description. Add schema.org structured data (for example ApartmentComplex and Apartment), a sitemap and canonical URLs. On a multilingual site, use hreflang tags for SI, HR, DE and EN, and reviewed translations rather than automatic ones.

Do not delete pages for sold units. Leave the status “sold” and add links to similar available units, otherwise the buyer lands on a 404 error and you lose the traffic those pages already attracted.

Common mistakes and a checklist

Most project websites do not fail because of their visual design, but because of missing data and slow processes. Use the list below as a quick check of an existing or new site.

If you answered “no” to most of these points, it makes sense to fix the structure first and only then add new visualisations.

• Only a gallery of visualisations, with no unit data
• A floor plan as a low-resolution image or a PDF without areas
• A form with more than five fields
• Unit statuses that someone updates by hand and that therefore lag behind
• 3D content that slows down the loading of the whole page
• A translation into English only, or no Impressum and data protection notice for the German market

What you can do next

Sketch the five levels (project, location, building, units, enquiry) and write under each what the buyer needs to learn there and what they should do next. Then check whether every unit has its own address, its own status and a route into your CRM.

You can see how a free-roam 3D walkthrough works in the browser in the public demo of a sample house at https://moderna-hisa-3d.netlify.app/. It will help you judge where on a unit subpage it would be most useful.