# Website Tech Stack Detector - CMS, Analytics, Hosting, Pixels (`datasignalslab/website-tech-stack-detector`) Actor

Detect the technologies behind any website from one request: CMS, framework, analytics, ad pixels, chat, payments, hosting, CDN, cookie consent, ATS and more, with the evidence for each match. Paste domains, get JSON. $10 per 1,000 websites, a tenth of the usual price.

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

## Pricing

$10.00 / 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 Tech Stack Detector: 150 technologies in 37 categories from one request

Paste a list of domains and get back, per website, the technologies behind it: CMS, framework, analytics, advertising pixels, chat, payments, cookie consent, hosting, CDN and the applicant tracking system behind the careers page. Every match comes with the evidence that triggered it, so you can trust a row without opening the site.

One HTTP request per website, ten in parallel, no browser, no proxy. That is why it costs a tenth of the usual price.

**Run it with the default input to see it work.** It analyses shopify.com, vercel.com and wordpress.org.

### What you get from the Website Tech Stack Detector

One row per website:

| field | meaning |
|---|---|
| `website`, `domain`, `url`, `final_url`, `status` | what you asked for, where it landed, and the HTTP status |
| `title`, `generator`, `server`, `ip` | page title, meta generator, Server header and resolved IP |
| `technologies` | list of `{name, category, evidence_in, evidence}`, with `evidence_in` html, script, header or cookie |
| `categories` | the same names grouped by category, for filters like "WordPress sites without a cookie banner" |
| `technology_count` | number of detections |
| `emails` | up to 10 email addresses found on the page, for enrichment |
| `error` | why a site could not be fetched, otherwise null |

Example row:

```json
{
  "website": "shopify.com",
  "domain": "shopify.com",
  "final_url": "https://www.shopify.com/",
  "status": 200,
  "title": "Start and grow your e-commerce business - Shopify",
  "server": "cloudflare",
  "technologies": [
    {"name": "Cloudflare", "category": "CDN", "evidence_in": "header", "evidence": "server: cloudflare"},
    {"name": "Shopify", "category": "Ecommerce", "evidence_in": "html", "evidence": "cdn.shopify.com"},
    {"name": "React", "category": "Framework", "evidence_in": "html", "evidence": "data-reactroot"},
    {"name": "Tailwind CSS", "category": "UI framework", "evidence_in": "html", "evidence": "tailwindcss"}
  ],
  "categories": {"CDN": ["Cloudflare"], "Ecommerce": ["Shopify"], "Framework": ["React"], "UI framework": ["Tailwind CSS"]},
  "technology_count": 4,
  "emails": [],
  "error": null
}
```

### What the tech stack detector detects

153 detection rules for 150 technologies in 37 categories, matched against the HTML, the `src` of script tags, the response headers and the cookies. The main groups:

- CMS and ecommerce: WordPress, WooCommerce, Shopify, Wix, Squarespace, Webflow, Drupal, Joomla, Ghost, HubSpot CMS, Magento, BigCommerce, PrestaShop, Framer, Contentful, Sanity, Storyblok, Strapi. An unknown meta generator is added as a CMS row.
- Frameworks: Next.js, Nuxt, Gatsby, Remix, Astro, SvelteKit, Angular, Vue.js, React, jQuery, Bootstrap, Tailwind CSS, Laravel, Django, Ruby on Rails.
- Analytics: Google Analytics, Google Tag Manager, Segment, Mixpanel, Amplitude, Hotjar, Clarity, Plausible, PostHog, Heap, Matomo.
- Advertising pixels: Meta, LinkedIn Insight Tag, TikTok, Google Ads, X, Microsoft Advertising, Reddit.
- Marketing and email: HubSpot, Marketo, Pardot, Klaviyo, Mailchimp, ActiveCampaign, Braze.
- Chat and support: Intercom, Drift, Crisp, Zendesk, Freshdesk, Tawk.to, Tidio, LiveChat.
- Payments: Stripe, PayPal, Paddle, Lemon Squeezy, Chargebee, Mollie, Adyen, Klarna.
- Consent, security and monitoring: OneTrust, Cookiebot, CookieYes, Osano, Didomi, reCAPTCHA, hCaptcha, Turnstile, Sentry, Datadog, New Relic, Optimizely, VWO, Imperva.
- Authentication: Auth0, Clerk, Okta, Firebase, Supabase.
- ATS: Greenhouse, Lever, Ashby, Workable, Workday, SmartRecruiters, Teamtailor.
- Hosting, CDN and server from headers: Cloudflare, Vercel, Netlify, Fastly, Akamai, CloudFront, Fly.io, Heroku, GitHub Pages, Google Cloud, Azure, Kinsta, WP Engine, Nginx, Apache, IIS.

### How to detect a website tech stack with this Actor

1. Open the Actor in the Apify Console and paste your domains or URLs into `websites`, one per line. https is assumed when you leave the scheme out.
2. Set `maxWebsites` for a hard stop on a long list, or leave it at 0.
3. Click Start. Ten websites are fetched in parallel and each row lands in the dataset as soon as its request finishes.
4. From code: `POST /v2/acts/datasignalslab~website-tech-stack-detector/run-sync-get-dataset-items` with the same JSON input returns the dataset.

### Input

| field | what it does |
|---|---|
| `websites` | domains or URLs, one per line |
| `maxWebsites` | hard stop, 0 means all, max 100,000 |
| `skipFailed` | drop rows for sites that did not answer. Off by default, because "unreachable" is useful in a lead list too |

Minimal input:

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

First 500 of a long list, successful rows only:

```json
{ "websites": ["shopify.com", "vercel.com"], "maxWebsites": 500, "skipFailed": true }
```

### Pricing: how much does the Website Tech Stack Detector cost

Pay per website analysed: **$10 per 1,000 websites** ($0.01 each). A website that does not answer is still a row, with the error, and is charged like any other unless you switch on `skipFailed`. No start fee. Apify's free monthly credit covers hundreds of websites.

Example: 2,500 ecommerce domains cost 2,500 x $0.01 = $25.00. Filtering that list down to "Shopify stores with Klaviyo and no live chat" is a dataset filter, not a second run.

#### More from DataSignals Lab

This Actor is one of the pay-per-result data Actors of [DataSignals Lab](https://datasignalslab.com): job listings per ATS platform and job board, app and company reviews, YouTube comments and transcripts, website contacts and tech stacks. Every Actor returns the same clean JSON style and charges only for rows that land in the dataset, so you can combine feeds without remapping fields. All Actors and prices are listed on [datasignalslab.com](https://datasignalslab.com).

### Use cases for website tech stack detection

- Sales teams in Clay: run the domain column through this Actor and write `categories` back into the table, then build segments like "Shopify stores running Klaviyo but no live chat".
- HubSpot admins: schedule a weekly run over new company records and import the CSV, so every company carries its CMS, analytics and ATS as properties.
- Agencies in Google Sheets: paste prospect domains, run the Actor and get a technology column per row back.
- Automation builders in n8n or Make: trigger the Actor on a new lead, wait for the webhook, and route the lead by stack.
- AI agents that need a structured answer to "what does this company run on", as one JSON row through the Apify MCP server.

Need a contact for the shortlist? See [Website Contact Scraper](https://apify.com/datasignalslab/website-contact-scraper).

### Website tech stack API alternative: how it compares

- Price. Comparable tools charge $2 to $100 per 1,000 websites, or a monthly subscription. Here it is $10 per 1,000 with no plan.
- Evidence per match. Every technology row names where it was found (html, script, header, cookie) and the snippet that matched, so you can audit a list by reading it.
- 150 technologies, not thousands. Tools that advertise several thousand signatures include many that never appear on a company home page. These 150 are the ones that matter for lead lists.

### Limits of the Website Tech Stack Detector

- One request to the home page, at most 1.5 MB of HTML, no browser rendering. Technologies that only appear on inner pages, load after interaction or are injected by a tag manager at runtime are not seen. That trade-off makes it fast and cheap.
- No proxy. Requests go straight from the Apify platform. Websites behind aggressive bot protection may answer with a 403. The row then says so in `status` and `error`, and it is charged unless `skipFailed` is on.
- Signatures are deliberately strict: a mention of a brand in marketing copy does not count, only the real script, header or cookie. An unusual self-hosted setup can be missed.
- No version numbers, except what the `generator` and `server` fields reveal.

### FAQ

#### Is it legal to detect a website's tech stack?

The Actor performs one ordinary GET request to the home page and reads the public HTML and response headers. It does not log in or bypass access controls, and it stores no page content beyond the matched snippets. How you use the result falls under the rules that apply to you. This is not legal advice.

#### Do I need an API key, login or proxy for the tech stack detector?

No. Paste domains and start. No external API and no proxy.

#### How many technologies does the Website Tech Stack Detector know?

150 technologies through 153 detection rules in 37 categories. Missing one? Open an issue with a domain that uses it.

#### How often does the data update?

Every run fetches the live home page. There is no cache, so a scheduled run reflects the current stack.

#### Can I schedule the Website Tech Stack Detector?

Yes. Use the Schedules tab in the Apify Console with a fixed list, and add a webhook so your CRM or sheet is updated when the dataset is ready.

#### Can an AI agent (MCP) call it?

Yes. Through the Apify MCP server, Claude, ChatGPT and other agents can call this Actor as a tool and receive the rows as JSON.

#### How much do 10,000 websites cost?

$100. Every row in the dataset is charged at $0.01, including sites that answered with an error, unless `skipFailed` is on.

#### What happens when a website blocks the detector?

The row keeps the HTTP status, the error, the resolved IP and any technologies readable from the headers of the error response, such as the CDN or security vendor. Switch on `skipFailed` to leave such rows out.

### Integrations

Apify API, scheduled runs, webhooks, and the Apify MCP server, so Claude, ChatGPT and other agents can call it as a tool. Make, Zapier and n8n through the Apify apps in those platforms. Export to JSON, CSV, Excel or Google Sheets.

### Support

Issues tab on this page, or support@datasignalslab.com. Response within one working day. Built and maintained by [DataSignals Lab](https://datasignalslab.com).

### Changelog

- 2026-10: README restructured with the exact rule count (153 rules, 150 technologies, 37 categories), how-to, use cases, comparison, limits and FAQ.

# Actor input Schema

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

Domains or URLs, one per line. https is assumed when you leave the scheme out.

## `maxWebsites` (type: `integer`):

Hard stop. 0 means all of them. You pay per website analysed.

## `skipFailed` (type: `boolean`):

Off by default: a row with the error is still useful in a lead list. Turn on to only keep websites that answered.

## Actor input object example

```json
{
  "websites": [
    "shopify.com",
    "vercel.com",
    "wordpress.org"
  ],
  "maxWebsites": 0,
  "skipFailed": false
}
```

# Actor output Schema

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

One object per website with the detected technologies.

## `websitesCsv` (type: `string`):

The same as a CSV download.

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

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

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

```

## MCP server setup

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