# Shopify Store Email Scraper (`leads-scraper/shopify-store-email-scraper`) Actor

Shopify Store Email Scraper SD - Shopify Store Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Shopify Store results by keyword, location and email domain - Shopify Store email extractor.

- **URL**: https://apify.com/leads-scraper/shopify-store-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Shopify Store Email Scraper — Find Merchant Emails Behind "Powered by Shopify"

The **Shopify Store Email Scraper** builds a contact list of independent Shopify merchants from publicly indexed Google results, and returns it as clean, structured data.

You give it keywords such as `online store` or `brand`, choose the email domains you care about, and the Shopify Store Email Scraper writes a dataset of leads with store names, page snippets and — crucially — the merchant's own website address.

Shopify is not a marketplace with profile pages. Every merchant runs the platform on their own domain, so there is no `site:` target that lists them.

That is why this Shopify Store Email Scraper searches a **footprint phrase** instead of a domain, and why the URLs it returns are real merchant websites rather than platform profiles.

**Important:** the Shopify Store Email Scraper never logs into Shopify, never uses a Shopify API and never opens a storefront directly. Every record comes from publicly indexed Google search results.

It is a Shopify email extractor for agency prospecting, wholesale outreach and ecommerce lead generation — not a customer-data tool and not an order scraper.

In a measured live run, **7 out of 9 sampled rows carried usable account identity** alongside a real email, which is a healthy rate for a platform that publishes no handles at all.

***

### How the Shopify Store Email Scraper Finds Stores: the "Powered by Shopify" Footprint

This is the single most distinctive thing about the Shopify Store Email Scraper, so it is worth understanding before your first run.

Most Actors in this family restrict Google with `site:example.com`. On a storefront platform that would be useless — `thecandleco.com` is a Shopify store, but nothing in its domain says so.

So instead of a `site:` operator, the Shopify Store Email Scraper searches for the exact string:

```
"Powered by Shopify"
```

That phrase sits in the footer of an enormous number of Shopify themes. When Google has indexed a page carrying it, the page is a Shopify store — and the host Google prints in the breadcrumb **is the merchant's own domain**.

A finished query therefore looks like this, with no `site:` operator anywhere in it:

```
"Powered by Shopify" online store "@gmail.com" "Austin"
```

#### Why merchant domains beat platform profiles

Because `accept_any_host` is enabled, whatever host appears in the result block is accepted as the store, and both `profileUrl` and `url` are populated from it.

You get `https://thecandleco.com` — the site where the brand's real contact address, wholesale page and about page live — instead of a marketplace profile you cannot act on.

That is a genuine advantage for outreach. A merchant domain is verifiable in one click, and it tells you who you are actually emailing.

#### The honest trade-off

Footprint search only finds stores that **still carry the "Powered by Shopify" footer on a page Google has indexed**. That is a subset, not the whole platform.

Plenty of established brands remove or replace the footer credit during theme customisation, and those stores are invisible to this method. The Shopify Store Email Scraper cannot enumerate every Shopify merchant, and does not claim to.

What it can do is surface a large, steadily refreshed slice of them, filtered by your niche keywords and your chosen email domains.

***

### Key Features of the Shopify Store Email Scraper

The table below reflects what the Shopify Store Email Scraper genuinely does. No invented capabilities, no marketing fiction.

| Feature | What it means in practice |
|---|---|
| Footprint-based discovery | Queries search the literal phrase `"Powered by Shopify"` instead of a `site:` operator, because merchants run on their own domains |
| Merchant-domain output | The breadcrumb host is accepted as the store, so `profileUrl` and `url` hold the brand's real website |
| Query expansion | Each keyword × domain pair is searched in several phrasings: base, quoted, `intitle:`, plus one variant per query modifier |
| Domain-filtered extraction | Only emails ending in your `customDomains` list are kept |
| Global deduplication | One email appears once across every query and every page of the run |
| Obfuscation-aware parser | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Discards a hit that is only the tail of another email in the same result block |
| Structural HTML parsing | Locates the `<h3>` title, then the smallest surrounding block — it does not depend on Google's CSS class names |
| Whole-page fallback parser | If Google's markup changes, the run degrades to "emails without store metadata" rather than "no emails" |
| Concurrency | An `asyncio` worker pool runs several queries in parallel with a shared stop signal on `maxEmails` |
| Retry logic and proxy rotation | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not silently counted as empty |
| Blocked-query requeue | Failed or blocked queries are re-queued once at the end of the run |
| Resumable state | Progress is stored in the key-value store keyed by a hash of your input, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Streaming dataset writes | Each lead is pushed to the Apify dataset the moment it is found |
| Run summary logging | Pages fetched, blocked pages, retries and emails per page are reported at the end |

***

### How the Shopify Store Email Scraper Works: Crawler and Parser Pipeline

The pipeline is short and deliberately transparent. There is no browser, no JavaScript rendering, no authentication and no cookies.

**1. Read input.** The Shopify Store Email Scraper loads your keywords, optional location, email domains and limits.

**2. Build queries.** It composes Google queries around the `"Powered by Shopify"` footprint plus your keyword, domain and optional location phrase.

**3. Fetch search result pages.** Pagination runs asynchronously with `aiohttp` through the Apify **GOOGLE\_SERP** proxy, with retry logic and a fresh proxy session on every attempt.

**4. Parse result blocks.** For each result the Shopify Store Email Scraper finds the `<h3>` title, walks up to the smallest enclosing block, and reads the title, the breadcrumb host and the snippet.

**5. Extract and normalise emails.** A domain-filtered regex pulls addresses out of the block text, then normalisation and the junk filter clean them up.

**6. Deduplicate and push.** Every unique email is written to the dataset immediately, so you can start exporting mid-run.

Base queries run first, so the earliest rows the Shopify Store Email Scraper writes are usually the highest-signal ones.

***

### What Structured Data Does the Shopify Store Email Scraper Extract?

The Shopify Store Email Scraper produces one dataset item per unique email, and every item carries the same 14 fields.

Alongside the address you get the store label Google printed, the merchant's own domain as `profileUrl` and `url`, and the snippet the email came from.

You also get full provenance: the keyword and the exact Google query that produced the lead, plus a UTC timestamp.

That provenance is what turns a raw Shopify store owner email list into something you can tune. It shows which keywords in your niche actually produce contactable merchants.

Nothing outside these 14 fields is collected. The Shopify Store Email Scraper does not touch orders, revenue, apps installed or anything behind a login.

***

### Shopify Store Email Scraper Input Schema

Every field below is taken verbatim from the Shopify Store Email Scraper input schema.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["online store", "brand"]` | Search terms describing the Shopify Store accounts you want (niche, job title, industry) |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are collected; the leading `@` is optional |
| `maxEmails` | integer (1–10000) | `20` | Stop once this many unique emails have been collected |
| `countryCode` | string | `""` | Two-letter country code for the search proxy (`US`, `GB`, `DE`…) |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair with several phrasings |
| `queryModifiers` | array | `["email", "contact us", "wholesale", "customer service", "stockist"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer (1–50) | `30` | Page cap per query |
| `maxConcurrency` | integer (1–20) | `5` | How many queries run in parallel |

#### JSON input example

```json
{
  "keywords": ["candle brand", "skincare online store", "coffee roaster"],
  "location": "Austin",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact us", "wholesale", "customer service", "stockist"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

#### Why query expansion matters for footprint search

Google returns roughly 300 results for any single query, and `"Powered by Shopify"` on its own would burn that budget on noise.

With `expandQueries` on, `candle brand` × `@gmail.com` becomes a base query, a quoted query, an `intitle:` query and one query per modifier — `wholesale`, `stockist`, `contact us` and the rest.

Because deduplication is global, expansion can only add leads. The `wholesale` and `stockist` modifiers are especially productive here, since those pages are where merchants publish a working address.

***

### Shopify Store Email Scraper Output Schema

Every dataset item produced by the Shopify Store Email Scraper contains all 14 fields below.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints — on a storefront this is the brand or the store's own host |
| `fullName` | Display name parsed from a profile-style title; empty for page titles that carry no name |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` — Shopify merchants publish no handles, so this is often `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty — on this Actor it holds the merchant's own domain |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Bio or page snippet, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain (e.g. `@gmail.com`) |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email — verify before sending |
| `foundAt` | ISO 8601 UTC timestamp |

#### JSON output example

```json
{
  "network": "Shopify Store",
  "keyword": "candle brand",
  "query": "\"Powered by Shopify\" candle brand \"@gmail.com\" \"Austin\"",
  "title": "The Candle Co — Wholesale & Stockists",
  "accountName": "The Candle Co",
  "fullName": "The Candle Co",
  "username": null,
  "profileUrl": "https://thecandleco.com",
  "url": "https://thecandleco.com",
  "description": "Hand-poured soy candles made in Austin. Wholesale and stockist enquiries: thecandleco.wholesale@gmail.com",
  "email": "thecandleco.wholesale@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T09:42:17Z"
}
```

Export the Shopify Store Email Scraper dataset as JSON, CSV, XLSX or HTML, or pull it through the Apify API into your CRM.

***

### How to Use the Shopify Store Email Scraper

**Step 1 — open the Actor.** Launch the [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper) on the Apify platform.

**Step 2 — enter keywords.** Be specific. `candle brand` and `skincare online store` beat `shop`, because footprint results are dominated by generic storefront copy.

**Step 3 — pick your email domains.** Start with `@gmail.com` and `@yahoo.com`, then add `@outlook.com`, `@icloud.com` or `@hotmail.com` to widen the net.

**Step 4 — set `maxEmails` and run.** Leave query expansion on so the Shopify Store Email Scraper works around Google's per-query result cap.

**Step 5 — export.** Download the data, or schedule a weekly run so newly indexed storefronts get picked up automatically.

If you want the same footprint technique on a neighbouring platform, the [WooCommerce Email Scraper](https://apify.com/neuro-scraper/woocommerce-email-scraper) and the [Wix Stores Email Scraper](https://apify.com/leads-scraper/wix-stores-email-scraper) work exactly the same way.

***

### Use Cases for the Shopify Store Email Scraper

| Use case | How the Shopify Store Email Scraper helps |
|---|---|
| Agency prospecting | Find DTC brands that obviously already pay for a storefront and need ads, CRO or email work |
| Shopify app and theme marketing | Reach merchants directly instead of waiting for app-store discovery |
| Wholesale and stockist outreach | The `wholesale` and `stockist` modifiers surface brands actively seeking retail partners |
| Supplier and 3PL lead generation | Build a Shopify store owner email list for fulfilment, packaging or freight offers |
| Influencer and affiliate seeding | Contact small brands open to gifting and commission deals |
| Retail buying and curation | Scout independent makers in a category before a buying trip |
| Partnership and bundle research | Find complementary brands in an adjacent niche |
| Market research | Read `description` snippets to see how a niche positions and prices itself |
| CRM enrichment | Match brand names and store domains to accounts you already track |
| Competitive mapping | Measure how many brands in a vertical run a public "Powered by Shopify" footer |

Shopify's merchant base skews towards small and mid-sized brands who answer their own inbox, which is exactly what makes ecommerce lead generation on this platform work.

In every one of these scenarios the Shopify Store Email Scraper does the tedious part — reading thousands of search results — and leaves the judgement to you.

***

### Why Choose This Shopify Store Email Scraper

**It is honest about its source.** The Shopify Store Email Scraper reads Google's public index. Nothing more, nothing hidden.

**It returns merchant websites.** Footprint search plus `accept_any_host` means the URL in your dataset is the brand's own domain, not a dead-end profile.

**It is resilient.** Structural parsing plus a whole-page fallback means a Google layout change degrades output quality instead of breaking the crawler.

**It is resumable.** Migrations and aborts do not cost you a run; state is keyed by a hash of your input.

**It is precise.** Domain filtering, boundary-correct matching, obfuscation handling and the junk filter keep noise out of your dataset.

**It is part of a family.** The same engine powers dozens of sibling Actors, including the [Etsy Email Scraper](https://apify.com/leads-scraper/etsy-email-scraper) for handmade sellers and the [Faire Email Scraper](https://apify.com/leads-scraper/faire-email-scraper) for wholesale brands.

***

### Limitations of the Shopify Store Email Scraper

These are real constraints. Read them before you set expectations.

- **Footprint coverage is a subset.** The Shopify Store Email Scraper only finds stores that still carry `"Powered by Shopify"` on a page Google has indexed. Merchants who removed the footer credit are invisible to it, so this is not a census of the platform.
- **Only publicly indexed emails.** If an address is not visible in Google's index, it cannot be found. Private data is never accessed.
- **Google's ~300-result cap.** A single query returns roughly 300 results at most. Query expansion exists precisely to work around this, so keep `expandQueries` on.
- **`possiblyTruncated`.** When Google's snippet ellipsis touches an address, this flag is set to `true`. Verify those rows before sending anything.
- **Apify GOOGLE\_SERP proxy required.** The Actor cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
- **`username` and `profileUrl` availability.** These are only populated when Google's result exposes a handle. Shopify merchants publish no handles, so `username` is frequently `null`; `profileUrl` still carries the store domain whenever the breadcrumb host is present. That is a Google limitation, not a bug.
- **No guaranteed volume.** Results vary with keywords, domains and location.

Nothing here is affiliated with, endorsed by or officially supported by Shopify.

***

### Related Actors

| Actor | What it collects |
|---|---|
| [Shopify Store Email and Phone Number Scraper](https://apify.com/leads-scraper/shopify-store-email-and-phone-number-scraper) | Emails and phone numbers from Shopify Store |
| [Shopify Store Phone Number Scraper](https://apify.com/leads-scraper/shopify-store-phone-number-scraper) | Public phone numbers from Shopify Store |
| [AliExpress Email Scraper](https://apify.com/neuro-scraper/aliexpress-email-scraper) | Public contact emails from AliExpress |
| [Allegro Email Scraper](https://apify.com/neuro-scraper/allegro-email-scraper) | Public contact emails from Allegro |
| [Amazon Email Scraper](https://apify.com/leads-scraper/amazon-email-scraper) | Public contact emails from Amazon |
| [Best Buy Seller Email Scraper](https://apify.com/leads-scraper/best-buy-seller-email-scraper) | Public contact emails from Best Buy |
| [BigCommerce Store Email Scraper](https://apify.com/neuro-scraper/bigcommerce-store-email-scraper) | Public contact emails from BigCommerce Store |
| [Cdiscount Email Scraper](https://apify.com/neuro-scraper/cdiscount-email-scraper) | Public contact emails from Cdiscount |
| [Coupang Email Scraper](https://apify.com/neuro-scraper/coupang-email-scraper) | Public contact emails from Coupang |
| [Depop Email Scraper](https://apify.com/leads-scraper/depop-email-scraper) | Public contact emails from Depop |
| [DHgate Email Scraper](https://apify.com/neuro-scraper/dhgate-email-scraper) | Public contact emails from DHgate |
| [eBay Email Scraper](https://apify.com/leads-scraper/ebay-email-scraper) | Public contact emails from eBay |
| [Ecwid Store Email Scraper](https://apify.com/neuro-scraper/ecwid-store-email-scraper) | Public contact emails from Ecwid Store |
| [Etsy Email Scraper](https://apify.com/leads-scraper/etsy-email-scraper) | Public contact emails from Etsy |
| [Faire Email Scraper](https://apify.com/leads-scraper/faire-email-scraper) | Public contact emails from Faire |
| [Flipkart Email Scraper](https://apify.com/leads-scraper/flipkart-email-scraper) | Public contact emails from Flipkart |
| [Home Depot Seller Email Scraper](https://apify.com/leads-scraper/home-depot-seller-email-scraper) | Public contact emails from Home Depot |
| [JD.com Email Scraper](https://apify.com/leads-scraper/jd-com-email-scraper) | Public contact emails from JD.com |
| [Lazada Email Scraper](https://apify.com/neuro-scraper/lazada-email-scraper) | Public contact emails from Lazada |
| [Lowe's Seller Email Scraper](https://apify.com/leads-scraper/lowes-seller-email-scraper) | Public contact emails from Lowe's |
| [MercadoLibre Email Scraper](https://apify.com/neuro-scraper/mercadolibre-email-scraper) | Public contact emails from MercadoLibre |
| [Mercari Email Scraper](https://apify.com/neuro-scraper/mercari-email-scraper) | Public contact emails from Mercari |
| [Newegg Email Scraper](https://apify.com/leads-scraper/newegg-email-scraper) | Public contact emails from Newegg |
| [Otto Email Scraper](https://apify.com/leads-scraper/otto-email-scraper) | Public contact emails from Otto |
| [Overstock Email Scraper](https://apify.com/leads-scraper/overstock-email-scraper) | Public contact emails from Overstock |
| [Poshmark Email Scraper](https://apify.com/leads-scraper/poshmark-email-scraper) | Public contact emails from Poshmark |
| [Rakuten Email Scraper](https://apify.com/neuro-scraper/rakuten-email-scraper) | Public contact emails from Rakuten |
| [Shopee Email Scraper](https://apify.com/leads-scraper/shopee-email-scraper) | Public contact emails from Shopee |
| [Taobao Email Scraper](https://apify.com/leads-scraper/taobao-email-scraper) | Public contact emails from Taobao |
| [Target Seller Email Scraper](https://apify.com/neuro-scraper/target-seller-email-scraper) | Public contact emails from Target |
| [Temu Email Scraper](https://apify.com/leads-scraper/temu-email-scraper) | Public contact emails from Temu |
| [Tmall Email Scraper](https://apify.com/leads-scraper/tmall-email-scraper) | Public contact emails from Tmall |
| [Vinted Email Scraper](https://apify.com/leads-scraper/vinted-email-scraper) | Public contact emails from Vinted |
| [Walmart Email Scraper](https://apify.com/leads-scraper/walmart-email-scraper) | Public contact emails from Walmart |
| [Wayfair Email Scraper](https://apify.com/neuro-scraper/wayfair-email-scraper) | Public contact emails from Wayfair |
| [Wish Email Scraper](https://apify.com/leads-scraper/wish-email-scraper) | Public contact emails from Wish |
| [Wix Stores Email Scraper](https://apify.com/leads-scraper/wix-stores-email-scraper) | Public contact emails from Wix Stores |
| [WooCommerce Email Scraper](https://apify.com/neuro-scraper/woocommerce-email-scraper) | Public contact emails from WooCommerce |
| [Zalando Email Scraper](https://apify.com/leads-scraper/zalando-email-scraper) | Public contact emails from Zalando |
| [AliExpress Email and Phone Number Scraper](https://apify.com/neuro-scraper/aliexpress-email-and-phone-number-scraper) | Emails and phone numbers from AliExpress |
| [Allegro Email and Phone Number Scraper](https://apify.com/neuro-scraper/allegro-email-and-phone-number-scraper) | Emails and phone numbers from Allegro |
| [Amazon Email and Phone Number Scraper](https://apify.com/leads-scraper/amazon-email-and-phone-number-scraper) | Emails and phone numbers from Amazon |

### Shopify Store Email Scraper Example Run

A packaging supplier wants to pitch custom boxes to small beauty brands that already sell direct.

They run the Shopify Store Email Scraper with `keywords: ["skincare brand", "soap maker", "hair care brand"]`, `customDomains: ["@gmail.com", "@outlook.com"]` and `maxEmails: 250`.

Query expansion turns three keywords into more than twenty phrasings, each anchored on `"Powered by Shopify"`, and the dataset fills with brand names, store domains and addresses.

They sort by `possiblyTruncated`, drop the flagged rows, open a handful of store domains to sanity-check fit, then export a CSV. Total setup time: under five minutes.

***

### Shopify Store Email Scraper FAQ

**Does the Shopify Store Email Scraper find every store on Shopify?**
No, and it is important to be clear about this. It finds stores whose pages still carry the `"Powered by Shopify"` footer and have been indexed by Google. Merchants who removed that footer credit will not appear, so the result is a large sample of the platform, never a complete list.

**Why does it search a footprint phrase instead of `site:myshopify.com`?**
Because almost every serious merchant moves to their own domain. A `site:` query would only ever reach unmigrated development stores, while `"Powered by Shopify"` reaches live brands on their real websites.

**Does the Shopify Store Email Scraper log into Shopify?**
No. It never logs in, never uses a Shopify API and never opens a storefront. All data comes from publicly indexed Google search results.

**Where do the emails actually come from?**
From Google result titles, breadcrumb labels and snippets — usually contact pages, wholesale pages, stockist pages and about pages where the merchant published an address themselves.

**Will I get a working store URL?**
Usually yes. Because the host in Google's breadcrumb is the merchant's own domain, `profileUrl` and `url` typically point straight at the brand's website.

**Why is `username` often `null`?**
Shopify merchants do not have public handles the way a marketplace seller does. When Google prints only a brand name, `accountName` and `fullName` are populated and `username` stays `null`.

**Is this a Shopify email extractor or a full site scraper?**
It is a Shopify email extractor. It returns the 14 fields listed above and nothing else — no product catalogues, no pricing, no app stacks, no customer data.

**Do I need an Apify proxy?**
Yes. The Shopify Store Email Scraper requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials.

**How many emails can it collect per run?**
Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded only by your `maxEmails` value and what Google has indexed.

**What does `possiblyTruncated: true` mean?**
Google's snippet ellipsis touched the email, so the address may be cut off. Verify those rows before sending.

**Should I leave query expansion enabled?**
Yes. Google caps a single query at roughly 300 results, and expansion is how the Shopify Store Email Scraper reaches past that ceiling.

**Is this affiliated with Shopify?**
No. The Shopify Store Email Scraper is an independent tool and is not affiliated with, endorsed by or officially supported by Shopify.

***

### Responsible Use and GDPR

Publicly visible does not mean consent to bulk marketing. Treat every address the Shopify Store Email Scraper returns as personal data belonging to a real business owner.

Follow GDPR, CAN-SPAM, PECR and any other regime that applies to you: identify yourself, state why you are contacting them, honour opt-outs immediately and delete records on request.

Relevant, specific outreach to a merchant who published a wholesale address is reasonable. Blasting an unfiltered export is not, and it is the fastest way to burn your sending domain.

***

### Support

Questions, bug reports or a custom build request? Email **neurodata.apify@gmail.com** and include your run ID so the Shopify Store Email Scraper logs can be checked quickly.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Shopify Store accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Shopify Store.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

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

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "online store",
    "brand"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact us",
    "wholesale",
    "customer service",
    "stockist"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by Shopify Store Email Scraper, stored in the run's default dataset.

# 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 = {
    "keywords": [
        "online store",
        "brand"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact us",
        "wholesale",
        "customer service",
        "stockist"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/shopify-store-email-scraper").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 = {
    "keywords": [
        "online store",
        "brand",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
        "@outlook.com",
        "@hotmail.com",
        "@icloud.com",
        "@aol.com",
        "@protonmail.com",
        "@live.com",
        "@gmx.com",
        "@mail.com",
        "@yandex.com",
        "@zoho.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact us",
        "wholesale",
        "customer service",
        "stockist",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/shopify-store-email-scraper").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 '{
  "keywords": [
    "online store",
    "brand"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com",
    "@outlook.com",
    "@hotmail.com",
    "@icloud.com",
    "@aol.com",
    "@protonmail.com",
    "@live.com",
    "@gmx.com",
    "@mail.com",
    "@yandex.com",
    "@zoho.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact us",
    "wholesale",
    "customer service",
    "stockist"
  ]
}' |
apify call leads-scraper/shopify-store-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/shopify-store-email-scraper"
        }
    }
}

```

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/mKyRvfGHD6CbiGZhH/builds/nNiOU39AkJeFcqlt8/openapi.json