Niche Business Website Lead Qualifier

For agencies qualifying an existing prospect list before a website or booking-service proposal.

Qualify supplied business websites with niche keyword matches, contact and booking evidence, and transparent outreach-priority reasons. No lead discovery or outreach.

What it does

Visits the homepage and bounded same-origin contact/about/booking links. Extracts mailto/tel contacts, observed booking links, niche matches and page evidence. Priority is a transparent heuristic: 50 for no observed booking, 20 for no mailto/tel contact, 20 for HTTP, 10 for a keyword match. A niche mismatch scores zero; incomplete coverage has no score.

Quick start

Paste the example below into Input, run the Actor, then open REPORT for a readable HTML report or SUMMARY for run coverage and history status. Dataset output has one row per supplied businesses entry, with nested records and changes. Export JSON for full nested detail; CSV is best for summary fields.

{
  "businesses": [
    {
      "id": "demo",
      "name": "Example website",
      "url": "https://example.com/"
    }
  ],
  "nicheKeywords": [],
  "maxPagesPerBusiness": 2
}

Inputs

Each businesses object requires url; id and name are optional. nicheKeywords is an optional list of literal phrases. maxPagesPerBusiness defaults to 2 (1–3).

Supply 1–100 source objects. URLs must be public HTTP(S) on standard ports without credentials. timeoutSecs is 2–30 per request (default 15), maxRedirects 0–5 (default 3), and delayMillis 100–5000 between requests (default 250). Redirect destinations and DNS answers are validated; private and reserved network addresses are blocked. Response bodies are capped at 4 MB.

Results and interpretation

status is observed, baseline, unchanged, changed or unknown. sourceComplete distinguishes complete coverage from partial/failed evidence. records contains observations; facts provides summary metrics; issues and the report explain limitations. changeCounts gives full counts; changes includes at most 100 detailed changes per input, with changesTruncated when capped. The HTML report previews 20 changes and 10 records. SUMMARY.complete means all inputs were attempted, while coverageComplete means all sources were reliable.

Pricing

$15 per 1000 completed source checks ($0.015 per business-qualified event), plus Apify platform usage and the listed Actor-start event. A completed check can return unknown or problem evidence; it still incurs the custom check event. Transport/security exceptions with an error have no custom check charge. The Actor-start event is $0.00005 per GB of allocated memory, minimum one event. Use the run spending limit to bound charges; the report identifies partial budget runs. The Apify pricing tab is authoritative.

Coverage limits

Supplied websites only: no business discovery, email verification, outreach or guarantee of buying intent. Static HTML only; embedded apps, text-only contact details and unvisited pages may contain functionality this check does not see.

HTTP requests only. No CAPTCHA bypass, credentials, proxy subscription, external AI key, notifications or outbound messages are included. Use Apify schedules and your own integrations to consume changes. Reports show source evidence, not guaranteed business outcomes.

Troubleshooting and support

For unknown results, inspect issues and the source response before changing your workflow. Increase pagination limits only when needed. Retry rate limits later with a longer delay. Use a new monitor key when intentionally redefining a watchlist. Open an issue from this Actor's Issues tab with the run ID, expected behavior and a public reproducible input; omit tokens and personal data.

Local development

Node.js 22+. Run npm ci, npm test, npm run check, then npm start with an Apify INPUT record. Tests cover source fixtures, incomplete coverage, history, HTTP safety, report escaping and charging boundaries. Cloud release evidence is recorded separately in RELEASE.md in the local project.