By industry
IDX schema integration
Rendering IDX listing data into a site's own server-side HTML, with structured data per listing, instead of embedding it in an iframe or a client-side widget that crawlers cannot read.
By Shimon Carroll, Founder, SEO for AI Agents · Last updated
IDX (Internet Data Exchange) is the set of MLS policies and data feeds that let a brokerage display other brokers' listings on its own site. How that feed reaches the page decides whether search engines and AI systems can see it. Many IDX products deliver listings in an iframe hosted on the vendor's domain, or through a JavaScript widget that builds the listing grid in the browser. To a crawler, the agent's site then has empty listing pages.
The iframe case is the clearest: content in an iframe belongs to the iframe's URL, not the agent's. The widget case hits a second problem. Googlebot renders JavaScript, though later and at a cost, but the main AI crawlers, including GPTBot, ClaudeBot, and PerplexityBot, have been observed fetching pages without executing JavaScript, so client-rendered listings are invisible to them.
The fix is an IDX integration that writes listings into server-rendered HTML on the agent's own domain, typically through the RESO Web API or a vendor that supports server-side rendering, with RealEstateListing markup per page and the MLS-required attribution intact. Be realistic about the payoff: thousands of listings that duplicate the portals add little on their own. The value is that neighborhood pages and market reports can include live, crawlable inventory, which makes them complete answers. Our audit checks listing pages for render parity and markup.
How the audit measures this
JS render-parity diff (raw HTML vs rendered DOM)Methodology →Related terms
Primary sources
- RESO Web API
Real Estate Standards Organization
- Understand JavaScript SEO basics
Google Search Central
- The rise of the AI crawler
Vercel