# Website Tech Stack Detector (CMS, Analytics, CRM, E-commerce) (`pj_pai/website-tech-stack-detector`) Actor

- **URL**: https://apify.com/pj_pai/website-tech-stack-detector.md
- **Developed by:** [Rakesh Pai](https://apify.com/pj_pai) (community)
- **Categories:** Lead generation, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 websites

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 Tech Stack Detector (CMS, Analytics, CRM, E-commerce)

Detect the technologies behind any list of websites: CMS, e-commerce platform, analytics, tag managers, marketing automation and CRM, live chat, payments, JS frameworks, CDN and hosting. Returns grouped tech lists per domain for lead qualification.

**Data source:** the public homepage HTML and HTTP response headers of the websites you supply. Fetches one public page per website and matches 100+ technology fingerprints in the HTML, scripts, cookies and headers, with no login, proxy or browser. Results are returned as clean, flat JSON that is ready for spreadsheets, databases, BI tools and AI agents.

### What can you use it for?

- Find Shopify, WordPress or HubSpot users to sell integrations and services to
- Qualify leads by marketing stack (HubSpot vs Marketo vs Salesforce)
- Competitive intelligence on what tools rivals use
- Agency prospecting for site migrations and analytics audits
- Use it as a tool from AI agents through the Apify MCP server, or schedule it and send new results to Slack, Google Sheets or a webhook

### Input

| Field | Name | Description |
|---|---|---|
| `urls` | Website URLs | Websites or domains |
| `concurrency` | Concurrency | Sites in parallel |

#### Example input

```json
{
  "urls": [
    "https://www.allbirds.com",
    "https://wordpress.org",
    "https://www.hubspot.com",
    "https://vercel.com"
  ]
}
```

### Output

Each result is one dataset item with these fields: `inputUrl`, `finalUrl`, `domain`, `status`, `error`, `title`, `technologies`, `technologyCount`, `byCategory`, `cms`, `ecommerce`, `marketingAutomation`, `analytics`, `cdnHosting`, `generatorTag`, `server`, `poweredBy`, `checkedAt`.

#### Example output (real result, long fields shortened)

```json
{
  "inputUrl": "https://vercel.com/",
  "finalUrl": "https://vercel.com/",
  "domain": "vercel.com",
  "status": 200,
  "error": null,
  "title": "Agentic Infrastructure - Vercel",
  "technologies": [
    "Next.js",
    "Vercel"
  ],
  "technologyCount": 2,
  "byCategory": {
    "JS framework": [
      "Next.js"
    ],
    "CDN / hosting": [
      "Vercel"
    ]
  },
  "cms": null,
  "ecommerce": null,
  "marketingAutomation": [],
  "analytics": [],
  "cdnHosting": [
    "Vercel"
  ],
  "generatorTag": null,
  "server": "Vercel",
  "poweredBy": "Next.js, Payload",
  "checkedAt": "2026-10-30T19:32:18.396Z"
}
```

Download the results as JSON, CSV, Excel or XML, or read them through the Apify API.

### Pricing

This Actor uses **pay-per-event** pricing. You pay **$0.003 per website** returned, plus standard Apify platform usage, which is small because the Actor uses lightweight HTTP requests (no browser). You are never charged for results that are not returned. To cap spending, set a maximum cost per run in the run options.

### Tips

- Start with a small max-results value to check your filters, then scale up.
- Schedule the Actor (for example daily) with a "since" date filter where available to get change alerts.
- The data comes straight from the source, so its freshness and completeness depend on that publisher.

### Disclaimer

This Actor is not affiliated with or endorsed by any website, platform or data publisher named here. Use it in line with the target sites' terms and applicable privacy laws (e.g. GDPR/CAN-SPAM for contact data). Verify critical decisions against the official source.

# Actor input Schema

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

Websites or domains

## `concurrency` (type: `integer`):

Sites in parallel

## Actor input object example

```json
{
  "urls": [
    "https://www.allbirds.com"
  ],
  "concurrency": 8
}
```

# 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://www.allbirds.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("pj_pai/website-tech-stack-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://www.allbirds.com"] }

# Run the Actor and wait for it to finish
run = client.actor("pj_pai/website-tech-stack-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://www.allbirds.com"
  ]
}' |
apify call pj_pai/website-tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pj_pai/website-tech-stack-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/otMW4OohxLdsISjmo/builds/sOgP0jyv9TZVhc0vi/openapi.json