# Website Technology Detector (`mighty_monk/website-technology-detector`) Actor

Detect CMS, frameworks, analytics, payment providers, chat widgets, CDN, hosting, and JavaScript libraries from any website using Wappalyzer-style signature matching.

- **URL**: https://apify.com/mighty_monk/website-technology-detector.md
- **Developed by:** [Harsh](https://apify.com/mighty_monk) (community)
- **Categories:** Developer tools, SEO tools
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 result items

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Website Technology Detector

Detect the technology stack behind any website — CMS, frameworks, analytics, payment providers, chat widgets, CDN, hosting, and JavaScript libraries.

Built with **TypeScript**, **Crawlee**, and **Cheerio**, this Actor uses Wappalyzer-style signature matching against HTML content, HTTP headers, script tags, and meta tags.

### Features

- **70+ built-in signatures** for common technologies (WordPress, Shopify, React, Next.js, Google Analytics, Stripe, Intercom, Cloudflare, Vercel, and more)
- **Structured JSON output** per URL with categorized results
- **Retries, rate limiting, and session pool** to reduce blocking
- **Proxy support** via Apify Proxy (datacenter and residential)
- **Aggregated JSON report** saved to key-value store (`REPORT`)
- **Pay-per-result pricing** at **$0.003 per scanned URL**

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `urls` | `string[]` | — | Website URLs to scan (**required**) |
| `maxConcurrency` | `integer` | `5` | Parallel scans |
| `maxRequestsPerMinute` | `integer` | `60` | Rate limit |
| `maxRequestRetries` | `integer` | `3` | Retry count for failed requests |
| `requestHandlerTimeoutSecs` | `integer` | `60` | Per-URL timeout |
| `proxyConfiguration` | `object` | Apify Proxy on | Proxy settings |
| `useResidentialProxy` | `boolean` | `false` | Enable residential proxy group |

#### Example input

```json
{
  "urls": [
    "https://wordpress.org",
    "https://react.dev",
    "https://www.shopify.com"
  ],
  "maxConcurrency": 5,
  "maxRequestsPerMinute": 60,
  "maxRequestRetries": 3
}
```

More examples are in the [`examples/`](./examples) folder.

### Output

Each dataset item contains:

```json
{
  "url": "https://wordpress.org",
  "cms": "WordPress",
  "framework": null,
  "analytics": ["Google Analytics", "Google Tag Manager"],
  "paymentProviders": [],
  "chatWidgets": [],
  "cdn": "Cloudflare",
  "hosting": null,
  "jsFrameworks": ["jQuery"],
  "detectedTechnologies": ["Cloudflare", "Google Analytics", "Google Tag Manager", "PHP", "WordPress", "jQuery"],
  "statusCode": 200,
  "scannedAt": "2026-07-05T12:00:00.000Z"
}
```

A full run report is also stored at `REPORT` in the default key-value store.

### Detected categories

| Category | Examples |
|----------|----------|
| CMS | WordPress, Shopify, Drupal, Wix, Webflow |
| Framework | Next.js, Nuxt.js, Laravel, Django, ASP.NET |
| Analytics | Google Analytics, GTM, Hotjar, Segment, Facebook Pixel |
| Payment providers | Stripe, PayPal, Square, Klarna |
| Chat widgets | Intercom, Drift, Zendesk, Crisp, Tawk.to |
| CDN | Cloudflare, Fastly, Akamai, CloudFront |
| Hosting | AWS, Vercel, Netlify, Azure, WP Engine |
| JS frameworks | React, Vue.js, Angular, jQuery, Svelte |

### Local development

```bash
npm install
apify run
```

Run tests:

```bash
npm test
```

Build for production:

```bash
npm run build
```

### Deploy to Apify

```bash
apify login
apify push
```

### Pricing

- **$0.003 per result** (one scanned URL)
- Failed URLs that return an error record are also charged as a result event

### How it works

1. The Actor receives a list of URLs.
2. `CheerioCrawler` fetches each page (with retries, rate limiting, and optional proxy).
3. HTML, headers, scripts, and meta tags are matched against the built-in signature database.
4. Detected technologies are categorized and saved to the dataset.
5. A consolidated JSON report is written to the key-value store.

### Use cases

- Sales prospecting and lead enrichment
- Competitive intelligence
- Security and compliance audits
- Migration planning (CMS/framework discovery)
- Market research across website portfolios

### Limitations

- Detection is based on static page analysis (no browser rendering)
- Some client-side-only technologies may not be detected
- Heavily protected sites may require residential proxies

### License

ISC

# Actor input Schema

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

List of website URLs to scan for technologies (CMS, frameworks, analytics, payment providers, chat widgets, CDN, hosting, and JS libraries).

## `maxConcurrency` (type: `integer`):

Maximum number of pages scanned in parallel.

## `maxRequestsPerMinute` (type: `integer`):

Rate limit to reduce blocking risk.

## `maxRequestRetries` (type: `integer`):

How many times failed requests are retried before reporting an error.

## `requestHandlerTimeoutSecs` (type: `integer`):

Maximum time allowed for processing a single URL.

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

Apify Proxy settings used to avoid IP blocks while scanning.

## `useResidentialProxy` (type: `boolean`):

Adds Apify RESIDENTIAL proxy group for harder targets.

## Actor input object example

```json
{
  "urls": [
    "https://wordpress.org",
    "https://react.dev",
    "https://www.shopify.com"
  ],
  "maxConcurrency": 5,
  "maxRequestsPerMinute": 60,
  "maxRequestRetries": 3,
  "requestHandlerTimeoutSecs": 60,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "useResidentialProxy": false
}
```

# Actor output Schema

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

Dataset with per-URL technology detections.

## `report` (type: `string`):

Aggregated run report with all scan results.

# 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 = {
    "urls": [
        "https://wordpress.org",
        "https://react.dev",
        "https://www.shopify.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mighty_monk/website-technology-detector").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 = { "urls": [
        "https://wordpress.org",
        "https://react.dev",
        "https://www.shopify.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mighty_monk/website-technology-detector").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 '{
  "urls": [
    "https://wordpress.org",
    "https://react.dev",
    "https://www.shopify.com"
  ]
}' |
apify call mighty_monk/website-technology-detector --silent --output-dataset

```

## MCP server setup

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

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/t2vdfum55rCjfLhbz/builds/wf5HamCov6PjEsEHb/openapi.json