# Website Tech Stack Detector with Evidence (`kirozhang/website-tech-stack-evidence`) Actor

Detect CMS, analytics, ecommerce and web frameworks from public HTML and headers. Export supporting evidence and compare technology changes across runs.

- **URL**: https://apify.com/kirozhang/website-tech-stack-evidence.md
- **Developed by:** [Kiro Zhang](https://apify.com/kirozhang) (community)
- **Categories:** Developer tools, Lead generation, Marketing
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 website checks

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 with Evidence

Turn a list of company websites into an evidence-backed technology inventory. Use it to qualify CMS migration prospects, maintain an agency client inventory, or detect changes in a recurring website check.

### Who this is for

For agencies qualifying CMS migrations, sales teams enriching an existing company list, and developers checking client websites. Bring the website URLs you already have; this Actor does not discover companies or contacts.

Start with at most 10 result rows: the Actor event charges for that batch are at most $0.03 at the listed rate. Set both `maxResults` and the run's maximum charge before starting.

### Quick start

Open the Input tab, paste your input and run. A small example:

```json
{
  "urls": [
    "https://www.wordpress.org/",
    "https://www.shopify.com/"
  ],
  "maxResults": 10
}
```

### What you receive

One row per successfully fetched HTML page, including the final URL, page title, technology names, categories and up to three pieces of evidence per technology. Evidence comes from script and stylesheet URLs, generator metadata, selected headers and framework attributes. The detector contains 60 focused signatures across CMS, ecommerce, analytics, marketing, support, payments, hosting and frameworks.

Examples include WordPress, Shopify, WooCommerce, Webflow, Wix, Next.js, Nuxt, Google Analytics, Google Tag Manager, HubSpot, Stripe and Cloudflare. A detection means a matching public artifact was observed; it does not establish an active subscription or paid customer relationship.

### Compare repeated checks

Paste the earlier dataset rows into `previousResults`. The Actor matches `key` and compares `technologyNames`, producing `comparison` (`no_baseline`, `unchanged` or `changed`) and `changedFields`. A new run always fetches fresh pages. Baselines are explicit input, never shared account-wide state.

### Scope and limitations

This is a lightweight server-HTML check. It does not execute JavaScript, traverse the entire site, read private pages or query a commercial technology database. A technology loaded after consent or in a client-only application may be missed. Zero matches means no supported signatures were found in the fetched page, not that the site has no technology. Version numbers and employee contacts are not inferred. Robots rules and access refusals are respected.

### Pricing and limits

$3 per 1,000 delivered website check results ($0.003 each). There is no Actor startup fee. Standard platform usage is included in this Actor's event price. A successfully delivered dataset row triggers one charge; error diagnostics live in `RUN_SUMMARY` and are not chargeable rows. Repeated runs are new checks and may return the same item again. The Pricing tab is authoritative.

Use the run's maximum charge setting and `maxResults` to control spending. No proxy subscription or external API key is required. Runs use 256 MB by default. For large batches, raise the run timeout or split the input; a hard timeout may leave an incomplete dataset. The presence of a finished `RUN_SUMMARY` helps distinguish completed processing from interrupted runs.

### Export and integrations

Use the Output tab to inspect results and the summary. Download JSON, CSV or Excel from the dataset, or use Apify's API, Make, Zapier or n8n to pass the output into your existing workflow. Nested evidence is most faithfully preserved in JSON. The default dataset belongs to the run; no external destination receives results automatically.

An API client can start `kirozhang/website-tech-stack-evidence` with the JSON above, wait for completion and read its default dataset. Set your Apify token in the client's credential store, never inside the input URLs.

### Troubleshooting

Read `RUN_SUMMARY.errors` and `limitReasons` first. A partial run may contain useful rows; it must not be treated as exhaustive. All-target failure marks the run failed. A valid search with no matches can succeed with zero rows. For support, open an Issue on this Actor with the run ID, expected behavior and a public example target. Remove credentials and private data from your report.

### Example output

Illustrative excerpt from a real verification run; values change over time.

```json
{
  "url": "https://www.wordpress.org/",
  "title": "Blog Tool, Publishing Platform, and CMS | WordPress.orgWordPress.orgWordPress.orgCode is Poetry",
  "technologyNames": [
    "Nginx",
    "WordPress"
  ],
  "technologyCount": 2,
  "comparison": "no_baseline",
  "checkedAt": "2026-11-06T12:35:35.990Z"
}
```

### Workflows and questions

#### Weekly client technology inventory

1. Start with 5–10 client URLs and inspect the evidence behind each match.
2. Save the resulting JSON, including `key` and `technologyNames`.
3. On the next check, send those rows as `previousResults` with the same URLs. Filter `comparison: "changed"` for review.
4. Keep each dated dataset. A scheduled run with a static baseline keeps comparing against that baseline; your workflow must explicitly supply the previous run's rows to advance it.

#### Common questions

**Is this a Wappalyzer or BuiltWith database export?** No. It performs a fresh public-page check using its own focused signatures. Use the returned evidence to decide whether a match is useful.

**Can it identify every technology on a site?** It inspects server HTML and selected headers without a browser. Client-only and consent-gated scripts can be absent.

**Can I use CSV?** Yes, for a flat inventory. Keep JSON when you need nested evidence or a baseline for the next run.

### API quick start

Save the Quick start JSON as `input.json`. Put your Apify token in the `APIFY_TOKEN` environment variable through your usual secret store, then run:

```bash
curl --fail-with-body --max-time 200 \
  --request POST \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header "Content-Type: application/json" \
  --data-binary @input.json \
  "https://api.apify.com/v2/acts/kirozhang~website-tech-stack-evidence/run-sync-get-dataset-items?timeout=180&memory=256&maxTotalChargeUsd=0.10&format=json&clean=true" \
  --output results.json
```

This example starts a real run and applies a $0.10 charge ceiling. The smaller `maxResults` cap still applies. An empty array can be a valid no-match result; inspect the run and `RUN_SUMMARY` in Console. If the connection times out, check Console before retrying, since the run may already exist. For larger exports, use the asynchronous API shown on this Actor's API tab and read the dataset after the run finishes.

### Scheduling and workflow tools

After a successful small run, save a task with your production input. [Apify schedules](https://docs.apify.com/actors/running/schedules) can run that task regularly. In Make, Zapier or n8n, store the token in the connection credentials, run this Actor, wait for completion, and read its dataset. Configure your own destination explicitly; this Actor does not send emails or post messages automatically. Each scheduled run may incur charges, including repeated results.

### Related tools for different steps

- [After identifying migration prospects, validate the old-to-new URL mappings with the Website Migration Redirect Audit.](https://apify.com/kirozhang/website-migration-redirect-audit)
- [For the same client domains, inspect email configuration with the Email DNS Audit.](https://apify.com/kirozhang/email-dns-auth-audit)

# Actor input Schema

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

Public HTTP or HTTPS pages. Each distinct supplied URL is one check; up to 500 URLs. No JavaScript rendering.

## `previousResults` (type: `array`):

Paste up to 500 prior result objects to compare the same key. No persistent baseline is shared between runs or users.

## `maxResults` (type: `integer`):

Additional global cap for this run. Stops before another paid result is saved. The lower of this value, product-specific caps and your charge budget applies.

## Actor input object example

```json
{
  "urls": [
    "https://www.wordpress.org/",
    "https://www.shopify.com/"
  ],
  "maxResults": 500
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered rows, exportable as JSON, CSV or Excel.

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

Counts, limits and unbilled errors. Check complete before treating the result as exhaustive.

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

// Run the Actor and wait for it to finish
const run = await client.actor("kirozhang/website-tech-stack-evidence").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.wordpress.org/",
        "https://www.shopify.com/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("kirozhang/website-tech-stack-evidence").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.wordpress.org/",
    "https://www.shopify.com/"
  ]
}' |
apify call kirozhang/website-tech-stack-evidence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kirozhang/website-tech-stack-evidence"
        }
    }
}
```

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/gI5WbWjweESDVs5mg/builds/wmTvJsKcfQgmsuU6K/openapi.json