Wappalyzer Technology Lookup

Detect the public technology stack behind websites from a list of domains or URLs. This actor is built for enrichment workflows where you need normalized CMS, ecommerce, analytics, CDN, hosting, JavaScript framework, and server evidence without running a browser.

What does Wappalyzer Technology Lookup do?

Wappalyzer Technology Lookup fetches public website pages, reads response headers and HTML, extracts script/style/meta signals, and returns technology matches with confidence scores and evidence. It is a lightweight alternative to a browser-based site audit when you need fast lead-list enrichment.

Who is it for?

• 🧑‍💼 Sales teams enriching company/domain lists before outreach.
• 📈 Growth teams finding Shopify, WordPress, Webflow, or analytics users.
• 🧰 Agencies qualifying prospects by CMS, ecommerce platform, CDN, or hosting.
• 🔎 SEO and competitive-intelligence teams comparing public technology stacks.
• 🧪 Data teams adding technology fields to CRM, warehouse, or Clay-style workflows.

Why use this actor?

• HTTP-first: fast and inexpensive for large lists.
• One row per website: easy to export to CSV, Sheets, or a CRM.
• Evidence included: audit why a technology was detected.
• Flat and nested fields: use technologyNames for spreadsheets and technologies for richer apps.
• Optional raw signals: keep datasets small by default, expand when needed.

What technologies can it detect?

The initial signature map covers common public signals including WordPress, WooCommerce, Shopify, Wix, Squarespace, Webflow, Drupal, Joomla, React, Next.js, Nuxt.js, Vue.js, Angular, Google Analytics, Google Tag Manager, Meta Pixel, Cloudflare, Akamai, Fastly, Nginx, Apache, Vercel, Netlify, Bootstrap, and jQuery.

Data table

Field	Description
input	Normalized input URL/domain.
url	Starting URL.
finalUrl	URL after redirects.
domain	Hostname without leading www.
statusCode	First page HTTP status.
title	Page title.
metaGenerator	CMS generator meta tag if present.
technologies	Technology objects with name, category, confidence, and evidence.
technologyNames	Flat list of technology names.
categories	Flat list of detected categories.
confidence	Average technology confidence.
pageCount	Number of pages inspected.
pages	Per-page signal summary.
error	Fetch error if the site could not be reached.
detectedAt	ISO timestamp.

How much does it cost to detect website technology stacks?

The actor uses pay-per-event pricing: a $0.005 run-start fee plus a per-website result charge. Because it runs HTTP requests instead of browsers by default, it is designed for affordable bulk enrichment.

Apify plan tier	Per website result	Example calculation for 1,000 websites
FREE	$0.0002405	0.005 start + 1,000 × 0.0002405 = 0.2455 USD
BRONZE	$0.00020913	0.005 start + 1,000 × 0.00020913 = 0.21413 USD
SILVER	$0.00016312	0.005 start + 1,000 × 0.00016312 = 0.16812 USD
GOLD	$0.00012548	0.005 start + 1,000 × 0.00012548 = 0.13048 USD
PLATINUM	$0.000083653	0.005 start + 1,000 × 0.000083653 = 0.088653 USD
DIAMOND	$0.000058557	0.005 start + 1,000 × 0.000058557 = 0.063557 USD

Free-plan estimate: checking 100 websites costs about 0.02905 USD (0.005 + 100 × 0.0002405). Checking 10,000 websites on BRONZE costs about 2.0963 USD (0.005 + 10,000 × 0.00020913). Exact live pricing is shown on the Apify actor page and may vary by your Apify plan tier.

How to use Wappalyzer Technology Lookup

1. Open the actor on Apify.
2. Paste website URLs into Website URLs or bare domains into Domains.
3. Keep Max pages per domain at 1 for fast lead enrichment.
4. Increase it to 2-5 if you need more same-domain evidence.
5. Run the actor.
6. Export the dataset as JSON, CSV, Excel, or via API.

Input example

{
  "startUrls": [
    { "url": "https://www.shopify.com" },
    { "url": "https://wordpress.org" }
  ],
  "domains": ["example.com"],
  "maxPagesPerDomain": 1,
  "requestTimeoutSecs": 20,
  "includeRawSignals": false
}

Output example

{
  "domain": "shopify.com",
  "statusCode": 200,
  "technologyNames": ["Cloudflare", "Google Analytics", "React", "Shopify"],
  "categories": ["Analytics", "CDN", "Ecommerce", "JavaScript framework"],
  "confidence": 90,
  "technologies": [
    {
      "name": "Shopify",
      "category": "Ecommerce",
      "confidence": 96,
      "evidence": ["Shopify asset or global"]
    }
  ]
}

Tips for best results

• Use canonical homepage URLs when you have them.
• Bare domains are fine; the actor adds https:// automatically.
• Keep includeRawSignals off for normal CRM exports.
• Enable includeRawSignals when you need audit evidence for scripts and headers.
• Use small page depth for large lists; higher depth costs more and takes longer.

Integrations

Use this actor in workflows such as:

• Enrich a CSV of prospect domains before importing into HubSpot or Salesforce.
• Add technology tags to a Clay, Airtable, or Google Sheets pipeline.
• Monitor a list of competitors for CMS or ecommerce changes.
• Feed technology names into lead scoring or segmentation rules.
• Combine with contact-finding actors from https://apify.com/automation-lab/ for account research.

API usage: Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/wappalyzer-technology-lookup').call({
  domains: ['shopify.com', 'wordpress.org'],
  maxPagesPerDomain: 1
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage: Python

from apify_client import ApifyClient

client = ApifyClient(token='YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/wappalyzer-technology-lookup').call(run_input={
    'domains': ['shopify.com', 'wordpress.org'],
    'maxPagesPerDomain': 1,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage: cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~wappalyzer-technology-lookup/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"domains":["shopify.com","wordpress.org"],"maxPagesPerDomain":1}'

MCP usage

Use the Apify MCP server with Claude Desktop or Claude Code:

$claude mcp add apify-wappalyzer-technology-lookup https://mcp.apify.com/?tools=automation-lab/wappalyzer-technology-lookup

For Claude Desktop, add an MCP server configuration like this:

{
  "mcpServers": {
    "apify-wappalyzer-technology-lookup": {
      "url": "https://mcp.apify.com/?tools=automation-lab/wappalyzer-technology-lookup"
    }
  }
}

Example prompts:

• "Detect technologies for these 50 prospect domains and group them by ecommerce platform."
• "Find which of these competitor sites use Shopify, WordPress, or Webflow."
• "Return domains with Google Tag Manager and Cloudflare from this input list."

Reliability notes

This actor detects public signals visible in headers and HTML. Some technologies are only visible after user interactions, login, or browser execution. For those sites, results may be partial. The actor reports reachable pages and errors so you can identify failed domains.

Proxy guidance

Most website technology lookups do not need proxies. Leave proxy disabled for lower cost. If a specific target list blocks requests, enable Apify Proxy or provide your own proxy URLs.

Legality and ethics

The actor uses public webpages supplied by the user and does not log in, bypass private areas, or collect personal data by design. Always follow target website terms, applicable laws, and your internal data policies.

FAQ

Is this the official Wappalyzer product?

No. It is an Apify actor that performs Wappalyzer-style public technology detection using local signatures and evidence fields.

Why is a technology missing?

The website may hide it behind JavaScript, load it only after consent, or use custom asset names. Increase page depth or enable raw signals for audit trails.

Why did a domain return an error?

The domain may not resolve, may block automated HTTP clients, or may require a browser. Check the error field and retry with a proxy if appropriate.

Can I enrich thousands of domains?

Yes. Keep page depth at 1, disable raw signals, and use batched runs for predictable cost and runtime.

Related scrapers

Use these specific automation-lab actors with Wappalyzer Technology Lookup:

• Tech Stack Detector — broader technology stack detection workflows.
• Shopify Store Analyzer — inspect Shopify stores after this actor flags Shopify technology.
• Website Change Monitor — monitor domains where technology changes matter.
• Broken Link Checker — combine technology enrichment with website QA checks.
• Email Finder — find outreach emails for domains enriched by technology stack.

Changelog

• 0.1 — Initial HTTP-first technology lookup with normalized evidence output.

Support

If a site category is important for your workflow and is not detected yet, open an Apify issue with example URLs and the expected technology. Include dataset rows so the signature can be improved.