Website Technology Checker – Tech Stack & CMS Lookup avatar

Website Technology Checker – Tech Stack & CMS Lookup

Pricing

from $2.00 / 1,000 website checkeds

Go to Apify Store
Website Technology Checker – Tech Stack & CMS Lookup

Website Technology Checker – Tech Stack & CMS Lookup

Find the tech stack of any website: CMS, e-commerce platform, analytics, ad pixels, marketing and chat tools, payments, frameworks, hosting and CDN. Bulk domains in, one row per site out, grouped by category. $2 per 1,000 websites; sites that block visits are looked up in a technology database.

Pricing

from $2.00 / 1,000 website checkeds

Rating

0.0

(0)

Developer

Rowfeed

Rowfeed

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Security

Limited permissions

Share

A BuiltWith and Wappalyzer alternative.

Find out what any website is built with: CMS, e-commerce platform, analytics, ad pixels, marketing automation, live chat, payments, front-end framework, hosting, CDN and more. Paste a list of domains; get one row per site with every technology found, grouped into columns by category, ready for a spreadsheet or a CRM. Built for SaaS sales and lead qualification ("which shops run Shopify and Klaviyo?"), agencies, competitor research, investors and AI agents that need a tech stack lookup as JSON. No BuiltWith subscription, no browser extension.

What you get

  • One row per website: cms, ecommerce, analytics, advertising, marketing, chat, payments, frameworks, hosting, servers, cdn, consent, reviews, fonts, video, security, monitoring, testing, search – each a comma-separated list, empty when nothing in that category was found.
  • technologies: the same as a list of {name, category, version}; the version is filled in when the site states it (e.g. WordPress 6.4.2).
  • technology_count, page_title, final_url (after redirects) and source: page (read live) or database.
  • Over 160 technologies, among them Shopify, WooCommerce, Magento, BigCommerce, WordPress, Webflow, Wix, Squarespace, HubSpot, Klaviyo, Mailchimp, Google Analytics and Tag Manager, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, Google Ads, Intercom, Zendesk, Stripe, PayPal, Klarna, Next.js, React, Vue, Cloudflare, Vercel, AWS and OneTrust.

Example output

{
"query": "apify.com",
"domain": "apify.com",
"final_url": "https://apify.com/",
"status_code": 200,
"source": "page",
"technology_count": 8,
"cms": null,
"ecommerce": null,
"analytics": "Google Tag Manager",
"marketing": "HubSpot",
"chat": "Intercom",
"frameworks": "Next.js, Bootstrap",
"hosting": "Amazon Web Services",
"cdn": "Amazon CloudFront",
"security": "HSTS",
"technologies": [{ "name": "Google Tag Manager", "category": "analytics", "version": null }, "..."]
}

Input

FieldWhat it does
domainsOne website per line: a domain (shopify.com) or any link on the site. Up to 5,000 per run.
useDatabaseSites that refuse automated visits are looked up in a licensed technology database instead (default on, paid Apify plan). Off: they get a free error row.

Pricing

Pay per event, no subscription:

  • $0.002 per website checked ($2 per 1,000).
  • $0.02 per technology database lookup, only for sites that answered but refused the live visit (a block or bot challenge). The database bills every lookup, also when it has no data for the site, so that lookup is charged too (the error row says so). Turn it off with useDatabase: false.
  • $0.001 per run start.
  • Sites that cannot be reached, do not exist, time out or have a broken certificate are free; so are sites that refuse the visit when the database is off.

Example: 1,000 websites where 50 refuse the visit cost $1.90 + $1.00 for the 50 database lookups + $0.001. Cap the cost of a run with the maximum charge setting; no database lookup is made that the budget cannot pay for.

Good to know

  • Each site's home page is read once, like a visitor would, with an honest bot name, within 30 seconds. Nothing is bypassed: a site that blocks bots or shows a challenge page is not read. www.x.com and x.com count as one site. Addresses inside private networks are never visited.
  • Detection uses what the home page reveals: its scripts, styles, meta tags, response headers and cookie names. Tools that only load on other pages, after a click or after cookie consent can be missed; so can back-office software that leaves no trace on the page.
  • The database is an earlier crawl, so it can be a few weeks old and lists fewer tools than a live check; rows from it have source: database.

More tools from Rowfeed

Not affiliated with BuiltWith or Wappalyzer.