Fast Evidence-Backed Website Tech Stack Detector

Detect 72 common website technologies in bulk from public response headers and bounded HTML. Every detection can include the source-backed evidence behind it, making the results useful for lead enrichment, sales intelligence, competitor research, migration planning, and portfolio audits.

What it detects

• CMS and ecommerce platforms
• JavaScript and CSS frameworks
• analytics and tag managers
• marketing, chat, and support tools
• hosting platforms, servers, and CDNs
• visible version or implementation clues when a signature exposes them

Results include the final URL, HTTP status, title, relevant server headers, technology count, categorized technologies, optional evidence, errors, and timestamp.

Common use cases

• identify WordPress, Shopify, analytics, CDN, or framework users for prospecting
• enrich domains in a CRM or lead-scoring pipeline
• compare competitor and portfolio technology choices
• scope migrations and technical due diligence
• replace slow manual BuiltWith-style checks for a focused URL list

Quick start

1. Click Try for free or Run.
2. Paste one or more public website URLs.
3. Leave Include detection evidence enabled when you need auditable results.
4. Run the Actor and export the dataset.

{
  "urls": ["https://apify.com", "https://wordpress.org"],
  "concurrency": 10,
  "timeoutSeconds": 20,
  "maxRedirects": 5,
  "includeEvidence": true
}

Example result

{
  "inputUrl": "https://wordpress.org",
  "finalUrl": "https://wordpress.org/",
  "statusCode": 200,
  "ok": true,
  "title": "Blog Tool, Publishing Platform, and CMS – WordPress.org",
  "server": "nginx",
  "technologyCount": 2,
  "technologies": [
    {
      "name": "WordPress",
      "category": "CMS",
      "evidence": ["HTML contains wp-content"]
    },
    {
      "name": "Nginx",
      "category": "Web server",
      "evidence": ["server: nginx"]
    }
  ],
  "checkedAt": "2026-07-10T12:00:00.000Z"
}

The values above illustrate the output schema. Live detections depend on the site's current public response.

Run by API

Set APIFY_TOKEN in your environment and never commit it.

cURL

curl -X POST \
  "https://api.apify.com/v2/acts/rtworule~bulk-website-tech-detector/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://wordpress.org"],"includeEvidence":true}'

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('rtworule/bulk-website-tech-detector').call({
  urls: ['https://wordpress.org'],
  includeEvidence: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("rtworule/bulk-website-tech-detector").call(run_input={
    "urls": ["https://wordpress.org"],
    "includeEvidence": True,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

Pricing

This Actor uses pay per event. A website-analyzed event costs $0.001 per stored result: 100 websites cost $0.10 and 1,000 cost $1.00 in event charges. Apify applies a $0.01 minimum run charge. The Actor respects the run's maximum total charge.

Integrations and automation

• enrich CRM records through Make, Zapier, n8n, or the Apify API
• schedule repeat scans to flag technology changes
• export CSV/XLSX to Sheets or join JSON results to a domain list
• send high-value detections, such as a target CMS, to a sales webhook
• feed categorized technologies into BI, lead-scoring, or migration workflows

FAQ and troubleshooting

Is this a complete view of a site's private stack? No. Detection is best-effort and uses public headers and HTML signals. Hidden, server-side, obfuscated, or exclusively client-rendered tools may not be visible.

Why was a technology missed? The site may hide its signature, load it after JavaScript executes, or use a product for which the Actor has no current signature.

Can a detection be a false positive? Heuristic detection can produce false positives. Enable evidence and validate critical decisions against the live site.

Why was a URL rejected? URLs with credentials and local, private, reserved, or metadata-service destinations are blocked. Every redirect target is validated too.

How do I improve throughput? Increase concurrency for unrelated hosts. Lower it when repeatedly checking one host, and increase the timeout only for known slow sites.

Responsible use, limitations, and support

The Actor reads public pages only, follows a bounded number of redirects, and downloads at most 2 MB of HTML per page. It does not log in or bypass access controls. Users are responsible for lawful access, honoring applicable terms, and their downstream use of results.

If you find an inaccurate detection, open an issue from the Actor page with the run ID, URL, expected technology, and visible evidence. Do not share secrets or non-public URLs.

More tools from this developer

• Bulk URL Status Checker & Redirect Audit
• AI Search Readiness / GEO & AEO Auditor
• RSS, Atom & JSON Feed Normalizer
• Greenhouse, Lever & Ashby Jobs Normalizer