# E-commerce Tech Stack Detector (Italy-focused) (`visioweb/ecommerce-tech-stack-detector`) Actor

Detect PrestaShop, WooCommerce, Shopify, Magento and more for a list of domains: version, theme, modules/plugins, server/CDN, SSL expiry, TTFB, sitemap, analytics, pixels, cookie banners and Italian payment methods. Technical, non-personal data only.

- **URL**: https://apify.com/visioweb/ecommerce-tech-stack-detector.md
- **Developed by:** [Francesco Ingrosso](https://apify.com/visioweb) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 domain analyzeds

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

## E-commerce Tech Stack Detector (Italy-focused)

Find out **which e-commerce platform a website runs on** – PrestaShop, WooCommerce, Shopify, Magento or other CMS – together with its **version, theme, installed modules/plugins, server and CDN, SSL expiry, response time (TTFB), sitemap/robots.txt** and the **marketing and payment tools** visible in the page (analytics, ad pixels, cookie banners, Italian payment methods like Scalapay, Satispay, Nexi XPay, PagoLight).

Built for agencies, freelancers and SaaS teams working on the **Italian e-commerce market**, but it works on any domain.

> **Outputs only technical, non-personal website data. Users are responsible for lawful use.**
> No e-mails, phone numbers, names, company names, VAT numbers, addresses or social profiles are ever extracted.

### What it detects

| Group | Fields |
|---|---|
| Platform | `platform` (PrestaShop / WooCommerce / Shopify / Magento / other / unknown), `platformName`, `platformVersion`, `platformConfidence`, `platformSignals` |
| Theme & extensions | `theme`, `extensions` (from `/modules/<name>/`, `/wp-content/plugins/<name>/`, Magento module paths), `extensionsCount` |
| Infrastructure | `server`, `poweredBy`, `cdn` (Cloudflare, Fastly, CloudFront, Akamai, Sucuri, Bunny, Varnish…), `hsts`, `compression` |
| Security & speed | `httpsAvailable`, `sslValid`, `sslDaysLeft`, `ttfbMs`, `httpStatus`, `redirectCount`, `pageSizeKb` |
| SEO basics | `sitemapPresent`, `robotsTxtPresent` |
| Tools | `tools.analytics`, `tools.adPixels`, `tools.cookieConsent`, `tools.payments`, `tools.liveChat`, `tools.reviews`, `tools.emailMarketing` |

Detection is signature-based on the public homepage HTML and response headers. Tools injected only through Google Tag Manager are not visible in the HTML and may not be listed.

### Input example

```json
{
  "domains": ["example-shop.it", "https://www.another-store.it/"],
  "maxConcurrency": 5,
  "requestTimeoutSecs": 10
}
```

### Output example

```json
{
  "input": "example-shop.it",
  "domain": "example-shop.it",
  "status": "ok",
  "httpStatus": 200,
  "finalUrlHost": "www.example-shop.it",
  "ttfbMs": 148,
  "platform": "WooCommerce",
  "platformName": "WooCommerce (WordPress)",
  "platformVersion": "10.9.4",
  "theme": "betheme",
  "extensions": ["woocommerce", "contact-form-7", "revslider"],
  "extensionsCount": 7,
  "server": "nginx",
  "cdn": [],
  "httpsAvailable": true,
  "sslValid": true,
  "sslDaysLeft": 44,
  "robotsTxtPresent": true,
  "sitemapPresent": true,
  "tools": {
    "analytics": ["Google Tag Manager"],
    "adPixels": [],
    "cookieConsent": ["iubenda"],
    "payments": ["PayPal"],
    "liveChat": [],
    "reviews": [],
    "emailMarketing": ["Mailchimp"]
  }
}
```

`status` can be `ok`, `bot_protection` (a WAF challenge was served: only headers analyzed), `unreachable`, `invalid_domain`, `disallowed_by_robots_txt` or `error`.

### Use cases

- **Lead qualification for agencies**: filter a list of stores by platform (e.g. only PrestaShop 1.6/1.7 or WooCommerce) before any outreach.
- **Migration targeting**: find stores on old or end-of-life platforms.
- **Competitive research**: which payment methods, review widgets or cookie banners do Italian stores in a niche use?
- **SaaS / plugin vendors**: measure adoption of a module, app or payment method across a list of domains.
- **Portfolio monitoring**: SSL expiry and TTFB on your own clients' stores.

### Responsible crawling

- Identifies itself as `ShopTechAuditBot/1.0` with a link to this page.
- Reads and obeys **robots.txt**; disallowed sites are reported as `disallowed_by_robots_txt`.
- Maximum **1 request per second per domain**, short timeouts, 3–5 requests per domain (homepage, robots.txt, sitemap check).
- Only public pages, no login, no forms, no JavaScript execution.

### Pricing

Pay per event: **$0.004 per analyzed domain** (= $4 per 1,000 domains). Invalid, unreachable and robots-disallowed domains are **not charged**; duplicates in the input are removed.

### FAQ

**Can it find e-mails or phone numbers?** No, by design. It returns technical data only.
**Why is the version empty?** Many stores hide it. The Actor only reports what is publicly exposed (e.g. `meta generator`, asset versions, theme markers).
**Is it legal to use?** The Actor reads public technical information at a polite rate and obeys robots.txt. You are responsible for how you use the results (e.g. GDPR/ePrivacy rules for any marketing you do).

# Actor input Schema

## `domains` (type: `array`):

Domains or URLs to analyze (one per line). Only the homepage and a few technical files (robots.txt, sitemap) are requested.

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

How many different domains are analyzed in parallel. Each single domain is always limited to 1 request per second.

## `requestTimeoutSecs` (type: `integer`):

Timeout for each HTTP request.

## Actor input object example

```json
{
  "domains": [
    "tannico.it",
    "tartufi.it",
    "vitaminstore.it"
  ],
  "maxConcurrency": 5,
  "requestTimeoutSecs": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "domains": [
        "tannico.it",
        "tartufi.it",
        "vitaminstore.it"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("visioweb/ecommerce-tech-stack-detector").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 = { "domains": [
        "tannico.it",
        "tartufi.it",
        "vitaminstore.it",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("visioweb/ecommerce-tech-stack-detector").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 '{
  "domains": [
    "tannico.it",
    "tartufi.it",
    "vitaminstore.it"
  ]
}' |
apify call visioweb/ecommerce-tech-stack-detector --silent --output-dataset

```

## MCP server setup

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

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/1I5JK3A8c9pldyybH/builds/97LYMd9bhWL2vYZM5/openapi.json