Local Business Website Health Monitor

Audit public business websites for technical health, contact, conversion, and SEO signals, then prioritize the strongest agency opportunities with transparent scores.

What this Actor does

Local Business Website Health Monitor is designed for local SEO agencies, web-design agencies, reputation-management providers, and sales teams. Give it a list of public business websites and it returns one normalized record per site with reachability, HTTP status, redirect count, HTTPS, response time, page title, meta description, mobile viewport, canonical URL, robots.txt, public business phones and emails, contact paths, forms, booking links, social profiles, sampled broken internal links, and transparent health and opportunity scores.

The Actor is also designed for repeat use. When changeDetection is enabled, it stores a compact snapshot in the Actor’s key-value store and reports material changes on later runs. Create an Apify task with the same URL list and schedule it daily or weekly to maintain a lightweight website watchlist.

Quick start

Provide public website URLs in websiteUrls:

{
  "websiteUrls": [
    "https://example-business.com",
    "https://another-business.com"
  ],
  "businessNames": [
    "Example Business",
    "Another Business"
  ],
  "maxUrls": 25,
  "crawlInternalLinks": true,
  "maxInternalLinks": 8,
  "auditContactPages": true,
  "websiteTimeoutSecs": 15,
  "slowResponseMs": 3000,
  "changeDetection": true,
  "maxConcurrency": 3
}

For a first run, keep the defaults. Increase maxUrls for a batch, reduce maxInternalLinks for faster audits, and keep concurrency moderate to be considerate of audited websites. The Actor rejects private, local, and internal network targets.

Output views

The default dataset includes three useful views.

View	Use
Health overview	Sort by reachability, response time, HTTPS, health score, opportunity score, and whether a site changed.
Agency opportunity signals	Review public phones and emails, contact paths, forms, booking links, metadata, broken links, and issue details.
Changes since prior run	Focus on websites whose observable status changed since a previous run of the same Actor.

The output contains both a healthScore and an opportunityScore. A higher health score means fewer observable issues. A higher opportunity score means the audit found more visible improvement opportunities that may be relevant to web, SEO, or maintenance services. These are prioritization aids, not guarantees of ranking, conversion, deliverability, or technical compliance.

Scoring

The health score starts at 100 and deducts points for observable issues, including unreachable pages, HTTP-only URLs, missing or weak metadata, missing mobile viewport, missing contact paths, missing public business contact details, missing booking flows, sampled broken internal links, and slow response. The score is bounded to 0–100. The opportunity score is derived from the health score with additional weight for missing contact and conversion paths, then bounded to 0–100.

Each record includes issueCodes and issueSummary so users can understand why a score was assigned. The monitor does not infer sensitive personal attributes and does not claim that a public contact value is independently verified.

Recurring monitoring

To use the Actor as a daily or weekly monitor, create a saved Apify task with a stable URL list and leave changeDetection enabled. Schedule the task at a frequency appropriate for the sites being checked. The Changes since prior run view is most useful after the first baseline run. If the URL list changes substantially, treat the next run as a new baseline for the added websites.

Responsible use

Audit only public URLs that you are permitted to inspect. Respect each website’s terms, robots guidance where practical, rate limits, privacy law, and applicable anti-spam and marketing rules. The Actor collects only publicly detectable business contact details from the supplied public pages; users remain responsible for verifying data and using it lawfully and responsibly.

Local development

npm install
npm test
npm start

A local run can use an INPUT.json file with the same fields as the Apify input schema. The hosted build uses the included Playwright/Chrome Dockerfile.

License

MIT