# Website Technology Stack Detector | Public Page Evidence (`springlike_meadowland/website-tech-stack-detector`) Actor

Detect common website technologies from supplied public HTTPS pages. Export one result per hostname with the HTML asset, generator tag or response header behind each match. No browser rendering or full-site scan.

- **URL**: https://apify.com/springlike\_meadowland/website-tech-stack-detector.md
- **Developed by:** [Akshay Aggarwal](https://apify.com/springlike_meadowland) (community)
- **Categories:** Developer tools, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 domain results

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 Technology Stack Detector

See which common website tools leave visible clues on a public page. Enter public HTTPS URLs and export one result per fetched domain. Every detected technology includes the HTML asset, generator tag, or response header that supports the match. Agencies and software sales teams can use the list to prioritize websites for a closer look.

### Try it

```json
{"websiteUrls":["https://wordpress.org/"],"maxWebsites":10,"includeEvidence":true}
```

The WordPress.org homepage returned this result on September 23, 2026:

```json
{"input_url":"https://wordpress.org/","final_url":"https://wordpress.org/","technologies":[{"name":"WordPress","category":"CMS","evidence_type":"meta generator","evidence":"WordPress 7.2-alpha-63792","version_if_explicit":"7.2-alpha-63792"}],"status":"ok","source_url":"https://wordpress.org/"}
```

Open **Domain results** to export saved rows. Open **Coverage and errors** to see which URLs were fetched, skipped, challenged, or inaccessible, along with remaining URLs if a run stops at a limit.

### Signals covered

The detector recognizes visible page clues for WordPress, Drupal, Shopify, Wix, Squarespace, Webflow, Next.js, Nuxt, Google Tag Manager, Google tag, Stripe.js, PayPal JavaScript SDK, Meta Pixel, Hotjar, and Cloudflare. It reads the supplied public page HTML and HTTP response headers. `version_if_explicit` appears only when a recognized generator tag states a version; otherwise it is null.

A script or asset match shows that the fetched page includes that resource. It does not establish that analytics is collecting data, payments are enabled, or a service is configured throughout the site. An empty `technologies` list means no supported clue was found in the fetched page; it does not prove a technology is absent.

### Inputs, limits, and billing

- Supply 1–100 public HTTPS URLs. `maxWebsites` limits processing to 1–100 distinct hostnames and defaults to 10. A hostname appears once even if you submit multiple URLs on that host.
- The detector fetches the first supplied URL per hostname, up to 2 MiB. It does not render JavaScript, follow links to additional pages, bypass challenges, or provide historical technology records.
- The billing unit is **one saved domain result**, including a fetched page with an empty technology list. Challenge, inaccessible, non-HTML, and error cases appear in the run summary and do not produce a dataset result. The Apify pricing panel shows the current charge per result.
- Runs can stop at the configured charge or runtime limit. Saved results remain available, and the summary identifies URLs left unprocessed.

This is a focused public-page signal detector. For broader coverage or technologies hidden behind JavaScript and additional pages, inspect the site directly or use a broader specialist service.

# Actor input Schema

## `websiteUrls` (type: `array`):

Enter 1–100 public HTTPS homepage URLs. One domain is analyzed once. Start with the example for a small sample.

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

Process at most this many distinct domains from websiteUrls.

## `includeEvidence` (type: `boolean`):

Include the matched HTML asset, generator or header signal for each detection.

## Actor input object example

```json
{
  "websiteUrls": [
    "https://wordpress.org/"
  ],
  "maxWebsites": 10,
  "includeEvidence": true
}
```

# Actor output Schema

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

One row per successfully fetched public page, with evidence-backed detections.

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

Counts, challenge pages, inaccessible URLs and budget limits.

# 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 = {
    "websiteUrls": [
        "https://wordpress.org/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("springlike_meadowland/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 = { "websiteUrls": ["https://wordpress.org/"] }

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

```

## MCP server setup

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