IDX for Brokerages: When You Need It, and When It Hurts You

Most brokerages treat IDX as a given: you get a website, you bolt on a search box, buyers browse the MLS on your domain. It is presented as the baseline rather than as a decision, which is how firms end up paying for infrastructure that actively works against the thing they are trying to rank for.

IDX is genuinely right for some brokerages and genuinely wrong for others, and the split is not about size. It is about where your business actually comes from.

What you are actually buying

IDX is permission plus plumbing. The permission comes from your MLS and governs what you may display, how you must attribute it, how often you must refresh it, and which listings you must exclude when a seller has opted out. The plumbing is the integration that pulls the feed and renders it on your domain.

Those two halves are worth separating in your head, because the permission half is contractual and non-negotiable while the plumbing half has real choices in it. The same MLS data can arrive as a hosted widget on a subdomain you do not control, as an embedded frame, or as a proper server-side integration that renders as pages on your own domain. Those three produce completely different SEO outcomes from identical data.

The duplicate-content problem nobody mentions

A full IDX integration can add thousands of URLs to your site overnight. Nearly every one of them describes a property using the same remarks, the same photographs and the same specifications as the identical page on every other IDX site in your MLS.

From a search engine's perspective, you have just published a very large quantity of content that exists verbatim in hundreds of other places. That is not a penalty in the punitive sense, it is simply that none of those pages has a reason to be the one that ranks, and collectively they change what your site looks like it is for.

The practical damage shows up as crawl allocation. A site with sixty thousand syndicated listing URLs and eleven genuinely useful pages spends its crawl budget on the sixty thousand. We measured a version of this on our own site with a programmatic page set: 35% of indexed pages producing under 3% of clicks. We deleted it.

The three configurations, honestly

Full IDX search, indexed

Every listing in the feed rendered as an indexable page. Right for a buyer-side operation whose acquisition model is people browsing inventory and registering to save searches. The registration gate is the product, and the volume of pages is the point.

Wrong for almost everyone else, because you are competing on breadth against portals that have more of it and spend more to keep it.

Full IDX search, not indexed

The search experience exists for visitors who want it, but the syndicated listing pages are kept out of the index. Your own listings stay indexed and are treated as content: written properly, photographed properly, marked up properly.

This is the configuration most brokerages should be running and almost none are. It keeps the utility and removes the dilution.

Curated, no IDX

Your listings, your sold work, and editorial pages about the communities you sell in. No feed at all. Right for listing-side firms, luxury specialists, and any brokerage whose business comes from reputation and referral rather than from strangers browsing.

Counter-intuitively this often ranks better, because every page on the site is unique and about a place you actually know, and Google indexes the depth of that rather than the breadth of a feed.

What it costs, in the parts that are not the invoice

Vendor pricing varies too much to be worth quoting, and it is the smaller half of the cost anyway. The parts that surprise people:

• MLS fees are separate from vendor fees, and some markets charge per feed as well as per seat.
• Per-agent pricing scales against you. A model priced per seat gets more expensive precisely as you grow, which is worth modelling at your three-year headcount rather than today's.
• Performance is a recurring cost. Most hosted IDX widgets load a large amount of third-party JavaScript, and that shows up in every Core Web Vitals measurement of every page it appears on, forever.
• Migration is the real lock-in. If your listing URLs live on a vendor subdomain, whatever ranking they have accrued is theirs, not yours. Ask where the URLs live before you ask what it costs.

How to decide in one sitting

Pull your analytics and answer three questions. What share of your closed business last year originated from someone browsing listings on your own site, as opposed to referral, sphere, or your Google profile? Of your indexed pages, how many are syndicated? And if you removed the search box tomorrow, what would actually break?

Most listing-side firms discover the honest answers are: almost none, most of them, and nothing. That is a curated site with a strong Google profile, not an IDX build.

IDX for brokerages FAQ

Do real estate websites need IDX to rank well?

No. A brokerage running curated listings, strong editorial neighborhood pages and hyperlocal SEO often ranks better than an IDX-heavy site, because Google indexes the depth of neighborhood content rather than the breadth of an MLS feed. IDX is essential where the acquisition model is buyers browsing every listing and registering to save searches. Firms with a curated book of business frequently convert better without a search box.

Should IDX listing pages be indexed?

Usually not for syndicated listings. Those pages describe a property using the same remarks and photographs as the identical page on every other IDX site in the MLS, so none of them has a reason to be the one that ranks, and collectively they consume crawl budget. Your own listings are the exception and should be indexed, written and marked up as real content.

What is the most important question to ask an IDX vendor?

Where the listing URLs live. If they sit on a vendor subdomain, whatever ranking they accrue belongs to the vendor rather than to your brokerage, and you cannot take it with you. Ask that before asking what it costs, because it determines whether the spend is an investment or a rental.

Does IDX slow a brokerage website down?

Most hosted IDX widgets load a substantial amount of third-party JavaScript, and it affects Core Web Vitals on every page the widget appears on, not only the search page. A server-side integration that renders listings as pages on your own domain avoids most of it, which is one of the practical differences between the integration types.