LandWatch Email Scraper

LandWatch Email Scraper for rural and recreational land broker contacts

The LandWatch Email Scraper collects publicly indexed contact emails belonging to the land brokers and listing agents who advertise rural property on landwatch.com. Supply keywords, an optional location and the email domains you want to keep, and it returns a deduplicated dataset of land broker leads. Every field is derived from Google's public index; nothing is fetched from the platform itself.

Yield note, stated plainly: LandWatch indexes land listings rather than broker profiles, so rows usually carry a broker email without a resolvable profile URL. In a measured live run, roughly 10 parsed result blocks produced 8 identified broker records, only 1 resolvable profile URL and 5 unique emails. That split is the defining characteristic of this Actor and it is explained honestly further down.

LandWatch is the rural and recreational end of the land market: hunting tracts, timberland, waterfront acreage, ranches and off-grid parcels. The people listing that inventory are often small independent brokerages and owner-agents rather than institutional firms, which is exactly why consumer email domains perform so well here. Land brokers publish their addresses because a 900-acre tract sells to a buyer who found the listing and picked up the phone.

Understanding the identity versus URL split

The number that matters most is 8 identified records against 1 profile URL, and it is worth being precise about what that means. LandWatch pages that reach Google's index are overwhelmingly property listings, and a listing title names the broker without exposing a URL-safe handle. So the LandWatch Email Scraper reads the broker's name from the title and their address from the block, but has nothing to build a canonical profile URL from.

This is why the LandWatch Email Scraper reports strong identity coverage next to almost no URL coverage.

The practical consequence is that you get a name plus an email, which is what an outreach sequence actually needs. What you do not reliably get is a clickable profile you can research before writing. If profile URLs matter to your workflow, the Land.com Email Scraper resolves them far more consistently.

This is a Google indexing outcome, not a defect in the Actor. No configuration change will manufacture a handle that Google never printed.

What the LandWatch Email Scraper actually does

The LandWatch Email Scraper builds Google queries with the site: operator against landwatch.com, fetches result pages through the Apify GOOGLE_SERP proxy with aiohttp, and parses each result block structurally. It locates the <h3> title, walks up to the smallest surrounding block, then runs a domain-filtered regular expression over that block's text. Structural parsing means it never depends on Google's CSS class names, so a markup change degrades a run instead of ending it.

It does not log into LandWatch, never uses a LandWatch API and never opens landwatch.com in a browser. There is no JavaScript rendering, no authentication and no cookies in the pipeline.

Key features of the LandWatch Email Scraper

Everything below ships with the LandWatch Email Scraper today; none of it is a roadmap item.

Feature	What it does for rural land broker prospecting
Query expansion	Each keyword x domain pair runs as a base query, a quoted query, an intitle: query and one variant per modifier, base queries first.
Global deduplication	A broker who lists forty tracts is written to the dataset once, not forty times.
Email normalisation	Handles name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width ＠ sign.
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character local parts.
Boundary-correct matching	@gmail.com will not match inside @gmail.company or @gmail.com.br.
Soft-wrap repair	Drops a hit that is only the tail of another email in the same result block.
Concurrency control	An asyncio worker pool with a shared stop signal on maxEmails.
Retries and block detection	Three attempts per page with exponential backoff, a fresh proxy session per request, and CAPTCHA or consent pages retried rather than counted as empty.
Failed-query requeue	Blocked or failed queries are retried once at the end of the run.
Resumable state	Key-value store state keyed by an input hash, saved on PERSIST_STATE, MIGRATING and ABORTING.
Whole-page fallback parser	A Google layout change degrades to emails without account details rather than to zero results.
Run summary	Pages fetched, blocked pages, retries and emails per page are logged.

Global deduplication deserves particular emphasis on a listing-driven source. One rural brokerage can hold hundreds of active tracts, so without deduplication a single agent would flood your dataset.

How the LandWatch Email Scraper works

A LandWatch Email Scraper run begins by reading your input and hashing it into a resumable state key. The query set is built by multiplying keywords by email domains and, when expandQueries is on, by every query modifier. A representative query looks like site:landwatch.com "hunting land" broker "@gmail.com" "Val Verde County".

The LandWatch Email Scraper fetches result pages concurrently through the Apify GOOGLE_SERP proxy and parses them block by block. Emails are extracted, normalised, domain-filtered and deduplicated globally before each lead is pushed to the dataset immediately. Runs stop as soon as maxEmails unique addresses have been collected, with the stop signal shared across all workers.

Free Apify plans are capped at 100 emails per run; paid plans are uncapped.

LandWatch Email Scraper input fields

Field	Type	Default	Meaning
keywords	array (required)	["land broker", "ranch for sale"]	Search terms describing the accounts you want
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com","@yahoo.com"]	Only emails on these domains are kept; the @ is optional
maxEmails	integer 1-10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email","contact","listing agent","inquiries","broker"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1-50	30	Page cap per query
maxConcurrency	integer 1-20	5	Parallel queries

Only keywords is required, so the LandWatch Email Scraper runs on defaults out of the box. Because listings dominate the index here, listing-flavoured keywords such as "hunting land" or "ranch for sale" outperform profile-flavoured terms.

Location targeting in the LandWatch Email Scraper

location is by far the most valuable input in this Actor, because rural land is a county-level business. A land broker's territory is measured in counties, not metros, and their listing copy says so. Running the LandWatch Email Scraper once per county or region produces dramatically cleaner lists than a single national sweep.

County phrases are the primary tool and should be your default here: "Val Verde County", "Marquette County", "Coos County", "Fentress County". Rural listing titles name the county constantly, because acreage, mineral rights and hunting regulations are all administered at county level. This is the single biggest difference between land prospecting and metro-driven commercial prospecting.

Named regions are the second tool and work unusually well on LandWatch: "Texas Hill Country", "Upper Peninsula", "Ozarks", "Cumberland Plateau", "Black Hills". Recreational land is sold on regional identity, so brokers write those phrases into their listings deliberately.

State phrases suit agricultural lenders, surveying firms and rural insurance brokers licensed statewide: "Montana", "Georgia", "Missouri". Pair a state-level location with countryCode: "US" so the search proxy resolves to the right index. Avoid metro names on this Actor; a query for "Dallas" will mostly miss the rural inventory LandWatch actually carries.

Example input JSON

{
  "keywords": ["hunting land", "ranch for sale", "timberland broker"],
  "location": "Texas Hill Country",
  "customDomains": ["@gmail.com", "@yahoo.com", "@outlook.com", "@hotmail.com"],
  "maxEmails": 150,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "listing agent", "inquiries", "broker"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

LandWatch Email Scraper output fields

Every dataset item written by the LandWatch Email Scraper carries all fourteen fields below.

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints
fullName	Display name parsed from a profile-style title; empty for non-profile results
username	URL-safe handle when LandWatch exposes one; otherwise null
profileUrl	Canonical account URL when a handle is known; otherwise empty
url	Direct platform link when exposed, else the profile URL
description	Bio or snippet text, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain, for example @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email
foundAt	ISO 8601 UTC timestamp

Expect most rows to have username: null and an empty profileUrl while still carrying a usable email and fullName. The example below shows the typical case first and the rarer resolved-handle case second, rather than pretending the split does not exist.

Example output JSON

[
  {
    "network": "LandWatch",
    "keyword": "hunting land",
    "query": "site:landwatch.com \"hunting land\" broker \"@gmail.com\" \"Texas Hill Country\"",
    "title": "312 Acres Hunting Land, Edwards County TX - Listed by Wade Ruskin | LandWatch",
    "accountName": "Wade Ruskin",
    "fullName": "Wade Ruskin",
    "username": null,
    "profileUrl": "",
    "url": "https://www.landwatch.com/edwards-county-texas-land-for-sale/pid/412876",
    "description": "312 acres high-fence hunting property, Edwards County. Showings: wade.ruskin.land@gmail.com",
    "email": "wade.ruskin.land@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-03-16T13:22:41Z"
  },
  {
    "network": "LandWatch",
    "keyword": "ranch for sale",
    "query": "site:landwatch.com \"ranch for sale\" contact \"@yahoo.com\" \"Texas Hill Country\"",
    "title": "1,140 Acre Working Ranch, Gillespie County TX | LandWatch",
    "accountName": "Hill Country Land Partners",
    "fullName": "Marla Devereaux",
    "username": null,
    "profileUrl": "",
    "url": "https://www.landwatch.com/gillespie-county-texas-farms-and-ranches-for-sale/pid/398210",
    "description": "Working cattle ranch with live water, Gillespie County. Enquiries to marla.devereaux.ranch@yahoo.com",
    "email": "marla.devereaux.ranch@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-03-16T13:23:17Z"
  },
  {
    "network": "LandWatch",
    "keyword": "timberland broker",
    "query": "site:landwatch.com intitle:\"timberland broker\" \"@gmail.com\" \"Texas Hill Country\"",
    "title": "Cal Brennerman - Timberland Broker | LandWatch",
    "accountName": "Cal Brennerman",
    "fullName": "Cal Brennerman",
    "username": "cal-brennerman",
    "profileUrl": "https://www.landwatch.com/cal-brennerman",
    "url": "https://www.landwatch.com/cal-brennerman",
    "description": "Timber and recreational tracts across central Texas. Contact cal.brennerman.timber@gmail.com",
    "email": "cal.brennerman.timber@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-03-16T13:24:03Z"
  }
]

Use cases for the LandWatch Email Scraper

Audience	How they use the LandWatch Email Scraper
Agricultural and farm credit lenders	Reach the brokers whose buyers need land, ranch or recreational-property financing.
Land surveyors	Prospect brokers in counties where boundary, plat and acreage work is routine.
Timber and mineral buyers	Find brokers listing timbered tracts and parcels with severed mineral rights.
Hunting-lease and recreational operators	Reach brokers who market high-fence, waterfowl and deer-lease inventory.
Rural insurance brokers	Target the agents whose clients need farm, ranch and outbuilding cover.
Title and closing firms	Build county-level lists of the brokers routing rural closings.
Fencing, water and land-improvement contractors	Reach brokers whose listings mention wells, fencing and access work.
Rural appraisal firms	Find the brokers who commission acreage and agricultural valuations.

The LandWatch Email Scraper is a top-of-funnel sourcing step rather than a whole go-to-market motion. Given the profile URL limitation, plan on enriching names yourself rather than expecting a research-ready profile link.

LandWatch Email Scraper examples

A farm credit lender building a Hill Country pipeline runs the LandWatch Email Scraper with keywords set to ["ranch for sale", "land broker"] and location "Texas Hill Country". They widen customDomains with @outlook.com and @hotmail.com, which matters more here than on commercial platforms because independent land brokers rarely run branded mail. Rows arrive with names and emails but mostly empty profileUrl, so the lender enriches by name and brokerage before outreach.

A surveying firm covering three rural counties runs the LandWatch Email Scraper three times with location set to "Val Verde County", "Edwards County" and "Real County". County-level runs match how land brokers describe their own territory, so relevance is far higher than a state-level sweep would give. Comparing dataset sizes shows where broker density justifies a field crew.

A timber buyer points the LandWatch Email Scraper at brokers listing timbered acreage across the Southeast. They set keywords to ["timberland broker", "timber tract", "hunting land"] and rotate location through "Ozarks", "Cumberland Plateau" and "Georgia". They then merge with the Land And Farm Email Scraper and deduplicate on email, since rural brokers commonly list on several land portals.

Responsible use of scraped land broker contacts

Everything the LandWatch Email Scraper returns was already published on a public web page and indexed by Google. That does not make every downstream use lawful, and knowing which rules apply to you is your responsibility. The notes below are practical guidance, not legal advice.

Under CAN-SPAM in the United States, commercial email must avoid deceptive headers and subject lines, identify itself as an advertisement where required, carry a valid physical postal address, and honour opt-out requests promptly. Under the GDPR and UK GDPR, a named individual's business address is still personal data, so you need a lawful basis, a genuine legitimate-interest assessment where you rely on one, transparency about the source, and a working route to object or erase. ePrivacy rules and several EU member states add consent requirements for electronic marketing beyond the GDPR baseline.

One point deserves extra care when you use the LandWatch Email Scraper. Because land brokers frequently use personal consumer mailboxes, an address in your dataset may be closer to a personal account than a corporate one, so keep messages professional, relevant and easy to opt out of. Hold possiblyTruncated rows out of a first send, keep a suppression list across runs, and retain query and foundAt as provenance.

Limitations of the LandWatch Email Scraper

LandWatch indexes land listings rather than broker profiles, so rows usually carry a broker email without a resolvable profile URL. In a measured live run, roughly 10 parsed blocks produced 8 identified records but only 1 profile URL and 5 unique emails. Plan your workflow around name-plus-email enrichment rather than around clickable profiles.

The LandWatch Email Scraper only finds accounts whose email is publicly visible in Google's index. A broker who keeps their address behind a contact form or inside an image will never appear, however many pages you fetch.

Google caps a single query at roughly 300 results, which is exactly why query expansion exists. Leaving expandQueries on turns one 300-result ceiling into dozens of them.

username and profileUrl are only populated when LandWatch exposes a handle in the Google result, which here is the exception rather than the rule. Those rows still carry accountName and often fullName. That is a Google limitation, not a bug.

possiblyTruncated: true means Google's snippet ellipsis touched the address and it may be incomplete. The LandWatch Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials. Free Apify plans stop at 100 emails per run, and results vary with keywords, domains and location, so no volume is guaranteed.

LandWatch Email Scraper FAQ

How many results should I expect from the LandWatch Email Scraper?

Moderate email volume with weak URL resolution: a measured live run produced 8 identified records, 1 profile URL and 5 unique emails per roughly 10 parsed blocks. LandWatch indexes land listings rather than broker profiles, so rows usually carry a broker email without a resolvable profile URL.

Why do I get names but not profile URLs?

Because the indexed pages are property listings. A listing title names the broker but exposes no URL-safe handle for the Actor to build a canonical profile URL from. You still get the name and the email, which is what an outreach sequence needs.

Can I make the LandWatch Email Scraper produce the missing profile URLs?

No. No configuration will manufacture a handle Google never printed. If profile links matter, use the Land.com Email Scraper, which resolves them far more consistently.

Does the LandWatch Email Scraper log into LandWatch?

No. It never logs in, never calls a LandWatch API and never opens landwatch.com in a browser. Every field comes from publicly indexed Google search results.

Is this an official LandWatch tool?

No. It is an independent Apify Actor and is not affiliated with, supported by or endorsed by LandWatch.

What keywords work best in the LandWatch Email Scraper?

Listing language beats profile language on this platform. "hunting land", "ranch for sale", "timberland broker" and "acreage for sale" outperform generic agent-directory phrasing.

Should the LandWatch Email Scraper use counties or metros in location?

Counties, almost always. Rural land markets are administered and described at county level, and named regions such as "Ozarks" are the strong second option. Metro names will mostly miss the inventory LandWatch carries.

Which email domains should I use with the LandWatch Email Scraper?

Widen past the defaults immediately: add @outlook.com and @hotmail.com to @gmail.com and @yahoo.com. Independent land brokers use consumer mailboxes at a much higher rate than commercial brokerages do.

What does possiblyTruncated mean?

Google's snippet cut the text with an ellipsis close enough to the address that it may be incomplete. Verify those rows before sending.

Will one busy brokerage flood my dataset?

No. The LandWatch Email Scraper deduplicates globally, so a broker with hundreds of active tracts appears once.

Does a LandWatch Email Scraper run resume if it is interrupted?

Yes. State lives in the key-value store keyed by an input hash, with saves on PERSIST_STATE, MIGRATING and ABORTING.

Do I need my own proxy?

No, but Apify proxy credentials are required, because the LandWatch Email Scraper uses the Apify GOOGLE_SERP proxy.

Related Actors

Actor	What it collects
LandWatch Email and Phone Number Scraper	Emails and phone numbers from LandWatch
LandWatch Phone Number Scraper	Public phone numbers from LandWatch
Apartment List Email Scraper	Public contact emails from Apartment List
ApartmentFinder Email Scraper	Public contact emails from ApartmentFinder
Apartments.com Email Scraper	Public contact emails from Apartments.com
Century 21 Agent Email Scraper	Public contact emails from Century 21
Coldwell Banker Agent Email Scraper	Public contact emails from Coldwell Banker
CommercialCafe Email Scraper	Public contact emails from CommercialCafe
CommercialSearch Email Scraper	Public contact emails from CommercialSearch
Compass Agent Email Scraper	Public contact emails from Compass
Crexi Email Scraper	Public contact emails from Crexi
Domain Agents Email Scraper	Public contact emails from Domain
Homes & Land Email Scraper	Public contact emails from Homes & Land
Homes.com Email Scraper	Public contact emails from Homes.com
HotPads Email Scraper	Public contact emails from HotPads
Keller Williams Agent Email Scraper	Public contact emails from Keller Williams
Land And Farm Email Scraper	Public contact emails from Land And Farm
Land.com Email Scraper	Public contact emails from Land.com
LoopNet Email Scraper	Public contact emails from LoopNet
OnTheMarket Email Scraper	Public contact emails from OnTheMarket
RealEstate.com.au Agents Email Scraper	Public contact emails from realestate.com.au
Realtor.ca Email Scraper	Public contact emails from Realtor.ca
Realtor.com Rentals Email Scraper	Public contact emails from Realtor.com
Redfin Rentals Email Scraper	Public contact emails from Redfin
RE/MAX Agent Email Scraper	Public contact emails from RE/MAX
Rent.com Email Scraper	Public contact emails from Rent.com
RentCafe Email Scraper	Public contact emails from RentCafe
Zillow Rentals Email Scraper	Public contact emails from Zillow
Zumper Email Scraper	Public contact emails from Zumper
Apartment List Email and Phone Number Scraper	Emails and phone numbers from Apartment List
ApartmentFinder Email and Phone Number Scraper	Emails and phone numbers from ApartmentFinder
Apartments.com Email and Phone Number Scraper	Emails and phone numbers from Apartments.com
Century 21 Email and Phone Number Scraper	Emails and phone numbers from Century 21
Coldwell Banker Email and Phone Number Scraper	Emails and phone numbers from Coldwell Banker
CommercialCafe Email and Phone Number Scraper	Emails and phone numbers from CommercialCafe
CommercialSearch Email and Phone Number Scraper	Emails and phone numbers from CommercialSearch
Compass Email and Phone Number Scraper	Emails and phone numbers from Compass
Crexi Email and Phone Number Scraper	Emails and phone numbers from Crexi
Domain Email and Phone Number Scraper	Emails and phone numbers from Domain
Homes & Land Email and Phone Number Scraper	Emails and phone numbers from Homes & Land
Homes.com Email and Phone Number Scraper	Emails and phone numbers from Homes.com
Keller Williams Email and Phone Number Scraper	Emails and phone numbers from Keller Williams

Leave a review

If the LandWatch Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.

Support

Questions about the LandWatch Email Scraper, bug reports or a request for a custom build: contact neurodata.apify@gmail.com.