Websites for agencies and developers.

A listing is a page, or it does not exist

Nobody wakes up wanting to visit an estate agency's website. They want a two-bedroom in a specific area, under a specific number, and they will type approximately that. The consequence is that the homepage is close to irrelevant as an entry point, and every individual property has to be findable on its own terms.

Plenty of property sites fail this at the foundation. The listings live inside a search interface that loads results dynamically, which means there is no address you can send to anybody, nothing for a search engine to index, and no page for an assistant to cite. The catalogue exists, and none of it is reachable. From outside, the site is one page with a search box.

Built properly, each property has a real URL that loads the property, describes it in text, and can be shared in a message, bookmarked, indexed and quoted. Structured data lets a search engine understand price, location, size and type as facts rather than as a paragraph, which is what makes a listing eligible to appear as something richer than a blue link.

This also decides how filtering should behave. Narrowing by area and price is what visitors came to do, and it should be instant — but the filtered view is a convenience layered over pages that each stand alone, not a replacement for them. Get that order wrong and the site's entire inventory is invisible.

What happens to a listing when the property sells

This is the question specific to property, and it is nearly always answered badly, because the obvious action is the wrong one.

When a property sells or is let, the listing page is usually deleted. It is a reasonable instinct — it is no longer for sale. But that page is very often the best-ranked URL on the whole site: it accumulated links, it was shared, it matched exactly the search somebody was making, and it had been indexed for months. Deleting it throws all of that away and hands visitors a 404, and on a statically hosted site there is no redirect mechanism waiting to catch them.

The better pattern costs nothing. Keep the page. Mark it clearly as sold or let, with the date, and remove the price if you would rather not publish what it went for. Then use the space it has already earned to point at genuinely comparable properties — same area, same bracket. Somebody arriving from a search for exactly that kind of home has told you precisely what they want, and the page is now a well-ranked entry point into current stock instead of an error.

It is also honest proof of work in a way a testimonial is not. A page saying this sold, in this area, at this time is a record. Agencies claiming a strong track record while their site shows only what is currently unsold are throwing away the evidence.

The exception worth naming: if a listing has to disappear for a client's privacy, it should be removed deliberately with the right response rather than left to rot into a broken link. That is a decision to make per property, not a default.

Thirty photographs per property, which changes everything

Every kind of website has images. Property has a quantity of them that stops being an optimisation problem and becomes a structural one: twenty to thirty photographs per listing, dozens of listings, all of them large, and the whole point is that they look good.

The naive build loads the full gallery when the page opens. On a property site that means the visitor waits through several megabytes before reading the description, and on Lebanese mobile data a meaningful number of them leave first. The competing failure is over-correcting into lazy loading everything, so the first photograph — the one the page is really about — arrives late and the page looks broken while it does.

What actually works is boring and specific. The lead image is treated as the most important thing on the page and loads immediately at a size chosen for the slot it occupies rather than the size the camera produced. The rest of the gallery loads as it is needed. Everything is served in a modern format, and dimensions are declared so the layout does not jump while photographs arrive — a page that reflows under someone's thumb as they scroll is the most irritating thing a listing can do.

There is a related discipline nobody enjoys: the photographs have to be prepared. A folder of untouched camera exports is the single most common reason a property site is slow, and no amount of build cleverness fully compensates for a four-thousand-pixel image in an eight-hundred-pixel slot.

Agencies and developers need different sites

These get treated as one category and they behave nothing alike.

An agency sells a changing inventory. Its site is a system: listings arrive and leave, several agents each need attribution and their own contact route, buyers arrive through individual properties, and the value is in how quickly and cleanly stock can be added by someone who is not a developer. If adding a listing requires an email to an agency, listings will go up late or not at all, and the site will lose to whichever competitor made it easy.

A developer sells one thing, over a long time, to someone making the largest purchase of their life. There is no changing inventory — there is a single development, a set of unit types, a location argument, a construction timeline, and a decision that takes months and involves more than one family member. That site is closer to a considered brochure: floor plans that can be examined, an honest account of what is finished and what is not, and a payment-plan explanation that survives being read twice. Off-plan buying is largely a trust exercise, and everything about the page is either building that or spending it.

The enquiry differs too. In both cases the conversation almost always continues on WhatsApp, and pretending otherwise with a formal contact form adds a step everyone will route around. What the site should do is make sure the enquiry arrives with the property attached, so nobody has to ask which one — and so you can tell which listings and which areas actually generate interest.