Business Website Enricher

What it does

Enriches one user-provided official public business domain from its homepage. It extracts an organization name, description, and (if explicitly declared) company logo URL using schema.org Organization/LocalBusiness JSON-LD, Open Graph metadata, HTML description, and page title. It does not discover leads, search engines, people, or additional pages.

Who it is for

B2B sales ops, CRM data quality teams, and market researchers updating basic company profiles from official sources.

Input example (one domain)

{"domain":"example.com"}

The Apify input form prefills only example.com. Production use should substitute the official business's domain. Bare domains and domain-only https:// URLs work; paths, ports, IP addresses, and logins do not.

Output example

This example illustrates the field structure and is not a claim that the example domain contains this data.

{
  "domain": "sample-business.example",
  "company_name": "Sample Business",
  "description": "Sample Business provides commercial building services.",
  "logo_url": "https://sample-business.example/assets/logo.png",
  "source_url": "https://sample-business.example/",
  "status": "ok",
  "error": null
}

Missing fields are null, not guesses. status is ok if any profile field is found or no_data if none is found. Input/network/robots errors produce a plain-language log message with nonzero exit code and no result item; tracebacks are suppressed.

Limits and source policy

• One domain, one homepage per run; up to 1 MB of HTML, three same-site redirects, and nine seconds per HTTP request.
• Official public pages only: no login, LinkedIn, personal-data collection, search engine use, headless browser, or JavaScript rendering.
• HTTPS first; HTTP is attempted only if HTTPS fails at the connection layer. Apex/www redirects only. Private/non-public DNS addresses, IP literals, unusual ports, off-site redirects, and non-HTML pages are blocked.
• robots.txt is checked before homepage retrieval; if it disallows access or cannot be checked (except 404/410), retrieval stops. DNS is checked before requests, but this is not a hardened network-isolation boundary against DNS rebinding; deploy with network egress restrictions when processing untrusted domains.
• Structured data can be missing, inaccurate, or outdated. logo_url is recorded only from explicit JSON-LD logo, never inferred from a generic image. No human review or company identity verification is performed.
• Captures corporate fields only, not personal email addresses or individual contacts. Does not crawl subpages.

Apify configuration and dataset

This folder is an independently deployable Actor project. .actor/actor.json references the root input_schema.json. The main script uses the Apify REST API directly (no SDK) to read INPUT from the run's default key-value store and push one JSON record to the default dataset. It honors APIFY_API_BASE_URL, APIFY_INPUT_KEY, APIFY_DEFAULT_KEY_VALUE_STORE_ID, APIFY_DEFAULT_DATASET_ID, and APIFY_TOKEN when APIFY_IS_AT_HOME=true. Authorization is sent by bearer header, not in URLs.

For local testing, create storage/key_value_stores/default/INPUT.json with the input above, then run:

$python src/main.py

Or use ACTOR_INPUT_JSON='{"domain":"example.com"}' python src/main.py. Local results are appended to storage/datasets/default/000000001.json (or the next available numeric file). In Docker, mount the storage directory at /usr/src/app/storage for local testing. The storage directory is not included in this source deliverable.

Store placement and suggested pricing

Suggested Apify Store categories (max 3): Generate leads · Enrich company profiles · Company research. These are placement recommendations, not unsupported properties in actor.json; Apify is transitioning to platform-assigned category classification.

Suggested monetization: Pay per event (PPE), synthetic apify-default-dataset-item, $0.004 per emitted dataset item (~$4 per 1,000 items), plus an optional small actor-start fee if needed to cover run overhead. Set pricing in the Apify Console: this source package does not activate monetization. Each successful/no-data row is an item; errors emit no item. At one item per run, verify economics against actual run costs before Store publication. Do not assume this is a published or live rate.