# Tech Stack Detector for Local Business Websites (`greensboro-web-studio/tech-stack-detector-smb`) Actor

Find out what any list of websites is built with: website builder, CMS, booking and field-service tools (Jobber, Housecall Pro, ServiceTitan, Calendly), analytics, ad pixels, chat, payments and hosting. Fast, no browser, pay only for sites analyzed.

- **URL**: https://apify.com/greensboro-web-studio/tech-stack-detector-smb.md
- **Developed by:** [Gavin Wolfe](https://apify.com/greensboro-web-studio) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 websites

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Tech Stack Detector for Local Business Websites

Paste in a list of websites and get back what each one is built with: the website builder or CMS, booking and field-service software, review widgets, analytics, ad pixels, live chat, payments, hosting and more.

It is built for people who sell to **local and small businesses**: agencies, web designers, SaaS sales teams and lead-gen folks who need to know "is this plumber on Wix or WordPress?" or "does this HVAC company already use ServiceTitan?" before they reach out.

### What it detects

Around 90 technologies, including tools most detectors miss:

- **Website builders and CMS:** WordPress, Wix, Squarespace, GoDaddy Website Builder, Shopify, Webflow, Weebly, Duda, Framer, Hibu, Joomla, Drupal, HubSpot CMS, Square Online, BigCommerce, Magento
- **Field service and booking:** Jobber, Housecall Pro, ServiceTitan, Calendly, Acuity Scheduling, Square Appointments, Vagaro, Mindbody
- **Reviews and lead tools:** Podium, Birdeye, NiceJob, GoHighLevel, Thryv, Angi / HomeAdvisor badges, CallRail
- **Page builders and plugins:** Elementor, Divi, WooCommerce, Yoast SEO
- **Analytics and ads:** Google Analytics 4, Universal Analytics, Google Tag Manager, Google Ads conversion tracking, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, Microsoft Clarity, Hotjar
- **Marketing and chat:** HubSpot, Mailchimp, Klaviyo, Intercom, Drift, Tawk.to, Zendesk, LiveChat, Tidio
- **Payments:** Stripe, PayPal
- **Frameworks:** React, Next.js, Vue.js, Nuxt, Angular, Gatsby, Astro, jQuery, Bootstrap, Tailwind CSS
- **Hosting, CDN and servers:** Cloudflare, Vercel, Netlify, WP Engine, Kinsta, Amazon CloudFront, Fastly, Akamai, Sucuri, Nginx, Apache, IIS, LiteSpeed, PHP, ASP.NET

### How to use it

1. Paste website URLs or bare domains into **Websites**, one per line (for example `joesplumbing.com`). Duplicates are removed for you.
2. Optional: pick categories to keep, such as `Website builder` or `Field service`.
3. Click **Start**. Download the results as CSV, Excel or JSON.

### Output

One row per website:

```json
{
  "inputUrl": "joesplumbing.com",
  "finalUrl": "https://www.joesplumbing.com/",
  "domain": "joesplumbing.com",
  "statusCode": 200,
  "technologies": [
    { "name": "WordPress", "slug": "wordpress", "version": "6.5.2", "confidence": 100, "categories": ["CMS"], "website": "https://wordpress.org" },
    { "name": "Jobber", "slug": "jobber", "version": null, "confidence": 100, "categories": ["Field service"], "website": "https://getjobber.com" }
  ],
  "techNames": ["WordPress", "Jobber"],
  "techList": "WordPress, Jobber",
  "categories": ["CMS", "Field service"],
  "serverHeader": "nginx",
  "scanTimeMs": 412,
  "checkedAt": "2026-10-22T20:15:03.000Z",
  "error": null
}
```

If a site can't be checked, its row says why in `error`: `invalid_url`, `dns_fail`, `timeout`, `tls_error`, `connection_failed`, `http_4xx`, `http_5xx`, `blocked` or `internal_error`. A run summary with the most common technologies is saved to the key-value store as `SUMMARY`.

### Pricing

**You pay only for websites that were analyzed successfully.** Sites that fail (dead domains, timeouts, errors, blocks) still get a row, free. Set a maximum spend for a run and the actor stops when it reaches it.

### Speed

It makes one plain request per website (no browser), so it is fast and cheap. That also means it reads what the server sends. Technologies loaded only after JavaScript runs may not show up.

### Good to know

- Detection is based on public signals in each homepage: headers, cookies, meta tags, script URLs and HTML. It does not log in or crawl past the first page.
- Only check websites you have a legitimate reason to look at, and follow the laws that apply to how you use the results.
- Found something it misses or gets wrong? Open an issue on the actor's page and include the website.

# Actor input Schema

## `urls` (type: `array`):

Website URLs or bare domains, one per line (example: joesplumbing.com). Duplicates are removed automatically.

## `categoriesFilter` (type: `array`):

Leave empty to return everything. Examples: Website builder, CMS, Ecommerce, Field service, Scheduling, Reviews, Analytics, Advertising, Live chat, Payments, Hosting, CDN.

## `includeVersions` (type: `boolean`):

Report version numbers when a site exposes them (for example WordPress 6.5).

## `includeEvidence` (type: `boolean`):

Add a short note for each technology showing what gave it away (header, script URL or HTML snippet). Useful for auditing results.

## `maxConcurrency` (type: `integer`):

How many websites to check in parallel.

## `timeoutSecs` (type: `integer`):

Give up on a site after this many seconds.

## `proxyConfiguration` (type: `object`):

Optional. Most sites work without a proxy. Turn it on if many sites come back as blocked.

## Actor input object example

```json
{
  "urls": [
    "https://www.shopify.com",
    "wordpress.org",
    "https://www.wix.com"
  ],
  "categoriesFilter": [],
  "includeVersions": true,
  "includeEvidence": false,
  "maxConcurrency": 10,
  "timeoutSecs": 15,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

One row per website with the technologies found.

## `summary` (type: `string`):

Counts of analyzed and failed sites and the most common technologies.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://www.shopify.com",
        "wordpress.org",
        "https://www.wix.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("greensboro-web-studio/tech-stack-detector-smb").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        "https://www.shopify.com",
        "wordpress.org",
        "https://www.wix.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("greensboro-web-studio/tech-stack-detector-smb").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://www.shopify.com",
    "wordpress.org",
    "https://www.wix.com"
  ]
}' |
apify call greensboro-web-studio/tech-stack-detector-smb --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,greensboro-web-studio/tech-stack-detector-smb"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/IqArzk18CG8MTN26h/builds/IUA8B6feV06fED3sH/openapi.json