Real estate, US
IDX website development for US brokers and real estate teams
IDX website development means building a brokerage site that shows your MLS's shared listings under your MLS's display rules, keeps them refreshed, and sends every enquiry to the right agent. We build these remotely from Noida for US brokers and teams, using your MLS's RESO Web API feed or an IDX vendor, at a fixed price per milestone.
- Brokerage site
- $1,500–4,500 indicative
- Custom IDX search
- $5,500–22,000 indicative
- Listing data
- Your MLS, via RESO Web API or vendor
- Display rules
- From your MLS, approved by your broker
Updated · By the Codebrix team
IDX, VOW or your own listings: which one you are building
Three different things get called an IDX site. NAR describes IDX as giving MLS participants the ability to authorise limited electronic display of their listings by other participants. A Virtual Office Website (VOW) is a brokerage service: under NAR's model rules, consumers can search MLS data on it only after the broker has first set up a broker-consumer relationship as defined by state law.
| IDX display | VOW | |
|---|---|---|
| Who can search | Any visitor, unless your MLS or your design adds registration | Only registered consumers in a broker-consumer relationship |
| Sign-up | Optional, a marketing choice | Name and verified email, unique login, and agreement to terms of use |
| Refresh | Downloads and displays refreshed at least every 12 hours | Refreshed at least once every 3 days |
| Typical use | Public search on a broker or team site | Deeper search for clients the brokerage already represents |
Most brokerages and teams want IDX. A client-only VOW area is scoped separately, because its registration steps change the sign-up flow.
Getting the feed: MLS approval, licence terms and the RESO Web API
Listing data belongs to the broker who participates in the MLS; we cannot apply for it. RESO says access to Web API data is gained through local MLSs and that RESO does not provide MLS data. It calls the Web API, built on OData, the modern way to move real estate data, and says the older RETS standard is deprecated.
- Your broker notifies the MLS of the intention to display IDX information. NAR's policy requires this and gives the MLS direct access to monitor the site.
- The broker signs the MLS's data licence agreement. Read it before design starts: NAR's policy, for example, lets an MLS require security protection and a consumer activity audit trail from sites storing a persistent download.
- The MLS issues Web API credentials, or approves an IDX vendor you choose.
- We build against a test feed first, then switch to production once your broker or MLS signs off the display.
| Route | Good for | Trade-off |
|---|---|---|
| IDX vendor's search embedded in your site | Fast launch, small team, one MLS | Listing pages often sit on the vendor's domain or in a frame, so less control over speed and SEO. Vendor fees are separate. |
| Custom build on the RESO Web API | Brokerages that want their own search, listing pages and data model | Takes longer, and you carry the duty to apply every display rule correctly |
Display rules we put into the templates
These come from the IDX policy in NAR's 2024 Handbook. Your MLS adopts its own version and may add rules, such as hiding expired listings or confidential fields.
- Your brokerage name in a readily visible colour and typeface on every listing.
- The listing firm and the listing participant's email or phone number in a reasonably prominent spot, in type no smaller than the median used for listing data.
- Listings sellers have withheld from internet display excluded at import, not just hidden.
- Comments, reviews or automated value estimates switched off per listing when the seller asks.
- Other brokers' listing data never edited. Extra data from other sources shown separately, with its source named next to it.
- An email address or phone number for reporting inaccurate information.
- Feeds from more than one MLS combined only where your broker holds participation rights in each.
We show you each rule working on the staging link. Whether the site meets your MLS agreement is your broker's call, not ours.
Fair Housing in listing copy, search filters and ads
The Fair Housing Act makes it unlawful to publish any notice, statement or advertisement for the sale or rental of a dwelling that indicates a preference, limitation or discrimination based on a protected characteristic (42 U.S.C. 3604(c)). HUD lists those characteristics as race, colour, national origin, religion, sex, familial status and disability. HUD's regulation (24 CFR 100.75) covers words, photographs, illustrations and symbols, and choosing media or locations for ads that deny parts of the market information about housing.
A website has many such surfaces: agent remarks, neighbourhood pages, stock photos, filters, chatbot replies and ad audiences. What we build in:
- Search filters on property attributes only: price, beds, area, school district as a boundary, features.
- A review step in the CMS for agent-written area and listing copy before it publishes.
- Any AI writing or chat feature limited to describing the property.
- Ad landing pages built so audience choices stay with your team and your counsel.
Lead routing that respects how US teams work
An IDX enquiry is only useful if it reaches an agent with context. Each one carries the MLS number, the listing address, the search the visitor saved and the page they came from, and goes to your CRM through its API.
- Registration asked for on save-search or after a few listing views, not before the first result.
- Routing by listing area, price band, language or round robin, with a fallback agent and an alert if nobody claims the lead in the time you set.
- Saved-search emails sent from your own domain.
If you also need after-hours calls answered, see our page on an AI receptionist for US businesses.
Listing SEO without thousands of thin pages
NAR's policy does not require participants to block search engines from indexing IDX listings, though your MLS may have its own rules. But the same listing appears on the portals and every other broker's IDX site, so we put the effort where you can be different:
- Neighbourhood and building pages your agents actually write, with the live listings for that area underneath.
- Sold or withdrawn listing pages that redirect to the area page instead of piling up as dead URLs.
- Fast image delivery for listing photos, the usual cause of slow property pages. Our Core Web Vitals guide explains what is measured.
We do not promise rankings. The local side of search is covered on our local SEO for US businesses page.
Price, timeline and what we need from you
| Build | Indicative range | Timeline |
|---|---|---|
| Brokerage or team site with an IDX vendor's search embedded | Marketing website range, $1,500–4,500 | 2–6 weeks plus MLS approval time |
| Custom IDX search on the RESO Web API, listing pages, saved searches, CRM routing | Web application range, $5,500–22,000 | 6–16 weeks plus MLS approval time |
From you: the broker's MLS participation, the signed data licence or vendor account, your MLS's display rules, CRM access and agent routing rules. Your MLS sets the approval timeline, so design work runs while you wait. Our general real estate website development page covers non-US property sites, and our offshore development overview for US businesses covers working across time zones.
Frequently asked questions
What is the difference between IDX and VOW?
IDX lets MLS participants display each other's listings to the public under the MLS's rules. A VOW is a brokerage tool where, under NAR's model rules, consumers search MLS data only after registering and entering a broker-consumer relationship defined by state law, including verified email, their own login and agreement to terms of use. Most broker and team sites need IDX; a VOW is an added client area.
Can an offshore developer get MLS data for us?
No. Access comes from your local MLS to the broker who participates in it. RESO states that it does not provide MLS data itself. Your broker applies, signs the data licence, and gives us credentials or a test feed. If your MLS's agreement asks the developer to sign anything, we review it with you before work starts.
How often do IDX listings have to refresh?
NAR's IDX policy in its 2024 Handbook requires participants to refresh MLS downloads and the displays they feed at least every 12 hours. Its model VOW rules require at least once every three days. Your MLS may set its own schedule. We schedule syncs more often than the minimum where the MLS allows, and sold or withdrawn listings drop off on the next sync.
Should we use an IDX plugin or a custom build?
A vendor's search is quicker and cheaper to launch, and fine if your edge is your agents rather than the website. A custom build on the RESO Web API gives you your own listing pages, speed and design, but you take on applying every display rule. Starting with a vendor and moving to custom later is common.
How do you handle Fair Housing on the website?
We keep search filters to property attributes, add a review step for agent-written copy in the CMS, limit any AI features to describing properties, and leave ad audience choices with your team. The Fair Housing Act and HUD's rules cover words, photos and where ads are placed. Your counsel or compliance lead reviews the copy; we build the guardrails.
What does IDX website development cost with Codebrix?
Indicatively, a brokerage site with an IDX vendor's search embedded falls in our marketing website range of $1,500 to $4,500, and a custom search built on the RESO Web API falls in our web application range of $5,500 to $22,000. Vendor and MLS fees are separate. The fixed quote follows a discovery call.
Sources
- RESO: Web API
- NAR: Internet Data Exchange (IDX) policy
- NAR: Handbook on Multiple Listing Policy, 2024 (IDX policy and model VOW rules)
- NAR: Virtual Office Websites policy
- 42 U.S.C. 3604 (Cornell LII)
- 24 CFR 100.75: Discriminatory advertisements, statements and notices (Cornell LII)
- HUD: Housing Discrimination Under the Fair Housing Act
Related
United States
An offshore web development company in India for US businesses
Offshore web development company in India for US businesses: USD pricing, Stripe or wire payment, IP assigned to you, and a planned ET and PT overlap.
Read moreReal estate
Real estate website development for developers, brokers and agencies
Real estate website development with listings, portal and MLS feeds, CRM lead routing, WhatsApp and RERA number display. Fixed price per milestone.
Read moreWeb applications
Custom web application development for portals, dashboards and internal tools
Custom web application development for portals, dashboards and internal tools: roles, Postgres, integrations and tests. Fixed price, code in your name.
Read moreLocal SEO
Local SEO for US small businesses: profile, reviews, pages and schema
Local SEO services for US small businesses: a Google Business Profile built to Google's rules, honest review requests, real location pages and schema.
Read moreNext.js development
Next.js development for sites and products that have to load fast and rank
Next.js development company in Noida building fast App Router sites and apps with server components, ISR and SEO built in. Fixed price, weekly demos.
Read morePerformance guide
How to improve Core Web Vitals: practical fixes for LCP, INP and CLS
How to improve Core Web Vitals: LCP, INP and CLS thresholds, field vs lab data, a fix table for each metric and Next.js-specific changes that help.
Read more