Local Service Growth Agent
Pricing
from $5.00 / 1,000 results
Local Service Growth Agent
Turns public local-service websites, directory pages, review profiles, and lead files into workflow-ready growth actions.
Pricing
from $5.00 / 1,000 results
Rating
0.0
(0)
Developer
Tony Le
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
What does Local Service Growth Agent do?
Local Service Growth Agent turns public service-business websites, directory pages, review profiles, and optional uploaded lead files into workflow-ready growth actions. It is an API-style Apify Actor for finding prospect leads, stale follow-ups, local SEO fixes, review issues, competitor service gaps, blocked sources, and summary rows.
It does not log into CRMs, Google Business Profile, email, or ad platforms. The Actor works from public URLs and optional files you provide.
Why use Local Service Growth Agent?
Most lead and SEO scrapers export raw pages. This Actor produces action rows that a local-service owner, agency, or operator can triage immediately.
Use it to:
- Turn directory pages into prospect lead rows with service and location evidence
- Identify stale uploaded leads that need follow-up
- Find local SEO gaps such as missing titles, descriptions, or contact paths
- Compare competitor pages against your own public service signals
- Flag weak public review patterns when ratings are available in page text
- Keep scheduled monitoring, API access, integrations, proxy configuration, and run logs inside Apify
What data can Local Service Growth Agent extract?
| Field | Type | Description |
|---|---|---|
recordType | string | prospect_lead, follow_up_task, review_action, local_seo_action, competitor_gap, blocked_or_unavailable, or summary |
priority | string | critical, high, medium, or low |
confidence | string | Deterministic confidence in the row |
actionTitle | string | Short action label for operators |
recommendedNextStep | string | Suggested manual next step |
evidence | array | Structured facts used to produce the row |
targetName | string | Lead, business, or profile name when available |
targetWebsite | string | Target website when found |
reviewRating / reviewCount | number | Review signals parsed from source text |
aiSummary / aiDraft | string | Optional AI enrichment when runMode is ai |
How to scrape local service sources
- Open the Actor input tab.
- Add
serviceCategories, such asplumbing,drainage, orroofing. - Add target
locations, such asaucklandorwellington. - Provide at least one source: a business website, competitor URL, directory URL, review profile URL, or uploaded lead CSV key.
- Keep
runModeasstandardfor deterministic rows, or chooseaiand provide AI settings for summaries and drafts. - Run the Actor and download the default dataset.
How much will it cost to scrape local service sources?
Cost depends mainly on the number of URLs fetched and the size of each page. The Actor uses HTTP requests and HTML parsing rather than a browser by default, so standard-mode runs should be lightweight for public pages that return normal HTML.
AI mode may add separate model-provider costs and should be limited with aiMaxRows when scanning many sources.
Input
See the input tab for full configuration options. The key fields are:
businessName: business or client being analyzedbusinessWebsite: own public website pageserviceCategories: service terms to matchlocations: location terms to matchcompetitorOrDirectoryUrls: competitor, directory, or listing pagesreviewProfileUrls: public review pagesexistingLeadsFile: key-value store key for a CSV lead filerunMode:standardorai
Uploaded lead CSV or JSON files should include fields such as leadName, companyName, email, phone, website, location, serviceInterest, leadStatus, lastContactedAt, nextFollowUpAt, and notes. JSON files can be an array of leads or an object with a leads array.
Output
You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.
Example rows:
[{"recordType": "prospect_lead","priority": "high","confidence": "high","actionTitle": "Review local prospect: North Shore Plumbers","recommendedNextStep": "Review the target and decide whether to add it to CRM or an outreach list.","targetWebsite": "https://northshore.example","evidence": [{"label": "Matched services", "value": ["plumbing"]}],"status": "ready"},{"recordType": "summary","actionCount": 1,"blockedCount": 0}]
Tips
Use focused source URLs instead of a generic homepage when possible. Directory pages with structured business cards tend to produce better prospect rows than broad search-result pages.
Keep service and location terms short and lowercase-friendly. For example, use hot water, drainage, and auckland.
AI mode
Standard mode is deterministic and does not require an AI key. AI mode is optional and only enriches rows that already have deterministic evidence. If an AI provider call fails for a row, the Actor keeps the deterministic row unchanged.
FAQ, disclaimers, and support
Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.
If a source returns a blocked row, check the URL in a browser and replace it with another public source if needed. Use the Issues tab for feedback and the API tab for programmatic access.