Care.com Scraper avatar

Care.com Scraper

Pricing

Pay per usage

Go to Apify Store
Care.com Scraper

Care.com Scraper

Extract public Care.com caregiver search results and profiles, including rates, experience, services, ratings, checks, and reviews; independent and not endorsed by Care.com.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Coding Frontned

Coding Frontned

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Share

Extract structured data from publicly accessible Care.com caregiver search pages and public profiles. Search by supported care category and US city/state slug, or submit explicit public profile URLs.

The Actor uses lightweight HTTP requests and parses the structured data Care.com publishes in each page. It does not sign in, solve CAPTCHAs, access contact details, or cross a private-profile boundary.

What it extracts

Each dataset record can include:

  • Public profile and service identifiers
  • Display name, job title, care categories, city, state, and postal code
  • Public profile bio, years of experience, image, and availability
  • Hourly rate range, currency, and category-specific published rates
  • Overall rating, review count, and rating breakdown
  • CareCheck completion flag and published check status/date
  • Services, care age groups, qualities, credentials, and languages
  • Education, public badges, and public reviews
  • Canonical profile URL, originating search URL, and scrape timestamp

Unavailable optional values are omitted rather than replaced with empty strings, nulls, or invented placeholders.

Input

Search by category and location

{
"category": "babysitters",
"locationSlug": "new-york-ny",
"maxResults": 10,
"maxPages": 1,
"maxReviewsPerProfile": 10
}

Supported categories are babysitters, nannies, caregivers, pet-sitters, housekeepers, and tutors. The location uses the public Care.com URL slug, such as austin-tx.

Extract explicit profiles

{
"profileUrls": [
"https://www.care.com/p/rachels6792/cc"
],
"maxResults": 1,
"maxReviewsPerProfile": 10
}

Only public HTTPS URLs on care.com with the /p/.../... profile pattern are accepted.

Output example

{
"recordId": "public-profile-id",
"displayName": "Rachel S.",
"jobTitle": "Nanny",
"careTypes": ["Child Care", "Pet Care"],
"city": "New York",
"state": "NY",
"yearsExperience": 10,
"hourlyRateMin": 17,
"hourlyRateMax": 25,
"rateCurrency": "USD",
"rating": 5,
"reviewCount": 1,
"careCheckCompleted": true,
"services": ["Carpooling", "Craft Assistance", "Light Housekeeping"],
"profileUrl": "https://www.care.com/p/example/cc",
"scrapedAt": "2026-01-01T00:00:00.000Z"
}

Values above illustrate the record shape. Actor results always come from the requested live public pages.

Limits and responsible use

  • maxResults is capped at 100 and maxPages at 5.
  • Concurrency is capped at 3, with at least 750 ms pacing.
  • Requests use bounded retries with backoff and an actor-side deadline below five minutes.
  • Direct public access is the default; Apify Proxy can be enabled in the input.
  • Duplicate records are removed by the public profile identifier.
  • Unexpectedly large responses and invalid/off-site URLs are rejected.

Care.com can change its markup, URL formats, availability, or access policy without notice. Some fields differ by caregiver category. A CareCheck or background-check status is a platform-published attribute, not a safety guarantee or endorsement.

You are responsible for complying with Care.com's terms, robots directives, privacy rules, employment and anti-discrimination laws, and all applicable regulations. Do not use the output for harassment, surveillance, identity enrichment, automated eligibility decisions, or other harmful purposes. Collect and retain only the data you need.

Dataset access

Results are written to the default Apify dataset. Download them through the Console or dataset API in JSON, CSV, Excel, XML, and other supported formats.

Support

If a public page stops producing records, include the input (without secrets), run ID, affected public URL, and a short description of the expected field in your issue report.