Website Tech Stack Detector (CMS, Analytics, Frameworks)

Paste in a list of websites and you get back what each one runs on. That covers the CMS (WordPress, Drupal, Ghost, Statamic and others), the shop platform if there is one (Shopify, WooCommerce, Magento, BigCommerce), the front-end framework (React, Next.js, Vue, Angular, Astro), analytics and tag managers, ad pixels, cookie banners, chat widgets, payments, CDN and hosting.

Each result is grouped by category and shows how it was detected, plus the version when the site gives it away. You pay per site checked, so it works out cheap for one-off lookups and big lists alike.

What it does

• Picks up the web server, CDN and hosting from the HTTP headers
• Spots the CMS, site builder and framework from the page itself
• Finds analytics, ad pixels, chat and other third-party tools, including ones loaded by inline scripts
• Shows version numbers when a site gives them away
• Groups everything by category and shows where each one was found
• Ignores tools that are only mentioned in the page text
• One bad address doesn't stop the rest of the list
• Refuses private and internal addresses

Use cases

• Build lead lists by platform, for example every Shopify or WordPress store in a spreadsheet of domains.
• Check which analytics, chat or marketing tools a company uses before a sales call.
• Compare your stack with competitors'.
• Speed up SEO and agency audits: CMS, tag manager and tracking setup in one go.
• Count how common a technology is across a few hundred sites.

How to use

1. Put one or more website addresses into URLs (https:// is optional).
2. Press Start. Each site takes about a second.
3. Open the results table and export to CSV, Excel or JSON if you need to.

You can also call it from the Apify API, run it on a schedule, or hook it up to Make, Zapier or n8n. AI agents can use it through Apify's MCP server.

Input

{
  "urls": [
    "https://example.com",
    "https://www.wikipedia.org"
  ]
}

Output

One dataset item per input with fields: url, finalUrl, status, technologies, categories, techCount, error.

Here's a real result:

{
  "url": "https://laravel.com",
  "finalUrl": "https://laravel.com",
  "status": 200,
  "technologies": [
    {
      "name": "Fathom",
      "category": "Analytics",
      "version": null
    },
    {
      "name": "Cloudflare",
      "category": "CDN",
      "version": null
    },
    {
      "name": "Statamic",
      "category": "CMS",
      "version": null
    },
    {
      "name": "HubSpot",
      "category": "Marketing automation",
      "version": null
    },
    {
      "name": "PHP",
      "category": "Programming language",
      "version": null
    },
    {
      "name": "Google Tag Manager",
      "category": "Tag manager",
      "version": null
    }
  ],
  "categories": {
    "Analytics": [
      "Fathom"
    ],
    "CDN": [
      "Cloudflare"
    ],
    "CMS": [
      "Statamic"
    ],
    "Marketing automation": [
      "HubSpot"
    ],
    "Programming language": [
      "PHP"
    ],
    "Tag manager": [
      "Google Tag Manager"
    ],
    "Web framework": [
      "Laravel"
    ]
  },
  "techCount": 7,
  "error": null
}

Pricing

Pay per event: $0.0024 per site analyzed (successful results only; failed items are returned with an error field and are not charged). Set a maximum charge per run in the run options.

So 100 sites cost about $0.24, and 1,000 cost about $2.40.

FAQ

How many technologies does it know?

Around 180, from web servers and CDNs through to analytics, ad pixels, consent tools, chat, payments and monitoring. Where one thing implies another (Next.js means React, for example) it adds that too.

Why do some big sites come back with very little?

A few large sites (big news publishers, Apple) run their own custom setup and host everything themselves, so there isn't much standard to spot. This tool reads the headers and HTML. It doesn't run the page's JavaScript in a browser.

Am I charged for sites that fail?

No. If a site can't be reached or the address is invalid, you get an error row and no charge.

Can I check thousands of sites?

Up to 500 per run. For more, split the list or schedule several runs.

Limitations

• It reads headers, cookies and HTML but doesn't run JavaScript, so things loaded later by scripts can be missed.
• Only public http(s) sites. Private and internal addresses are refused.
• Results show the page as it was when checked.

Other tools you might like

• Sitemap URL Extractor & XML Sitemap Checker: pull every URL out of a site's sitemaps and check them for problems.
• Steam Reviews Analyzer: why players like (or drop) a game, from its Steam reviews.

Support

This Actor is built and maintained by an automated system run by its publisher. If something's wrong, open an issue and it'll be looked at within 7 days. Please don't put passwords or personal details in an issue.