# Website Technology Detector with Evidence (`codedbyloan/website-tech-evidence`) Actor

Detect 81 supported website technologies from public HTML and headers. Identify CMS, ecommerce, analytics and marketing tools with evidence for each match. Batch up to 500 URLs; export JSON, CSV or Excel. No browser or external API subscription required.

- **URL**: https://apify.com/codedbyloan/website-tech-evidence.md
- **Developed by:** [CodedByLoan](https://apify.com/codedbyloan) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 website inspections

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Technology Detector with Evidence

Turn a list of website URLs into structured technology observations. Identify supported CMS, ecommerce platforms, analytics tags, marketing tools and infrastructure, with a signal explaining each match.

Use the results to qualify company lists, find stores using Shopify or WooCommerce, or group websites by the tools visible on their pages. This Actor inspects the HTML and response headers from one public page per URL. It does not execute JavaScript or load third-party assets.

### Start with two websites

```json
{
  "urls": ["https://apify.com/", "https://wordpress.org/"],
  "maxConcurrency": 3,
  "timeoutSecs": 20
}
```

Add URLs, click Start, then export the dataset as JSON, CSV or Excel. JSON retains the full evidence objects. Use `technologyNames` for spreadsheet filters. You can also run the Actor through Apify's API, integrations and schedules.

### What you receive

Each dataset row contains:

- `url` and `finalUrl`: requested and final addresses after redirects.
- `status`: `ok`, `blocked`, `http_error` or `error`.
- `title`, `httpStatus`, `scannedAt` and `durationMs`.
- `technologyNames` and `technologyCount`: convenient fields for filtering.
- `technologies`: names, categories and the source/signal for each observation.
- `redirects`, `error`, `method` and `limitation` where applicable.

For example, an observed Next.js script path produces this technology entry:

```json
{
  "name": "Next.js",
  "category": "Web framework",
  "evidence": [
    { "source": "assets", "signal": "/_next/ asset" }
  ]
}
```

The evidence describes the matched marker rather than returning cookies, complete response headers or tracking IDs. Framework implications are explicit: a React entry derived from Next.js has `inferredFrom: "Next.js"` and an empty evidence array. It is not presented as a separate direct observation.

The key-value store record `SUMMARY` reports requested, delivered, successful and failed counts, plus whether the run reached its charge limit. If the charge limit stops a run, unprocessed URLs do not produce rows.

### Price and charge behavior

The launch price is **$0.001 per successfully inspected HTML page ($1 per 1,000)** under the `website-scanned` event. A successful inspection with zero supported technologies found is still one billable observation. The price is per page, not per technology.

Blocked pages, HTTP errors, timeouts, invalid URLs and non-HTML responses do not trigger the inspection event. There is no Actor start fee or separate charge per dataset row. The current Pricing tab is authoritative for the active rate.

Duplicate input strings are trimmed and processed once within a run. Distinct URLs, including different paths on the same domain, count separately. Redirect aliases are not deduplicated across inputs. Running the same list again creates new inspections and charges.

### Complete example result

This is a complete row from our WordPress.org validation run on 6 September 2026. Website signals can change; the example demonstrates the output format.

```json
{
  "url": "https://wordpress.org/",
  "status": "ok",
  "scannedAt": "2026-09-06T21:33:01.018Z",
  "technologyNames": [
    "Google Tag Manager",
    "Nginx",
    "WordPress"
  ],
  "technologyCount": 3,
  "technologies": [
    {
      "name": "Google Tag Manager",
      "category": "Tag manager",
      "evidence": [
        {
          "source": "assets",
          "signal": "Google Tag Manager gtm.js script"
        }
      ]
    },
    {
      "name": "Nginx",
      "category": "Web server",
      "evidence": [
        {
          "source": "headers",
          "signal": "Nginx server header"
        }
      ]
    },
    {
      "name": "WordPress",
      "category": "CMS",
      "evidence": [
        {
          "source": "generator",
          "signal": "WordPress generator"
        },
        {
          "source": "assets",
          "signal": "/wp-content/ or /wp-includes/ asset"
        }
      ]
    }
  ],
  "error": null,
  "finalUrl": "https://wordpress.org/",
  "httpStatus": 200,
  "redirects": [],
  "title": "Blog Tool, Publishing Platform, and CMS – WordPress.org",
  "method": "http-html-and-response-headers",
  "limitation": "Only the returned HTML and headers were inspected. No JavaScript execution. An absent detection does not prove absence.",
  "durationMs": 388
}
```

### Coverage and limits

The initial rules cover **81 named technologies**. Detection requires a supported visible marker; coverage of a product does not guarantee detection on every installation.

- CMS and stores include WordPress, Drupal, Joomla, Ghost, Hugo, Jekyll, Shopify, WooCommerce, Magento, BigCommerce, PrestaShop and Shopware.
- Builders and frameworks include Wix, Squarespace, Webflow, Framer, Duda, Elementor, Divi, Next.js, Nuxt, Astro, Gatsby, SvelteKit and Angular.
- Analytics and marketing include Google Analytics, Google Tag Manager, Plausible, Matomo, Clarity, Hotjar, Mixpanel, Amplitude, Segment, PostHog, HubSpot, Klaviyo, Mailchimp and several advertising tags.
- Other rules cover support widgets, payment scripts, consent tools, CDNs, hosting headers, web servers and observability scripts.

Only the returned HTML and headers are inspected. Technologies loaded after consent, user interaction or JavaScript execution may be missed. Compiled or renamed assets, removed metadata and hidden server components may also be missed. An absent match does not establish that a technology is absent. A matched script can be embedded but inactive. This is an observed-signal report, not a verified inventory of the website's backend.

Limits are 500 unique URLs per run, 1 to 5 concurrent requests, 5 to 40 seconds per URL including redirects, at most 5 redirects, and 3 MB of decompressed HTML per page. HTML is decoded as UTF-8. Only public HTTP(S) destinations on ports 80 and 443 are accepted. Private networks, credentialed URLs, login sessions, PDF files and browser challenges are unsupported. No software versions or vulnerability assessments are produced.

Keep runs small initially. Review error rows before increasing batch size. When inspecting several pages on the same host, use concurrency 1. No residential proxy or separate third-party API subscription is required.

### Support

Open an issue from this Actor's Issues tab with a public example URL, the run ID and the missing or incorrect technology. Avoid including passwords or confidential URLs. Technology names belong to their respective owners; this Actor is independent of those products.

# Actor input Schema

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

Public HTTP(S) pages to inspect. One request per page, with redirects followed. Up to 500 unique URLs. No login is supported.

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

Number of different pages inspected in parallel. Lower this when checking many pages on one host.

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

Total time allowed for one website including DNS lookup, redirects and download.

## Actor input object example

```json
{
  "urls": [
    "https://apify.com/",
    "https://wordpress.org/"
  ],
  "maxConcurrency": 3,
  "timeoutSecs": 20
}
```

# Actor output Schema

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

Dataset rows containing URLs, inspection status, supported technologies and their evidence. Error rows contain a reason and no technology detections.

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

Requested, delivered, successful and failed counts, and whether the spending limit stopped the run.

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

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

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

```

## MCP server setup

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