Homes.com Property Scraper

Extract structured property listing data from Homes.com search pages, including pricing, location, property attributes, broker/agent metadata, and listing images. This scraper is designed for fast multi-page collection with no per-property page visits.

Features

• Search URL scraping - Collect listings directly from city, neighborhood, or filtered Homes.com result pages.
• Automatic pagination - Follow next pages until your result limit or page limit is reached.
• List-only extraction - Collect data directly from listing-level structured sources without opening individual property pages.
• Structured output - Save normalized records for analytics, lead generation, and market research.
• Clean datasets - Automatically omits null and empty values from output records.
• Event and map context - Captures open-house schedule and coordinates when available.
• Image galleries - Adds image_urls from listing cards when multiple images are available.

---

Use Cases

Real Estate Market Monitoring

Track property inventory, pricing, and listing changes in target cities to monitor market movement over time.

Investment Research

Build local listing datasets for price trend analysis, property comparison, and opportunity scouting.

Lead Generation

Collect listing and broker context to support acquisition workflows and outreach pipelines.

Location-Based Analysis

Compare listing characteristics across neighborhoods and regions using structured address data.

---

Input Parameters

Parameter	Type	Required	Default	Description
startUrl	String	Yes	https://www.homes.com/seattle-wa/	Primary Homes.com search URL to start from.
results_wanted	Integer	No	20	Maximum number of listings to save.
max_pages	Integer	No	10	Maximum number of result pages to visit.
proxyConfiguration	Object	No	Disabled	Optional proxy settings. If proxy traffic is blocked, the actor retries without proxy automatically.

---

Output Data

Each dataset item can include the following fields (only non-empty fields are saved):

Field	Type	Description
position	Number	Listing position in results.
listing_id	String	Listing identifier when available.
name	String	Listing title/name.
url	String	Listing URL.
image	String	Main image URL.
image_urls	Array	All discovered listing image URLs from listing cards.
image_count	Number	Count of URLs in image_urls.
price	Number	Listing price.
price_currency	String	Price currency code.
availability	String	Listing availability status.
listing_type	String	Property type/category.
bedrooms	Number	Number of bedrooms.
bathrooms	Number	Number of bathrooms.
floor_size_value	Number	Floor area value.
floor_size_unit	String	Floor area unit code.
address_street	String	Street address.
address_city	String	City/locality.
address_region	String	State/region.
address_postal_code	String	Postal code.
address_country	String	Country code/name.
description	String	Listing description text.
seller_name	String	Seller name when available.
broker_name	String	Brokerage/organization name.
agent_name	String	Agent name.
agent_title	String	Agent role/title.
agent_phone	String	Agent phone number.
open_house_start	String	Open-house start timestamp when available.
open_house_end	String	Open-house end timestamp when available.
latitude	Number	Property latitude when available.
longitude	Number	Property longitude when available.
source_url	String	Search page where listing was discovered.
scraped_at	String	ISO timestamp of extraction.

---

Usage Examples

Basic City Scrape

{
	"startUrl": "https://www.homes.com/seattle-wa/",
	"results_wanted": 20,
	"max_pages": 10
}

With Proxy Configuration

{
	"startUrl": "https://www.homes.com/seattle-wa/",
	"results_wanted": 30,
	"proxyConfiguration": {
		"useApifyProxy": true,
		"apifyProxyGroups": ["RESIDENTIAL"]
	}
}

---

Sample Output

{
	"position": 1,
	"name": "1234 Example Ave, Seattle, WA 98101",
	"url": "https://www.homes.com/property/1234-example-ave-seattle-wa/abcd1234/",
	"image_urls": [
		"https://images.homes.com/listings/115/example-primary.jpg",
		"https://images.homes.com/listings/115/example-buildingphoto-2.jpg"
	],
	"image_count": 2,
	"price": 899000,
	"price_currency": "USD",
	"bedrooms": 3,
	"bathrooms": 2,
	"address_city": "Seattle",
	"address_region": "WA",
	"listing_type": "SingleFamilyResidence",
	"open_house_start": "2026-03-21T10:00:00.000",
	"latitude": 47.560275,
	"longitude": -122.379175,
	"broker_name": "Example Realty Group",
	"source_url": "https://www.homes.com/seattle-wa/",
	"scraped_at": "2026-03-18T12:00:00.000Z"
}

---

Tips for Best Results

Start with Focused URLs

Use city, ZIP, or filtered search pages so the dataset aligns with your exact research scope.

Keep Test Runs Small

Use results_wanted: 20 for quick validation, then scale to larger production runs.

Start Without Proxy

For Homes.com, proxy traffic may trigger blocking on some runs. Start without proxy and enable it only if needed.

Keep Page Limits Practical

Use max_pages and results_wanted together to keep runs fast and predictable.

---

Integrations

• Google Sheets - Export listing datasets for team review and reporting.
• Airtable - Build searchable property intelligence tables.
• Make - Trigger workflows on new listing collection runs.
• Zapier - Send listing data to CRMs and automation tools.
• Webhooks - Push records to your own pipelines and APIs.

Export Formats

• JSON
• CSV
• Excel
• XML

---

Frequently Asked Questions

How many listings can I collect?

You can collect as many as available for your search scope, limited by your input settings and run resources.

Why do some records have different fields?

Listings vary by page and market. The actor saves only fields that exist for each listing.

Can I scrape multiple cities in one run?

Yes. Run the actor once per city URL and schedule runs for each target location.

Does it support pagination automatically?

Yes. It follows next pages until max_pages or results_wanted is reached.

How do I improve reliability?

Use Apify Proxy with residential groups and keep realistic per-run limits.

---

Support

For issues or feature requests, use the Apify Actor issue/contact options in the Apify Console.

Resources

• Apify Documentation
• Apify API Reference
• Apify Scheduling

---

Legal Notice

This actor is intended for legitimate data collection and analysis workflows. You are responsible for complying with website terms and applicable laws in your jurisdiction.