Putting MLS listings on a Webflow site with IDX
Webflow has no MLS connection of its own. Here is what links the two, what MLS approval costs you in time, and which pages are worth optimising.
Every agent who moves to Webflow asks the same question in the first call: can it show my listings. The short answer is yes, and the useful answer is that Webflow itself has nothing to do with it. There is no MLS connector in Site Settings and no listings toggle. What makes an IDX site work is a third-party provider that holds the MLS relationship on your behalf, and the build is designed around whichever one you pick.
Pick the provider before you design the site
iHomeFinder, IDX Broker and Add On IDX are the three that come up most often for Webflow builds. They differ in how much of the search experience you can restyle, how the lead capture behaves, and which CRMs they hand leads to. That last one matters more than the styling, because the site exists to produce enquiries and the provider decides where those enquiries land.
How long does IDX and MLS approval take?
Weeks, and it is the MLS approval that takes them rather than the build. The embed itself is an afternoon. Every board runs its own process, its own paperwork and its own display rules about what you may show and how attribution must appear, so the timeline is set by whichever board you are applying to and not by your developer. Most boards have moved to the RESO Web API rather than the older RETS feed, which is better for everyone, but it does not make the approval any faster. Start the application on day one and build the rest of the site while it moves, because the alternative is a finished site waiting on a form.
What replaced Webflow User Accounts for saved searches?
Saved searches and property alerts now belong to the IDX provider, because Webflow disabled User Accounts on all sites on 29 January 2026. Webflow's own guidance points at membership platforms, which is right for most sites and wrong for this one. A membership tool can hold the login, but a saved search is a query that has to be re-run against a live listing feed and compared with the previous result, and a tool with no access to that feed cannot do it. The account layer records who wants the alert. The provider is what actually sends it.
How it looked on a real build
On the Erin Tunney site we ran iHomeFinder for search and left everything editorial in the Webflow CMS. The split matters: the provider owns the listing data, which changes constantly and is not ours to hold, while the neighbourhood guides, the case studies and the short-term rental content are collections we control and can restructure whenever the positioning moves. Trying to force listing data into the CMS is the mistake that makes these projects expensive.
Do IDX listing pages rank in Google?
Essentially not, and this is the part agents are usually not told. Individual listing pages are served from the provider, are near-identical to the same listing on every other agent site in the market, and disappear the moment the property sells. They are a service to visitors rather than an SEO asset, which means a site built around them is building on rented ground. The pages worth optimising are the ones only you can write: the neighbourhood guides, the buyer and seller explainers, the local market notes. Those keep earning after the listing is gone, and that difference is the whole argument.
The provider owns the listings. You own the neighbourhood. Only one of those is still working for you next year.
