Real estate website development for Dutch makelaars and expat rental agencies: listings in automatically, valuation leads out

What should a makelaar website do in the Netherlands?

It should do three things well: show your current listings accurately without manual work, persuade homeowners to ask you for a valuation, and help buyers and tenants book a viewing. Everything else, from team pages to blog posts, supports those three jobs.

Most Dutch house hunters start on the big portals, so your website is rarely where people first see a home. It is where they go to check who you are, look at the rest of your stock, and decide whether to contact you. Sellers behave differently: a homeowner thinking about selling searches for a makelaar in their town, compares a few office websites and requests a valuation from one or two. That second journey is where real estate website development pays back.

A good site therefore answers the seller's questions directly: what you charge in principle, how you work, what you sold recently in their area, and how quickly they can get a waardebepaling. It gives buyers and tenants a clean way to browse and ask for viewings. And it runs itself, because listings flow in from your CRM rather than being typed twice.

• For sellers: valuation funnel, process explanation, fees in principle, reviews you collect yourself, recent sales.
• For buyers and tenants: current listings, search, map, viewing requests, alerts for new homes.
• For internationals: English listings and guides to renting or buying in the Netherlands.
• For your office: automatic sync, leads routed to the right colleague, no manual updates.

Your CRM vendor's website or custom real estate website development?

Stay with your CRM vendor's website when a standard template does the job; commission custom real estate website development when your office needs to stand out, run English content, rank for local searches or offer search features the template lacks.

Both major Dutch CRMs for estate agents offer websites of their own. Kolibri, for example, sells websites integrated with its CRM. These are sensible for many offices: the listings sync without effort and the vendor handles updates. The trade-off is that many offices using the same vendor end up with similar sites, and changes happen on the vendor's schedule.

A custom site makes sense when your brand, your expat focus or your local SEO ambitions matter. The CRM stays your system for listings and relations; the website reads from it and sends leads back. If you ever change CRM, only the feed layer needs rebuilding, not the whole site.

Pulling listings automatically from Realworks

Realworks offers a set of APIs that a developer chosen by the makelaar can use, with the makelaar deciding what data is released. For a website, the Wonen API is usually the core: it exports residential listings and can take leads and search requests back into the CRM.

Realworks' own API page describes the process. A developer selected by the broker registers on the Realworks developer portal and receives a developer ID. The broker then buys the API in the Realworks CRM Marketplace, after which the developer can make the connection. Realworks notes that brokers can release data at different levels per API, so you control what the website can see. Besides Wonen, Realworks lists APIs for business property, new-build projects, relations and agenda data, among others.

On our side, the feed is built to be dull and dependable. New and changed listings are fetched on a schedule, photos are resized into fast web formats, and sold or withdrawn homes change status on the site automatically. Every sync is logged; if the connection fails, you get an alert rather than a website quietly showing last week's stock.

• Koop, huur and nieuwbouw listings with photos, floor plans, features and status.
• Viewing and valuation requests written back into Realworks as leads, where the API allows.
• Sold and rented homes kept or hidden according to your policy.
• Sync log and alerts visible to your office.

Any Realworks fee for API access is between you and Realworks. For general CRM connections, see website CRM integration.

Kolibri and other makelaar CRMs: feeds, exports and APIs

If your office uses Kolibri or another CRM, the first step is asking the vendor which data export or API options your subscription includes. The answer decides whether the site reads a live API, a scheduled XML or JSON feed, or a file export.

We work with whichever route the vendor supports and document it. A live API gives the freshest data and the easiest lead write-back. A scheduled feed works well for listings, with leads sent by email or through a separate form integration. A file export is the fallback when nothing else is available, and still beats typing listings in by hand.

Whatever the source, the website stores listings in its own database, mapped to a consistent structure: address, price, type, rooms, surface, energy label, status, media. That separation matters. If you ever switch CRM, only the mapping changes; your pages, search and URLs stay the same, and so do your Google rankings.

If the vendor's own website product already covers what you need, we will tell you so before quoting anything.

Funda-style search, filters and map views on your own site

Visitors expect the search patterns they know from the big portals: filters for price, type, rooms, surface and status, a list and map toggle, and results that update without reloading. Built properly, that works fast even on a mid-range phone.

The filters follow your stock. An Amsterdam rental agency needs furnished or unfurnished, available-from date and maximum rent; a makelaar in Brabant selling family homes needs plot size, garden orientation and energy label. We build the filter set you actually use, rather than a generic one.

Maps need care. Loading hundreds of pins at once slows everything, so pins cluster when zoomed out and details load when a pin is tapped. Map tiles come from a provider you choose, with its own terms and cookie implications, which your consent banner then reflects.

• Shareable URLs for every search, so a filtered result can be sent by WhatsApp.
• Clean, indexable pages per listing and per area, with filtered combinations kept out of the index.
• Saved searches with email alerts, only after explicit opt-in.
• Fast photos in modern formats, sized per device.

We build an interface in the style visitors know; we do not copy any portal's design or data.

Waardebepaling lead forms that homeowners actually finish

A good valuation form is short, stepwise and honest: address first, then a few questions about the home, then contact details, with a clear promise of what happens next. Long single-page forms asking for everything up front lose most of the people who start them.

The first step asks for postcode and house number and fills in the street and town, which feels effortless. The next step asks for type of home, rough size, and when the owner is thinking of selling. Only then come name, email and phone number, plus a free-text field for anything else. The confirmation page says exactly what follows: “a colleague will call you within one working day to plan a visit”, or whatever your office really does.

Be careful with instant online valuations. An automated figure can attract clicks, but a wrong one damages trust and your office's reputation. If you want an indicative range, make clear it is indicative and that the real valuation follows a visit. Many offices prefer no figure at all, only a quick personal response.

• Postcode and house number first; the rest filled in from address data where available.
• Three to five questions about the property and timing.
• Consent text for follow-up, separate from any newsletter opt-in.
• Lead sent to your CRM, with a copy to the right branch or colleague.

Forms and follow-up automation can be combined with AI lead summaries; see AI lead qualification.

English pages for expat tenants and international buyers

If you let or sell to internationals, your English pages are as important as your Dutch ones. Expats moving to Amsterdam, The Hague, Utrecht or Eindhoven search in English, often before they arrive, and choose agencies whose websites explain the process clearly.

This is where a team that writes in English is an advantage rather than a compromise. We write the English content: how renting works in the Netherlands in general terms, what documents tenants are usually asked for, what furnished and upholstered mean in Dutch rental listings, how viewings are arranged remotely, and what happens after an offer. Your office checks every factual and legal point, since practice differs between offices and rules change.

Technically, the English pages sit under their own path with hreflang tags linking Dutch and English versions, so Google shows the right language to each searcher. Listings show English labels for every feature, driven by the same data as the Dutch pages. The Dutch copy itself is supplied or approved by your office.

For rental rules on tenant selection and fair treatment, such as the Good Landlordship Act, rely on your own lawyer or branch association. Our international SEO page covers multilingual set-ups in more depth.

AVG-compliant viewing requests and lead handling

Collect only what you need for the step you are at, keep it only as long as you need it, and be open about both. For a viewing request, that usually means name, contact details, the listing and a preferred time, not income statements or copies of passports.

Rental agencies are often tempted to collect everything at once: employer, income, household size, ID. Under the AVG that is hard to justify at the viewing-request stage, and it creates a pile of sensitive data to protect. Ask for documents later, only from serious candidates, through a secure channel rather than a website form or email attachment.

The Dutch government's explanation of the cookie rules is also relevant: tracking cookies need permission, while functional cookies and analytics with little privacy impact do not. The build keeps marketing pixels and tracking off until visitors agree, and the consent banner lists map and video providers honestly.

• Minimal fields per form, with purpose explained next to the submit button.
• Leads stored in your CRM or mailbox, not in a forgotten plugin table.
• Automatic deletion of old leads after the period you set.
• Separate opt-in for search alerts and newsletters.
• A privacy statement that matches what the forms really collect; your adviser signs it off.

Local SEO for makelaars: ranking for makelaar plus your town

Sellers search for a makelaar in their town or district, so your website needs a clear page for each area you work in, a complete Google Business Profile per office, and consistent office details everywhere. Nobody can guarantee a ranking, but offices without these basics rarely appear.

Area pages must be genuinely useful: what homes typically look like there, which streets and neighbourhoods you know, what buyers ask about, and links to your current listings in that area. Written with your local knowledge, they give Google and AI assistants something specific to cite. Templated pages that swap only the town name do the opposite.

On the technical side, listing pages get structured data, fast loading and clean URLs; sold listings are handled consistently so Google does not find hundreds of dead pages; and each office page carries structured data for the business. Answers to common seller questions, written plainly, help your site appear in AI overviews and assistant answers too.

An SEO-led site with area pages starts from US$300, and ongoing SEO from US$150/mo. See real estate SEO and the sibling page on technical SEO for Dutch sites.

How much does real estate website development cost in the Netherlands?

With BtechWaleTech, an office website starts from US$150, an SEO site with many area and expat pages from US$300, and a listing feed with custom search from US$900. Dutch web bureaus and CRM vendors price very differently, often combining a build fee with a subscription, so compare the total over a few years rather than the first invoice.

These factors move a real estate website quote most:

• The CRM connection: a documented API is quicker than a file export; lead write-back adds work.
• Search features: map view, saved searches and alerts each add development and testing.
• Listing types: sale, rental, new-build projects and commercial property each have their own fields.
• Languages: English pages are straightforward; further languages need copy you supply.
• Area pages: the number of neighbourhood and service pages you want to rank.
• Branches: multiple offices mean routing leads and separate local pages.

Running costs are hosting, your domain, any CRM API fee and optional care from US$120/mo after the two free months. The pricing page lists all starting prices.

How long does a makelaar website take to build?

An office website takes 1–2 weeks, an SEO site with area pages 3–5 weeks, and a site with a live listing feed and custom search 6–12 weeks. CRM access is usually the step that takes longest to arrange, so it starts in week one.

For a feed-driven site, the sequence runs like this. First, you request API access or an export from your CRM vendor and confirm which data may be released. Meanwhile, page designs and the search layout are agreed. Then the feed is connected and tested with your real listings, search and forms are built on top, and English and Dutch content goes in. Finally, redirects from your old site are mapped so existing Google rankings carry over.

• Week 1: kick-off, CRM access requested, sitemap and page designs.
• Weeks 2–5: feed connected, listing pages and search built.
• Weeks 5–8: forms, alerts, English pages, area pages.
• Final weeks: redirects, speed checks, consent banner, launch.

How to choose a developer for a real estate website

Choose the developer who asks about your CRM, your sellers and your stock before talking about design. Pretty templates are easy to find; reliable feeds and forms that turn into appointments are not.

More general questions are in questions to ask a developer.

Working with a remote real estate website team from the Netherlands

It runs on short video calls during your working day and messages in between. Estate agents are busy with viewings, so we keep calls brief and send decisions in writing.

We never visit your office or properties; photos, floor plans and descriptions come from your CRM and your team.

Domain, hosting, API access and content: keep them in your office's name

Your domain, hosting, website code, CRM API access and content should all belong to your office. That protects you if you change developer, and it keeps your Google rankings tied to an address you control.

In practice, the domain is registered to your business, hosting runs on your account, and the CRM API connection is purchased and approved by you, with our developer ID or credentials revocable at any time. The code lives in a repository you own, and copyright in the work written for you transfers in writing as set out in the quote; have your lawyer check the wording.

Content is yours too: area pages, English guides and team texts. We keep a simple guide for editing pages, adding team members and checking the feed log, so your office staff can handle day-to-day changes without us.

Common mistakes in real estate website projects

The costly mistakes are rarely about design. They are about stale data, lost leads and lost rankings.

• Listings copied by hand, so sold homes stay online and new ones appear days late.
• A relaunch without redirects, wiping out years of Google visibility for area and listing pages.
• Valuation forms that email a shared inbox nobody owns.
• Heavy map scripts that make the search page crawl on phones.
• Collecting income and ID documents through web forms.
• English pages produced by raw machine translation.
• Domain or hosting registered to the developer.

If your current site was left unfinished by a previous developer, see developer left a project midway. For a site losing traffic after a relaunch, traffic drop after migration explains the recovery steps.

Worked example: a hypothetical Eindhoven makelaar serving expats

Say a makelaar with offices in Eindhoven and Veldhoven sells family homes and handles rentals for international employees of technology companies in the region. Listings live in Realworks, the current website is a template, and English speakers make up a large share of rental enquiries.

A sensible build would connect the Realworks Wonen API after the office purchases and approves access, so koop and huur listings sync automatically. Search would offer rental-specific filters in English and Dutch, and a map with clustered pins. Separate funnels would handle valuation requests from local homeowners and viewing requests from internationals, each routed to the right team.

English guides would explain renting in the region and remote viewings, checked by the office for accuracy, with Dutch area pages for Eindhoven districts and Veldhoven. The office website part would start from US$150, the SEO area pages from US$300, and the feed and search from US$900, spread over about ten weeks.

The scenario is fictional and only illustrates scope; it is not a client project or a forecast of results.

Checklist before commissioning real estate website development

Have these answers ready and every quote you receive will be easier to compare.

• Which CRM do you use, and which API or export options does your subscription include?
• Which listing types must appear: sale, rental, new-build, commercial?
• Which filters do your buyers and tenants actually use?
• Do you want a map view, saved searches and alerts?
• How should sold and rented listings be handled?
• Which lead forms do you need, and where should each lead go?
• Will you serve expats or international buyers in English?
• Which towns and neighbourhoods should have their own pages?
• Who writes or approves Dutch copy?
• Is the domain and hosting in your office's name?
• What happens to your old site's URLs?

Send your answers or a link to your current site and you will receive an itemised quote in about two working days. The Netherlands overview lists our other services.