Caring.com Senior Living Directory Scraper avatar

Caring.com Senior Living Directory Scraper

Pricing

Pay per usage

Go to Apify Store
Caring.com Senior Living Directory Scraper

Caring.com Senior Living Directory Scraper

Extract public Caring.com senior living directory listings, provider profiles, costs, ratings, services, amenities, and reviews; independent and not endorsed by Caring.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

15 hours ago

Last modified

Categories

Share

Extract structured facility data from public Caring.com senior living and senior care directories. Supply city/state/care-type directory URLs, explicit provider profile URLs, or both.

The Actor uses lightweight HTTP requests and parses public structured page data. It does not submit lead forms, sign in, bypass access controls, or collect private resident information.

Data included

Each provider record can include:

  • Stable provider IDs, name, category, and care types
  • Public description, street address, city, state, county, postal code, and coordinates
  • Published phone number and provider website
  • Overall rating, review count, rating breakdown, and public reviews
  • Minimum and maximum published costs with currency
  • Service-level starting costs, room-type costs, and license identifiers
  • Resident capacity, amenities, accommodations, awards, and photos
  • Caring.com profile URL, originating directory URL, and scrape timestamp

Optional values that are not published are omitted rather than represented as null, empty strings, placeholders, or invented estimates.

Search a directory

{
"searchUrls": [
"https://www.caring.com/senior-living/assisted-living/new-york/new-york"
],
"maxResults": 10,
"maxReviewsPerProvider": 10,
"maxPhotosPerProvider": 10
}

Use any public Caring.com directory path under /senior-living/ or /senior-care/, including assisted living, memory care, nursing homes, independent living, continuing care, adult day care, and in-home care pages where Caring.com publishes a provider list.

Extract explicit provider profiles

{
"searchUrls": [],
"providerUrls": [
"https://www.caring.com/senior-living/new-york/new-york/sunrise-at-east-56th"
],
"maxResults": 1
}

Only public HTTPS Caring.com URLs are accepted.

Output example

{
"recordId": "provider-id",
"name": "Example Senior Living Community",
"careTypes": ["Assisted Living", "Memory Care"],
"formattedAddress": "123 Example St, New York, NY 10001",
"rating": 4.2,
"reviewCount": 4,
"minimumCost": 5000,
"costCurrency": "USD",
"amenities": ["Pets", "All Inclusive Rent"],
"providerUrl": "https://www.caring.com/senior-living/example",
"scrapedAt": "2026-01-01T00:00:00.000Z"
}

This illustrates the record shape. Production results always come from the requested live public pages.

Responsible limits

  • Results are capped at 100 profiles per run.
  • Concurrency is capped at 3 with at least 750 ms request pacing.
  • Every request uses bounded retries with exponential backoff.
  • The actor-side deadline is below five minutes, and unexpectedly large pages are rejected.
  • Records are deduplicated by stable public provider ID.
  • Direct public access is the default; Apify Proxy can be enabled in the input.

Caring.com content, pricing, availability, licenses, reviews, and contact details can change. Published cost fields are reproduced as provided and may not identify a billing period or all required fees. Verify important financial, medical, licensing, and availability decisions directly with the provider and relevant regulator.

You are responsible for complying with Caring.com's terms, robots directives, privacy requirements, and applicable law. Do not use the output for harassment, health profiling, deceptive marketing, or automated high-impact decisions.

Dataset access

The Actor writes records to the default Apify dataset. Export them through the Console or dataset API in JSON, CSV, Excel, XML, and other supported formats.

Support

When reporting a problem, include the public URL, input without secrets, run ID, and the expected field.