Webflow Site Detector | Bulk Website Lookup

Find Webflow websites for a technical review

Webflow Site Detector: Identify exposed Webflow signals across supplied website URLs. Export matches, analytics and hosting context for agency research. Checks public HTML and headers; custom or hidden implementations 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, matchesFilter, cms, analytics, cdn, error.
4. Export JSON for nested data or CSV for a spreadsheet. Review a small sample before increasing the scope.

{
  "startUrls": [
    "https://webflow.com",
    "https://www.jasper.ai",
    "https://wordpress.org"
  ],
  "filterTechnologies": [
    "Webflow"
  ],
  "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?

• Webflow agency and freelancer prospecting. Sites already on Webflow are the ones that buy Webflow redesigns, maintenance, SEO and app integrations.
• Selling Webflow apps and templates. Turn any domain list into the subset running the platform your product plugs into.
• Migration targeting in both directions. Find Webflow sites that have outgrown the platform, or exclude Webflow matches to find sites on WordPress, Wix or Squarespace that might move.
• Market research. Measure Webflow's share against other site builders across an industry, a region or a startup directory.
• Enriching your data. Add an isWebflow column and the surrounding stack to a spreadsheet of accounts 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
matchesFilter	true when the site runs any of the signals you listed under Signals to look for
matchedTechnologies	Which signals were found, e.g. ["Webflow"]
cms	Webflow for a match, or whatever else the site runs
ecommerce	Webflow Ecommerce where the store is visible, or another platform
analytics, tagManager, advertising	Google Analytics, GTM, Meta Pixel, LinkedIn Insight Tag and others
marketingAutomation, liveChat	HubSpot, Mailchimp, Intercom and similar where loaded directly
cdn, hosting	Infrastructure — Webflow sites are typically served through its own edge
technologyCount	Total technologies detected
technologies	The complete list with categories, versions and confidence scores
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://www.jasper.ai",
  "finalUrl": "https://www.jasper.ai/",
  "statusCode": 200,
  "title": "Jasper | AI built for marketers",
  "matchesFilter": true,
  "matchedTechnologies": ["Webflow"],
  "cms": "Webflow",
  "analytics": null,
  "cdn": "Cloudflare",
  "technologyCount": 5,
  "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 Signals to look for at its default for a strict Webflow check, or add Framer, Squarespace and Wix to compare site builders in one run.
3. Switch on Store only matching websites to pay only for the Webflow sites 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://webflow.com",
    "jasper.ai",
    "https://wordpress.org"
  ],
  "filterTechnologies": ["Webflow"],
  "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

Webflow sites carry distinctive markers in the server-rendered page: the data-wf-site and data-wf-page attributes on the <html> element, the webflow.js runtime and w- utility classes, assets served from assets.website-files.com or cdn.prod.website-files.com, and the generator meta tag on many sites. The detector fetches each homepage once and checks the headers, cookies, HTML, script sources and meta tags against more than 7,600 technology fingerprints, then reports every match with a confidence score.

A site is only reported as Webflow when the evidence sits on the page itself, not in an embedded third-party asset, so a site that merely links to a Webflow page is not counted. Because the page's JavaScript is never executed, signals that only appear after scripts run are not evaluated; for Webflow that does not matter — its markup is the evidence.

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 Webflow site found; 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 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

• Webflow sites exported to static HTML and hosted elsewhere keep most markers but not all; they are usually still detected, sometimes at lower confidence.
• A Webflow marketing site in front of a separately built application is reported for the page you supply.
• Very large 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.

Something not detected?

Open an issue on this actor's Issues tab with the URL and what 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://webflow.com",
    "https://www.jasper.ai",
    "https://wordpress.org"
  ],
  "filterTechnologies": [
    "Webflow"
  ],
  "onlyMatching": false
};
const run = await client.actor('keystonelabs/webflow-site-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.