# Website Technology Detector - CMS, Frameworks, Analytics & CDN (`plotpointtech/website-technology-detector`) Actor

- **URL**: https://apify.com/plotpointtech/website-technology-detector.md
- **Developed by:** [Plot Point Technologies](https://apify.com/plotpointtech) (community)
- **Categories:** Lead generation, Developer tools, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 website analyzeds

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 website is built with. Give it a list of domains and it returns, for each site, the content management system, ecommerce platform, JavaScript framework, analytics and advertising tags, chat and email-marketing tools, payment providers, CDN, hosting, web server and more, with the evidence for every finding.

The detector recognises **over 290 technologies in more than 40 categories**, including WordPress, Shopify, Wix, Squarespace, Webflow, Drupal, Joomla, Ghost, HubSpot CMS, BigCommerce, Magento and WooCommerce; React, Next.js, Vue, Nuxt, Angular, Svelte, Gatsby and Astro; Google Analytics 4, Google Tag Manager, Meta Pixel, TikTok Pixel, LinkedIn Insight, Hotjar, Segment, Mixpanel, Plausible, Matomo and Microsoft Clarity; HubSpot, Intercom, Drift, Zendesk, Crisp, Tawk.to, Klaviyo and Mailchimp; Stripe and PayPal; Cloudflare, Fastly, Akamai, Amazon CloudFront, Vercel and Netlify; plus fonts, cookie-consent tools, review widgets, search, A/B testing, error tracking and security services.

### Who uses it

- **Sales and business-development teams** qualifying leads by the tools a prospect already uses ("Shopify stores using Klaviyo", "WordPress sites without analytics").
- **Agencies and freelancers** preparing audits and pitches.
- **Software companies** sizing a market or tracking competitors' adoption.
- **Researchers and investors** studying technology trends across lists of companies.

### How it works

Each site's home page is fetched once over plain HTTP(S), the way a browser would request it. The detector then checks response headers, cookie names, meta tags (including the generator tag), the URLs of scripts and stylesheets, and known patterns in the HTML and inline scripts. No browser is launched, which keeps it fast and inexpensive. Matches based on headers, cookies, meta tags or script/stylesheet URLs are marked **high** confidence; matches based only on HTML patterns are marked **medium**. Some technologies imply others (for example, WooCommerce implies WordPress) and are added with the evidence "implied by ...".

### Input

| Field | What it does |
|---|---|
| Websites | URLs or bare domains. Duplicates are removed. |
| Include sites that could not be reached | Off by default, so you pay only for sites that answered. |
| Timeout per site | Seconds before giving up on a slow site. Default 25. |
| Sites checked in parallel | Default 10. |

### Output

One row per site: `url` (as entered), `finalUrl` (after redirects), `domain`, `status` (ok, http_error or blocked), `statusCode`, `title`, `description`, `language`, `technologyCount`, `technologies` (list of `{name, category, confidence, evidence}`), `categories` (category to technology names), quick columns `cms`, `ecommerce`, `frameworks`, `analytics`, `cdn` and `hosting`, plus `server`, `redirects`, `responseTimeMs` and `htmlBytes`.

### Notes and limits

- Only the home page is checked. Tools loaded later by JavaScript, only on inner pages, or only after cookie consent may be missed. A tag manager is detected, but the tags it loads afterwards usually are not.
- Sites behind a bot check (for example a Cloudflare challenge) return status `blocked`; their CDN and security headers are still reported, but page-level technologies are not. The detector does not try to get around such checks.
- Results reflect what the site serves at the time of the run.

Plot Point Technologies is not affiliated with Wappalyzer, BuiltWith or any of the technology vendors named above.

# Actor input Schema

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

Website URLs or bare domains, one per line (e.g. example.com). Each one is a result.

## `includeFailedSites` (type: `boolean`):

Add a row with status 'error' for sites that do not respond (each row is a billable result). Off by default: failures are only written to the log.

## `timeoutSecs` (type: `integer`):

Give up on a site after this many seconds.

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

How many sites to fetch at the same time.

## Actor input object example

```json
{
  "urls": [
    "https://wordpress.org",
    "https://nextjs.org",
    "https://www.nalgene.com"
  ],
  "includeFailedSites": false,
  "timeoutSecs": 25,
  "maxConcurrency": 10
}
```

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

// Run the Actor and wait for it to finish
const run = await client.actor("plotpointtech/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://nextjs.org",
        "https://www.nalgene.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("plotpointtech/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://nextjs.org",
    "https://www.nalgene.com"
  ]
}' |
apify call plotpointtech/website-technology-detector --silent --output-dataset

```

## MCP server setup

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