Zillow's Real Moat Is MLS Contracts, Not Lawsuits
Despite the reputation, Zillow has not pursued CFAA lawsuits against open-source scrapers in 2024–2026. The actual enforcement runs through MLS contracts and listing-access policy — Compass v. Zillow lost on the injunction, dropped the suit in March 2026.
The reputation of Zillow in scraping circles is “litigious.” The actual record across 2024–2026 is the opposite: no Computer Fraud and Abuse Act lawsuit against an open-source scraper in the time frame, no public cease-and-desist served on the dominant open-source real-estate scraping library HomeHarvest, no enforcement against any visible Apify-class actor.
What did happen in the same window: a brokerage (Compass) sued Zillow over the new Listing Access Standards, lost the preliminary-injunction motion in February 2026, and dropped the suit in March 2026. The legal action ran in the opposite direction from the trope.
That gap between perception and record is the story. It tells you where the actual moat is, and it tells scrapers something important about which targets are defended by lawsuits versus which are defended by something else.
The Compass case in plain terms
In April 2025, Zillow announced its Listing Access Standards — a policy that effectively required a listing agent to upload a property to Zillow within one day of marketing it anywhere else, on penalty of having the listing excluded from Zillow entirely. The policy is a counter-move against off-MLS / “private listing network” growth in the brokerage industry.
Compass, a major brokerage that had built marketing strategy around exclusive private listings, sued Zillow in June 2025 alleging antitrust violations. The court denied Compass’s request for a preliminary injunction in February 2026 — a serious early-stage loss — and Compass dropped the case in March 2026.
Substantively, the ruling and the dismissal mean Zillow’s listing-policy enforcement stands. Listings get on Zillow within a day of marketing, or they get excluded. The penalty is loss of distribution to roughly 200M+ monthly visitors — the dominant consumer real-estate audience in the US.
Why this matters for scraping economics
The Listing Access Standards do not target scrapers. They target listing flow. But they describe how Zillow actually defends its position in the market, which has direct implications for what scrapers can and cannot do.
Zillow does not need CFAA lawsuits to control its data because it controls the supply chain that produces the data. Listings flow into Zillow through MLS feeds and direct-broker uploads governed by contracts. A scraper that pulls Zillow’s public-facing pages is downstream of that supply chain — useful for spot research, but limited by the fact that Zillow can change page structure, throttle request rates, or restrict particular features at will, with no legal exposure to the scraper.
The contrast with LinkedIn is illustrative. LinkedIn’s data is contributed by users under a ToS that LinkedIn enforces. The Bright Data v. Meta line of cases is about whether that ToS can restrain logged-out scrapers — and the answer in 2024 was no. LinkedIn therefore has to live with logged-out scraping as a fact, and the lead-extractors segment on Apify is built on exactly that fact.
Zillow’s moat is structurally different. It is a contracting moat (MLS feeds, broker agreements, listing rules) rather than a ToS moat. Scrapers cannot litigate around it because there is nothing to litigate. The data either appears on the Zillow surface or it does not, and Zillow controls which.
What HomeHarvest’s existence tells you
HomeHarvest is an open-source Python library that scrapes Zillow, Realtor.com, and Redfin into MLS-style schemas. It has roughly 660 GitHub stars, active development through 2025–2026, and zero recorded takedown actions from any of the three target sites.
The absence of enforcement is itself information. It says one of two things: either the targets do not view HomeHarvest as a meaningful threat (because it does not impact MLS supply or paid subscriber numbers), or the targets have decided that public CFAA enforcement is not worth the legal-risk premium given the unfavorable case law. Probably both.
The practical implication for scrapers is that real-estate listing data is technically accessible at scale, with low legal risk for non-commercial or research use, and limited commercial value precisely because the structural moat (MLS access) is not something scraping can replicate.
Why the Apify real-estate segment stays thin
Real-estate scrapers exist on the Apify Store, but the segment is not large — meaningfully smaller than the LinkedIn-targeting lead segment or the job-board segment. The thinness of the segment is consistent with the structural read: the buyers of real-estate data want MLS feeds and direct broker integrations, both of which require contractual access that an Apify Actor cannot provide.
That said, there are specific use cases where Zillow / Realtor.com / Redfin scraping has real value: investor research, comp-pulling for individual transactions, market-trend analysis, and data-science pipelines that need historical pricing series. None of those buyers are big enough individually to support a high-volume actor, but together they form a real long-tail market.
The opportunity for actor publishers is the data-science segment specifically. A self-healing real-estate scraper (per the self-healing pattern) targeting one of the major US real-estate sites, with clean schema output and competitive per-listing pricing, would compete favorably against HomeHarvest on operational simplicity for buyers without the engineering capacity to maintain their own pipeline. The economics work because there is no incumbent extracting margin from this segment of buyers — Zillow’s own paid products target professional brokers and agents, not data scientists.
The structural lesson
The broader lesson — applicable beyond real estate — is that the most defensible data moats in 2026 are contractual, not technical. Sites that win in court (Bright Data v. Meta) get scraped; sites that win through supply-chain control (Zillow MLS access, Lightcast enterprise contracts, Reddit’s Google licensing deal) keep their data inside a fence that scraping can poke at but cannot replicate.
For an Apify Store publisher choosing a target, the question worth asking is not “can I scrape this site” but “what is the buyer paying for that the scraper cannot deliver”. When the answer is “nothing real,” the scraper wins. When the answer is “MLS access” or “vendor relationships” or “compliance posture,” the scraper is filling a marginal use case rather than competing for the main revenue.
Zillow is the cleanest illustration of the second category. The site is technically scrapable. The data is partially valuable. But the segment is small precisely because the buyers who would pay the most are paying Zillow directly for something the scraper cannot replicate — and that has nothing to do with whether Zillow files lawsuits.
Sources