Shopify Store Detector | Bulk Website Checker

Find Shopify matches in a website shortlist

Shopify Store Detector: Check your domain list for Shopify, Shop Pay and related technology signals. Export matched technologies, payment and analytics fields for agency research. HTTP-only inspection; does not estimate store revenue.

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, matchedTechnologies, paymentProcessors, analytics, error.
4. Export JSON for nested data or CSV for a spreadsheet. Review a small sample before increasing the scope.

{
  "startUrls": [
    "https://www.allbirds.com",
    "https://www.shopify.com",
    "https://wordpress.org"
  ],
  "filterTechnologies": [
    "Shopify",
    "Shop Pay",
    "Shopify Plus"
  ],
  "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?

• Selling to Shopify merchants. If you build a Shopify app, run a 3PL, offer store design, or sell anything that plugs into Shopify, this turns a scraped or purchased domain list into a list of stores you can actually pitch.
• Agency prospecting. Filter a city's or a niche's businesses down to the ones already on Shopify and approach them with a platform-specific offer.
• Migration targeting. The reverse works too: exclude Shopify stores from a list to find merchants still on other platforms who could move.
• Competitive and market research. Measure how much of a category runs on Shopify, and which Shopify stores use which payment, review or email tools.
• Enriching your CRM. Add an isShopify 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 Shopify signals you listed
matchedTechnologies	Which of those signals were found, e.g. ["Shopify", "Shop Pay"]
ecommerce	The ecommerce platform detected — Shopify for a match, or whatever else the site runs
paymentProcessors	Shop Pay, Stripe, PayPal, Klarna and similar
analytics, tagManager, advertising	Google Analytics, GTM, Meta Pixel, TikTok Pixel and others
marketingAutomation, liveChat	Klaviyo, Mailchimp, Gorgias, Intercom and similar
cdn, hosting, webServer	Infrastructure behind the store
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 set, so your 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.allbirds.com",
  "finalUrl": "https://www.allbirds.com/",
  "statusCode": 200,
  "title": "Allbirds: Sustainable Shoes & Clothing",
  "matchesFilter": true,
  "matchedTechnologies": ["Shopify"],
  "ecommerce": "Shopify",
  "paymentProcessors": null,
  "analytics": null,
  "cdn": "Cloudflare",
  "technologyCount": 5,
  "technologies": [
    { "name": "Shopify", "categories": ["Ecommerce"], "version": null, "confidence": 100, "website": "https://www.shopify.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.
2. Leave Shopify signals to look for at its defaults unless you want a stricter or broader definition of a match.
3. Decide whether to keep everything or only the hits. With Store only matching websites switched on, non-Shopify sites are still checked but not saved, so you pay only for the stores you wanted.
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://www.allbirds.com",
    "brooklinen.com",
    "wordpress.org"
  ],
  "filterTechnologies": ["Shopify", "Shop Pay", "Shopify Plus"],
  "onlyMatching": true
}

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

How detection works

A Shopify store leaves unmistakable fingerprints on its very first response: X-Shopify-Stage and X-ShopId headers, _shopify_s and _shopify_y cookies, assets served from cdn.shopify.com, and the Shopify.theme object in the page's inline scripts. 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. Because it never runs the page's JavaScript, it cannot see signals that only appear after the app boots — in practice Shopify stores are identified from the response itself, and the trade-off buys you speed and a much lower cost per site.

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 Shopify store 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

• Very large retail homepages that deliberately stall automated traffic can exceed the request timeout; they come back as rows with an error rather than being dropped.
• Headless storefronts (Shopify Hydrogen and other custom front ends) expose fewer of the classic signals and may be reported with lower confidence or missed; check technologies for Shopify Storefront API or Hydrogen in those cases.
• Password-protected or unpublished stores return their placeholder page, which still identifies as Shopify.
• Only the URL you supply is fetched; a Shopify checkout hosted on a different domain from the marketing site is not followed.
• Version numbers are reported only where a site publishes them.

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://www.allbirds.com",
    "https://www.shopify.com",
    "https://wordpress.org"
  ],
  "filterTechnologies": [
    "Shopify",
    "Shop Pay",
    "Shopify Plus"
  ],
  "onlyMatching": false
};
const run = await client.actor('keystonelabs/shopify-store-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.