# Website Tech Stack Detector + 295 E-Commerce Apps (`northwestsouth/website-tech-stack-detector`) Actor

Detects the platform, CMS, framework, analytics, payment providers, consent tool and hosting behind any website — plus 295 e-commerce app fingerprints no generic detector has. Never charges twice for the same domain.

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

## Pricing

from $15.00 / 1,000 domain 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

Find out what any website is built on — and, uniquely, which **e-commerce apps** it actually runs.

Give it a list of domains. Get back the platform, CMS, framework, analytics, payment providers, consent tool and hosting — plus **295 e-commerce app fingerprints** that generic detectors don't carry.

### Never charged twice for the same domain

Every domain you receive is remembered across **all** your runs. Send the same list again next month and you pay only for what is new.

- Already analyzed → skipped, free, and the log says how many.
- Site down, blocked or unreachable → **free**, with the reason in a separate `FAILED-URLS` dataset.
- Want fresh data anyway? Set `chargeForPreviouslyAnalyzed` to true. Nothing hidden, nothing automatic.

There are **no hidden row limits**.

### Why this one is different

Most detectors tell you "nginx, jQuery, Google Analytics" and stop. That's fine for a generic tech census, but useless if you're targeting DTC brands and need to know whether a store runs Klaviyo or Omnisend, Yotpo or Judge.me, Recharge or Bold.

This actor carries **295 e-commerce app fingerprints** alongside the usual stack detection. If you sell to Shopify merchants, that's the column you actually need.

### What you get per site

| Field | Example |
|---|---|
| `ecommerce_platform` | Shopify, WooCommerce, Magento, Shopware, PrestaShop, BigCommerce, Salesforce Commerce Cloud, JTL-Shop … |
| `cms` | WordPress, Webflow, Squarespace, Wix, Drupal, TYPO3, Contentful, Sanity, Storyblok … |
| `frameworks` | Next.js, Nuxt, React, Vue, Angular, Svelte, Astro, Remix, Tailwind, Bootstrap … |
| `analytics` | GA4, Google Tag Manager, Meta Pixel, TikTok, Pinterest, LinkedIn, Clarity, Hotjar, Matomo, Plausible, Segment … |
| `marketing_tools` | Klaviyo, Mailchimp, HubSpot, ActiveCampaign, Brevo, Intercom, Zendesk, Crisp … |
| `payment_providers` | Stripe, PayPal, Klarna, Adyen, Mollie, Braintree, Afterpay, Apple Pay, Google Pay … |
| `consent_platform` | Cookiebot, OneTrust, Usercentrics, CookieYes, Complianz, Borlabs, Didomi … |
| `hosting` | Cloudflare, Vercel, Netlify, CloudFront, Fastly, Akamai, nginx, Apache, IIS … |
| `ecommerce_apps` | 295 fingerprints with app name, category and Shopify App Store link |
| `title`, `description`, `language`, `generator`, `server` | page metadata |

### Honest limitations — please read

**Static HTML only.** This actor reads the HTML and response headers a server delivers. Technologies injected later by JavaScript, or loaded only after consent is granted, will not be seen. If you need full JS-rendered detection, use a browser-based tool — it will cost more and run slower, and it will find things this one misses.

**Detection favours precision over recall.** Every fingerprint requires a technical marker — a script URL, an asset path, a header — never just a brand name in the page text. An article *about* Shopify will not be reported as running Shopify. The trade-off is that unusual or self-hosted setups may be missed.

**One request per site.** No crawling of subpages, no proxy rotation, no anti-bot circumvention. Sites that block plain HTTP requests are reported as failures, and cost you nothing.

### Input

```json
{
  "urls": ["snocks.com", "vercel.com", "wordpress.org"],
  "includeEcommerceApps": true,
  "includeMeta": true
}
```

### Example output

```json
{
  "url": "snocks.com",
  "ecommerce_platform": "Shopify",
  "cms": null,
  "frameworks": [],
  "analytics": ["Google Tag Manager", "TikTok Pixel", "Pinterest Tag"],
  "marketing_tools": ["Klaviyo"],
  "payment_providers": ["PayPal", "Apple Pay"],
  "hosting": ["Cloudflare"],
  "ecommerce_apps": [
    { "name": "Klaviyo", "category": "Marketing", "appStoreUrl": "https://apps.shopify.com/klaviyo-email-marketing" }
  ],
  "technology_count": 11
}
```

### Choose your fields

Set `outputFields` to just what you need — for example `["ecommerce_platform", "ecommerce_apps"]` — and your export contains nothing else.

### Pricing

Pay per **successfully analyzed domain**. Not per technology found, not per row.

### Credits

E-commerce app fingerprints derived from [feracommerce/shopify_app_detector](https://github.com/feracommerce/shopify_app_detector) (Apache-2.0). All platform, framework, analytics, payment, consent and hosting fingerprints are original work.

### Support

A technology it should have found, or one it reported wrongly? [Open an issue](https://console.apify.com/actors) on this actor — false positives are treated as bugs and fixed.

# Actor input Schema

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

Bare domains (stripe.com), full URLs or subdomains all work. Duplicates and www variants are merged automatically, so you never pay twice for the same site.

## `includeEcommerceApps` (type: `boolean`):

Identifies installed Shopify apps — reviews, subscriptions, loyalty, upsell, email and more. This is the depth generic detectors don't have, and it's what tells you which tools a DTC brand actually pays for.

## `includeMeta` (type: `boolean`):

Title, meta description, language, generator tag and server header.

## `outputFields` (type: `array`):

Leave empty for everything. Otherwise name the fields you want, e.g. ecommerce_platform, frameworks, ecommerce_apps — so your export has no noise.

## `chargeForPreviouslyAnalyzed` (type: `boolean`):

OFF by default: any domain analyzed in an earlier run is skipped and NOT charged again. Turn on only when you deliberately want fresh data.

## Actor input object example

```json
{
  "urls": [
    "snocks.com",
    "vercel.com"
  ],
  "includeEcommerceApps": true,
  "includeMeta": true,
  "outputFields": [],
  "chargeForPreviouslyAnalyzed": false
}
```

# 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": [
        "snocks.com",
        "vercel.com"
    ],
    "outputFields": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("northwestsouth/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": [
        "snocks.com",
        "vercel.com",
    ],
    "outputFields": [],
}

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

```

## MCP server setup

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