What a Dubai brokerage website needs: listings, portal feeds, lead capture and Arabic

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: A Dubai brokerage website earns its keep by capturing enquiries you own and keeping them tied to a listing and a source, not by competing with Property Finder and Bayut (the two big property portals where most buyers browse). Before you pick a platform, decide where your listings live. If agents enter listings in your CRM (the system that holds your leads and listings), the website should read from it. If agents edit the website, the website must publish out to the portals. One source, edited once. Then check four things: enquiries reach the CRM with the listing and source attached, Arabic pages are properly written, off-plan projects have their own pages, and the site loads fast on a phone.

Ranjit Bhinge

Your site looks dated and an agency has quoted you for a rebuild. Before you sign, you want to know what the site should actually do for a brokerage, and who will keep it up to date.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

What a brokerage website is for in Dubai, and what the portals already do

Property Finder and Bayut are portals: websites where agencies pay to list properties and buyers search. They bring huge traffic. Your own site will not outrank them for generic searches, and I would not promise that to anyone. Its job is different:

  • Capture enquiries that are yours, with no per-lead portal credit attached.
  • Show your team, your track record and your areas, so a buyer who finds you elsewhere can check you out.
  • Host pages the portals do not: off-plan project pages, investor content, area guides.
  • Give you data on what visitors look at.

Measure the site by one number: how many enquiries per month reach your CRM with a listing and a source attached. Visits and "looks modern" are not the measure.

Decide the source of truth for listings first

This is the decision no agency page I reviewed makes for you, and it determines everything else. A listing exists in up to four places: your CRM or listing system, your website, Property Finder, and Bayut. If agents type it into each one, you will get sold units still live, mismatched prices and duplicated work.

  • Option A, the CRM is the source. Agents add and edit listings in the CRM. The website reads from it. The portals are fed from it. Best for a brokerage with a proper listings system.
  • Option B, the website CMS (content management system, the admin area where site content is edited) is the source. Agents edit listings in the website's admin. The website then has to publish out to the portals. This only works if your developer builds and maintains those feeds.
  • Option C, nobody decides. Everyone types everything everywhere. This is the usual case and the reason sites go stale.

Pick A or B before you pick WordPress (a widely used website platform) or anything else. I also recommend the order: fix the CRM and listing data first, build the site second. A beautiful site on messy listing data copies the mess. See property listing management software for the listing-system side.

Listings and portal feeds: what the website can and cannot do

A feed is a file or connection that sends listings from one system to another, often in XML (a plain-text data format). I can tell you what the vendors say, not what the portals publish, so treat the following as vendor claims:

  • Access is partner-gated. You cannot simply build a feed on your own; your account has to be enabled. Groovyweb, an integration vendor, says this, and says no sync interval is published.
  • Codingclave, another vendor, says Bayut's integration points are an XML listing feed and a leads connection, with the full XML documentation emailed to agencies rather than published.
  • The Property Finder and Bayut formats differ, so one feed will not validate on both.

I could not confirm these details on an official portal page. So before any agency quotes you for portal integration, ask your portal account manager or your CRM vendor what route your account supports. For the specifics, read my guides to the Property Finder API and the Bayut API.

One compliance point carries over: the Dubai Land Department (DLD, the emirate's property registry and regulator) says the advertising permit number must appear in all real estate ads. A feed that drops the permit number from a listing is a problem, whichever platform you use.

Enquiries: from the website to the CRM with listing and source kept

This is where most websites fail quietly. Check that an enquiry:

  1. Creates a record in the CRM, not only an email to a shared inbox.
  2. Carries the listing reference, so the agent knows what the buyer was looking at.
  3. Carries the source (organic, ad campaign, WhatsApp button, a particular portal link).
  4. Is assigned to an agent automatically, with a timestamp.
  5. Triggers an instant reply that confirms receipt.
  6. Does not create a duplicate if the same phone number already exists.

Ask the agency to demonstrate this live on a test enquiry before you sign. For what happens after the enquiry, see real estate lead management software and speed to lead on WhatsApp.

Search, filters and listing pages that agents can maintain

Buyers expect to filter by area, price, property type, bedrooms, ready or off-plan, and furnished or unfurnished. Each listing page needs good photos, a clear price, the permit number, the agent's name and a WhatsApp button. The test is maintenance: if updating a listing takes an agent ten minutes in a clumsy admin screen, they will not do it, and your site goes stale. Ask to see the edit screen, not just the public pages.

Off-plan project pages

Off-plan means sold before completion. Each project you market should have its own page: project facts, payment plan, floor plans, map, developer profile and a short form. These pages are also where paid ads should point. I cover the detail in the off-plan launch landing page guide. Build a reusable project-page template rather than a new design each time.

Arabic and English done properly

Most ranking guides give Arabic one line. In practice, "bilingual" involves several separate jobs:

  • Right-to-left layout. Arabic reads right to left, so the whole page mirrors: menus, forms, number alignment. A site that only swaps the text looks broken.
  • Translation quality. Machine translation of a property description or payment plan can change meaning. Have a fluent reader review it.
  • Separate pages and addresses. Each language should have its own page and web address so search engines can index both.
  • Forms and replies. The enquiry form, the confirmation and the first message should work in the visitor's language.

If you only need Arabic for a small share of listings, say so up front and price it separately. My generic guide on building a website in two languages covers the basics. For social posts in both languages, see a weekly Arabic and English content plan.

Speed, schema and the basics that affect findability

  • Speed: property sites are image-heavy, so image compression and sensible caching matter. Test on a phone on mobile data, not on your office wifi.
  • Structured data (schema): hidden labels in the page code that help search engines understand a listing, a business or an agent. Ask whether the site includes them.
  • Clean addresses and no duplicate pages: one address per listing.
  • Hosting, SSL (the padlock) and backups: ask who pays, who monitors, and how fast a restore would be.
  • Analytics: conversions tracked, not just page views.

I will not quote a percentage for mobile traffic or a claim that Google ranks fast sites higher by a set amount, because the sources I found gave none.

Template, WordPress or custom: choose by who edits listings

RouteWho edits listingsPortal feedsEnquiries to CRMCost to change later
Template platformAgents in the platform's adminUsually limited or none; askOften via simple form add-onsLow to start, limited room
WordPressAgents in WordPress, or a plug-in reads from CRMVia plug-ins or custom workDepends on plug-ins; check what is savedModerate; plug-ins need updates
Custom buildWherever you design it, ideally the CRMBuilt to your account's routeBuilt to carry listing and sourceHigher upfront; you own the logic

The right answer follows the source-of-truth decision. If the CRM is the source, a lighter website that reads from it is often enough. If you need unusual inventory logic or integrations, custom becomes sensible.

How software and AI help with listing copy, translation drafts and enquiry replies (and where people stay in charge)

  • Listing copy: AI can turn an agent's bullet points into a clean description in English and a draft in Arabic. A person must check facts such as size, view, floor and what is included, and a fluent reader must review the Arabic. Starter wording is in ChatGPT and Claude prompts for Dubai agents.
  • Enquiry replies: software can send an instant acknowledgement with the listing details and book a viewing slot. A human takes over once the buyer replies with a real question.
  • Syncing: software, not people, should move listings between CRM, site and portals, and should alert you when a feed fails, because a feed that breaks silently is the classic failure.
  • Checks: a scheduled check can flag listings sold in the CRM but still live on the site or a portal.

Try it yourself with Claude: paste an agent's rough notes for a listing and ask: "Write a 100 word property description in plain English from these notes only. Do not add any feature not in the notes. List any detail that is missing and needed for a listing." Then add the missing facts yourself.

I build the connecting pieces, such as a website that reads from a brokerage's own listing data and sends enquiries into its CRM, but that is only worth it if the simpler routes above do not fit.

What to ask an agency before you sign

  1. Where will listings be edited, and by whom?
  2. Show me a test enquiry arriving in my CRM with the listing and source.
  3. What route does my portal account support for feeds, and who confirmed it?
  4. Who owns the code, the design files and the domain?
  5. Who pays for hosting, and who monitors the feed?
  6. What happens if you stop working with us?
  7. How do Arabic pages work: layout, translation, addresses?
  8. What does a change cost after launch?

Cost: the quotes I see and what they leave out

RedSpider, a Dubai web agency, quotes three tiers on its own page: AED 6,000 to 10,000 for a basic site, AED 12,000 to 25,000 for a dynamic portal-style site, and AED 25,000 to 60,000 or more for one with a CRM connection and XML feeds. These are an agency's own quotes and the tier differences are not defined, so treat them as a rough reference only. What quotes often leave out: hosting, feed monitoring, Arabic content, changes after launch, and the portal-side work that you need your account manager for. Ask for the total over three years.

How I would approach this

I would not start with the site. I would first decide where listings live, confirm what feeds your portal accounts support, and make sure enquiries land in the CRM with listing and source. Then I would pick the lightest platform that fits who edits what. Owner view: judge it by enquiries that reach the CRM with source each month. Agent view: a listing appears once, and is edited once. If a quote does not address both, keep looking.

Questions people ask

How much does a real estate website cost in Dubai?

One agency quotes AED 6,000 to 60,000 or more across three tiers, depending on features. These are the agency's own quotes. Ask for a written, itemised quote that includes hosting, Arabic and changes after launch.

Can my website push listings to Property Finder and Bayut?

Possibly, but portal access is partner-gated and the formats differ. Ask your portal account manager or CRM vendor which route your account supports. See my Property Finder API and Bayut API guides.

WordPress or custom for a brokerage site?

Decide who edits listings first. If the CRM is the source, a lighter site that reads from it may be enough. Custom makes sense for unusual inventory logic or integrations.

Does the website need to connect to my CRM?

Yes, if you want to know which listing and source produced each enquiry. A website that only emails a shared inbox loses that information. See real estate lead management software.

Do I need Arabic pages?

If any of your buyers or landlords read Arabic, yes. It needs right-to-left layout, reviewed translation and its own page addresses, not a quick machine translation.

Who should be able to edit listings?

Agents, in one place only. Which place depends on your source-of-truth choice: the CRM or the website admin. Avoid editing in both.

Do I still need portals if I have a website?

For most brokerages, yes. The portals bring traffic your site will not. The website captures enquiries you own and supports your brand and off-plan pages.

Sources

Ready for the next step?

A 30 minute call. No pitch. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. No pitch. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…