Houzz Scraper

Extract structured home-design data from Houzz for design research, inspiration discovery, competitor monitoring, and home-improvement lead generation.

What it extracts

• Houzz inspiration photos and image URLs
• Design professionals and firms
• Products and project pages
• Titles, descriptions, authors, ratings, review counts, and source URLs
• A machine-readable run summary in the OUTPUT key-value store

You can provide direct Houzz URLs or let the Actor create a search URL from one or more queries. Use pageType to target photos, professionals, products, or projects. Set maxResults and maxPages to keep runs predictable.

Input examples

Search photos:

{
  "searchQueries": ["modern kitchen ideas", "small bathroom remodel"],
  "pageType": "photos",
  "maxResults": 50,
  "maxPages": 3
}

Scrape direct pages:

{
  "startUrls": [{"url": "https://www.houzz.com/photos/kitchen-ideas-phbr1-bp~t_709"}],
  "pageType": "auto",
  "maxResults": 25
}

Reliability and access

The Actor uses a headless browser because Houzz can serve JavaScript client challenges to plain HTTP clients. Apify Proxy is enabled by default and can be disabled for a known-good network. If Houzz presents a challenge, the run completes with an EMPTY summary and a warning in OUTPUT rather than pretending the page contained no results. Retry later or use a suitable residential proxy.

Output

Each dataset item has a stable shape with recordType, title, url, imageUrl, description, author, location, rating, reviewCount, categories, sourcePage, and scrapedAt. See dataset_schema.json for field definitions.

Pricing

The Actor charges $0.005 per structured result written to the dataset, plus a $0.00005 run-start event. Empty and challenge-only runs do not incur result charges. Apify Proxy usage, if enabled, is billed by Apify separately.

Scope and responsible use

This Actor is for publicly accessible Houzz pages. Do not bypass authentication, paywalls, or access controls. Respect Houzz terms, robots guidance, applicable law, and reasonable request rates. You are responsible for the URLs and data you submit.

Use cases

• Compare listings, locations, availability, and market signals for property research.
• Build public prospect lists and qualify organizations or professionals before responsible outreach.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Run Houzz Scraper with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/houzz-scraper').call({
  "searchQueries": [
    "modern kitchen ideas",
    "small bathroom remodel"
  ],
  "pageType": "photos",
  "maxResults": 50,
  "maxPages": 3,
  "useProxy": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Support

When reporting a problem, include the Actor run ID, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.

Frequently asked questions

Can I schedule Houzz Scraper?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/houzz-scraper through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.

Recommended workflow

1. Define the smallest useful scope. Choose a representative public URL, query, identifier, or filter and keep the first result limit low.
2. Run and inspect. Check the run log, dataset item count, field coverage, source URLs, and live event or usage charges.
3. Validate downstream assumptions. Confirm nullable fields, deduplication keys, timestamps, and any locale-specific formats before importing records into another system.
4. Scale gradually. Increase limits or scheduling frequency only after the small run behaves as expected. Use Apify's maximum-cost and timeout controls to bound large jobs.
5. Monitor changes. Keep a small known-good input as a canary. If the source layout or API changes, compare the new dataset with a previously validated run and report the run ID when requesting support.

For recurring workflows, store the exact Actor input with your pipeline configuration. This makes runs reproducible and helps distinguish a source-data change from an input change.