IDX rendering reference · Earnest

The rendering pattern on the IDX feed governs whether listing content counts as the agent's site, or as the vendor's.

✓Iframe IDX renders listing content from the vendor's domain; the agent's host page is a window into someone else's content.
✓Truly embedded ingestion via the RESO Web API renders the listing payload as native HTML on the agent's domain.
✓Same listing data, opposite SEO outcome: zero topical relevance versus full topical relevance to the host site.

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

● BOOKING NEW OPERATORS

[ WHY ] What this spoke covers

The rendering-pattern distinction that governs every downstream SEO outcome on the listing inventory from schema coverage to topical authority.

Real estate operators reading IDX vendor marketing rarely encounter the rendering-pattern decision named explicitly. The vendor pitches lead-management features, search-UI customization, and pricing tiers. The rendering pattern hides inside the implementation. The four sections below cover what the distinction actually is at the HTML level, why iframe rendering caps the SEO ceiling structurally, what truly embedded ingestion unlocks, and how to tell which pattern a current site already runs on without asking the vendor.

IFRAME OUTCOME ZERO HOST RELEVANCE

TRULY EMBEDDED FULL HOST RELEVANCE

VIEW-SOURCE TELL IFRAME ELEMENT PRESENT?

[ 01 ]

What iframe rendering actually is at the HTML level.

An iframe IDX implementation 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 a header, footer, and minor surrounding content. Googlebot parses the iframe content as belonging to the vendor's domain, not the agent's. 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.

[ 02 ]

What truly embedded ingestion looks like in the rendered HTML.

A truly embedded implementation 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 rather than the vendor's.

[ 03 ]

What the rendering decision unlocks beyond raw indexation.

Topical relevance is the surface-level outcome. The deeper consequence is the schema layer: native schema on the host page is impossible inside an iframe rendered from a vendor domain, so iframe-rendered sites are structurally locked out of RealEstateListing rich-result eligibility on their own URLs. Truly embedded sites ship full schema per listing, with parentOrganization linking the listing to the brokerage and the author Person node linking the listing to the agent. The schema-driven rich-result surface and the topical-authority surface both open together when the rendering decision flips from iframe to truly embedded.

[ 04 ]

How to tell which pattern a current site runs on.

View-source on any listing detail page on the site. Search the rendered HTML for the iframe element. If the listing search results and the listing detail content live inside an iframe pointing at a vendor subdomain, the implementation is iframe-rendered. If the listing text, price, beds, baths, photos, and RealEstateListing JSON-LD appear directly in the HTML without an iframe wrapper, the implementation is truly embedded. The schema layer is the secondary tell: native schema on the host page only exists when the rendering pattern is truly embedded. A vendor sales call can confirm the pattern; the view-source check confirms the actual delivered state.

[ FAQ ] Common questions

What operators ask about iframe versus truly embedded IDX before they commit to a migration.

[ 01 ] How do I tell whether my current IDX is iframe or truly embedded? +

View-source on a listing detail page on your site. Search the rendered HTML for the iframe element. If the listing search results and the listing detail content live inside an iframe pointing at a vendor subdomain (search.vendor.com, idx.brokerage.com routed through vendor DNS), the implementation is iframe-rendered. If the listing text, price, beds, baths, photos, and RealEstateListing JSON-LD appear directly in the HTML of the page without an iframe wrapper, the implementation is truly embedded. The schema layer is the second tell: native schema on the host page is impossible inside an iframe rendered from a vendor domain.

[ 02 ] If my site has inbound links to iframe-rendered listing pages, where does the authority go? +

To the agent's URL the link points at, which Google parses as a page containing minimal native listing content because the listing lives inside an iframe from the vendor's domain. The inbound link signal accrues to a page Google reads as thin. The agent's domain-level authority benefits from the link in aggregate, but the listing page itself does not rank for the listing-specific queries the link might suggest. Inbound links to the iframe URL itself (the vendor subdomain) accrue to the vendor's domain. The fix is the rendering migration, not link cleanup.

[ 03 ] Is the truly embedded migration actually worth the cost for a small brokerage? +

Depends on the inventory size, the time horizon, and the surface where the brokerage's SEO program is bottlenecked. A small brokerage with thirty active listings and a stable inventory at a low-volume market may extract more value from non-listing surfaces (neighborhood content, buyer education, post-Sitzer/Burnett agreement content) than from migrating the iframe. A brokerage with several hundred listings across a high-volume market typically clears the migration cost within the first year because the listing inventory becomes a contributing topical-authority surface on the host domain rather than a thin frame around vendor content. The diagnostic tells the answer.

MLS and IDX diagnostics · Q3 2026

If the IDX rendering pattern is iframe, the listing inventory is contributing zero topical authority to the host site no matter how much content sits around it. Book an MLS and IDX diagnostic.

We inspect the current rendering pattern via view-source on listing detail pages, the schema layer on the rendered HTML, the iframe-source domain when present, and the migration path to a truly embedded implementation via the RESO Web API. Output is the rendering assessment plus the migration scope, sequenced for the brokerage's inventory size and the market's SERP competition. Funnels into our /mls-idx-seo/ retainer when the migration warrants ongoing implementation work.

Book a diagnostic → Email us