← All posts

A real estate website with property listings: what it needs and how it gets built

A property website is a small search engine, a lead machine and a content system in one. Here is what a real estate agency or developer site needs, which parts are worth building custom, and how I approach the build.

Author
Elie Chaaban
Published
Reading time
8 min
Topics
Websites, Web Apps, Real Estate, Planning

A real estate website looks simple: photos, a price, a contact button. Underneath, it is a small search engine, a lead capture system and a content tool your team updates every week. When one part is weak, the site shows sold properties for months, buries listings behind clumsy filters, or sends enquiries into an inbox nobody checks.

This article is for agencies, brokers and developers about to hire someone to build or rebuild their site: what it needs, where a template is enough, and how I build it.

Start with who the site is for

Before features, decide what kind of property business the site serves, because the structure changes a lot.

An agency or brokerage lists many properties from many owners, for sale and for rent, across several areas. The site lives or dies on search, filters and keeping listings current.

A developer marketing one or more projects has fewer, bigger pages: a project, its buildings, unit types, floor plans, payment plan information, construction progress and a sales enquiry form. Search matters less; presentation and availability matter more.

A property manager or rental business cares about availability, viewing requests and sometimes a tenant or owner area, which starts to look like a portal rather than a website.

Many businesses are a mix; decide which one leads. If you are unsure whether you need a marketing site or something closer to an application, my post on website or web app walks through that line.

The listing is the core content type

Everything hangs off a well designed listing record. If the data model is vague, the filters, maps and SEO all suffer later. A typical listing holds:

Two details matter more than people expect. Location must be structured, not typed freely, or "Achrafieh" and "Ashrafieh" become two different areas in your filters. And status must be a real field with rules, so a sold property drops out of search automatically instead of waiting for someone to remember.

Search and filters people will actually use

Visitors arrive with a short list of hard requirements: area, budget, type, bedrooms, buy or rent. The search should let them set exactly those in a few taps on a phone and see results without reloading the whole page.

Put the five or six filters most people use up front and fold the rest into a "more filters" panel. Make the filters part of the URL, so a search like "3 bedroom apartments for rent in a given area under a set budget" can be shared on WhatsApp, bookmarked and indexed. Sort by newest and by price at minimum.

Behind the scenes, this is a database problem. For hundreds or a few thousand listings, a properly indexed Postgres database handles filtering comfortably; a dedicated search engine only earns its place on a very large inventory.

Maps, photos and speed

A map view helps buyers who think in neighbourhoods. It is worth offering as a toggle next to the list, with pins clustered when zoomed out. Decide early whether you show exact locations or an approximate area; many owners do not want their exact address public until a viewing is booked.

Photos are where property sites get slow, since a listing can have dozens of large images straight from a phone. The site has to resize and compress them on upload, serve modern formats in the right size for each screen, and lazy load everything below the first image. Without that, a listing page on mobile data feels broken. I covered the wider topic in website speed and Core Web Vitals, and on property sites it is the single most common problem I see.

Turning visitors into enquiries

The point of the site is a conversation with an agent. Make that easy on every listing:

Then make sure the enquiry lands somewhere useful. At the simplest level, that is an email to the responsible agent with the listing reference and the visitor's details. A step up is a lead list inside the admin, with status (new, contacted, viewing booked, closed) so the manager can see what happened to each enquiry. If you already track deals in a spreadsheet, that lead list is the natural start of a small CRM; I wrote about that move in replacing spreadsheets with a custom CRM.

The admin side: where the site is won or lost

Many property websites fail because updating them is a chore. The admin has to make the daily jobs fast:

Agents and managers usually need different permissions: an agent edits their own listings, a manager approves, publishes and sees all leads. That is the same roles and permissions question I described in who can do what in a business app, on a smaller scale.

Arabic, English and currencies

For many agencies in Lebanon and the GCC, a bilingual site is expected. That means more than translating labels. Listing descriptions need a field per language, the layout has to mirror properly for right to left, numbers and prices must display clearly in both, and each language version needs its own URLs so Google can index both. My post on bilingual Arabic and English builds covers the details.

Currency is a business decision first: which currency each listing uses, whether you show one or several, and whether rentals show monthly or yearly. The site then applies that rule consistently.

SEO for a property site

Property search on Google is competitive, and large listing portals dominate generic searches. A business site wins on more specific intent: an area, a property type, a project name, your agency name. That shapes the structure:

If you also list on the big portals, keep your own site the most complete source with the direct contact. Whether listings can be pushed to a portal automatically depends on what it offers, so I check before promising it.

Template, WordPress or custom?

There are three realistic routes, and each fits a different business.

WordPress with a real estate plugin suits a small agency with modest listing volume that wants to launch quickly and edit pages itself. It is the same kind of WordPress and Elementor work behind content heavy sites like AgriDev, extended with listing fields and filters. The limits show when you need custom workflows, a clean lead pipeline or very fast search on a large inventory.

A custom Next.js site with its own admin suits agencies and developers who see the website as a core sales tool: fast listing pages, filters in the URL, exactly the fields and statuses you use, and a lead pipeline built around your process. I build these with Next.js on the front, a Postgres database, and an API (Next.js or .NET Core depending on the rest of the system), deployed with Docker and CI/CD so updates are routine.

A website plus a portal suits property managers or developers who need owner or tenant logins, documents and payment schedules. That is a portal project with a public website in front, and it is scoped differently. The comparison between the first two routes is in WordPress with Elementor or a custom Next.js site.

How I run the build

  1. Discovery. We agree on the business type, the listing fields and statuses, the filters, languages, currencies and who updates what. Bringing two or three sites you like (and why) speeds this up.
  2. Data model and admin first. I build the listing structure and the admin before the polished front end, so your team can start entering real listings early. Real data exposes missing fields far better than a spec does.
  3. Front end. Home, search results, listing pages, area or project pages, about and contact, designed mobile first.
  4. Leads and integrations. Enquiry forms, WhatsApp links, email notifications, the lead list, analytics and anything else agreed.
  5. SEO and launch. Redirects from the old site if there is one, sitemap, Search Console, speed checks on real listings with real photos.

Timeline and cost depend mostly on four things: bilingual or not, the size and complexity of the listing data, how custom the admin and lead workflow need to be, and whether old listings must be migrated. A clear brief makes the estimate much more precise.

What to prepare before contacting a developer

If you are planning a property website for your agency or project, you can see how I approach web builds on my website development page, and get in touch to talk it through on a call or by email at hello@eliechaaban.com.

More from the blog

Let's work
together