# Ecwid Store Email Scraper (`neuro-scraper/ecwid-store-email-scraper`) Actor

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

- **URL**: https://apify.com/neuro-scraper/ecwid-store-email-scraper.md
- **Developed by:** [Neuro Scraper](https://apify.com/neuro-scraper) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.19 / 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?

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

### Ecwid Store Email Scraper — Small-Business Emails Behind the "Powered by Ecwid" Footer

The **Ecwid Store Email Scraper** finds publicly indexed contact emails belonging to real Ecwid merchants and returns them as clean, structured data.

Ecwid is not a marketplace, and it is not even a standalone storefront in the usual sense. It is a shopping cart merchants **embed into a website they already own** — a bakery's site, a gym's site, a farm shop's one-pager.

So this Actor works differently from a marketplace scraper: it searches Google for the **footprint phrase** `"Powered by Ecwid"` — the credit line the embedded store renders alongside the cart.

Any page Google returns for that phrase is a live Ecwid store. The Ecwid Store Email Scraper reads the merchant's own host straight out of Google's result breadcrumb and records it as the store URL.

That is the key advantage, and it is even sharper on this platform than on the others. Because the cart is embedded, `url` is usually the **business's main website** — `https://harboursidebakehouse.co.uk` — not a shop-only subdomain.

Which means you land on the page that carries the phone number, the opening hours and the contact address, rather than a bare product listing.

You give it keywords such as `online store` or `shop`, choose the email domains you care about, and the Ecwid Store Email Scraper writes a deduplicated dataset of business names, websites, page snippets and addresses.

**Important:** the Ecwid Store Email Scraper never logs into Ecwid, never uses an Ecwid API, and never opens a merchant's site directly. Every record comes from publicly indexed Google search results.

It is an Ecwid email extractor for small-business ecommerce lead generation, local prospecting and B2B partnership research — not a customer-data tool and not an order scraper.

***

### The Footprint Search: Why the Ecwid Store Email Scraper Skips `site:`

This is the most important mechanism in the Actor, so it comes before everything else.

A marketplace scraper narrows Google with `site:etsy.com` or `site:ebay.com`. An embeddable cart has no shared public domain at all, so there is nothing useful to put after `site:`.

Instead, the platform config sets `site_footprint` to the exact string `Powered by Ecwid`, and every query the Actor builds is anchored on that quoted phrase.

A finished base query looks like this — note the complete absence of a `site:` operator:

```text
"Powered by Ecwid" online store "@gmail.com" "Brighton"
```

Because the target is a phrase rather than a domain, `accept_any_host` is set to true. Whatever host Google prints in the result breadcrumb **is** the merchant's site.

The parser writes that host verbatim into both `profileUrl` and `url`. No rewriting, no guessing, no platform-hosted intermediary.

#### Why merchant domains beat platform profiles

On Ecwid the merchant domain is not merely a better link — it is a different class of data. It is a real local business's website.

That makes it the join key for almost any enrichment workflow: technology detection, map and directory matching, CRM deduplication, and simple manual qualification by opening the page.

Contact and about pages are where these merchants publish an address, which is exactly why the default `queryModifiers` list includes `contact us`, `wholesale`, `customer service` and `stockist`.

#### The honest trade-off

The footprint search only reaches stores that **left the "Powered by Ecwid" credit line in place** and had that page indexed by Google.

Paid Ecwid plans allow the credit to be removed, and some site builders strip it during theme customisation. Those stores are invisible to this method.

So the Ecwid Store Email Scraper finds a **subset** of Ecwid merchants, not the whole population. It is a discovery tool, not a census of the platform.

In a small measured sample of live runs, **9 out of every 9 parsed results** carried a usable store identity alongside the email, and every run returned real addresses. That is an observation from a sample, not a guaranteed rate — though it is consistent with the embedded model, where Google indexes an ordinary business homepage with a clean title and breadcrumb.

***

### Key Features of the Ecwid Store Email Scraper

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

| Feature | What it means in practice |
|---|---|
| Footprint-phrase discovery | Every query is anchored on the quoted string `"Powered by Ecwid"` instead of a `site:` operator |
| Host-site capture | `accept_any_host` is on, so the host in Google's breadcrumb — usually the business's own website — is recorded as the store URL |
| 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" |
| Location and country targeting | A `location` phrase is appended to every query and `countryCode` routes the search proxy — both matter for local merchants |
| 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 Ecwid 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 Ecwid Store Email Scraper loads your keywords, optional location, email domains and limits.

**2. Build footprint queries.** It composes Google queries from the quoted phrase `"Powered by Ecwid"` plus your keyword and email domain — never a `site:` operator.

**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 it finds the `<h3>` title, walks up to the smallest enclosing block, and reads the title, the breadcrumb host and the snippet.

**5. Recover the site URL.** Because any host is accepted, the breadcrumb host becomes the merchant's website for that row.

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

**7. 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 Ecwid Store Email Scraper writes are usually the highest-signal ones.

***

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

The Actor produces one dataset item per unique email, and every item carries the same 14 fields.

Alongside the address you get the business label Google printed, the merchant's own website, and the page snippet the email was lifted from.

Because an Ecwid store is embedded in the merchant's own site, `accountName` is the trading name of the business — "Harbourside Bakehouse", never a platform handle. That is expected metadata here, not a defect.

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 pull into a maintainable Ecwid merchants list. It shows which keyword is productive in your market so you can retire the ones that are not.

Nothing outside these 14 fields is collected. The Ecwid Store Email Scraper does not touch orders, customers, revenue figures or anything behind a login.

***

### Ecwid Store Email Scraper Input Schema

Every field below is taken verbatim from the Ecwid Store Email Scraper input schema in `.actor/actor.json`.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["online store", "shop"]` | Search terms describing the Ecwid 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 |

`location` earns its keep on this platform more than on any other in the family, because Ecwid merchants are overwhelmingly local businesses.

#### JSON input example

```json
{
  "keywords": ["bakery", "farm shop", "coffee roaster"],
  "location": "Brighton",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 300,
  "countryCode": "GB",
  "expandQueries": true,
  "queryModifiers": ["email", "contact us", "wholesale", "customer service", "stockist"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

#### Why query expansion matters for merchant discovery

Google returns roughly 300 results for any single query, which is a hard ceiling on a one-shot search.

With `expandQueries` on, `bakery` × `@gmail.com` becomes a base query, a quoted query, an `intitle:` query and one query per modifier — each still anchored on the same footprint phrase:

```text
"Powered by Ecwid" bakery "@gmail.com"
"Powered by Ecwid" "bakery" "gmail.com"
"Powered by Ecwid" intitle:"bakery" "@gmail.com"
"Powered by Ecwid" bakery contact us "@gmail.com"
"Powered by Ecwid" bakery wholesale "@gmail.com"
```

Because deduplication is global, expansion can only add leads to the Ecwid Store Email Scraper dataset. Leave it enabled unless you are running a deliberately tiny test.

***

### Ecwid Store Email Scraper Output Schema

Every dataset item produced by the Ecwid 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 Ecwid, the trading name of the business |
| `fullName` | Display name parsed from a profile-style title; empty for plain page titles |
| `username` | URL-safe handle when the platform exposes one; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `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": "Ecwid Store",
  "keyword": "bakery",
  "query": "\"Powered by Ecwid\" bakery contact us \"@gmail.com\" \"Brighton\"",
  "title": "Order Online & Contact Us — Harbourside Bakehouse",
  "accountName": "Harbourside Bakehouse",
  "fullName": "Harbourside Bakehouse",
  "username": null,
  "profileUrl": "https://harboursidebakehouse.co.uk",
  "url": "https://harboursidebakehouse.co.uk",
  "description": "Sourdough and pastries baked daily in Brighton. Click and collect, plus wholesale trays for cafés: harbourside.bakehouse@gmail.com",
  "email": "harbourside.bakehouse@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T09:42:17+00:00"
}
```

Note that `username` is `null` while `profileUrl` and `url` both hold the merchant's own website. That is the normal shape of a row from this Actor.

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

***

### How to Use the Ecwid Store Email Scraper

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

**Step 2 — enter keywords that describe a business, not a product.** `bakery`, `butcher`, `garden centre`, `bike shop` and `farm shop` outperform generic ecommerce terms here.

**Step 3 — set `location` and `countryCode`.** Ecwid's installed base is local and small, so a town or region turns a broad sweep into a workable territory list.

**Step 4 — pick your email domains and run.** Small merchants lean heavily on free inboxes, so `@gmail.com`, `@yahoo.com`, `@outlook.com` and `@hotmail.com` all pay off. Leave query expansion on.

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

If you want the same footprint workflow on neighbouring platforms, the [Wix Stores Email Scraper](https://apify.com/leads-scraper/wix-stores-email-scraper) and the **Squarespace Commerce Email Scraper** reach a similar small-business audience.

***

### Use Cases for the Ecwid Store Email Scraper

| Use case | How the Ecwid Store Email Scraper helps |
|---|---|
| Local web design and SEO agencies | Small merchants with a live cart are already committed to selling online |
| App and plugin vendors | Booking, loyalty, review and delivery tools sell directly to these owners |
| POS and payment providers | Businesses running an embedded cart usually have a physical till to modernise too |
| Local delivery and courier services | Bakeries, butchers and farm shops are the archetypal same-day delivery customers |
| 3PL and fulfilment prospecting | Merchants graduating from click-and-collect to national shipping |
| B2B wholesale prospecting | The `wholesale` and `stockist` modifiers surface trade pages by design |
| Food and produce distributors | Reach independent retailers directly rather than through a broker |
| Merch and packaging suppliers | Small brands buying labels, boxes and print in low volumes |
| Market research | Read `description` snippets to see how a local category positions and prices |
| CRM enrichment | Match business names and websites to accounts you already track |

Ecwid sits at the micro end of ecommerce, which makes this Actor ideal for territory-based, high-volume outreach rather than enterprise account planning.

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

***

### Who Uses the Ecwid Store Email Scraper?

**Ecommerce and local agencies.** Web designers, local SEO shops and Google Business Profile consultants who sell to independent retailers.

**App and plugin vendors.** Delivery slots, loyalty, reviews and subscription tools all sell directly to small store owners.

**3PL and payment providers.** Couriers, pickup networks and card processors need the business's website — not a marketplace handle — before an account can be qualified.

**Dropship suppliers.** Category keywords plus the `stockist` modifier surface shops already selling adjacent products locally.

**B2B wholesalers.** Independent retailers are the classic wholesale customer, and their trade pages are the ones most likely to carry a real address.

***

### Why Choose This Ecwid Store Email Scraper

**It gives you the business's real website.** Because `accept_any_host` is on, `url` is a domain you can open, enrich and match — not a platform profile.

**It reaches businesses other tools miss.** An embedded cart leaves no marketplace footprint, so these merchants are absent from most seller databases.

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

**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 and precise.** State is keyed by a hash of your input, while domain filtering, boundary-correct matching and the junk filter keep noise out of the dataset.

**It is part of a family.** The same engine powers dozens of sibling Actors, including the [WooCommerce Email Scraper](https://apify.com/neuro-scraper/woocommerce-email-scraper) and the **PrestaShop Store Email Scraper**.

***

### Limitations of the Ecwid Store Email Scraper

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

- **The footprint caveat comes first.** Results depend on the store leaving the `"Powered by Ecwid"` credit in place and on Google having indexed that page. Paid plans can remove the credit, so this is a subset of Ecwid merchants, never all of them.
- **Only publicly indexed emails.** If an address is not visible in Google's index, the Ecwid Store Email Scraper cannot find it. 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` behave differently here.** An embedded cart exposes no platform handle, so `username` is usually `null` and `profileUrl` falls back to the merchant's own website. When `username` is populated it comes from a path segment Google printed, so treat `url` as the authoritative link. This is a Google limitation, not a bug.
- **No guaranteed volume.** Results vary with keywords, domains and location — and because these are small local businesses, thin niches really do run dry.

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

***

### Related Actors

| Actor | What it collects |
|---|---|
| [Ecwid Store Email and Phone Number Scraper](https://apify.com/neuro-scraper/ecwid-store-email-and-phone-number-scraper) | Emails and phone numbers from Ecwid Store |
| [Ecwid Store Phone Number Scraper](https://apify.com/neuro-scraper/ecwid-store-phone-number-scraper) | Public phone numbers from Ecwid 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 |
| [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 |
| [Shopify Store Email Scraper](https://apify.com/leads-scraper/shopify-store-email-scraper) | Public contact emails from Shopify Store |
| [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 |

### Ecwid Store Email Scraper Example Run

A regional food distributor wants to reach independent shops that already sell online.

They run the Ecwid Store Email Scraper with `keywords: ["farm shop", "deli", "bakery"]`, `location: "Brighton"`, `countryCode: "GB"`, `customDomains: ["@gmail.com", "@outlook.com"]` and `maxEmails: 250`.

Query expansion turns three keywords into more than twenty phrasings, all anchored on `"Powered by Ecwid"`; the crawler paginates through Google while the dataset fills with business names, websites and addresses.

They sort by `possiblyTruncated`, drop the flagged rows, open a handful of sites to check the shops stock the right categories, then export a CSV. Total setup time: under five minutes.

***

### Ecwid Store Email Scraper FAQ

#### Does this find every store on Ecwid?

No — and no tool built this way can. The Ecwid Store Email Scraper only reaches stores whose pages carry the `"Powered by Ecwid"` footprint phrase *and* were indexed by Google. Merchants on plans that remove the credit are not reachable by this method.

#### Why does the query have no `site:` operator?

Because an Ecwid store is embedded in the merchant's own website. There is no shared host to restrict to, so the Actor searches the quoted footprint phrase instead.

#### Does the Ecwid Store Email Scraper log into Ecwid?

No. It never logs in, never uses an Ecwid API and never opens a merchant's site. All data comes from publicly indexed Google search results.

#### What is in the `url` field?

The merchant's own host, taken from Google's result breadcrumb — on this platform, usually the business's main website. That is the deliberate advantage of this Actor over a marketplace scraper.

#### Why is `username` usually `null`?

An embedded cart gives Google no platform handle to print. `profileUrl` therefore falls back to the merchant's own website, which is the link you actually want.

#### Where do the emails actually come from?

From Google result titles, breadcrumbs and snippets — typically contact pages, about pages, wholesale pages and ordering pages where the merchant published an address themselves.

#### Is this an Ecwid email extractor or a full store scraper?

It is an Ecwid email extractor. It returns the 14 fields listed above and nothing else — no products, no prices, no orders, no customer data.

#### Do I need an Apify proxy?

Yes. The Ecwid 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 query expansion is how the Ecwid Store Email Scraper reaches past that ceiling.

#### How do I build a territory list rather than a global one?

Set `countryCode` to a two-letter code and put a town, county or region in `location`; that phrase is appended to every query the Actor builds.

#### Does it deduplicate?

Yes, globally. An email appears once per run no matter how many queries or pages surfaced it.

#### What happens if a run is interrupted?

Progress is saved in the key-value store, keyed by a hash of your input, and flushed on `PERSIST_STATE`, `MIGRATING` and `ABORTING`. Restarting resumes rather than starting over.

#### Is this affiliated with Ecwid?

No. The Ecwid Store Email Scraper is an independent tool and is not affiliated with, endorsed by or officially supported by Ecwid or Lightspeed.

***

### Responsible Use and GDPR

Small local businesses often publish a single inbox that is both a business and a personal address, so treat these records with extra care.

Publicly visible does not mean consent to bulk marketing. Follow GDPR, CAN-SPAM, PECR and any other law that applies to you, keep outreach relevant to the shop's actual trade, identify yourself honestly, and honour opt-outs immediately.

Delete records you no longer have a lawful basis to hold, and do not use the Ecwid Store Email Scraper to build spam lists.

***

### Leave a review

If the Ecwid Store Email Scraper saved you time, please leave a star rating and a short review
on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

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

# Actor input Schema

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

Search terms describing the Ecwid 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 Ecwid 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",
    "shop"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.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 Ecwid 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",
        "shop"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact us",
        "wholesale",
        "customer service",
        "stockist"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/ecwid-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",
        "shop",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact us",
        "wholesale",
        "customer service",
        "stockist",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/ecwid-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",
    "shop"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact us",
    "wholesale",
    "customer service",
    "stockist"
  ]
}' |
apify call neuro-scraper/ecwid-store-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/ecwid-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/ME18J6KJ8LwqG5Er9/builds/MJDgCh4fTr9jnpuBB/openapi.json
