IDX integration reference · Earnest

IDX makes the listing data available. It does not make your site rank for it.

✓IDX creates structurally mandated duplicate content across Zillow, Realtor.com, Redfin, the brokerage, and thousands of agents.
✓Self-referential canonicals are hints; Google overrides them in favor of higher-authority directory clusters.
✓RESO Web API and the rendering pattern (iframe versus truly embedded) determine whether a site can extract SEO value at all.

NAR-COMPLIANT · FAIR HOUSING-SAFE · MLS/IDX-FLUENT

● BOOKING NEW OPERATORS

[ WHY ] What this reference covers

The IDX integration decisions that govern whether a real estate site ranks on its own listings.

Internet Data Exchange is the NAR policy framework that lets brokerages and agents display MLS listings on their own sites. It was established in the late 1990s and expanded by a 2008 DOJ antitrust settlement requiring NAR to allow internet-only brokerages access. The framework creates a structurally mandated duplicate-content environment because the same listing text and image array gets syndicated to Zillow, Realtor.com, Redfin, the listing brokerage, and thousands of agents simultaneously. The integration choices (vendor, rendering pattern, canonical strategy, schema completeness, MLS data layer) decide what topical relevance a site can actually accrue.

POLICY ORIGIN NAR + 2008 DOJ

DATA LAYER RESO WEB API 2.0

RENDERING DECISION IFRAME / EMBEDDED

[ 01 ]

The IDX policy framework and the duplicate-content reality.

IDX comes from NAR policy plus the 2008 DOJ antitrust settlement. The framework gives every IDX-enabled site the same listing text simultaneously. Google's canonicalization algorithm evaluates duplicates via standard signals (canonical tag, internal linking, sitemap inclusion, PageRank) and frequently folds the agent's self-referential canonical into the directory's canonical cluster. Spokes: IDX Broker integration patterns and MLS database syndication mechanics.

[ 02 ]

RESO Web API and the data layer migration.

RETS was launched by NAR in 1999 with wildly varying field names across local MLSs, which required bespoke data normalization for every feed. The 2018 industry migration to RESO Web API (RESTful, Data Dictionary 2.0) standardized the payloads. Resources, Fields, Lookups now map almost 1:1 into RealEstateListing JSON-LD. Local custom fields route through additionalProperty. Spoke: the RESO Data Dictionary 2.0 in detail.

[ 03 ]

Iframe versus truly embedded rendering.

Iframe IDX renders listing content from the vendor's domain inside a window on the host page. Google sees the content as belonging to the vendor; zero topical relevance accrues to the host domain. Truly-embedded IDX ingests via RESO Web API or RETS and renders server-side or statically on the host domain. Googlebot parses the listing text as belonging to the host entity. The distinction governs whether a site can participate in IDX SEO at all. Spoke: the iframe versus truly embedded rendering comparison.

[ 04 ]

Canonical strategy under directory authority.

Google treats canonical tags as hints, not directives. Because Zillow and Realtor.com have higher PageRank and faster sitemap ingestion, Google frequently overrides the agent's self-referential canonical and folds the listing into the directory's canonical cluster. The fix is not stronger canonicals. The fix is extracting SEO value from RealEstateListing schema completeness and from non-listing content (neighborhood guides on the SOP 10-2 pattern, buyer education) where the directory does not dominate. Spokes: IDX duplicate content and canonical tags, plus the StreetEasy versus MLS dynamic in NYC.

[ FAQ ] Common questions

What operators ask about IDX integration before they pick a vendor.

[ 01 ] What is IDX and where did the policy come from? +

Internet Data Exchange is a NAR policy framework established in the late 1990s, then expanded by a 2008 DOJ antitrust settlement that required NAR to allow internet-only brokerages access to MLS data. IDX is what permits brokerages and agents to display MLS listings on their own websites. The framework creates a structurally mandated duplicate-content environment because the same listing text and image array gets syndicated to Zillow, Realtor.com, Redfin, the listing brokerage, and thousands of agents' IDX-enabled sites simultaneously.

[ 02 ] Why does the duplicate-content problem on IDX listings persist even with canonical tags? +

Google treats canonical tags as hints, not directives. Individual agent IDX plugins emit self-referential canonicals on listing pages, but because Zillow and Realtor.com have higher PageRank, faster sitemap ingestion, and denser internal linking, Google frequently overrides the agent's canonical and folds the listing page into the directory's canonical cluster. The agent page is effectively neutralized for property-specific queries. The work-around is extracting SEO value from RealEstateListing schema completeness and from non-listing content (neighborhood guides on the SOP 10-2 pattern, buyer education) where the directory does not dominate.

[ 03 ] What changed with the RETS to RESO Web API migration? +

RETS was launched by NAR in 1999 to replace FTP-based MLS transfers. RETS allowed querying, but the underlying field names varied wildly across local MLSs, which required bespoke data normalization for every feed just to generate accurate structured data. The 2018 industry migration to RESO Web API (a RESTful architecture) standardized the Data Dictionary 2.0. The standardized JSON payloads now map almost 1:1 into RealEstateListing JSON-LD, which makes scalable schema generation possible across multi-MLS brokerages. If the IDX vendor still runs on RETS, the schema layer stays brittle.

[ 04 ] How do I know if my IDX implementation is iframe or truly embedded? +

View the listing detail page on the site. Right-click and inspect the listing content. If the content sits inside an iframe element rendered from the vendor's domain, the pattern is iframe and zero topical relevance accrues to the host domain. If the content sits in the page's own HTML and the canonical tag points to the agent or brokerage domain, the pattern is truly embedded and Googlebot parses the listing as belonging to that entity. If the listings sit on a subdomain (homes.youragency.com), topical relevance routes to the subdomain rather than the root. The rendered DOM is the source of truth; vendor marketing copy on this point is often optimistic.

MLS and IDX diagnostics · Q3 2026

If your IDX is an iframe or your canonicals get overridden by Zillow, the SEO ceiling is set by the integration, not the content. Book an MLS and IDX diagnostic.

We inspect the rendering pattern, the RESO Web API field mapping, the canonical strategy, the RealEstateListing schema completeness, and the freshness signal carried through datePosted. Output is the per-page integration ledger plus the rebuild path where the integration is capping the SEO ceiling. Funnels into our /mls-idx-seo/ retainer when the work runs deeper than a one-pass audit.

Book a diagnostic → Email us