Website Tech Stack Detector — CMS, Framework & BuiltWith-Style Technology Lookup (No API)

Find out what any website is built with — in bulk. Drop in a list of domains and get back the CMS, ecommerce platform, JavaScript framework, analytics, marketing/CRM tools, payment widgets, CDN, hosting and web server behind each one. A fast, BuiltWith-style technology lookup and CMS detector for competitive intelligence, lead generation and market research — reading response headers, set-cookies and page HTML in one pass. Domains in → tech stack out, as clean structured JSON, CSV or Excel. No browser, no API key, no monthly subscription.

🏆 Why this tech stack detector?

8+ signal fields per domain across 8 tech categories · hundreds of domains per run, parallelized · header + cookie + HTML fingerprinting (catches signals single-source scrapers miss) · HTTP-only, no headless browser · grouped and flat output for one-click filtering · export to JSON / CSV / Excel. The pay-per-result BuiltWith / Wappalyzer API alternative — no seat fees, no per-lookup credits.

---

✨ What this Actor does / Key features

• 🧱 Detects the full stack — CMS, ecommerce, JS framework, analytics, marketing/CRM, payments, CDN/hosting and web server, per domain.
• 📦 Bulk-first — hundreds of domains per run, parallelized for speed; paste a list or pipe one in via Start URLs.
• 🕵️ Header + cookie + HTML fingerprinting — reads response headers, set-cookies and page markup, so it catches signals single-source scrapers miss.
• 🎯 Precision-tuned — detection patterns are kept specific to avoid the false positives that plague naive keyword matching; when a signal is ambiguous, it's omitted rather than guessed.
• 🗂️ Grouped output — technologies organized byCategory plus a flat technologies list, so you can filter prospect lists in one click.
• ⚡ HTTP-only & cheap — no browser needed, low cost per result.
• 🌐 Optional proxy — Apify Proxy integration; datacenter proxy is enough for most sites.
• 🔀 Flexible input — accepts domains with or without https://, plus a startUrls list for piping from another Actor or an uploaded file.

✅ What it detects

Category	Examples
CMS	WordPress, Shopify, Wix, Squarespace, Webflow, Framer, Drupal, Joomla, Ghost, HubSpot CMS, Contentful, Sitecore
Ecommerce	Shopify, WooCommerce, Magento, BigCommerce, PrestaShop, Salesforce Commerce, Ecwid
JS frameworks	Next.js, Nuxt, React, Vue, Angular, Svelte, Gatsby, Astro, jQuery
Analytics	Google Analytics, GTM, Meta Pixel, Hotjar, Segment, Mixpanel, Plausible, Matomo, Amplitude
Marketing / CRM	HubSpot, Mailchimp, Klaviyo, Intercom, Drift, Zendesk, Tawk.to, Crisp
Payments	Stripe, PayPal, Klarna
CDN / hosting	Cloudflare, Fastly, Akamai, Vercel, Netlify, CloudFront, GitHub Pages, S3
Web server	Nginx, Apache, IIS, LiteSpeed, OpenResty, Caddy

🚀 Quick start (3 steps)

1. Add your domains — paste them into Domains (shopify.com, https://www.bbc.com — with or without https://). Big list? Pipe it via Start URLs.
2. Run — click Start. The Actor fetches each site in parallel and streams one row per domain into your dataset.
3. Get your data — open the Output tab and export to JSON, CSV, Excel or XML, or pull it via the Apify API. Filter by cms, ecommerce or any value in technologies to build a laser-targeted prospect list.

📥 Input

Provide domains in Domains and/or Start URLs. Everything else is optional.

Example — quick domain list

{
  "domains": ["shopify.com", "techcrunch.com", "gatsbyjs.com", "stripe.com"],
  "concurrency": 10
}

Example — bulk prospecting run (find the ecommerce stacks)

{
  "domains": [
    "store-one.com", "store-two.com", "store-three.com", "store-four.com"
  ],
  "concurrency": 20,
  "proxyConfiguration": { "useApifyProxy": true }
}

Example — pipe a URL list from another Actor / uploaded file

{
  "startUrls": [
    { "url": "https://www.wordpress.org" },
    { "url": "https://www.vercel.com" }
  ],
  "concurrency": 15
}

Field	Type	Description
domains	array	Domains or URLs to analyze (e.g. shopify.com, https://www.bbc.com). With or without https://.
startUrls	array	Alternative URL list input (e.g. from another Actor or an uploaded file). Merged with domains.
concurrency	integer	Parallel requests (1–30). Higher = faster on large lists. Default 10.
proxyConfiguration	object	Optional Apify Proxy settings. Datacenter is enough for most sites. Default: Apify Proxy on.

Tip: you don't need a fully-formed URL — bare domains like example.com work fine, and domains + startUrls are merged, so you can combine a quick paste with a piped list.

📤 Output

One row per domain — technologies detected across all categories, both grouped and flat, exportable to JSON, CSV, Excel or XML. Here is a sample record:

{
  "domain": "techcrunch.com",
  "statusCode": 200,
  "title": "TechCrunch | Startup and Technology News",
  "cms": "WordPress",
  "ecommerce": null,
  "server": "Nginx",
  "generator": "WordPress 6.x",
  "technologies": ["WordPress", "HubSpot", "Google Tag Manager", "Cloudflare"],
  "byCategory": {
    "CMS": ["WordPress"],
    "Analytics": ["Google Tag Manager"],
    "Marketing": ["HubSpot"],
    "CDN/Hosting": ["Cloudflare"]
  },
  "technologyCount": 4
}

💡 Use cases

• B2B prospecting — build target lists by technology: "all Shopify + Klaviyo stores", "Magento merchants", "sites on HubSpot", "WooCommerce shops".
• Competitive intelligence — see what stack competitors and their customers run.
• Agencies & SaaS sales — find sites using (or missing) a specific tool you replace, integrate with, or migrate from.
• Market research — measure technology adoption across an industry, niche or country.
• Lead enrichment — append tech-stack signals to your CRM records for sharper targeting and messaging.
• Recruiting & sourcing — find companies running the stack you hire for.

Prospecting recipes

• Find Shopify stores to pitch → run your domain list, filter ecommerce = Shopify.
• Target WordPress sites for a plugin/migration offer → filter cms = WordPress.
• Sell a Klaviyo/HubSpot competitor → filter technologies contains Klaviyo or HubSpot.
• Find sites with NO analytics → filter rows where byCategory.Analytics is empty (an easy upsell).
• Map a competitor's customer base → scrape their "customers" page for domains, then detect each one's stack.

👥 Who uses it

B2B sales & outbound teams · agencies and SaaS vendors targeting a specific stack · competitive-intelligence and market researchers · growth/RevOps enriching CRM records · recruiters sourcing by technology — anyone who needs to know what a website is built with at scale.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the domains you fingerprint, with no separate Apify platform fees to calculate, no seat fees and no per-lookup credits. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

Is it legal to detect a website's tech stack? Yes. The Actor fetches each site's public homepage and reads publicly served headers, cookies and HTML — the same signals your own browser receives. You are responsible for using the data in compliance with the target sites' terms and applicable laws.

Is there a BuiltWith / Wappalyzer public API — is this an API alternative? BuiltWith and Wappalyzer are paid tools with monthly subscriptions and per-lookup credits. This Actor does the same job — identify the technologies a site runs — as a bulk Apify Actor with pay-per-result pricing and full API access, no subscription. It's a drop-in BuiltWith API alternative you can call from your own code via the Apify API.

Do I need an API key or a login? No. There is no third-party API key, login or account to configure — only an Apify account. Paste your domains and run.

Does it render JavaScript?

It fingerprints the served HTML, headers and cookies, which reveals the vast majority of stacks (CMS, ecommerce, frameworks, analytics, marketing, payments, CDN/hosting, server) without the cost of a full headless browser. For most prospecting and intelligence use cases this is both faster and cheaper.

How accurate is it?

Detection patterns are deliberately specific to minimize false positives — this is a paid tool, so it favours accuracy over guesses. When a signal is ambiguous, the Actor prefers to omit it rather than report a technology that isn't there.

Can I detect a website's CMS in bulk?

Yes. Paste hundreds of domains and the Actor returns each site's CMS, ecommerce platform and framework in one run, so you can build lists like "all Shopify stores" or "WordPress sites running WooCommerce".

How do I find all Shopify or WooCommerce stores in a domain list?

Run your domains through the detector, then filter the output by ecommerce = Shopify or technologies containing WooCommerce to build a targeted store list.

Can I detect the analytics and marketing tools a website uses?

Yes. The detector fingerprints headers, cookies and HTML to report analytics and marketing tools like Google Analytics, GTM, HubSpot, Klaviyo and Meta Pixel per domain, grouped under byCategory.Analytics and byCategory.Marketing.

Can I feed it a big domain list without an API or login?

Yes. Paste hundreds of domains into domains, or pipe them from another Actor or an uploaded file via startUrls. No key or login required — only an Apify account.

How much data can I get / how many domains per run?

Hundreds of domains per run, parallelized. Raise the concurrency input (1–30) to go faster on large lists; the HTTP-only design keeps cost per result low so big prospecting sweeps stay cheap.

How do I export website tech-stack data to CSV or JSON?

Run your domain list, then download the dataset as CSV, Excel, JSON, XML or JSONL from the Apify console, or pull it via the Apify API. Every detected CMS, framework and tool comes back as structured, filterable fields (cms, ecommerce, technologies, byCategory).

Can I run it on a schedule?

Yes. Schedule periodic runs to track when target sites adopt or drop technologies — a strong buying/selling signal for sales and competitive intelligence.

🔗 More website & lead-gen tools by logiover

Pair the tech-stack detector with the rest of the website-intelligence suite — build a domain list, fingerprint it, then enrich and audit:

Tool	What it does
🌐 Website Contact Scraper	Add emails, phones & socials to each domain you detect
✉️ Bulk Email Verifier	Clean those contacts before outreach (syntax, MX, disposable, typo)
📈 Website SEO Audit Crawler	On-page SEO audit for any site
🔗 Website Link Graph Crawler	Map internal/external link structure
🗺️ Sitemap to URL Crawler	Expand sitemaps into a full URL list
🏷️ JSON-LD & Schema Meta-Tag Extractor	Pull structured data & meta tags per page
🧭 Bulk DNS Records Lookup	Bulk A/MX/TXT/NS records for any domain list
🔐 Bulk SSL Certificate Checker	Certificate validity & expiry in bulk
🛡️ Bulk HTTP Security Headers	Audit security headers across domains
🚦 Bulk URL Status Checker	Bulk HTTP status / uptime checks
🛰️ Subdomain Finder	Discover subdomains for any root domain
🏢 B2B Lead Scraper	Company + person + email B2B leads by sector & country

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Schedule this Actor on Apify to track your target list's technology changes weekly or monthly and catch adoption/churn signals early. Export results to JSON, CSV or Excel, sync to Google Sheets, or push enriched rows to your CRM, database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to build an automated "collect domains → detect stack → enrich → route to sales" pipeline.

⭐ Support & feedback

Found a bug or need an extra field or detection? Open an issue on the Issues tab — response is usually fast. If this Actor saves you research time, a ★★★★★ review on the Store page genuinely helps and is hugely appreciated. 🙏

⚖️ Legal

This Actor fetches publicly served pages and reads publicly available headers, cookies and HTML for technology fingerprinting, and is intended for legitimate research, competitive-intelligence and lead-generation use. You are responsible for complying with the target sites' terms of service and any applicable local laws.

---

📝 Changelog

2026-07-06

• ✨ README overhaul: full field reference, three ready-to-run example scenarios, website-intelligence suite links, expanded high-intent FAQ, and clearer quick-start.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
• Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
• Added ready-to-run example tasks that cover common real-world use cases.

2026-06-15

• Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.

2026-06-07

• Docs: added coverage for BuiltWith API alternative, exporting website tech stack to CSV/JSON, and bulk CMS detection.

2026-06-05

• 🛡️ Reliability fix: results are no longer dropped by strict output validation — runs now complete cleanly even at high volume (thousands of results).
• ⚡ Stability & performance hardening; fresh rebuild.

2026-06-04

• Verified live & refreshed build — reliability/maintenance pass.