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.
MLS approval is the long pole, not the build
The embed itself is an afternoon. What takes weeks is your MLS approving the feed, and every board runs its own process, its own paperwork and its own display rules about what you may show and how attribution must appear. 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 faster. Start the application on day one and build the rest of the site while it moves.
What Webflow stopped doing in January 2026
Webflow sunset User Accounts on 29 January 2026, and any site still relying on it lost the feature and the account data with it. For a real estate site this matters specifically, because saved searches, favourited listings and property alerts are exactly the sort of thing people used to build on it. Those now belong in the IDX provider, which usually has its own account system built for precisely this, or in a third-party tool such as Memberstack or Outseta. If you are reading an older tutorial that tells you to use Webflow Memberships for this, it is out of date.
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.
The listings are not the pages you rank
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, not an SEO asset. 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.
The provider owns the listings. You own the neighbourhood. Only one of those is still working for you next year.
