# Website Intelligence (`moving_beacon-owner1/website-intelligence`) Actor

Universal Website Intelligence — extract structured, observable website data including technology stack, SEO, contact details, social links, analytics, structured data, robots.txt, and sitemap information.

- **URL**: https://apify.com/moving\_beacon-owner1/website-intelligence.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:** Developer tools, SEO tools, Lead generation
- **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 Intelligence

A reusable, structured **website analysis** Actor — the foundation other actors build on. Give it one or more URLs and it returns the **raw structured intelligence** for each site: HTTP status, title, meta description, headings, links, images, CMS, technologies, analytics, advertising, social links, contact info, structured data, `robots.txt`/`sitemap.xml` summaries and basic SEO signals. No scoring, no opinion — just what is publicly observable on the page.

### What does this Actor do?

For each target URL it fetches the homepage (and, optionally, `robots.txt`, `sitemap.xml`, and a few contact/about pages) and extracts a single **structured report**:

- **Identity & content** — final URL, HTTP status, HTTPS, title, meta description, headings, links, images.
- **Stack** — CMS, technologies, analytics platforms, advertising pixels, e‑commerce and booking signals.
- **Contact & social** — emails, phones, contact-form presence, and social profile links.
- **Discoverability** — structured data (schema.org types), `robots.txt` and `sitemap.xml` summaries, and SEO signals (title length, H1 count, viewport, canonical, Open Graph, image alt coverage).

It produces **one record per URL**.

### Why use it?

- A clean, consistent **structured snapshot** of any website that you can feed into lead scoring, competitive analysis, tech-stack research, or your own downstream Actors.
- Because it only reports observable facts, the output is auditable and safe to build on.

### How to use it

1. Provide a single **`url`**, a list of **`urls`**, or Apify **`startUrls`**.
2. Toggle **`checkRobots`**, **`checkSitemap`** and **`crawlContactPages`** as needed (all default on).
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": "…" }`). |
| `checkRobots` | boolean | Fetch & summarise `robots.txt` (default true). |
| `checkSitemap` | boolean | Fetch & summarise `sitemap.xml` (default true). |
| `crawlContactPages` | boolean | Crawl a few contact/about pages for more contact info (default true). |
| `maxPages` | integer | Max extra contact/about pages per site (default 2). |
| `proxyConfiguration` | object | Proxy settings. |
| `cookies` | string | Optional Cookie header to replay on every request. |

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

#### Input example

```json
{
  "url": "https://example.com",
  "checkRobots": true,
  "checkSitemap": true,
  "crawlContactPages": true
}
```

### Output

One structured record per URL. Keys include: `url`, `status`, `reachable`, `https`, `title`, `metaDescription`, `headings`, `links`, `images`, `cms`, `technologies`, `analytics`, `advertising`, `ecommerce`, `booking`, `contact` (`emails`, `phones`, `hasContactForm`, `formCount`), `socialLinks`, `structuredData`, `seo`, `robots`, `sitemap`, `domain`.

#### Output example

```json
{
  "url": "https://acme.example",
  "status": 200,
  "reachable": true,
  "https": true,
  "title": "Acme Widgets Co.",
  "cms": ["WordPress"],
  "technologies": ["WordPress"],
  "analytics": { "Google Analytics": true },
  "socialLinks": { "linkedin": "https://www.linkedin.com/company/acme-widgets" },
  "contact": { "emails": ["sales@acme.example"], "phones": [], "hasContactForm": false, "formCount": 0 },
  "structuredData": ["Organization"],
  "robots": { "exists": true, "hasSitemap": true, "disallowCount": 1 },
  "sitemap": { "exists": true, "urlCount": 2 },
  "seo": { "titleLength": 16, "h1Count": 1, "hasViewport": true, "hasCanonical": false }
}
```

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

### 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'.

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

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

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

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

## `checkRobots` (type: `boolean`):

Fetch and summarise the site's robots.txt (existence, sitemap directive, disallow count).

## `checkSitemap` (type: `boolean`):

Fetch and summarise the site's sitemap.xml (existence, URL count).

## `crawlContactPages` (type: `boolean`):

Also fetch a few contact/about pages to gather more emails, phones and social links.

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

Maximum number of extra contact/about pages to crawl per site when the above is enabled.

## `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://datavyn.com",
  "checkRobots": true,
  "checkSitemap": true,
  "crawlContactPages": true,
  "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://datavyn.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/website-intelligence").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://datavyn.com" }

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/website-intelligence").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://datavyn.com"
}' |
apify call moving_beacon-owner1/website-intelligence --silent --output-dataset

```

## MCP server setup

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

```

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/cBsHdNirnozRQgxKM/builds/I7ett50SOY0bYbd9Y/openapi.json