Website Tech Stack Detector — Identify Technologies Behind Any Website

Detect the complete technology stack of any website in seconds. Analyze CMS, frameworks, analytics tools, payment providers, CDN, email marketing, chat widgets, monitoring, and 80+ other technologies — all from a single URL.

A faster, cheaper alternative to BuiltWith ($295/mo) and Wappalyzer.

Detect Website Technology Stack

Identify what CMS, frameworks, analytics tools, and hosting a website uses. Supports 80+ technologies including WordPress, Shopify, React, Next.js, GA4, and more.

Alternative to BuiltWith and Wappalyzer

Get the same technology detection at a fraction of the cost. Pay per website analyzed — no monthly subscription.

Bulk Website Technology Analysis

Scan up to 1000 websites in a single run. Perfect for competitive research, lead qualification, and market analysis.

What it does

Enter one or thousands of URLs, and the actor will:

1. Fetch each website's HTML, HTTP headers, and cookies
2. Match against 80+ technology signatures across 15 categories
3. Return a structured JSON dataset with all detected technologies, security headers, and server info

No browser needed. No JavaScript rendering. Just fast HTTP analysis — processes ~100 websites per minute.

Why use this over BuiltWith or Wappalyzer?

Feature	BuiltWith	Wappalyzer	This Actor
Price	$295/month	$250/month (Teams)	~$0.002/site (PPE)
Bulk analysis	Limited	Limited free tier	Unlimited
API access	Paid add-on	Paid	Included (Apify API)
Technologies detected	50,000+	1,500+	80+ (most common)
AI/MCP compatible	No	No	Yes (PPE pricing)
Real-time analysis	Cached data	Cached data	Live analysis
Custom deployment	No	Browser extension	Full API control

Key advantage: BuiltWith costs $295/month for 50 lookups. This actor costs ~$0.002 per site — analyze 1,000 sites for $2.

Trade-off: BuiltWith and Wappalyzer detect many more niche technologies. This actor focuses on the 80+ most common and commercially relevant technologies that matter for sales, marketing, and competitive analysis.

Detected technologies (80+)

Category	Technologies
CMS	WordPress, Shopify, Wix, Squarespace, Webflow, Ghost, Drupal, Joomla, Hugo, Gatsby
Framework	Next.js, Nuxt.js, Astro, Remix, SvelteKit, Angular, React, Vue.js, Laravel, Django, Rails, Express
Analytics	Google Analytics, GTM, Plausible, Fathom, Hotjar, Mixpanel, Segment, Amplitude, PostHog, Heap, Matomo, Clarity, Facebook Pixel
Payment	Stripe, PayPal, Paddle, LemonSqueezy, Gumroad
CDN/Hosting	Cloudflare, Vercel, Netlify, AWS CloudFront, Fastly, Akamai, Render, Fly.io, Railway
Email	Mailchimp, SendGrid, ConvertKit, ActiveCampaign, Brevo, Klaviyo
Marketing	HubSpot, Intercom, Drift
Chat	Crisp, Tawk.to, Zendesk, LiveChat, Freshdesk
SEO	Semrush, Ahrefs
A/B Testing	Google Optimize, Optimizely, VWO, LaunchDarkly
Auth	Auth0, Clerk, Supabase, Firebase
Monitoring	Sentry, Datadog, LogRocket, FullStory
CSS	Tailwind CSS, Bootstrap
Ads	Google Ads, Meta Ads
CRM	Salesforce, Pipedrive

Input examples

Analyze a single website

{
  "urls": ["https://stripe.com"]
}

Analyze competitors (batch)

{
  "urls": [
    "https://stripe.com",
    "https://shopify.com",
    "https://vercel.com",
    "https://notion.so",
    "https://linear.app"
  ],
  "maxConcurrency": 10
}

Analyze with proxy (for geo-restricted sites)

{
  "urls": ["https://example.jp", "https://example.de"],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Large-scale analysis (1000+ sites)

{
  "urls": ["https://site1.com", "https://site2.com", "..."],
  "maxConcurrency": 20,
  "timeout": 15
}

Input parameters

Parameter	Type	Default	Required	Description
urls	Array	—	Yes	Website URLs to analyze
maxConcurrency	Integer	5	No	Parallel requests (1–20)
timeout	Integer	30	No	Request timeout in seconds
proxyConfiguration	Object	None	No	Proxy settings

Output format

Field	Type	Description
url	String	Input URL
finalUrl	String	Final URL after redirects
statusCode	Integer	HTTP response status code
technologies	Object	Detected technologies grouped by category
techCount	Integer	Total number of detected technologies
serverInfo	Object	Server header and security headers
analyzedAt	String	Analysis timestamp (ISO 8601)

Example output

{
  "url": "https://stripe.com",
  "finalUrl": "https://stripe.com/",
  "statusCode": 200,
  "technologies": {
    "Framework": ["Next.js", "React"],
    "CDN": ["Cloudflare", "Vercel"],
    "Analytics": ["Google Analytics", "Segment"],
    "Payment": ["Stripe"],
    "Monitoring": ["Sentry"],
    "CSS": ["Tailwind CSS"]
  },
  "techCount": 8,
  "serverInfo": {
    "server": "cloudflare",
    "securityHeaders": {
      "strict-transport-security": "max-age=63072000",
      "x-content-type-options": "nosniff"
    }
  },
  "analyzedAt": "2026-03-22T10:00:00.000Z"
}

Example: E-commerce site

{
  "url": "https://example-shop.com",
  "finalUrl": "https://example-shop.com/",
  "statusCode": 200,
  "technologies": {
    "CMS": ["Shopify"],
    "Analytics": ["Google Analytics", "GTM", "Facebook Pixel"],
    "Payment": ["Stripe", "PayPal"],
    "Email": ["Klaviyo"],
    "Chat": ["Zendesk"],
    "Ads": ["Google Ads", "Meta Ads"]
  },
  "techCount": 10,
  "serverInfo": {
    "server": "cloudflare",
    "securityHeaders": {}
  },
  "analyzedAt": "2026-03-22T10:01:00.000Z"
}

Integrations

Python integration

from apify_client import ApifyClient

client = ApifyClient("your-apify-api-token")

run = client.actor("tugelbay/website-tech-stack-detector").call(
    run_input={
        "urls": ["https://stripe.com", "https://shopify.com", "https://vercel.com"],
        "maxConcurrency": 10,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(f"\n{item['url']} ({item['techCount']} technologies)")
    for category, techs in item["technologies"].items():
        print(f"  {category}: {', '.join(techs)}")

JavaScript/TypeScript integration

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "your-apify-api-token" });

const run = await client.actor("tugelbay/website-tech-stack-detector").call({
  urls: ["https://stripe.com", "https://shopify.com"],
  maxConcurrency: 10,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const item of items) {
  console.log(`${item.url}: ${item.techCount} technologies`);
  console.log(JSON.stringify(item.technologies, null, 2));
}

Other integrations

• Google Sheets — export tech stack data to a spreadsheet for analysis
• Zapier / Make — trigger workflows based on detected technologies
• Slack — get notifications when analysis completes
• API — call programmatically via Apify REST API
• AI agents — MCP-compatible for AI-powered sales and research workflows

Use cases

Sales prospecting

Find companies using specific tools your product integrates with. Example: find all Shopify stores using Stripe but not your payment analytics tool — those are qualified leads.

Competitive analysis

See exactly what tech competitors use. Compare your stack against theirs. Identify technology trends in your industry.

Lead qualification

Verify if a prospect uses tools your product integrates with before reaching out. Personalize outreach based on their tech stack.

Market research

Map technology adoption across industries. How many SaaS companies use Next.js vs Nuxt.js? How many e-commerce sites use Stripe vs PayPal?

Agency pitches

Show prospects their current stack and suggest improvements. "You're using X for analytics but missing Y for conversion tracking — here's how we'd fix that."

Security audits

Check security headers across your client portfolio. Identify sites missing HSTS, CSP, or other critical headers.

Technology trend tracking

Run weekly analysis on a list of 1,000 top sites to track technology adoption trends over time.

Performance & cost

• Analyzes ~100 websites per minute (depends on target response times)
• Memory: 256MB is sufficient for most runs
• Cost: approximately $0.002 per website on Apify platform

Example costs:

Scenario	Sites	Cost
Quick competitor check (5 sites)	5	~$0.01
Industry analysis (100 sites)	100	~$0.20
Large-scale research (1,000 sites)	1,000	~$2.00
Weekly monitoring (500 sites x 4)	2,000/mo	~$4.00/mo

Compare: BuiltWith charges $295/month. This actor does the same analysis for $2–10/month at typical usage levels.

FAQ

How does it detect technologies?

The actor analyzes three sources:

1. HTML content — looks for framework-specific tags, script includes, meta tags, and DOM patterns
2. HTTP headers — checks server headers, X-Powered-By, and CDN-specific headers
3. Cookies — identifies technology-specific cookies (e.g., Shopify session cookies)

Each technology has a unique signature (regex patterns, header values, cookie names) that the actor matches against.

How accurate is the detection?

Very accurate for the technologies it detects. The actor uses the same detection patterns as Wappalyzer and BuiltWith. However, it covers 80+ technologies vs 1,500+ for Wappalyzer — so it may miss niche or less common tools.

Does it detect technologies loaded via JavaScript?

Partially. The actor uses HTTP-only analysis (no browser), so it detects technologies referenced in the initial HTML. Technologies loaded entirely via JavaScript (e.g., some chat widgets that load asynchronously) may not be detected. For those, you'd need a browser-based analysis tool.

Can I analyze sites behind login walls?

No. The actor only analyzes publicly accessible pages. It sends a single HTTP GET request to each URL.

How often should I re-analyze sites?

For competitive monitoring, weekly or monthly is sufficient. Tech stacks don't change frequently.

Can I export results to Google Sheets?

Yes. Apify has a built-in Google Sheets integration. After the run completes, you can export the dataset directly to a spreadsheet.

Troubleshooting

Low tech count (0-2 technologies)

• Cause: The site may use server-side rendering with minimal client-side technology signatures
• Fix: This is expected for some sites. The actor only detects technologies that leave detectable signatures in HTML/headers.
• Alternative: Sites using custom/proprietary technology won't match any known signatures.

Timeout errors

• Cause: Target site is slow to respond
• Fix: Increase timeout parameter or reduce maxConcurrency

403 / blocked responses

• Cause: Some sites block automated requests
• Fix: Enable Apify proxy with residential proxy groups

Missing CDN detection

• Cause: Some CDNs are transparent and don't add identifiable headers
• Fix: This is a limitation of HTTP-only analysis. The CDN may still be in use but undetectable from headers alone.

Limitations

• Detects 80+ technologies (not the 50,000+ that BuiltWith covers)
• HTTP-only analysis — no JavaScript rendering, so some client-side-only technologies may be missed
• Only analyzes publicly accessible pages (no login-protected content)
• Some CDNs and technologies are transparent and don't leave detectable signatures
• Security header analysis is basic (presence/absence, not full policy validation)

Changelog

v1.0 (2026-03-22)

• Initial release
• 80+ technology signatures across 15 categories
• HTTP headers, HTML content, and cookie analysis
• Concurrent processing with configurable concurrency
• Security header detection
• Proxy support
• PPE pricing

Related Actors

• RAG Web Browser — Search Google + extract as Markdown for AI agents
• Article Extractor — Extract clean article text from any URL
• Google SERP & Indexation Checker — Compare sitemap vs Google index
• Keyword Rank Tracker — Track keyword positions in Google daily
• Google Maps Lead Extractor — Extract business leads with emails from Google Maps

See all actors: apify.com/tugelbay