Websites for housing projects: the showroom before the sales office
A housing project’s website is where buyers look for answers before they ever visit the sales office. A good project page answers five questions plainly: which unit types are available, what the floor plans look like, where the development is and what is nearby, how construction is progressing, and when handover is due. A buyer who finds them arrives at the sales office close to a decision.
Below we go through what a project page needs, section by section.
Why the project page is the first showroom
A family looking for a home rarely starts at the sales office. They start by searching — for the development’s name, the neighbourhood, or a phrase such as “three-bedroom flat with garden”. They browse property portals, notice an image on social media, hear the name from a friend.
All of these routes end in the same place: the project’s own page. A portal listing describes one flat. The project page tells the whole story — who is building it, why there, how, and when it will be finished.
The biggest question on a buyer’s mind is trust. They are committing to a payment plan that may run for years, on a building that does not yet exist. A project page earns that trust not with grand sentences but with orderly, verifiable information.
What a project page should contain
The checklist below shows the core sections of a housing project page and the question each one answers.
| Section | Question it answers | What it should include |
|---|---|---|
| At a glance | What is this development? | Site area, number of blocks and units, storeys, share of green space, a short introduction |
| Unit types | Is there a home for me? | Type (one-bedroom, two-bedroom…), gross and net area, room layout, availability |
| Floor plans | What is it like inside? | A legible plan for each type, orientation, a note on scale |
| Shared spaces and features | What does the development offer? | Parking, landscaping, communal areas, security, insulation and structural system |
| Location | Where is it, and what is nearby? | Map, schools, shops, hospital, travel times to main roads |
| Construction progress | Where are things now? | Percentage complete, stages with dates, recent site photographs |
| Handover | When will it be finished? | Planned handover date, clear information on completion and title processes |
| Sales office | How can I see it? | Address, opening hours, visit booking form |
| Listings | Which units are for sale? | Current listings linked to the development, or links to portals |
Unit types: in a table, and honest
Showing unit types in a table makes comparison easy. Type, gross area, net area, layout and availability should sit side by side. Keeping statuses such as “last few remaining” or “sold out” up to date matters. A type that has sold out but still appears available damages trust.
A note that areas are design figures and may differ slightly at the title stage heads off a misunderstanding before it happens.
Floor plans: legible and accessible
The floor plan is the image a buyer studies longest. It should zoom cleanly on a phone, with readable room names and dimensions and north clearly marked.
A plan should not be an image alone, either. Alternative text and a short description beneath it — “the living room and kitchen face south; two bedrooms face north” — make the plan understandable to people using screen readers too. If you offer plans as downloadable files, stating the file size on the page is a good habit.
Location: a map and realistic times
“Close to the centre” says nothing. Minutes to the school, the supermarket, the hospital and the main roads say something. Those times need to be realistic — a visiting buyer will walk or drive the route themselves.
The map should not slow the page down. We load it only when it is needed and put a plain text list beside it, so the information survives even if the map does not load.
Construction progress: the most frequently updated section
On an unfinished development, the question buyers ask most often is “how far along is it?” A progress percentage, a timeline with completed and upcoming stages and their dates, and recent site photographs answer it.
If this section is not updated regularly, it does more harm than good. A photograph from six months ago prompts the question “has work stopped?” That is why the progress section should be built so that someone without technical knowledge can update it.
Handover and information notes
The handover date shapes a buyer’s own plans. State the planned date clearly, and update the page whenever it changes.
Selling and advertising homes is subject to consumer-protection and advertising rules. Whether images are illustrative, how areas are calculated, what the handover date depends on — we recommend confirming how such information should appear with your legal adviser, against the rules that currently apply. We build the page layout with room for these notes from the start.
Booking a sales-office visit
The target action of a project page is usually a visit to the sales office — to see the model, touch the material samples, talk to a sales adviser. The page should make that visit as easy as possible.
A good visit form is short:
- Name and phone number
- The unit type of interest (with an option for those who have not yet decided)
- Preferred day and time window
- A link to the privacy notice explaining how personal data will be used
Say what happens after the form is sent, too: “Once we receive your request, we will call to confirm the time.” The sales office’s address, opening hours and weekend booking arrangements should sit right beside the form.
You can see how this looks on the Yıldız Park Evleri project page, part of a Turkish-language example site we built for a fictional developer. The at-a-glance facts, unit-type table, shared spaces, location and nearby places, construction progress and handover timeline, and the sales-office visit form all appear in order on a single page. The forms on the example site send nothing; they are there only to show the flow.
How the site works with portal listings
Property portals are one of the most common places buyers begin their search. A project website does not replace them; it complements them.
The division of labour looks like this:
- A portal listing shows a single unit to a wide audience. Visitors compare, filter and shortlist.
- The project page describes the development that unit belongs to — the company, the structural system, progress, location and the sales office.
Linking from listings to the project page, and from the project page to its current listings, joins the two routes. If the developer’s own site carries listing pages, each listing should link to its project, and sold units should come off the list.
One more detail: copying the same text word for word onto the portal and the site sets the two pages against each other in search. Giving the project page its own, fuller copy avoids the problem.
A company site, or a separate project site?
Some developers register a separate domain for every project. Others gather all their projects under the company website. Both have their place:
- Project pages within the company site: The company’s history, completed projects and team are visible in one place. A new project benefits from trust already earned, and search visibility accumulates on a single domain.
- A separate project site: Worth considering for a large, long-running development that needs its own brand voice — but even then, it should link clearly back to the company site.
For most developers, the starting point is a set of project pages within the company site, each following the same layout. Keeping completed projects on the site matters too: they are the strongest reference for new ones. The page of a delivered project answers the question “did they do what they said?”
Speed and image quality
Housing project pages are image-heavy: exteriors, interiors, landscaping, the site itself. Those images should not slow the page down.
Preparing images for different screen sizes, compressing them in modern formats and loading off-screen images later keeps the page quick on a phone. In mobile Lighthouse tests, our example sites score 96–100 for performance and 100 for accessibility, with layout shift (CLS) below 0.05.
For our general approach, see our web design and development service. If the project is still at the planning stage, how long a website takes may help with the timeline.
Frequently asked questions
Does a housing project need its own website if it is already on the portals?
Portals show individual units; they do not tell the story of the development. A project page carries the information that builds trust — the developer, the structural system, construction progress and the handover date — and links back to the listings.
Who should update the construction progress section?
Ideally someone on your own team, without waiting for a developer. We build the progress section so that a percentage, a stage date or new site photographs can be added without technical knowledge.
Should a completed project stay on the website?
Yes. A delivered project is the clearest evidence a buyer can find that you finish what you start. It also keeps the search visibility that page has built up.
If you are considering a project page for a new or ongoing development, have a look at our web design and development service or write to us with a few lines about the project. We reply within two working days.