Website Tech Stack: Frameworks Analytics CDN Detect

Wappalyzer-style HTML probe. One HTTP GET per URL → detect JS frameworks, analytics tools, CDN, CMS, and language. Pure HTTP, no JS execution required.

---

Example output row

{
  "url": "stripe.com",
  "finalUrl": "https://stripe.com/",
  "httpStatus": 200,
  "server": "envoy",
  "cdn": "Cloudflare",
  "frameworks": ["React", "Next.js"],
  "analytics": ["Google Analytics", "Segment"],
  "cms": "",
  "language": "en"
}

---

How to use

Input shape:

{
  "urls": ["stripe.com", "notion.so", "figma.com"],
  "followRedirects": true
}

Field	Type	Default	Description
urls	array of strings	["stripe.com","notion.so","figma.com"]	Domains or full https:// URLs to probe
followRedirects	boolean	true	Follow HTTP redirects. A URL that redirects too many times is emitted with an error field

Output: one dataset row per input URL with the fields shown above. Rows for probes that failed or were blocked by robots.txt carry an extra error field (robots_closed, too_many_redirects or an error message).

Detected signals:

• Frameworks: React, Vue, Next.js, Nuxt, Svelte, Angular, Ember
• Analytics: Google Analytics, Plausible, Mixpanel, Amplitude, Segment, Hotjar, PostHog
• CDN: Cloudflare, Vercel, Netlify, CloudFront, Fastly, Akamai (via headers)
• CMS: WordPress, Shopify, Drupal, Ghost, Webflow, Squarespace, Wix
• Language: from <html lang=""> attribute

---

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
Result	$4.25	$3.83	$3.40	$2.98

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

You are charged one tech_snapshot event per URL that was probed successfully, regardless of what is detected. A 404 page still costs one event because the HTTP probe was made. URLs that fail (network error, too many redirects) or are closed by robots.txt are emitted with an error field and are not charged.

---

Buyer

• Sales engineers and SaaS founders who need to qualify prospects by the tools their site runs, for example targeting only Next.js shops or Shopify merchants.
• Marketing teams building competitor intelligence dashboards by tech category.
• Growth hackers looking for sites running a specific analytics or CMS stack to pitch migration services.
• Agencies auditing client site hygiene before onboarding, to identify legacy stacks or missing analytics in bulk.
• Researchers mapping technology adoption trends across a curated URL list.

---

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/website-tech-stack-detector").call(run_input={"urls": ["stripe.com", "notion.so", "figma.com"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/website-tech-stack-detector').call({"urls": ["stripe.com", "notion.so", "figma.com"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~website-tech-stack-detector/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"urls": ["stripe.com", "notion.so", "figma.com"]}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/website-tech-stack-detector",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Sitemap URL Extractor: Robots.txt and Sitemap Index to URLs
• SEO Audit Tool (On-Page Checker, Canonical, Alt Text)
• Website Content Crawler: Pages to Clean Text
• FCC ECFS Public Notices & Filings Scraper
• Federal Register Scraper: Rules, Proposed Rules, Notices
• Yahoo Finance Scraper: Stock Quotes and Key Statistics

Source

Data is collected directly from the target website via a single HTTP GET request per URL, plus one request for the site's robots.txt (cached per site within a run). No third-party API is involved.

• Endpoint pattern: https://{url} (GET)
• robots.txt: pages disallowed for all crawlers (User-agent: *) are not fetched; if robots.txt cannot be read (access denied, server error or no answer), the page is not fetched either. Such rows carry error: "robots_closed".
• Detection method: response headers (Server, CF-Ray, X-Powered-By and CDN request-id headers) + static HTML body regex
• No JavaScript execution: dynamic or client-side-only signals are not detected