# ⚖️ Lawyer Leads Scraper - Law Firm Emails & Phones (`renzomacar/lawyer-leads-scraper`) Actor

Law firm leads by practice area and city: firm name, address, phone, website, emails and social profiles extracted live from each firm's own website. $8 per 1,000 lawyer leads, no subscription.

- **URL**: https://apify.com/renzomacar/lawyer-leads-scraper.md
- **Developed by:** [Renzo Madueno](https://apify.com/renzomacar) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.44 / 1,000 leads

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ⚖️ Lawyer Leads Scraper — Law Firm Emails & Phones

Legal is one of the highest-value B2B verticals there is: firms pay $50–$300 per *click* on Google Ads, which makes a verified law-firm contact list worth real money to anyone selling marketing, software, staffing or services to attorneys. This actor builds that list on demand — every law firm in a city, with **firm name, practice area, address, phone, website, emails harvested from the firm's own site, LinkedIn/social profiles, and Google review counts** — for $8 per 1,000 firms.

### The 60-second workflow

1. Pick practice areas: `law firm`, `personal injury attorney`, `immigration lawyer`, `family law attorney`, `criminal defense lawyer`, `estate planning attorney`...
2. Type the city: `"Houston, TX"`.
3. Run → download CSV/Excel/JSON, or pipe the dataset into Clay, Instantly, HubSpot or your own stack via API.

Each selected practice area runs as its own search, and firms appearing in several are deduplicated so you never pay for the same firm twice.

### Why sellers into legal use this instead of a list broker

- **Fresh, not warehoused.** The scraper discovers firms live from the Google Maps index and then crawls each firm's public website for contacts at run time. List brokers sell you last year's bar directory.
- **Practice-area precision.** A PI-firm CLE seller doesn't want tax attorneys. Search exactly the segment you monetize.
- **Buying signals included.** `reviewsCount` separates a 3-partner firm with 400 reviews from a solo who hung a shingle last month. `techStack` reveals firms still on a 2015 WordPress theme — a web-design agency's dream column. `rating` under 4.0 flags firms bleeding reputation (reputation-management pitch).
- **No per-seat platform.** Legal marketing agencies typically need 5–10 metros a quarter, not a $12k/year contract.

#### Typical buyers

Legal marketing & SEO agencies · legal-tech SaaS (practice management, intake, e-signature) · court reporting & deposition services · legal staffing/paralegal agencies · litigation funding originators · CLE providers.

### Output fields

`name`, `category`, `address`, `city`, `country`, `phone`, `website`, `email`, `emails[]`, `emailFound`, `socialProfiles{linkedin,facebook,instagram,twitter}`, `websitePhones[]`, `techStack[]`, `contactPageUrl`, `rating`, `reviewsCount`, `latitude`, `longitude`, `placeUrl`, `searchQuery`, `scrapedAt`.

The `contactPageUrl` field is worth highlighting for legal: many firms hide emails behind intake forms, and this gives your SDRs the direct link to the page that has the form.

### FAQ

**How many law firms can I scrape in one city?**
Each search returns what Google Maps exposes — usually 60–120 firms. A metro like Houston across 6 practice areas commonly yields 400–600 unique firms in one run. For maximum depth, add suburb-level custom queries (`personal injury attorney in Sugar Land, TX`).

**Do lawyer leads actually include emails?**
When the firm publishes one on its site, yes — the scraper checks the homepage plus contact/about pages (configurable up to 8 pages with `maxPagesPerSite`). Expect roughly 40–65% email coverage; big PI firms often use intake forms only, which is why every row still carries phone, website and `contactPageUrl`.

**Can I target solo practitioners vs. big firms?**
Sort the output by `reviewsCount`. Solos and small firms cluster under ~20 reviews; volume firms run into the hundreds. Combine with `techStack` to segment further.

**Does it find attorneys' personal LinkedIn pages?**
It captures the LinkedIn URL the firm links from its own website — usually the firm page, sometimes a partner's profile. It does not crawl LinkedIn itself.

**Will it work for non-US markets?**
Yes — `solicitor in Birmingham, UK`, `abogado laboralista in Barcelona` (set `language: "es"`), `avocat in Lyon` (`language: "fr"`) all work via custom queries.

**What's the cost for a full-metro sweep?**
A 500-firm run: $0.02 start + $4.00 in leads = **$4.02**. No subscription, no minimums, no credits that expire.

**Is scraping law firm contact info legal?**
The actor only gathers information firms publish publicly to attract clients — their Maps listing and their own marketing websites. It accesses nothing behind a login and collects no client or case data. How you *use* the list is on you: comply with CAN-SPAM/GDPR/your bar's solicitation rules if you're an attorney marketing to attorneys.

### Pricing

**$0.02 per run start** (2 GB) + **$0.008 per law firm delivered** = $8 per 1,000 leads. You're charged only for rows that land in your dataset — never for firms filtered out by `onlyWithWebsite`.

### Estate planning, elder law and probate firms

`estate planning attorney` is one of the seven presets, but the neighbouring practices — elder law, probate, trusts, guardianship, special-needs planning — are not. Reach them through **Custom search queries**, which replace the practice-area picker entirely:

```
elder law attorney in Scottsdale, AZ
probate attorney in Scottsdale, AZ
trust and estate attorney in Phoenix, AZ
guardianship attorney in Mesa, AZ
```

Each line is scraped as its own Google Maps search and the results are merged and deduplicated by business, so a firm that advertises as both "estate planning" and "probate" is delivered — and charged — once.

Practically, this corner of legal is dominated by solo and two-partner offices. They publish a real mailbox on their own site far more often than the volume PI shops do, so `emailFound` rates here run at the top of the range rather than the bottom.

### Bankruptcy, debt relief and anything outside the dropdown

The preset list is a convenience, not a limit. Any practice a firm markets itself under on Google Maps is reachable:

```
bankruptcy attorney in Phoenix, AZ
chapter 7 bankruptcy lawyer in Glendale, AZ
debt relief attorney in Tucson, AZ
foreclosure defense attorney in Phoenix, AZ
tax resolution attorney in Chandler, AZ
```

Two things worth knowing before you write the list:

- **One search caps at 500 firms** (`maxResults`), and Google Maps itself usually stops exposing results somewhere around 60–120 per query. Splitting a metro into four suburb-level queries returns materially more unique firms than one city-wide query at a higher cap.
- Setting `searchQueries` makes `location` and the practice-area picker inert. Put the city inside every line.

### Spotting firms on a stale website

The `techStack` column is what turns this dataset into a redesign pitch list. It is populated from the firm's own HTML, and only on strong signals — an asset path or a `<meta generator>` tag — never a guess:

- **Site platform** (one winner, or blank if two platforms both matched): WordPress, Wix, Squarespace, Webflow, Duda, GoDaddy Website Builder, Drupal, Joomla, Magento, Shopify.
- **Libraries and tooling**: Next.js, Vue.js, Angular, jQuery, Bootstrap, Tailwind CSS, Google Analytics, Google Tag Manager, HubSpot, Intercom, Zendesk, Stripe.

The segment that converts for web agencies is `jQuery` + `Bootstrap` with **no** Google Analytics and no Tag Manager: a site built years ago that nobody is measuring. Filter that against `rating` below 4.0 and you have a firm that is both invisible and unhappy about it.

# Actor input Schema

## `searchTerms` (type: `array`):

Which legal practice areas to find. Each selected practice area runs as its own search in your location; firms found in several are deduplicated.

## `location` (type: `string`):

City, region or country to search in, e.g. 'Houston, TX', 'Austin, TX', 'London, UK'.

## `searchQueries` (type: `array`):

Full searches, one per line (e.g. 'personal injury attorney in Sugar Land, TX'). When set, these override the category picker + location. Use several queries to cover multiple cities or neighborhoods in one run.

## `maxResults` (type: `integer`):

Maximum number of companies to find per search. One search typically yields up to ~120 companies.

## `maxPagesPerSite` (type: `integer`):

How many pages to check on each company website when hunting for emails (homepage, /contact, /about...). More pages = more emails found, slightly slower run.

## `onlyWithWebsite` (type: `boolean`):

Drop companies that have no website (they can never have an email). You are not charged for dropped companies.

## `includeGenericEmails` (type: `boolean`):

Keep every published address, including shared inboxes like info@, hello@ and contact@. Disable to drop only non-deliverable system addresses (noreply@, no-reply@, donotreply@, mailer-daemon@, postmaster@, webmaster@, hostmaster@, abuse@).

## `language` (type: `string`):

Language code for the discovery search (e.g. 'en', 'es', 'fr', 'de').

## Actor input object example

```json
{
  "searchTerms": [
    "law firm"
  ],
  "location": "Houston, TX",
  "maxResults": 5,
  "maxPagesPerSite": 1,
  "onlyWithWebsite": false,
  "includeGenericEmails": true,
  "language": "en"
}
```

# Actor output Schema

## `leads` (type: `string`):

Complete B2B leads (company, website, phone, address, emails, social profiles), one item per lead in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchTerms": [
        "law firm"
    ],
    "location": "Houston, TX",
    "maxResults": 5,
    "maxPagesPerSite": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("renzomacar/lawyer-leads-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchTerms": ["law firm"],
    "location": "Houston, TX",
    "maxResults": 5,
    "maxPagesPerSite": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("renzomacar/lawyer-leads-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchTerms": [
    "law firm"
  ],
  "location": "Houston, TX",
  "maxResults": 5,
  "maxPagesPerSite": 1
}' |
apify call renzomacar/lawyer-leads-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,renzomacar/lawyer-leads-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jeF9c9cEXTxWWYSED/builds/HQdYQL1ynjD1GbHkn/openapi.json