Zillow Search Scraper

Browsing Zillow one search page at a time is slow, and copying numbers into a sheet by hand is worse. This scraper skips all of that. Hand it the search URLs you already use on Zillow and it returns every listing on those pages as clean rows: the Zestimate, the rent estimate, property type, living area, lot size, the broker, and a direct link back to each home. It talks to Zillow's own search endpoint, so results come back fast with no browser to wait on. Point it at one neighborhood or a stack of cities in a single run.

What you get

Each listing becomes one row with the same set of columns every time, so the data drops straight into a spreadsheet or database. Values that Zillow does not show come back as null rather than disappearing, which keeps your columns lined up. Every row carries:

• Property basics — propertyId, listingUrl, photoLink, propertyType, listingStatus
• Size and value — livingAreaSqft, lotSize, lotSizeUnit, estimatedValue, estimatedRent
• Listing source — brokerName, featuredListing, sourceUrl, collectedAt

Quick start

1. Hit Try for free and open the input form.
2. On Zillow, set your filters, then copy the link from the address bar into Zillow search URLs. The link has to include the searchQueryState part.
3. Set a Results limit to keep the run capped where you want it.
4. Press Start, then export the rows as JSON, CSV, Excel, or XML once it finishes.

Use cases

• Market research — pull listings across several neighborhoods or zip codes at once instead of paging through them by hand
• Investment analysis — grab Zestimate and rent Zestimate figures for a batch of areas to rough out cap rates and rental yields
• Agent lead lists — gather broker names and listing links from your target markets for outreach
• Inventory tracking — schedule a daily or weekly run to watch how many homes show up in an area over time
• Housing data stories — collect listing data across cities for supply or price-comparison reporting
• Portfolio checks — follow current Zestimates for properties you own across different markets

Input

Field	Type	Required	Description
searchUrls	array of strings	Yes	Zillow search page URLs to scrape. Each link must include the searchQueryState parameter copied from your browser.
resultsLimit	integer	No	Cap on total listings returned across every URL. Default 500.
runTimeoutSeconds	integer	No	Hard stop on the whole run, in seconds. Default 300; max 3600.
timeoutSeconds	integer	No	Per-request timeout in seconds. Default 45; max 120.

Example input

{
    "searchUrls": [
        "https://www.zillow.com/austin-tx/?searchQueryState=%7B%22regionId%22%3A10221%7D",
        "https://www.zillow.com/denver-co/?searchQueryState=%7B%22regionId%22%3A12345%7D"
    ],
    "resultsLimit": 500,
    "runTimeoutSeconds": 300,
    "timeoutSeconds": 45
}

Output

Each listing on your search pages comes back as one row, and every field is always present — anything Zillow leaves out arrives as null so the dataset stays rectangular.

Example output

{
    "sourceUrl": "https://www.zillow.com/austin-tx/?searchQueryState=%7B%22regionId%22%3A10221%7D",
    "propertyId": "29448729",
    "listingUrl": "https://www.zillow.com/homedetails/1207-Oak-Hollow-Dr-Austin-TX-78745/29448729_zpid/",
    "photoLink": "https://photos.zillowstatic.com/fp/abc123-p_e.jpg",
    "propertyType": "SINGLE_FAMILY",
    "listingStatus": "ForSale",
    "livingAreaSqft": 1980,
    "lotSize": 6534,
    "lotSizeUnit": "sqft",
    "estimatedValue": 615000,
    "estimatedRent": 2850,
    "brokerName": "Compass RE Texas, LLC",
    "featuredListing": false,
    "collectedAt": "2026-06-29T12:00:00.000000+00:00",
    "errorMessage": null
}

Output fields

Field	Type	Description
sourceUrl	string	The Zillow search URL this listing came from, handy for tracing which query produced which rows
propertyId	string	Zillow's property identifier (ZPID)
listingUrl	string	Direct link to the property's detail page on Zillow
photoLink	string	URL of the main listing photo
propertyType	string	Home category: SINGLE_FAMILY, CONDO, TOWNHOUSE, MULTI_FAMILY, and the like
listingStatus	string	Listing state: ForSale, RecentlySold, ForRent, and similar
livingAreaSqft	number	Interior living space in square feet, null when not shown
lotSize	number	Lot size value, null when not shown
lotSizeUnit	string	Unit the lot size uses, sqft or acres
estimatedValue	number	Zillow's estimated home value in USD, null when not shown
estimatedRent	number	Zillow's estimated monthly rent in USD, null when not shown
brokerName	string	Listing brokerage behind the property
featuredListing	boolean	True when Zillow flags the listing as promoted
collectedAt	string	ISO 8601 timestamp of when the row was captured
errorMessage	string	Reason a URL failed; null on success

Tips for best results

• Use full search URLs. The link has to carry the searchQueryState parameter. Run a search on Zillow, then copy the URL from the address bar — bare location links without that parameter won't return data.
• Start with a couple of URLs. Confirm the output fits your pipeline before you point it at a long list of cities.
• Cap test runs with resultsLimit. Keep it small while you check the columns, then raise it for the full pull.
• Tighten the geography for more depth. A run returns the map results for a search, so for dense areas split a wide search into smaller ones with tighter filters.
• Give international or slow networks more room by raising timeoutSeconds toward its 120 ceiling if requests start timing out.

How can I use Zillow search data?

How can I use the Zillow Search Scraper to compare housing markets across cities? Paste a Zillow search URL for each market you care about and the scraper returns every listing on those pages with its Zestimate, rent estimate, property type, and living area. Group the rows by sourceUrl or city to line up median values, rent levels, and inventory side by side — a quick base layer for any market-comparison project.

How can I pull Zillow listings in bulk without copying them by hand? Drop in a list of Zillow search URLs and set resultsLimit to the number of homes you want back. Each listing comes out as one flat row with a direct listingUrl, so a handful of searches turns into a clean dataset you can export to CSV or Excel and hand to the rest of your workflow.

How can I scrape Zestimate and rent data for real estate investment research? Point the scraper at search URLs for your target zip codes and read the estimatedValue and estimatedRent fields straight off each row. With value and rent side by side per property you can rough out cap rates and rental yields across a whole area, then drill into individual homes through the listing link.

How can I track Zillow inventory on a schedule? Save your search URLs, then use Apify's scheduler to run the actor daily or weekly. Each run captures the current listings with a collectedAt timestamp, so you build a running record of how an area's inventory, prices, and rent estimates shift over time.

Is it legal to scrape data?

Our actors are ethical and do not extract any private user data, such as email addresses or private contact information. They only extract what the user has chosen to share publicly. We therefore believe that our actors, when used for ethical purposes by Apify users, are safe.

However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

You can also read Apify's blog post on the legality of web scraping.

Support

Questions, feature requests, or a field you'd like added? Reach out at data.apify@proton.me and we'll get back to you.