NewHomeSource Real Estate Scraper — New Homes, Builders, Floor Plans & Communities

How It Works

All-in-one NewHomeSource.com scraper — pick any US state and the actor walks every market area, every community, and every home / floor-plan inside it. Output: one flat row per home with 33 fields covering home specs, community context, builder, location, and source URLs. JSON + CSV.

Input	Row(s) emitted
State (e.g. Texas, Florida, California)	N home rows — one per new home or floor plan available across that state's markets
Start URLs — specific community URLs (/community/..., /basiccommunity/...)	N home rows per community URL — one per home/plan in that community
Start URLs — specific home URLs (/plan/..., /specdetail/..., /basichome/...)	1 home row per URL (community-rollup fields will be empty)

Pure HTTP. No Puppeteer, no Playwright, no headless Chromium, no third-party CAPTCHA-bypass service.

---

Why Use This Scraper?

• All-in-one state coverage. Pick Florida once and get every market (Orlando, Miami, Tampa…), every community, every home, every floor plan — no URL juggling, no per-market job orchestration.
• Builder + community + home in one row. Most competing approaches give you community listings or home listings. This actor flattens them: each row carries the home's own price + size + beds + baths, the community's price band + floor-plan count + total homes, and the builder's name + ID + phone.
• Geo-ready. Latitude + longitude on every row, plus full street address, zip, state. Drop straight into your map / heatmap / territory-analysis pipeline.
• Bot-defense resilient. Auto-retry HTTP pipeline gets past NewHomeSource's protection layer without spinning up a browser.
• JSON or CSV out. No glue code. Connect to your warehouse, BI tool, or spreadsheet in one step.

---

Overview

NewHomeSource is the largest US new-construction listings site, operated by Builders Digital Experience (Move, Inc.). It indexes new-build homes, floor plans, communities, and builders across all 50 states.

This actor produces a single flat row shape — one record per home or floor plan. Each row denormalizes the community-level and builder-level context, so a single CSV is enough for downstream analytics (no joins required).

Coverage scope. The actor walks: State landing page → market areas (metro regions) → community detail pages → individual home / plan pages. Each home detail page is parsed for the structured data already embedded in the response, with DOM fallbacks for basic plan / spec pages that render the same content in a different shape.

---

Supported Inputs

The state input accepts any of the 50 US states by full name (e.g. Texas, Florida, California). The actor will:

1. Visit the state's all-communities listing and walk it page by page (40 communities per page).
2. For each community, extract its profile + builder + the list of available homes / floor plans.
3. For each home / floor plan, fetch the detail page and emit the 33-field row.

One state per run — if you need multiple states, schedule the actor with different state values via Apify scheduler. Use the maxItems cap below to keep cost predictable on big states.

Not supported: custom startUrls. The actor is state-driven only. If you need URL-driven scraping (e.g. "scrape these 200 specific communities"), open an issue (link below) — that's a roadmap candidate.

---

Use Cases

Audience	What they use it for
Real estate professionals	Daily/weekly snapshots of available new construction in target markets — pricing trends, builder presence, inventory levels
Home builders	Competitive monitoring — which builders are active in which markets at what price points
Market researchers	New-construction supply data by state/metro/zip — input to housing reports
Lead-generation / B2B sales	Builder contact data + community-level phone numbers for outreach
MLS / proptech competitors	Aggregating new-build inventory that doesn't always appear in MLS
Property data warehouses	Adding new-construction layer to existing resale-focused datasets

---

Input Configuration

Field	Type	Required	Default	Notes
state	enum	no	"Alabama"	One of the 50 US states. Dropdown in the Apify UI. The actor walks state → markets → communities → homes end-to-end. Optional when startUrls is set.
startUrls	string[]	no	[]	List of specific NewHomeSource URLs to scrape. Accepts community URLs (/community/{state}/.../{id}, /basiccommunity/community-{id}/...) — each emits every home/plan in that community — and home URLs (/plan/..., /specdetail/..., /basichome/...) — each emits one row. Can be combined with state: state walk runs first, then the URL list.
maxItems	integer	no	0 (unlimited)	Hard cap on the total home rows pushed in one run (applies across state walk + URL list combined).
maxConcurrency	integer	no	10	Max parallel page fetches across the funnel.
minConcurrency	integer	no	1	Lower bound for adaptive concurrency.
maxRequestRetries	integer	no	3	Per-request retry budget.
proxy	object	no	Apify Residential	Standard Apify proxy configuration. Residential proxies strongly recommended — datacenter IPs are flagged on first request by this site's bot detection.

Example input

State mode — walk an entire state end-to-end:

{
  "state": "Missouri",
  "maxItems": 2000,
  "maxConcurrency": 10,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

That walks Missouri's entire new-construction inventory, capped at 2,000 home rows.

URL mode — scrape only specific communities (no state walk):

{
  "startUrls": [
    "https://www.newhomesource.com/community/id/kuna/medallion-at-valor-by-tresidio-homes/202479",
    "https://www.newhomesource.com/community/al/talladega/cornerstone-meadows-by-smith-douglas-homes/199856"
  ],
  "maxConcurrency": 5,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Each community URL emits one row per home/plan in that community. Skip the state field entirely when running in URL mode.

Home URL mode — pull single home/plan pages directly:

{
  "startUrls": [
    "https://www.newhomesource.com/plan/the-pearson-smith-douglas-homes-columbiana-al/2787050",
    "https://www.newhomesource.com/specdetail/1379-barret-park-way-montgomery-al-36117/2777927",
    "https://www.newhomesource.com/basichome/pembrook-overland-park-ks/p3305873"
  ]
}

One row per URL. Community-rollup fields (Total Floor Plans, Community Min/Max Home Price, etc.) will be empty — those come from the community detail page which we're skipping in this mode.

Combined mode — state walk plus extra communities of interest in one job:

{
  "state": "Idaho",
  "startUrls": [
    "https://www.newhomesource.com/community/id/kuna/medallion-at-valor-by-tresidio-homes/202479",
    "https://www.newhomesource.com/community/al/talladega/cornerstone-meadows-by-smith-douglas-homes/199856"
  ]
}

Bump maxConcurrency only if your proxy plan can take the parallel load — Apify Residential handles 10 comfortably.

---

Output Overview

Single flat shape: 33 fields per row, one row per home / floor plan. Fields are alphabetically sorted in the CSV header so column order is stable across runs (e.g. BA → BR → Builder → Builder ID → … → Zip Code).

Both formats are written automatically at end of run:

• data.json — array of row objects in the Apify key-value store.
• data.csv — same rows as CSV, header row included, ready for Excel / Sheets / Snowflake / BigQuery.

---

Output Samples

Real row from a Missouri run (Lombardo Homes' "The Becket" floor plan in the South Wind community, Ashland MO):

{
  "BA": "2",
  "BR": "3",
  "Builder": "Lombardo Homes Missouri",
  "Builder ID": "74278",
  "Community Address": "Talladega Dr, Ashland, MO 65010 Ashland, MO 65010",
  "Community ID": 221963,
  "Community Max Home Price": 540000,
  "Community Max Home Size": 2968,
  "Community Min Home Price": 298000,
  "Community Min Home Size": 1655,
  "Community Name": "South Wind",
  "Floor Plan": "The Becket",
  "GA": 2,
  "Latitude": "38.756352",
  "Longitude": "-92.256633",
  "New Home Address": "Talladega Dr, Ashland, MO 65010",
  "New Home Price": "316000",
  "New Home Size": 1721,
  "Notes": "About South Wind. Lombardo Homes is excited to offer homesites in the desirable South Wind community in Ashland, Missouri! …",
  "Phone": "888-928-7606",
  "QMI Count": 1,
  "ST": 1,
  "Secondary Count": 1,
  "State": "MO",
  "Status": "Normal",
  "Subtype": "SBC",
  "Total Count": 1,
  "Total Floor Plans": 10,
  "Type": "Place",
  "URL 1": "https://nhs-dynamic-secure.akamaized.net/Images/Homes/Lomba11476/106564452-260320.jpg",
  "URL 2": "https://www.newhomesource.com/community/mo/ashland/south-wind-by-lombardo-homes-missouri/221963",
  "URL 3": "https://www.newhomesource.com/plan/the-becket-lombardo-homes-missouri-ashland-mo/3790637",
  "Zip Code": "65010"
}

---

Key Output Fields

Grouped by category. All field names match the column header in data.csv exactly.

Home specs (this individual home or floor plan)

• Floor Plan — plan name (e.g. "The Becket")
• BR — bedrooms
• BA — bathrooms
• GA — garage car count
• ST — number of stories
• New Home Size — square feet for this specific plan
• New Home Price — list price for this plan
• Status — current marketing status (e.g. "Normal", "Coming Soon", "Hot Deal")
• Type / Subtype — schema.org type + NewHomeSource subtype code

Community context (rolled up across the community)

• Community Name — community / subdivision name (e.g. "South Wind")
• Community ID — NewHomeSource numeric ID
• Community Address — community-level street address
• Community Min Home Price / Community Max Home Price — price band across all homes
• Community Min Home Size / Community Max Home Size — size band (sq ft)
• Total Count / Secondary Count — home counts at the community
• Total Floor Plans — number of distinct plans offered
• QMI Count — quick-move-in inventory count
• Notes — community description / marketing copy

Location

• Latitude / Longitude — geocoordinates (string)
• New Home Address — street address for this specific home
• State — 2-letter state abbreviation (e.g. "MO")
• Zip Code — 5-digit zip

Builder

• Builder — builder display name (e.g. "Lombardo Homes Missouri")
• Builder ID — NewHomeSource numeric builder ID
• Phone — community / builder contact number

Media + source URLs

• URL 1 — listing image (Akamai-hosted, full resolution)
• URL 2 — community detail page on NewHomeSource
• URL 3 — plan / spec detail page on NewHomeSource

---

FAQ

Q: Why is the input a state instead of a URL list? A: NewHomeSource is structured top-down (state → market → community → home), and the easiest way to get comprehensive new-build coverage is to walk that tree. If you need URL-driven scraping for specific communities or builders, file an issue — that's on the roadmap.

Q: Can I scrape multiple states in one run? A: One state per run by design. To cover multiple states, schedule the actor with different state values via the Apify scheduler (or call it from your own orchestration). Per-run is cleaner: predictable cost, easy debugging, isolated failure if one state's landing page hiccups.

Q: Can I scrape specific communities without walking a whole state? A: Yes — use the startUrls input. Paste any mix of community URLs (/community/..., /basiccommunity/...) and the actor processes only those, emitting one row per home in each. You can also pass individual home URLs (/plan/..., /specdetail/..., /basichome/...) — each emits one row, but community-rollup fields (Total Floor Plans, Community Min/Max Home Price, etc.) will be empty because those come from the community detail page.

Q: What if I set both state and startUrls? A: Both run in the same job — state walk first, then the URL list. The maxItems cap applies to the combined total. Useful when you want full coverage of one state plus specific competing communities elsewhere.

Q: How long does a full state take? A: Depends on the state. Texas / Florida / California have 20+ markets and tens of thousands of listings; small states like Wyoming or Vermont may have 1-3 markets and a few hundred listings. Plan on 10-60 minutes for typical states with maxConcurrency: 10 on Apify Residential.

Q: Why do I need residential proxies? A: NewHomeSource runs commercial bot detection that flags datacenter IPs on first request. Residential proxies (Apify Residential, or any reputable residential provider) work; standard non-residential proxies do not.

Q: What happens if a specific home page gets blocked? A: The per-URL retry budget is generous (up to ~100 attempts). If all retries fail, the URL is logged to failed-requests.json and skipped — the rest of the run continues. Expect 80-95% completion on typical states; the tail is usually URLs that 404 anyway.

Q: Does the output include open-house dates / lot maps / virtual tours? A: Not in the current schema. The actor focuses on the structured "home record" data (specs, prices, addresses, builder). Open houses + lot maps + tour links require deeper page parsing — open an issue if you need them.

Q: Is the data refreshed in real time? A: Each run pulls live data from NewHomeSource as of run time. There's no caching; if you run the actor at 9am and again at 9pm, you'll see any inventory changes between those snapshots. For continuous monitoring, schedule the actor with Apify scheduler.

Q: Does it pick up the QMI (Quick Move-In) homes vs floor plans? A: Both. The community detail page extracts the home list which includes spec/QMI homes and buildable plans; both are emitted as rows. The Status field distinguishes them (e.g. QMI-flagged homes vs plans).

---

Support

• Bug reports / feature requests: open an issue at the GitHub repo or use the Issues tab on the Apify Store listing.
• Custom field requests (e.g. add open-house dates, lot maps, virtual tour URLs): contact via the Apify Store messaging.
• Email: muhamed.didovic@gmail.com

---

Additional Services

Need something off-the-shelf doesn't cover? Custom services available:

• URL-driven scraping — scrape specific community / builder URLs instead of state-wide
• Incremental / change-detection runs — diff against last run, emit only new + changed listings
• Builder enrichment — augment rows with builder portfolio data, ratings, license info
• Other real-estate sources — Zillow, Redfin, Trulia, Realtor.com, broker-direct sites
• Data delivery to your warehouse — Snowflake / BigQuery / S3 / Postgres direct push

Reach out via the Apify Store contact or email.

---

Explore More Scrapers

• Capterra Software Reviews Scraper — product / reviews / category / compare URLs, 4-shape output
• TrustRadius Reviews Scraper — vendor + reviews + category + best-of-lists
• TotalJobs Jobs Search Scraper — UK jobs by keyword/location/URL
• Stepstone Jobs Search Scraper — DACH + EU jobs by URL/keywords

---

⚠️ Disclaimer

This Actor accesses publicly available data on NewHomeSource.com for legitimate research, market intelligence, and business-analysis purposes. NewHomeSource.com is operated by Builders Digital Experience, LLC, a subsidiary of Move, Inc. This Actor is not affiliated with, endorsed by, or sponsored by NewHomeSource, Builders Digital Experience, or Move, Inc. All trademarks are the property of their respective owners.

Use of this Actor must comply with NewHomeSource's Terms of Service and all applicable laws including data protection regulations (GDPR, CCPA, etc.). The Actor's authors are not responsible for any misuse. Users must:

• Respect rate limits and avoid overloading NewHomeSource's infrastructure
• Not use scraped data to violate user privacy or terms
• Use the data in compliance with applicable jurisdictions
• Not republish scraped content in violation of copyright
• Not impersonate, harass, or contact builders or sellers via scraped phone numbers without their consent

We do not store any scraped data; the Actor returns it directly to your Apify dataset for your authorized use.

---

SEO Keywords

newhomesource scraper, newhomesource.com scraper, new home listings scraper, new construction homes data, new homes for sale scraper, home builder data scraper, real estate listings api, new construction listings api, builder directory scraper, floor plans scraper, community listings scraper, MLS alternative new construction, real estate market data, housing inventory data, new build inventory scraper, residential construction data, home builder leads, real estate data extraction, real estate web scraping, Apify scraper, no-code scraper, JSON CSV real estate export, US new homes data, property data api