Caring.com Senior Living Directory Scraper
Pricing
Pay per usage
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
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 days ago
Last modified
Share
Extract structured public senior-living directory and provider data from Caring.com. The Actor accepts Caring.com directory URLs, direct provider-profile URLs, or a location from which it builds a bounded directory URL. Optional keywords can filter source-backed provider text; an empty keyword keeps every discovered provider.
Provider rows can include identity, care types, address, coordinates, phone, public website, rating and review counts, costs, services, amenities, accommodations, awards, photos, and bounded reviews. Every provider row includes its public Caring.com profile URL and scrape timestamp. Missing optional values are omitted instead of guessed.
Input
searchUrls: public Caring.com/senior-living/or/senior-care/directory URLs.providerUrls: direct public Caring.com provider URLs, combined with any discovered URLs.location: optional location used to construct one directory URL when no URL is supplied.keywords: optional local filter across provider identity, category, care types, summary, and address.maxResults: hard cap from 1 to 100 provider records.maxReviewsPerProviderandmaxPhotosPerProvider: per-record content caps.maxConcurrency,requestDelayMillis,maxRetries,maxPageMbytes, andmaxRunMillis: bounded runtime controls.maxContactPages: optional same-host public pages to inspect on the provider website for literal published emails. The default is0, so this enrichment is off unless requested.
Only public pages are requested. The Actor does not sign in, submit forms, use private APIs, guess contact details, or bypass CAPTCHA, WAF, paywall, geofence, or device barriers. If a run cannot save any valid provider, it records an explicit diagnostic and fails rather than presenting an empty dataset as success.
Output
Provider rows use recordType: "provider", found: true, and dataAvailable: true. Optional contact enrichment adds emails, emailSourceUrls, and an explicit non-verification status. Diagnostic rows use recordType: "diagnostic", found: false, and are never counted as providers. OUTPUT_SUMMARY reports discovery, filtering, saved-provider, email, diagnostic, and completion counts.
Local development
Use the public data lawfully and follow Caring.com and linked provider-site terms. Public provider pages can change, so validate the source URLs for decisions that require current or authoritative information.
