MLS syndication runs on a federation of ~529 local databases, NAR baseline policy, and per-MLS local rules layered on top.
- ✓Approximately 529 local and regional MLSs in the U.S., actively consolidating into mega-MLSs (CRMLS, Bright MLS).
- ✓NAR sets the baseline (Clear Cooperation Policy, IDX framework, cooperation rules); the local MLS layers its own rules on top.
- ✓NYC operates outside the MLS framework via REBNY's RLS, with Zillow-owned StreetEasy as the de facto consumer surface.
The MLS syndication patterns that govern listing visibility and SEO ceiling before any per-listing work begins.
A brokerage operating across multiple MLSs ships every active listing through three rule layers: NAR baseline policy, the originating MLS's local rules, and the IDX vendor's rendering and canonical pattern. The four sections below name what actually governs syndication outcomes. Operators who pick a single-MLS IDX vendor when their inventory spans three MLSs inherit a different syndication ceiling than operators who pick a multi-MLS vendor and map per-MLS local rules through the RESO Web API ingestion path.
The 529-MLS federation and what the count actually means.
The U.S. operates ~529 local and regional MLSs, governed by local REALTOR associations under NAR's baseline rule set. The count reflects decades of independent association governance, not an architectural decision. Consolidation runs steadily through mergers: California Regional Multiple Listing Service (CRMLS) aggregates a large portion of California through multi-association consolidation and is the largest MLS in the U.S. by participant count. Bright MLS covers Maryland, DC, Virginia, Pennsylvania, Delaware, New Jersey, and West Virginia through the merger of TREND, MRIS, and other Mid-Atlantic legacy MLSs. A national single MLS would require unwinding association governance, regional rule variation, and member ownership. The federation persists.
NAR baseline policy versus local MLS rule layers.
NAR sets the IDX framework, the cooperation rules, and the Clear Cooperation Policy that requires brokers to submit listings to the MLS within one business day of public marketing. Local MLSs layer their own rules on top: showing protocols, listing-status definitions, MLS-attribution display requirements on every IDX page, photo and remarks rules, per-MLS lookup tables that extend the RESO Data Dictionary 2.0 baseline. A brokerage operating across CRMLS, Bright MLS, and a smaller regional MLS ships three rule layers on the same listing template, surfaced per listing by source MLS. The schema layer and the rendering layer both reflect those rule differences.
Multi-MLS feed combination through RESO Web API ingestion.
Modern IDX vendors and custom builds ingest from multiple MLSs through separate RESO Web API connections per MLS, then normalize the standardized Data Dictionary 2.0 fields into a unified listing schema on the host site. The local custom fields per MLS route into additionalProperty on the RealEstateListing JSON-LD, which preserves local-market specificity without breaking the standardized schema or triggering Google's structured-data parser into validation errors. Vendors that ingest from only one MLS, or that flatten per-MLS local rules into a generic template, leave the brokerage with broken disclosure compliance and weaker schema coverage on the secondary MLSs.
The NYC RLS anomaly and what it means for syndication.
The Real Estate Board of New York (REBNY), founded 1896, operates its own Residential Listing Service for member brokerages. The RLS is not affiliated with NAR and operates outside the Clear Cooperation Policy, the IDX framework, and the standardized MLS-to-Google pipeline the rest of the U.S. runs on. Zillow Group acquired StreetEasy in 2013, and StreetEasy now functions as the de facto consumer surface for NYC residential inventory. NYC brokerages inherit a different syndication ceiling than the rest of the country: the SEO surface moves off listing competition entirely and onto buyer / seller education, neighborhood content, and brokerage entity authority, because StreetEasy owns the listing-discovery query layer.
What operators ask about MLS syndication before they pick a multi-MLS IDX vendor.
[ 01 ] Why are there 529 MLSs instead of one national database? +
[ 02 ] What do CRMLS and Bright MLS actually cover? +
[ 03 ] Our brokerage works across three MLSs. How do the feeds actually combine? +
If the IDX vendor was picked for a single-MLS workflow and the inventory spans three MLSs, the syndication ceiling is set before any retainer work begins. Book an MLS and IDX diagnostic.
We inspect the per-MLS rule layering on the rendered pages, the RESO Web API ingestion coverage per MLS, the schema fidelity across the unified inventory, and the disclosure-compliance surface for each originating MLS. Output is the per-MLS coverage assessment plus the migration path when the vendor is capping syndication value on the secondary MLSs. Funnels into our /mls-idx-seo/ retainer when the work runs deeper than a vendor-evaluation pass.