Website Tech Stack Detector – Technology Lookup API avatar

Website Tech Stack Detector – Technology Lookup API

Pricing

from $1.00 / 1,000 domains

Go to Apify Store
Website Tech Stack Detector – Technology Lookup API

Website Tech Stack Detector – Technology Lookup API

Find the technologies behind a list of websites: CMS, e-commerce platform, analytics, tag managers, ad pixels, consent tools, chat, CDN and payments, from one polite home-page request per domain. robots.txt obeyed, no personal data, pay only per analysed domain.

Pricing

from $1.00 / 1,000 domains

Rating

0.0

(0)

Developer

Rowcraft

Rowcraft

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

16 hours ago

Last modified

Share

Website Tech Stack Detector: Technology Lookup API

Find out which technologies a website runs on: its CMS, e-commerce platform, analytics, tag manager, ad pixels, cookie consent tool, live chat, CDN, hosting, web server, payment providers, frameworks, A/B testing, e-mail marketing and rating widgets. Give the actor a list of domains or URLs; it reads each home page once, politely, and returns one row per website with every technology it found, its version when the page shows it, and the evidence behind each detection, as JSON, CSV or Excel.

The detection rules are Rowcraft's own: 336 fingerprints in 41 categories, written and checked on real home pages, built for precision first. A technology is reported only when the page shows a clear sign of it, so a WooCommerce shop is not tagged as VTEX because the word "vtex" appears somewhere in its code.

Input form of Website Tech Stack Detector – Technology Lookup API

What you get

One row per website:

  • Identity: the domain, the address you gave, the home page address after redirects, HTTP status, page title and declared language
  • E-commerce platform: one name (Shopify, WooCommerce, Magento, PrestaShop, VTEX, Salesforce Commerce Cloud, BigCommerce, Shopware...) or null
  • Every technology found: name, category, version (when the page shows it, for example WordPress 7.2 or jQuery 3.7.1) and the evidence: the header, cookie name, generator tag, script address or code snippet that gave it away
  • 16 ready-made columns for filtering in a spreadsheet, each a comma-separated list of names (empty when nothing of that kind was found): cms, ecommerce, analytics, tagManagers, advertising, consent, chat, cdn, hosting, server, payments, frameworks, abTesting, emailMarketing, ratings, other
  • Change tracking: a stackHash of the set of technologies, which changes when a tool is added or removed, and the time of the check

The run also writes a COVERAGE record with one line per domain you asked for (ok, blocked, robots_disallowed, not_found, error or not_checked, with the reason) and a RUN_SUMMARY with counts and the most frequent technologies of the list.

Why this actor

  • Evidence with every detection. Each technology comes with what was seen on the page, so you can trust it, check it in the page source, or filter it out.
  • Precision first. A technology needs one strong sign (a header, a cookie name, a script from its own servers) or two independent weaker ones. Words that only look like a product name in minified code do not count.
  • Own rules, no third-party database. The 336 fingerprints were written by Rowcraft on the home pages of 126 real websites (shops on Shopify, WooCommerce, VTEX, PrestaShop, Magento, Salesforce Commerce Cloud and others, publishers, software companies and framework sites), then checked on 29 more that were not used to write them.
  • Shopify app detection. Apps that Shopify loads through its own loader (Klaviyo, Attentive, Smile.io, Postscript, Klevu and more) are read from the loader list, where a plain script scan misses them.
  • Pay only for websites read. Domains behind an anti-bot page, disallowed by robots.txt, not found, invalid or repeated in your list are never charged.
  • Polite by design. robots.txt is read and obeyed first, then one request for the home page, one request per second by default.

How to use it

  1. Open the Actor and paste your domains or URLs into Domains or URLs, one per line. A column copied from a spreadsheet works, and so do entries separated by commas.
  2. For a first try keep the list short, or set Maximum domains delivered to a small number.
  3. Click Start. The status line shows progress; the run stops cleanly at your maximum or at the charge limit you set in the run options.
  4. Open the Dataset tab: the Overview, Marketing stack and Infrastructure views show the main columns. Download JSON, CSV, Excel, XML or HTML, or send the rows to Google Sheets, Slack, Make, n8n or Zapier with the Integrations tab.
  5. Open the COVERAGE record in the key-value store to see which domains could not be read and why.
  6. To watch a list over time, run it on a schedule with Only new rows since the last run turned on: a website is delivered, and charged, again only when its technologies changed.

Input

FieldWhat it does
domainsDomains (example.com) or addresses (https://www.example.com/shop), one per line. Only the home page is read; the path is ignored. Up to 100,000 per run.
maxItemsStop after this many delivered rows. 0 = the whole list.
onlyNew, stateNameDeliver a website only when its set of technologies changed since the last run with the same state name
notifyUrl, notifyWhenEmptyA webhook that receives one message when the run ends; see Automation below
requestIntervalMsPause between requests, default 1000 ms, minimum 250 ms

Example: three websites, one row each.

{
"domains": ["landyachtz.com", "deathwishcoffee.com", "wordpress.org"]
}

Example: a weekly check of competitors that reports only the websites whose stack changed, with a Slack message.

{
"domains": ["competitor-one.com", "competitor-two.com", "competitor-three.com"],
"onlyNew": true,
"stateName": "competitors",
"notifyUrl": "https://hooks.slack.com/services/..."
}

Output

28 fields per row. Empty values are null, never missing, so CSV and Excel columns are stable.

FieldTypeExample
idstringpipsnacks.com
domainstringpipsnacks.com
inputUrlstringhttps://www.pipsnacks.com/collections
urlstringhttps://www.pipsnacks.com/
statusCodeinteger200
siteTitlestringPip's Heirloom Snacks | The Classics, Made Better with Heirloom Corn
languagestringen
ecommercePlatformstringShopify
technologyCountinteger10
technologiesarray[{"name": "Shopify", "category": "E-commerce", "version": null, "ev…
cmsstringWordPress
ecommercestringShopify
analyticsstringGoogle Analytics, Hotjar
tagManagersstringGoogle Tag Manager
advertisingstringMeta Pixel, TikTok Pixel
consentstringOneTrust
chatstringGorgias
cdnstringCloudflare
hostingstringNetlify
serverstringNginx, PHP
paymentsstringPayPal, Klarna
frameworksstringTailwind CSS
abTestingstringOptimizely
emailMarketingstringKlaviyo, Postscript
ratingsstringYotpo
otherstringaccessiBe, Adobe Fonts
stackHashstringecd687c9fdc5c713
checkedAtstring2026-10-12T16:36:39.772Z

Example rows

Two real rows from a run (long texts shortened here, complete in the dataset):

[
{
"id": "deathwishcoffee.com",
"domain": "deathwishcoffee.com",
"inputUrl": "deathwishcoffee.com",
"url": "https://www.deathwishcoffee.com/",
"statusCode": 200,
"siteTitle": "#1 Organic and #1 Fair Trade Coffee – Death Wish Coffee",
"language": "en",
"ecommercePlatform": "Shopify",
"technologyCount": 9,
"technologies": [
{
"name": "Cloudflare",
"category": "CDN",
"version": null,
"evidence": [
"header cf-ray",
"header cf-cache-status",
"header server: cloudflare"
]
},
{
"name": "Shopify",
"category": "E-commerce",
"version": null,
"evidence": [
"header shopify-complexity-score",
"header powered-by: Shopify",
"cookie _shopify_essential"
]
},
{
"name": "Klaviyo",
"category": "Email marketing",
"version": null,
"evidence": [
"script static.klaviyo.com/"
]
},
"… 6 more"
],
"cms": null,
"ecommerce": "Shopify",
"analytics": null,
"tagManagers": "Google Tag Manager",
"advertising": null,
"consent": null,
"chat": "Gorgias",
"cdn": "Cloudflare",
"hosting": null,
"server": null,
"payments": null,
"frameworks": null,
"abTesting": null,
"emailMarketing": "Klaviyo, Postscript",
"ratings": null,
"other": "Ordergroove, Smile.io, Rebuy",
"stackHash": "53e7ff3ea33e41c1",
"checkedAt": "2026-10-12T17:56:36.443Z"
},
{
"id": "landyachtz.com",
"domain": "landyachtz.com",
"inputUrl": "landyachtz.com",
"url": "https://landyachtz.com/",
"statusCode": 200,
"siteTitle": "Landyachtz Skateboards - Top Shelf Cruisers, Longboards & Skateboards",
"language": "en-US",
"ecommercePlatform": "WooCommerce",
"technologyCount": 18,
"technologies": [
{
"name": "Google Ads",
"category": "Advertising",
"version": null,
"evidence": [
"script www.googletagmanager.com/gtag/js",
"inline script: gtag('config', 'AW-1014719109"
]
},
{
"name": "Meta Pixel",
"category": "Advertising",
"version": null,
"evidence": [
"inline script: connect.facebook.net/en_US/fbevents.js",
"html: //www.facebook.com/tr?id=418194628954459"
]
},
{
"name": "Snap Pixel",
"category": "Advertising",
"version": null,
"evidence": [
"inline script: sc-static.net/scevent.min.js"
]
},
"… 15 more"
],
"cms": "WordPress",
"ecommerce": "WooCommerce",
"analytics": "Google Analytics, Hotjar",
"tagManagers": null,
"advertising": "Google Ads, Meta Pixel, Snap Pixel, TikTok Pixel",
"consent": null,
"chat": null,
"cdn": "Cloudflare, unpkg",
"hosting": null,
"server": "PHP",
"payments": null,
"frameworks": "jQuery, jQuery Migrate, Swiper",
"abTesting": null,
"emailMarketing": "Klaviyo",
"ratings": null,
"other": "Elementor, Cloudflare Turnstile, Rank Math",
"stackHash": "eee5a82bf3c9a382",
"checkedAt": "2026-10-12T17:56:31.521Z"
}
]

Results can be downloaded as JSON, CSV, Excel, XML or HTML from the Dataset tab, or read through the Apify API.

Results of Website Tech Stack Detector – Technology Lookup API in the Apify dataset view

Pricing

Pay per result. You pay for each website read and delivered to your dataset, nothing else: no subscription, no minimum, no charge for domains that could not be read (anti-bot page, robots.txt, not found, errors), for invalid or repeated entries, or for websites skipped by Only new rows because nothing changed.

Your Apify planPrice per 1,000 rowsPrice per row
Free plan$1.50$0.0015
Starter plan$1.30$0.0013
Scale plan$1.20$0.0012
Business plan and above$1.00$0.001

Example: 1,000 websites cost $1.50 on the Free plan and $1.00 on the Business plan. The Apify platform usage of a run (compute and storage) is billed by Apify separately, as for every Actor; the actor runs in 256 MB and spends most of its time waiting between requests. A start event of $0.00005 is charged once per run (Apify default). Cap your spend: set Maximum total charge in the run options. The actor stops cleanly when the cap is reached and you keep everything delivered until then. The run summary (RUN_SUMMARY in the key-value store) says why a run stopped.

Automation: only new rows, notifications, schedules

Only new rows since the last run. Turn on onlyNew and the actor remembers, for every website it delivered to you, the set of technologies it had (in a key-value store named rowcraft-website-tech-stack-detector-state in your Apify account). The next run with the same stateName delivers a website again only when a technology was added or removed; websites with the same stack are skipped and not charged. A version change alone (WordPress 7.1 to 7.2) does not count as a change. The first run delivers every website it can read. Use a different stateName for each list so they keep separate memories.

Notification when the run ends. Put a webhook address in notifyUrl and the actor sends one JSON POST with the number of delivered rows, links to the dataset (JSON and CSV) and the run. It works with Slack and Discord incoming webhooks (the message is in text and content), with Make, n8n and Zapier catch hooks, and with your own endpoint. By default it is sent only when at least one row was delivered; notifyWhenEmpty sends it every time.

Schedules. Create a schedule in Apify Console (daily, weekly, monthly or cron) with onlyNew on, and you get a feed of the websites in your list that changed their stack, for the price of those rows only.

Integrations. Send the results to Make, n8n, Zapier, Google Sheets, Slack, Google Drive, Airtable or any webhook from the Integrations tab of the Actor, with no code.

API, SDKs and AI agents. Every run is available through the Apify API and the official JavaScript and Python clients; the Actor can also be called by AI agents through the Apify MCP server. The example input in the API tab is a working call.

Use cases

  • Lead lists by platform: from a list of shop domains, keep the ones on Shopify, WooCommerce or Magento, or the ones without a consent tool, a live chat or an e-mail marketing tool, and sell to exactly those.
  • Agency and SaaS prospecting: find the websites that use a competitor's product (a chat widget, a rating widget, an A/B testing tool) and offer yours.
  • Competitor monitoring: a weekly schedule with Only new rows tells you when a competitor adds a new analytics tool, payment provider or marketing platform.
  • Market research: the share of each CMS, platform or consent tool in a list of thousands of websites, from the topTechnologies of the run summary or the dataset.
  • CRM enrichment: add platform and marketing stack columns to company accounts before a campaign.
  • Before scraping a shop: check the platform first, then use the matching Rowcraft actor, such as the Shopify Products Scraper, the WooCommerce Products Scraper or the VTEX Products Scraper.

Ready-made examples, each with the input filled in (open one and press Start, or save it as your own task):

What this actor does not do

  • Collect contacts: no e-mail addresses, phone numbers, names of people or social profiles, and no page text apart from the title.
  • Crawl a website: only the home page is read, never other pages, the shop, the checkout or the sitemap.
  • Use BuiltWith or Wappalyzer data: no third-party database is queried or copied; every detection comes from the page read during your run.
  • Return history: each row is the stack seen at the time of the run; for changes over time use Only new rows on a schedule.
  • Run JavaScript, log in, accept cookie banners, use proxies or solve CAPTCHAs: websites that answer with an anti-bot page are reported as blocked and not charged.

Limits and fair use

  • One request per second by default (minimum 250 ms). A website takes two to four requests: robots.txt, the home page and any redirects. In our test runs that came to about three seconds per website, roughly 1,200 websites an hour.
  • What is visible on the first load only. The actor reads the HTML and headers of the home page without running JavaScript. Tools that are added later by a tag manager, after cookie consent, on scroll or only on other pages (the checkout, a contact page) are not seen.
  • Anti-bot pages. Websites behind a bot challenge (Cloudflare, Akamai, DataDome and similar) are reported as blocked and not charged. In our tests 38 of 198 websites, mostly large brands and retailers, answered with an anti-bot page. After 10 blocked websites in a row the run stops and says why in the run summary, because the rest of the list would most likely be blocked too.
  • robots.txt is obeyed for every address the visit touches, including redirect targets. If robots.txt disallows the home page the domain is robots_disallowed; if robots.txt answers with a server error the site is not read, as the robots.txt standard (RFC 9309) requires.
  • Page size: the first 2 MB of a home page are read; larger pages are cut there and counted in the run summary.
  • Up to 100,000 domains per run. The run stops 90 seconds before its timeout with the summary, the coverage and the Only new rows memory saved; for long lists raise the timeout or split the list.

Data source and licence

The data is what each website sends to every visitor: the response headers, the names of the cookies it sets, and the HTML of its home page. The actor reads that page once, as a browser does on the first visit, after checking robots.txt, and keeps only the names of the technologies, their versions and short evidence (a header name, a script address, a code fragment of a few words). The page text, images and cookie values are not stored or delivered.

The detection rules are Rowcraft's own work, written and tested on real websites; they are not derived from Wappalyzer, webappanalyzer, BuiltWith or any other fingerprint database.

Rowcraft is independent: this actor is not provided, endorsed or authorised by the websites it reads or by the makers of the technologies it names. Product names and trademarks belong to their owners and are used only to say which product a website uses.

Privacy: no personal data

Rowcraft actors are built not to collect personal data:

  • Only the home page of a website is read, and the row holds technology names, categories, versions and evidence, plus the page title and language.
  • Cookie values are never read or stored, only cookie names (such as _shopify_essential), which identify a product, not a person.
  • An e-mail address or phone number inside the page title or a code fragment is removed, and a script address that would contain one is reduced to its host name.
  • The actor sends no cookies, fills no forms and never logs in.

You are responsible for using the data in line with the law that applies to you.

Other Rowcraft actors

All Rowcraft actors read official or public sources, deliver flat rows without personal data and support only-new runs and notifications:

FAQ

Which technologies can it detect? 336 technologies in 41 categories, including 26 CMS and site builders (WordPress, Drupal, Wix, Squarespace, Webflow...), 15 e-commerce platforms, 27 analytics tools, 6 tag managers, 21 advertising and affiliate tags, 17 consent tools, 15 chat tools, 13 payment providers, 12 rating widgets and 14 e-mail and marketing automation tools, plus CDNs, hosting, servers, frameworks, search, security, video, fonts and more.

How accurate is it? The rules favour precision over recall. On the 126 home pages used to write them the actor makes 818 detections, each checked by hand against its evidence; the false positives found there (for example the letters "vtex" inside minified code of a WooCommerce shop) were fixed. On 29 further websites that were not used to write the rules, all 162 detections named a technology the page really loads; one version was wrong (a cache-busting number read as the jQuery version) and has been fixed. Expect some technologies to be missed, and check any detection against its evidence.

Why does a tool I know the website uses not appear? The actor sees what the home page sends on the first load, without running JavaScript. Tools injected later by a tag manager, after cookie consent, or present only on other pages are not visible there. A tool can also be outside the 336 the actor knows.

Why is the result empty? Every domain in the list could not be read, or was skipped. The COVERAGE record gives the reason per domain: an anti-bot page (blocked), robots.txt (robots_disallowed), no website at that address (not_found), an invalid entry or a connection problem (error). With Only new rows on, websites whose stack did not change are skipped too. Nothing is charged for those, apart from the start event.

Is it legal? The actor reads one public page per website, the home page any visitor gets, obeys robots.txt and collects which tools the page loads, not personal data or page content. Whether and how you may use the results (for example for marketing) depends on the law that applies to you.

Does it collect personal data? No personal data: no e-mail addresses, phone numbers, people's names or cookie values. See the Privacy section.

Do I pay for websites that block the actor? No. Blocked, robots-disallowed, not found and invalid entries are never charged, and neither are duplicates in your list.

Does it show versions? When the page shows them: a generator tag (WordPress 7.2, Elementor 4.3.2) or a version in a file name (jQuery 3.7.1). Otherwise version is null.

Can I give full URLs instead of domains? Yes. The address is reduced to its website and only the home page is read; inputUrl keeps what you gave and url shows the home page that answered after redirects.

How does Only new rows work here? The actor remembers the set of technologies of each website delivered to you. The next run with the same state name delivers a website only when a technology was added or removed, so a weekly schedule costs only the websites that changed.

Support and reviews

Problems, missing fields, questions: open an issue on the Issues tab of this Actor. We answer within one working day and fix confirmed bugs in the next release; the changelog lists every change.

If this Actor saved you time, a short review on its page helps other users find it and helps us keep improving it.