Guides / How to build

How to Build a Real Estate Listing Website

Plan and build a property listing website: the data each listing needs, search and filters, photo uploads, enquiry forms, an admin area and going live.

Mythex Team · 2026-09-29 · 7 min read

A real estate listing website is a database of properties with a public face: a page for every listing, a search with filters, and a way for buyers or renters to ask about a property. Behind it sits a private admin area where the agent adds, edits and marks listings as sold. You can build a solid version with an AI app builder in a few sessions, as long as you design the listing data first and keep the first version small.

Who the site is for, and what it has to do

Before thinking about features, be clear about which kind of site you are building. They look similar but need different things.

This guide focuses on the first three. A portal with many listers is a two-sided marketplace, which is a different problem; see how to build a marketplace and how to build a directory website if that is what you have in mind.

The data each listing needs

Listing data is the heart of the site. Get the fields right and the search, the cards and the detail pages follow. A practical starting set:

• Basics: title, status (available, under offer, sold/let), listing type (sale or rent), price and price qualifier ("guide price", "per month").
• Location: address, area or neighbourhood, and coordinates if you want a map. Decide whether the full address is public; many agents show only the street or area.
• Size and layout: bedrooms, bathrooms, floor area (and the unit — square feet or square metres), property type.
• Description: a summary for cards and a longer description for the detail page.
• Features: a list such as parking, garden, balcony, pets allowed. Store these as tags so they can become filters.
• Media: photos in a fixed order, a cover photo, and optionally a floor plan or brochure PDF.
• Admin fields: date listed, date updated, and which agent owns it.

Enquiries are a second table: name, email, phone, message, which listing, and when. If you plan viewings, a third table holds requested times.

Decisions worth making early

• Currency and units. Pick one currency and one area unit, and say so in your first prompt. Changing later means touching every listing.
• Sold listings. Hide them, or keep them with a "Sold" badge as proof of activity? Either is fine; decide before you build the search.
• Rent vs sale. If you do both, make it a field and a top-level filter, not two separate sites.

Search and filters people actually use

Most visitors arrive with three questions: where, how much, how big. Build those first:

1. Location — a dropdown of areas you cover works better than free text for a small agency.
2. Price range — minimum and maximum.
3. Bedrooms — a minimum.
4. Sale or rent, if you do both.

Then add sorting (newest, price low to high, price high to low) and, if you have enough listings to justify it, feature filters from your tags. A map view is attractive but not essential for a first version; a static map on each detail page often does the job.

Put the filters in the URL (for example /properties?area=north&minBeds=2), so a visitor can share or bookmark a search and the back button works. Ask for this explicitly — it is easy to get wrong otherwise.

Photos: the part that makes or breaks it

Property sites live on photos, so plan for them:

• Upload, don't paste links. The admin should upload photos directly. On Mythex, uploads go to the project's file storage, which is enabled when the app needs it.
• Order and cover. Let the agent drag photos into order and pick the cover image.
• Size. Large originals slow the site on phones. Ask for images to be resized or served at sensible sizes, and use lazy loading on the gallery.
• Alt text. A short description per photo helps accessibility and search.

The enquiry flow

The point of the site is the enquiry. Keep it short: name, email, phone (optional), message pre-filled with the property title. On submit:

• Save it to the database, linked to the listing.
• Notify the agent by email. That needs an email provider such as Resend or Postmark; see sending email from your app.
• Show a clear confirmation, and optionally send the enquirer a copy.

If you want visitors to request viewing times, treat it as a small booking feature: available slots per listing, a request, and agent confirmation. The booking app guide covers the slot logic.

The admin area and permissions

The admin area is where the site earns its keep. It needs:

• A login, so only agents can reach it.
• A listings table with status, price and date, and quick actions (edit, mark sold, hide).
• A listing form with photo upload.
• An enquiries inbox, filterable by listing, with a "handled" flag.

Keep permissions simple: in a small agency, every agent can edit every listing. If you need "agents only edit their own", say so in the prompt and test it by logging in as two different agents.

If your enquiries turn into a real sales pipeline — follow-ups, stages, notes — that is a CRM. Start with the inbox and read how to build a CRM when you outgrow it.

A first prompt that works

Build a property listing website for a small estate agency in two neighbourhoods, North Park and Riverside. Public pages: a home page with featured listings, a search page with filters for area, sale or rent, price range and minimum bedrooms (filters kept in the URL), and a detail page per property with a photo gallery, price, bedrooms, bathrooms, floor area in square metres, features, description and an enquiry form. Agents log in to an admin area to add and edit listings, upload and reorder photos, mark a listing under offer or sold, and see enquiries per listing. Save everything in a database. Prices in GBP. Clean, calm design that works well on phones.

It names the users, the pages, the fields, the filters and who can do what — and nothing about code.

Build steps

1. Start with the public pages on sample data. Let the builder create ten realistic sample listings so you can judge the cards, search and detail page.
2. Add the database and admin. Move listings into the database, then add login and the admin screens. Add a listing yourself, end to end.
3. Add photo upload. Upload a real set of photos, reorder them, set a cover, check the gallery on a phone.
4. Wire up enquiries. Submit one, confirm it lands in the inbox and the agent email arrives.
5. SEO basics. Each listing needs a unique title and description, readable URLs (/properties/3-bed-house-riverside) and share images. Our SEO guide for AI-built websites explains why this matters more for listing pages than most.
6. Test permissions. Log out and try to open admin URLs directly. They should redirect to login.
7. Publish and connect your domain. Agencies should use their own domain rather than a builder subdomain.

Common mistakes

• Putting listings in the code. It works for a week, then the agent needs a developer to change a price. Use a database from the start.
• Forgetting the sold state. Visitors enquiring about sold properties waste everyone's time. Make status prominent and filterable.
• Heavy photos. A gallery of full-resolution camera images is slow on mobile data. Resize them.
• No indexable content. A site that loads every listing with JavaScript and has no per-listing titles is hard for search engines to understand. For listing sites, SEO is most of your free traffic.
• Showing the exact address by default. Decide deliberately, especially for rentals and occupied homes.
• Not checking listing rules. Some countries have rules about what a property advert must include, such as energy ratings or material information. Check what applies to you.

Costs and tools

For a small agency the running pieces are:

When a ready-made product is the better choice

Build your own when you want control over the design, your own search experience, and listings that are yours rather than rented space on a portal. Choose something ready-made when:

• Your listings must come from an MLS or a portal feed — the feed provider usually has approved website products and rules you must follow.
• You mainly need exposure. Portals bring buyers; your own site mostly converts people who already know your name.
• You need a full agency back office (tenancies, compliance, accounting). Dedicated agency software covers that and is hard to replicate well.

Many agencies do both: list on the portals for reach, and keep their own site for their brand and direct enquiries.

Building it with Mythex

Mythex fits this project well: describe the site in chat, see it running in a live preview (including a phone-size frame), and it adds a database for listings and enquiries and file storage for photos when the app needs them. Publish to a mythex.ai address on any plan, or to your own domain on Pro. For a head start, see the AI real estate website builder or browse website templates.