IDX vs MLS: The Database, the Feed, and the SEO Surface They Govern

The MLS and IDX distinction is the load-bearing technical fact in real estate SEO. Most agent sites lose ranking signal not because the SEO program is weak but because the IDX implementation is structurally incapable of accruing topical relevance to the host domain. Once the distinction is clear, the consequences for canonical strategy, schema deployment, and competitive positioning follow directly.

What the MLS Actually Is

A Multiple Listing Service is a regional database, owned and operated by a local or regional association of real estate brokers, that pools active property listings into a single source of truth. The U.S. has roughly 529 MLSs as of 2026, actively consolidating into mega-MLSs like CRMLS and Bright MLS. Each MLS sets its own membership terms, sets its own listing-display rules under NAR’s baseline IDX policy, and runs its own data layer.

Membership is restricted to licensed real estate professionals who pay association dues plus per-MLS access fees. The MLS itself is rarely consumer-facing. A small number of MLSs publish a consumer portal, but the dominant pattern is that the MLS database feeds third parties, who then expose the listings publicly.

New York City is the canonical anomaly. Most NYC residential brokerage runs through the Real Estate Board of New York’s RLS database rather than a traditional NAR-affiliated MLS, which produces a structurally different SEO landscape dominated by Zillow-owned StreetEasy. Plan for the exception explicitly when the geography includes NYC.

What IDX Actually Is

IDX stands for Internet Data Exchange. It is the policy framework, established by NAR in the late 1990s and expanded by a 2008 DOJ antitrust settlement, that permits brokers to syndicate MLS listing data to public-facing websites. The 2008 settlement specifically forced NAR to allow internet-only brokerages access to MLS data, which is why every modern brokerage site can carry inventory.

In practice, IDX is consumed through a vendor. The vendor establishes a data feed from the local MLS (historically via the Real Estate Transaction Standard, now via the RESO Web API), normalizes the field names, and delivers the listing payload to the brokerage or agent site. The site renders the listings publicly so consumers can search and inquire without bouncing to a directory.

The distinction matters at the SEO level because IDX is policy plus implementation. It is not a database. The database is the MLS. IDX is the rules and the plumbing that move the data from the MLS to the public-facing site.

The Duplicate Content Surface

When a listing posts to the MLS, the exact same text, image array, and property data syndicate to Zillow, Realtor.com, Redfin, the listing brokerage’s site, and every IDX-enabled agent site in the MLS coverage area. This is structurally mandated by the IDX framework. Every site in the canonical cluster carries the same listing content.

Google’s canonical algorithm evaluates the cluster using standard web signals: the rel="canonical" tag, internal linking structure, sitemap inclusion, and domain authority. It does not parse the IDX-mandated MLS attribution text to identify the original source. An individual agent’s IDX plugin will typically generate a self-referential canonical tag on each listing page. Google treats the canonical tag as a hint. It is not a directive.

Because directories like Zillow and Realtor.com possess vastly superior internal linking architectures, faster sitemap ingestion, and higher PageRank, Google routinely overrides the agent’s self-referential canonical and folds the listing page into the directory’s canonical cluster. The agent’s page gets effectively neutralized in the SERPs for property-specific queries. Individual agent sites cannot win the canonical cluster for duplicate listing text against Zillow at scale.

The SEO value extraction therefore shifts from winning the canonical to maximizing the structured data layer. The RESO Web API migration standardized field names across local MLSs, allowing for granular schema markup (price, bedrooms, bathrooms, square footage, listing date, status) that Google uses to determine eligibility for real-estate-specific rich results. Schema completeness is what an agent site can win even when canonical authority is unwinnable.

Iframe IDX vs Truly Embedded IDX

The rendering pattern on the IDX feed is the single largest determinant of whether a site can extract SEO value from its listing inventory at all. Two patterns dominate.

Iframe IDX puts the listing search results and the listing detail content inside an HTML iframe element on the agent’s page, sourced from a vendor subdomain (search.idxbroker.com, idx.brokerage.com routed through vendor DNS, or similar). The agent’s page wraps the iframe with header, footer, and minor surrounding content. Googlebot parses the iframe content as belonging to the vendor’s domain. The agent’s host page reads as a thin frame around vendor content, with no listing text, no listing image array, and no RealEstateListing schema accruing to the agent’s entity. The topical-authority surface for that site is effectively zero on the listing inventory.

Truly embedded IDX pulls the listing payload from the RESO Web API into the agent’s server-side or static-site build, then renders the listing as native HTML on the agent’s domain. View-source on a listing detail page shows the listing text, the price, the beds, the baths, the photos array, and the RealEstateListing JSON-LD directly in the page HTML, with no iframe wrapper. Googlebot reads the listing content as native to the agent’s entity. The host page accrues topical relevance from every listing in the inventory, and the schema-driven rich-result eligibility lands on the agent’s URL.

The view-source test resolves the distinction in under thirty seconds. Search the rendered HTML on a listing detail page for the iframe element. If the listing content lives inside an iframe pointing at a vendor subdomain, the implementation is iframe-rendered. If the listing payload appears directly in the HTML, the implementation is truly embedded. See the IDX iframe vs truly embedded spoke for the deeper working machinery.

The decision to ship a truly embedded IDX is irreversible once made and is the highest-yield architectural choice on the SEO side of the build. An iframe site shipping a content-marketing program against its listing inventory is operating against a hard ceiling no on-page work can lift.

The RESO Web API Replaces RETS

Historically, IDX feeds ran on the Real Estate Transaction Standard (RETS), launched by NAR in 1999 to replace inefficient FTP transfers. RETS allowed for querying, but the underlying field names varied wildly across local MLS markets. This required bespoke data normalization for every MLS feed just to generate accurate structured data. Schema generation across multiple MLSs was painful and expensive.

The 2018 industry migration to the RESO Web API resolved this. The Web API is RESTful, returns standardized JSON payloads, and aligns to the RESO Data Dictionary. For an SEO build, this is decisive. The standardized fields can be mapped almost one-to-one into RealEstateListing JSON-LD schema. Brokerages and agents operating across multiple MLSs can deploy scalable, automated schema generation for rich-result eligibility without custom mapping for each local market.

The Data Dictionary 2.0 structures the standardized data into a strict hierarchy: Resources (major categories like Property, Member, Office), Fields (specific data points), and Lookups (enumerated values for fields, like specific fence types). The dictionary operates on a principle of omissibility (not all 1,700+ fields are required for certification) and extensibility (local MLSs can add custom fields). The right pattern is to map the core RESO Property Resource fields directly to Google’s required schema properties, and to handle local custom fields via the additionalProperty slot so schema validation does not break.

When the IDX vendor handles this mapping cleanly, the agent site ships full schema with no custom development. When the vendor handles it poorly, the schema is incomplete or invalid and the rich-result eligibility evaporates regardless of the listing volume. The schema layer is therefore a vendor-evaluation criterion. Treat it that way at procurement time.

The Clear Cooperation Policy and the Freshness Signal

NAR’s 2019 Clear Cooperation Policy requires brokers to submit a listing to the MLS within one business day of marketing it to the public. This policy centralizes the freshness signal. Because the MLS is the definitive source of truth, Google’s crawlers prioritize the ingestion speed and update frequency of the IDX feed to maintain accurate SERP features.

For the agent site, the consequence is that listing freshness inherits from the MLS submission timestamp. The datePosted property on RealEstateListing schema should match the MLS submission rather than the time the listing was syndicated to the agent’s site. Truly embedded IDX sites that pull from the RESO Web API on a short polling interval inherit the freshness cleanly. Iframe-rendered sites inherit the freshness through the vendor’s domain instead of their own.

The policy also tightens what counts as a compliant listing-marketing program. Off-MLS marketing of an active listing risks NAR ethics complaints and can produce a structural disadvantage in the canonical cluster, because the listing’s freshness signal is fragmented across surfaces Google does not weight as authoritative.

What Compliance Looks Like at the Implementation Level

MLS rules typically require frequent listing-data updates, correct representation of property details, and display of specific disclaimers or copyright notices mandated by the local board. IDX policies usually require limiting display to properties approved for public viewing, preserving the broker attribution attached to each listing, and prohibiting alteration of essential property information without authorization.

Non-compliance produces real consequences: fines from the MLS, suspended IDX feeds, NAR ethics complaints under Article 12. The brokerage-firm-name disclosure required by NAR SOP 12-9 carries through every listing detail page on the agent site. State licensure jurisdictions require the broker license number disclosure alongside the brokerage name. The IDX vendor handles some of this automatically; the rest is on the agent or brokerage to verify.

Schema Coverage as the Independent-Site Lever

Because the canonical cluster on listing content is unwinnable, schema coverage is where independent-site SEO value concentrates. The minimum competent schema on a listing detail page surfaces RealEstateListing as the page type, with offers nested as an Offer carrying price, businessFunction for lease or sale, and availability for status. datePosted carries the MLS freshness signal. spatialCoverage carries the property boundary. numberOfRooms, floorSize, and the additionalProperty extensions cover the specifics that drive rich-result eligibility.

The RealEstateAgent and RealEstateAgency entity nesting on the broader site governs which listings get attributed to which agent and which brokerage. parentOrganization on the agent links the agent to the brokerage. memberOf signals NAR or local association membership. knowsAbout populated for the specific practice areas (luxury, first-time buyer, investment, relocation, commercial) signals the agent’s specialization to the entity graph.

See the real estate schema markup guide for the deeper pattern across the full entity model.

What Actually Determines Whether IDX Pays for Itself

IDX vendor pricing ranges from roughly $20/month at the entry tier to $200+/month at the higher tier, plus MLS pass-through fees, plus the cost of the truly-embedded rendering implementation if the vendor’s default is iframe. The pricing is therefore not the load-bearing variable. The load-bearing variables are the rendering pattern (iframe vs truly embedded), the schema coverage on listing detail pages, and the canonical strategy across the listing inventory.

A $20/month iframe IDX accruing zero topical relevance to the host domain is more expensive in opportunity cost than a $200/month truly-embedded IDX shipping clean schema. Evaluate the vendor on the rendering pattern, the schema completeness, and the canonical strategy first; price is a downstream consideration.

Where This Sits in the Larger SEO Surface

IDX and MLS govern the listing-inventory side of the site. The commercial-pages side of the site (service descriptions, practice-area capability, geography-specific content, buyer-representation surfaces post-Sitzer/Burnett) operates on the standard SEO surface, where canonical authority is winnable, schema is straightforward, and the regulatory layer concentrates on NAR Article 12 advertising rules and Fair Housing safe-harbor content patterns.

The right mental model: IDX is the inventory tier, where the canonical battle is lost structurally and schema is the remaining lever. The commercial pages are the practice tier, where the SEO battle is fully winnable and the citation-grade vocabulary (NAR SOPs, state-commission references, Fair Housing Title VIII safe-harbor content) carries the entity authority.

For the commercial-side work, see MLS & IDX SEO for the Tier 2 service framing, and the real estate SEO ultimate guide for the full architecture.

Frequently Asked Questions

Does every agent site need an IDX feed to rank?

No. Agent sites without IDX inventory can rank for commercial queries (service descriptions, practice-area pages, geography-specific content, buyer-representation queries) as cleanly as sites with IDX. The decision to ship IDX is a buyer-journey decision (whether visitors expect to search listings on the site) rather than an SEO decision. An IDX-free site loses access to the rich-result surface on listings but gains a simpler canonical and schema architecture.

What is the difference between IDX and VOW?

IDX is the public-facing display framework. Virtual Office Websites (VOW) is a separate, broker-controlled framework that allows display of additional listing data (sold history, withdrawn listings, days-on-market detail) behind a registration wall. VOW exists because NAR’s IDX rules limit what can display publicly without registration. For SEO purposes, VOW data is gated content that does not contribute to public-facing topical authority but does support lead-capture infrastructure.

Can the broker authority cluster with the agent canonical?

When the brokerage carries the canonical signal cleanly on the listing (truly embedded IDX, complete schema, fast freshness), the agent site can route inbound links to the brokerage’s listing page rather than the agent’s duplicate. This consolidates canonical authority on the broker URL while still preserving the agent’s attribution through RealEstateAgent schema with parentOrganization set. The pattern works when the brokerage controls the implementation; it breaks when the agent and brokerage run separate IDX vendors with conflicting canonicals.

How does NAR’s Clear Cooperation Policy affect the agent’s freshness signal?

The policy centralizes the freshness signal at the MLS submission timestamp. An agent site that mirrors that timestamp through datePosted on RealEstateListing schema inherits the freshness cleanly. An agent site that runs its own listing dates (lower granularity, longer cache windows) loses the freshness signal even when the listing content is up to date.

What about off-MLS listings (coming soon, exclusive)?

NAR Clear Cooperation requires public-marketing listings to enter the MLS within one business day. Genuinely off-MLS listings (coming-soon with no public marketing, broker-exclusive with no public marketing) sit outside this requirement but also sit outside the canonical cluster, the freshness signal, and the rich-result surface. Off-MLS marketing produces zero IDX inventory-side SEO value because the listing is not in the IDX feed at all.

Is iframe IDX ever the right choice?

For pure lead-capture use cases where the site treats listing search as a UX feature and does not depend on the inventory for organic search ranking, iframe IDX can be acceptable because the vendor handles the entire implementation and the implementation cost stays low. For any site whose SEO program depends on the listing inventory, iframe IDX caps the ceiling structurally and the right path is to migrate to a truly embedded implementation.