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

{
  "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

{
  "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.