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

Find out what a list of websites is built with: CMS, online shop platform, JavaScript framework, analytics, tag managers, chat widgets, payment providers, CDN and web server. One request per site, no browser needed.

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

## Pricing

from $0.60 / 1,000 website checkeds

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

Find out what a list of websites is built with. For each site you get its CMS or site builder, online shop platform, JavaScript frameworks, analytics and advertising tags, marketing tools, live chat, payment providers, CDN, hosting and web server, with version numbers where the site shows them.

It reads each site's home page once, the way any visitor's browser does, and recognises more than 140 technologies from the page's HTML, response headers and cookie names. No browser is used, so thousands of sites take minutes and cost very little.

Use it to:

- qualify leads: find every company in a list that runs Shopify, WordPress, HubSpot or Intercom
- size a market: how many sites in a niche use a competitor's product
- research competitors' marketing and analytics tools
- audit your own or a client's sites for outdated or unexpected software
- enrich a CRM with each account's tech stack

### Input

| Field | What it does |
|---|---|
| **Websites** | One per line: a domain such as `example.com`, or a full address. The page at that address is the one checked. |
| **Obey robots.txt** | On by default: a website whose robots.txt asks crawlers not to read the page is skipped and not charged for. |

```json
{
    "websites": ["wordpress.org", "shopify.com", "https://vercel.com/"]
}
```

### Output

One record per website:

```json
{
    "input": "wordpress.org",
    "domain": "wordpress.org",
    "url": "https://wordpress.org/",
    "title": "Blog Tool, Publishing Platform, and CMS – WordPress.org",
    "description": "Open source software which you can use to easily create a beautiful website, blog, or app.",
    "language": "en-us",
    "technologyCount": 4,
    "technologyNames": ["WordPress", "Google Analytics", "Google Tag Manager", "nginx"],
    "cms": "WordPress",
    "ecommerce": null,
    "frameworks": [],
    "analytics": ["Google Analytics", "Google Tag Manager"],
    "server": "nginx",
    "cdn": null,
    "hosting": null,
    "technologies": [
        { "name": "WordPress", "category": "CMS", "version": "6.8" },
        { "name": "Google Analytics", "category": "Analytics", "version": null },
        { "name": "Google Tag Manager", "category": "Tag manager", "version": null },
        { "name": "nginx", "category": "Web server", "version": null }
    ],
    "scrapedAt": "2026-11-18T12:00:00.000Z"
}
```

- `technologies` is the full list, each with its category and, where the site reveals it, its version.
- `technologyNames` is the same list as plain names, convenient for filtering a spreadsheet.
- `cms`, `ecommerce`, `server`, `cdn` and `hosting` are the first technology found in that group, or `null`. `frameworks` and `analytics` list all of them.
- `url` is the page actually read, after any redirects.

Categories: CMS, Website builder, Static site generator, E-commerce, JavaScript framework, JavaScript library, CSS framework, Fonts and icons, Analytics, Tag manager, Advertising, A/B testing, Marketing automation, Forms and scheduling, Live chat, Payments, Consent management, Security, Error tracking, Video, Maps, Reviews, CDN, Hosting, Web server, Programming language and Web framework.

A `SUMMARY` record in the run's key-value store lists any websites that could not be read and why.

### Pricing

Pay per result. You are charged once for each website saved to the dataset, at the per-result price shown on this page.

A website that could not be read (it did not answer, refused the request, or its robots.txt does not allow it) is not saved and not charged for; it is listed in the log and the summary. Lines that are not website addresses and repeated websites cost nothing. The run stops as soon as it reaches the maximum charge you set for it.

### Limits

- Only the one page is read, without running its JavaScript. A tool that a site loads later, on other pages, or only after a visitor accepts cookies will not be seen.
- A site can hide what it runs. An empty list means nothing was recognised, not that nothing is used.
- Detection works from tell-tale signs such as script addresses and header names. It is reliable for the technologies listed, but it cannot name custom or in-house software.
- Some sites refuse automated requests. The Actor identifies itself honestly and does not disguise itself or work around a refusal; such sites are reported as not read.
- At most 2 MB of each page is downloaded, and each request waits at most 20 seconds.

### Is this allowed?

The Actor reads one public page per website, identifies itself in its User-Agent, obeys robots.txt by default and paces its requests. It reads only what the site sends to every visitor.

# Actor input Schema

## `websites` (type: `array`):

One per line: a domain such as example.com, or a full address. The page at that address is the one checked.

## `respectRobotsTxt` (type: `boolean`):

Skip a website whose robots.txt asks crawlers not to read the page. Skipped websites are not charged for.

## Actor input object example

```json
{
  "websites": [
    "wordpress.org",
    "shopify.com",
    "vercel.com"
  ],
  "respectRobotsTxt": true
}
```

# Actor output Schema

## `websites` (type: `string`):

One record per website checked.

## `summary` (type: `string`):

Totals for the run and, for each batch of websites, how many results were saved and any error.

# 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 = {
    "websites": [
        "wordpress.org",
        "shopify.com",
        "vercel.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("properscraper/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 = { "websites": [
        "wordpress.org",
        "shopify.com",
        "vercel.com",
    ] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,properscraper/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/fNTLTtjO7T9fEu9eg/builds/gHm7cNV8bDBqDjOBR/openapi.json
