Website Tech Stack — Frameworks Analytics CDN Detect avatar

Website Tech Stack — Frameworks Analytics CDN Detect

Under maintenance

Pricing

Pay per usage

Go to Apify Store
Website Tech Stack — Frameworks Analytics CDN Detect

Website Tech Stack — Frameworks Analytics CDN Detect

Under maintenance

One HTTP probe per URL → detect frameworks (React, Vue, Next, Nuxt, Svelte), analytics (GA, Plausible, Mixpanel), CDN (Cloudflare, Vercel, Netlify), language hints. Static-HTML pattern match, no JS execution.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

vøiddo

vøiddo

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

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
}
FieldTypeDefaultDescription
urlsarray of strings["stripe.com","notion.so","figma.com"]Domains or full https:// URLs to probe
followRedirectsbooleantrueFollow up to 3 HTTP redirects per URL

Output: one dataset row per input URL with the fields shown above.

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

EventDescriptionPrice
tech_snapshotOne URL probed and tech-stack-detected.$0.001

You are charged one tech_snapshot event per URL in the urls input list, regardless of what is detected. A 404 or redirect error still costs one event because the HTTP probe was made.


Buyer

  • Sales engineers and SaaS founders who need to qualify prospects by the tools their site runs — target only Next.js shops, Shopify merchants, etc.
  • 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 — identify legacy stacks or missing analytics in bulk.
  • Researchers mapping technology adoption trends across a curated URL list.

Source

Data is collected directly from the target website via a single HTTP GET request per URL. No third-party API is involved.

  • Endpoint pattern: https://{url} (GET)
  • Detection method: response headers (Server, CF-Ray, Via, X-Powered-By) + static HTML body regex
  • No JavaScript execution — dynamic or client-side-only signals are not detected