The robots.txt file for Zillow imposes rigid rules limiting automated scraping for the standard crawlers. Essential directives such as Disallow: /homes/, Disallow: /homedetails/, Disallow: /howto/, and Disallow: /html/, prohibit access to the integral areas of the website. These instructions are applicable to all general user-agents, while distinguished search engine bots may have exemptions.

The file, however, does permit a few paths. Obvious permissions include Allow: /, Allow: /hotpads/, and Allow: /sitemap.xml along with sitemap locations specified. But given these permissions, it still creates a resilient environment where indiscriminate web scraping is largely restricted. The robots.txt file strongly signals a stringent stance towards web scraping, with controlled allowances for specific user agents.

The terms of service for Zillow explicitly prohibit automated access and data extraction. The terms state:

“You may not use any robot, spider, scraper or other automated means to access the Services for any purpose without our express written permission.”

This covers all scraping, crawling, or bot-driven collection across both public and logged-in parts of the site. While terms can apply differently depending on whether a user has explicitly agreed (for example, by creating an account), Zillow frames this restriction as universal.

Zillow does not offer a general public API for bulk data extraction; access to data via APIs is limited to approved partners under separate agreements. The terms also prohibit bypassing access controls such as logins, rate limits, or CAPTCHAs and warn of enforcement actions including technical blocks, account suspension, and legal remedies for violations. In practice, scraping Zillow is forbidden unless you have prior written permission or a contractual API arrangement—otherwise, attempts to automate access are likely to be blocked and can trigger further action.