CMS Detector | WordPress, Webflow, Wix & More

Classify websites by visible CMS signals

CMS Detector: Classify supplied websites by exposed CMS signals including WordPress, Webflow, Wix and Drupal. Export platform, matched technologies and versions where exposed. HTTP-only detection; headless CMSs can be missed.

Start with a small example

1. Open Input, switch to JSON and paste the example below. Replace the example startUrls with your own research targets when ready.
2. Check the live Pricing tab and set a run spending limit.
3. Run the Actor, then open the Workflow output view. Inspect url, cms, matchesFilter, matchedTechnologies, hosting, error.
4. Export JSON for nested data or CSV for a spreadsheet. Review a small sample before increasing the scope.

{
  "startUrls": [
    "https://wordpress.org",
    "https://webflow.com",
    "https://www.joomla.org"
  ],
  "filterTechnologies": [
    "WordPress",
    "Drupal",
    "Joomla",
    "Webflow",
    "Wix",
    "Squarespace",
    "HubSpot CMS Hub",
    "Craft CMS",
    "TYPO3 CMS",
    "Ghost",
    "Contentful",
    "Sitecore",
    "Adobe Experience Manager",
    "Umbraco",
    "Kentico",
    "Sanity",
    "Storyblok",
    "Strapi",
    "Prismic",
    "Contentstack",
    "Duda",
    "Weebly",
    "GoDaddy Website Builder",
    "Blogger",
    "Medium",
    "Framer",
    "Bubble",
    "Concrete CMS",
    "ExpressionEngine",
    "Statamic",
    "Kirby",
    "SilverStripe",
    "Liferay",
    "Optimizely",
    "Magnolia",
    "Bloomreach"
  ],
  "onlyMatching": false
}

At the rate checked September 9, 2026, 3 saved rows cost $0.009 in Actor event fees ($3.00 per 1,000 rows). Actual returned rows determine the event fee. Taxes and other account services may be separate.

What can I use it for?

• Platform-specific prospecting. Agencies, plugin vendors, hosting companies and migration specialists can turn any domain list into the subset on the CMS they serve.
• Migration campaigns. Find every site on a platform you migrate away from — legacy Drupal, Joomla, or an ageing WordPress install.
• Market sizing and share. Measure how a category, region or list of competitors splits across WordPress, Webflow, headless CMSs and the rest.
• Portfolio audits. Inventory which platforms and versions a group's sites run before a security or consolidation review.
• Sales intelligence. Technology signals can help segment research, but do not establish company size, budget or purchase intent.
• Enriching your data. Add a cms column to a spreadsheet of domains in one run.

What data does it return?

One record per website:

Field	Meaning
url, finalUrl, statusCode, title	What you asked for, where it resolved to, and the page title
cms	The platform detected, e.g. WordPress, Webflow, Drupal — null when none is recognised
matchesFilter	true when the CMS is one of those you listed under Platforms to look for
matchedTechnologies	Which listed platforms were found
programmingLanguages, webServer	PHP, Nginx and similar, for context
hosting, paas, cdn	Where it runs — WordPress on WP Engine, Webflow on its own edge, and so on
ecommerce	WooCommerce, Shopify and others when a store is present
technologyCount	Total technologies detected
technologies	The complete list with categories, versions and confidence scores — this is where the CMS version appears
error	null on success, otherwise why the site could not be checked

Sites that time out or refuse the connection are still returned with an error, so input and output line up one to one.

Illustrative output

Values explain the output shape; they are not a live result or guaranteed field coverage.

{
  "url": "https://webflow.com",
  "finalUrl": "https://webflow.com/",
  "statusCode": 200,
  "title": "Webflow: Create a custom website | Visual website builder",
  "cms": "Webflow",
  "matchesFilter": true,
  "matchedTechnologies": ["Webflow"],
  "hosting": "Amazon Web Services",
  "cdn": "Cloudflare",
  "technologyCount": 6,
  "technologies": [
    { "name": "Webflow", "categories": ["CMS", "Page builders"], "version": null, "confidence": 100, "website": "https://webflow.com" },
    { "name": "Cloudflare", "categories": ["CDN"], "version": null, "confidence": 100, "website": "https://www.cloudflare.com" }
  ],
  "error": null
}

How to use it

1. Paste your domains under Websites to check, upload a file, or pass them through the API as startUrls. Bare domains like example.com are fine.
2. Leave Platforms to look for at its defaults to classify across all major systems, or narrow it to one platform to build a targeted list.
3. Switch on Store only matching websites to pay only for sites on the platforms you listed and discard the rest.
4. Click Start and download the results as JSON, CSV or Excel from the Output tab, or read them from the dataset via the API.

Input example

{
  "startUrls": [
    "https://wordpress.org",
    "webflow.com",
    "https://www.joomla.org"
  ],
  "filterTechnologies": ["WordPress", "Webflow", "Joomla", "Drupal"],
  "onlyMatching": false
}

Raise Max concurrency for large lists. Turn on Proxy configuration only if some sites block the platform's IP range — most do not.

How detection works

Every CMS leaves fingerprints on its own pages: WordPress's wp-content paths and generator meta tag, Drupal's /sites/default/files/ and X-Generator header, Joomla's /media/jui/ paths, Webflow's data-wf-site attributes and webflow.js, Wix's X-Wix-Request-Id, Squarespace's static1.squarespace.com, AEM's /etc.clientlibs/, Craft's CSRF token markup, and so on. The detector fetches each homepage once and checks the headers, cookies, HTML, script sources and meta tags against more than 7,600 technology fingerprints.

One rule keeps results honest: a CMS is only reported when the evidence sits on the site's own domain. A WordPress-hosted image embedded from another site is an embed, not a platform, and is ignored — so a news site that links to a WordPress blog does not come back as WordPress.

Because the page's JavaScript is never executed, headless setups that render everything client-side expose fewer signals; the detector reports what it can see and never guesses.

The fingerprint database is the open-source webappanalyzer technology dataset, used under the GNU GPL v3. The matching engine in this actor is original code.

Pricing

You pay per website saved to the dataset. With Store only matching websites on, that means per matching site; with it off, per site checked. There are no subscriptions, seats or minimums, and you can cap the maximum spend of a run before it starts.

Scope and responsible use

The actor requests only the publicly served homepage of each URL you provide, exactly as a browser would. It requires no login, no cookies and no credentials, does not probe admin paths, login pages or any other endpoint, does not crawl beyond the page you give it, and does not attempt to bypass any access control or bot-protection challenge. You are responsible for using the results in accordance with the laws that apply to you and the terms of the websites you check.

Limitations

• Sites that deliberately hide their platform (security plugins that rename paths and strip generator tags) can be missed or reported at lower confidence.
• Headless CMSs behind a custom front end (Contentful, Sanity, Strapi) are reported only when the front end leaves a trace of them.
• Very large retail and media homepages that deliberately stall automated traffic can exceed the request timeout; they come back as rows with an error rather than being dropped.
• Only the URL you supply is fetched; a blog under /blog/ on an otherwise custom site is not found unless you pass that path.

Something not detected?

Open an issue on this actor's Issues tab with the URL and the platform you expected. Include a reproducible input and the expected signal so the report can be investigated.

Interpret empty results and errors

A null technology field means no recognized signal was found in the inspected response; it does not prove absence. A returned error means that URL was not successfully analyzed. With onlyMatching: true, non-matches and errors are omitted from the dataset, so a zero-row result cannot distinguish an unavailable site from no matches. Start with onlyMatching: false when checking coverage.

Every saved row, including an error row, incurs the configured per-row event fee. Proxy selection and run duration can affect operating costs. Do not increase concurrency or enable a more expensive proxy merely to work around an unclear result.

For a reproducible problem, open this Actor’s Issues tab with a small public input, expected behavior and relevant error text. Remove tokens and confidential information. No response-time or uptime guarantee is offered.

Use the result in an automation

In Make or n8n, use the Apify integration to run this Actor with the same JSON input, wait for completion, then retrieve its default dataset. Route failed runs and error rows to a review step before sending valid results to your spreadsheet or CRM. Scheduling does not make these Actors emit only new records: deduplicate downstream using the source URL or record ID.

For Node.js, install the official apify-client package and set your own APIFY_TOKEN environment variable. The following example starts a paid run with a small spending limit.

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
  "startUrls": [
    "https://wordpress.org",
    "https://webflow.com",
    "https://www.joomla.org"
  ],
  "filterTechnologies": [
    "WordPress",
    "Drupal",
    "Joomla",
    "Webflow",
    "Wix",
    "Squarespace",
    "HubSpot CMS Hub",
    "Craft CMS",
    "TYPO3 CMS",
    "Ghost",
    "Contentful",
    "Sitecore",
    "Adobe Experience Manager",
    "Umbraco",
    "Kentico",
    "Sanity",
    "Storyblok",
    "Strapi",
    "Prismic",
    "Contentstack",
    "Duda",
    "Weebly",
    "GoDaddy Website Builder",
    "Blogger",
    "Medium",
    "Framer",
    "Bubble",
    "Concrete CMS",
    "ExpressionEngine",
    "Statamic",
    "Kirby",
    "SilverStripe",
    "Liferay",
    "Optimizely",
    "Magnolia",
    "Bloomreach"
  ],
  "onlyMatching": false
};
const run = await client.actor('keystonelabs/cms-detector').call(input, {
  memory: 512, timeout: 180, maxTotalChargeUsd: 0.10
});
if (run.status !== 'SUCCEEDED') throw new Error('Run did not succeed: ' + run.id);
const { items } = await client.dataset(run.defaultDatasetId).listItems({ limit: 100 });
console.log(items);

The first 100 rows are retrieved in this example. Use the dataset API pagination for a larger result. Keep credentials out of shared inputs and source files.

A useful next step

• Website Tech Stack Detector | Bulk URL Lookup: qualify a website list by its technology. This is a separate Actor with its own input and price.

Understand the run at a glance

Open Run summary in Output for counts of unique URLs, analyzed responses, failures, matches and saved rows. It remains useful when onlyMatching produces an empty dataset. The summary is written at normal completion and does not add a billable dataset row. Failed or aborted runs may not have a final summary; check run status first. The summary contains counts only, not a second copy of scraped content.