# Website Sales Opportunity Analyzer (`moving_beacon-owner1/website-sales-opportunity-analyzer`) Actor

Identify and rank publicly observable website sales opportunities, with every finding backed by concrete on-page evidence, severity, and a recommended action.

- **URL**: https://apify.com/moving\_beacon-owner1/website-sales-opportunity-analyzer.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:** Lead generation, SEO tools, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $9.99 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Sales Opportunity Analyzer

Point this Actor at any website (or a list of them) and it returns a list of **publicly observable sales opportunities** — no HTTPS, missing SEO metadata, no contact form, no online booking, thin social presence, no analytics, no structured data — each ranked and, crucially, **backed by concrete evidence pulled from the page itself**. Every finding cites the observation that triggered it; the Actor never invents conclusions.

### What does this Actor do?

For each target URL it:

1. **Fetches the site** — the homepage plus `robots.txt`, `sitemap.xml`, and (optionally) a few contact/about pages to gather more contact info.
2. **Analyzes public signals** — HTTPS, page title/meta description, headings, contact form, booking widget, e‑commerce, CMS/technologies, analytics, social links, structured data and basic SEO.
3. **Derives findings** — turns the observed gaps into a scored, prioritised list of opportunities, each with evidence, a severity, and a recommended action.

It produces **one dataset record per URL**, with an auditable `opportunityScore` and `priority`.

### Why use it?

- Agencies and freelancers selling web design, SEO, reputation, analytics or booking systems get a **qualified, pre‑scored assessment** of a prospect's site instead of a manual audit.
- Every finding ships with the *evidence* behind it, so your outreach can reference a real, checkable fact ("your site has no contact form on the pages we checked").

### How to use it

1. Provide a single **`url`**, a list of **`urls`**, or Apify **`startUrls`**.
2. Optionally set **`maxPages`** to control how many extra contact/about pages are crawled per site (0 disables the extra crawl).
3. Run the Actor and download the dataset as JSON, CSV or Excel.

### Input

| Field | Type | Description |
| --- | --- | --- |
| `url` | string | A single website to analyze. |
| `urls` | array | A list of websites to analyze (one record per URL). |
| `startUrls` | array | Apify request-list sources (`{ "url": "…" }`). |
| `maxPages` | integer | Extra contact/about pages to crawl per site (default 2, 0 disables). |
| `proxyConfiguration` | object | Proxy settings (residential helps with bot protection). |
| `cookies` | string | Optional Cookie header to replay on every request. |

At least one of `url` / `urls` / `startUrls` is required.

#### Input example

```json
{
  "urls": ["https://example.com", "https://another-site.com"],
  "maxPages": 2,
  "proxyConfiguration": { "useApifyProxy": true }
}
```

### Output

One record per URL. Fields include the fetched signals — `url`, `httpStatus`, `reachable`, `https`, `title`, `metaDescription`, `headings`, `contactInfo` (`emails`, `phones`, `hasContactForm`), `booking`, `ecommerce`, `cms`, `technologies`, `socialLinks`, `structuredData`, `sitemap`, `robots`, `seoSignals` — plus the derived `findings`, `findingCount`, `opportunityScore` and `priority`.

Each entry in `findings` has: `finding` (human label), `opportunity` (machine tag), `severity`, `evidence`, `recommendedAction`, and `sourceUrl`.

#### Output example

```json
{
  "url": "http://weak-example.com",
  "httpStatus": 200,
  "reachable": true,
  "https": false,
  "title": null,
  "contactInfo": { "emails": [], "phones": [], "hasContactForm": false },
  "findings": [
    {
      "finding": "Website not served over HTTPS",
      "opportunity": "no_https",
      "severity": "high",
      "evidence": "Final URL uses http://",
      "recommendedAction": "Install an SSL certificate",
      "sourceUrl": "http://weak-example.com"
    }
  ],
  "findingCount": 6,
  "opportunityScore": 41,
  "priority": "MEDIUM"
}
```

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

### Detected opportunities

`no_https`, `missing_title`, `missing_meta_description`, `weak_title`, `no_h1`, `not_mobile_ready`, `no_contact_form`, `no_public_email`, `no_booking`, `no_social_presence`, `no_analytics`, `no_structured_data`, `website_unreachable`.

### Sources & configuration

- **The target websites themselves** — only publicly served HTML, `robots.txt` and `sitemap.xml` are fetched. No authentication is bypassed.
- **Environment variables** — none required. The Apify Proxy password is injected by the platform.

# Actor input Schema

## `url` (type: `string`):

A single website to analyze, e.g. 'https://example.com'. Use this for a one-off check.

## `urls` (type: `array`):

A list of website URLs to analyze (one record per URL).

## `startUrls` (type: `array`):

Apify request-list sources. Accepts objects like { "url": "https://example.com" }.

## `maxPages` (type: `integer`):

How many extra contact/about pages to fetch per site to gather more contact info (0 disables the extra crawl).

## `proxyConfiguration` (type: `object`):

Proxy settings. Residential proxies help with sites behind bot protection.

## `cookies` (type: `string`):

Optional Cookie header string to replay on every request (for sites behind a challenge).

## Actor input object example

```json
{
  "url": "https://example.com",
  "maxPages": 2,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "url": "https://example.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/website-sales-opportunity-analyzer").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "url": "https://example.com" }

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/website-sales-opportunity-analyzer").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "url": "https://example.com"
}' |
apify call moving_beacon-owner1/website-sales-opportunity-analyzer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moving_beacon-owner1/website-sales-opportunity-analyzer"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/36mNFece1CmkfC7mH/builds/zJ3YTpE7bwzXtioU4/openapi.json