AliExpress Email Scraper

AliExpress Email Scraper - public supplier emails from AliExpress listings

The AliExpress Email Scraper turns publicly indexed AliExpress pages into a deduplicated list of supplier contact emails. It is built for dropshippers, importers, product-sourcing agents, private-label brands and wholesale buyers who need a direct line to a supplier rather than a chat thread in a message centre. Give it keywords, optional email domains and a location, and it returns a structured dataset ready for CSV, JSON or Excel export.

Be clear-eyed about what this Actor returns. AliExpress indexes product listings far more than store pages, so most rows carry a supplier email from a listing without a store handle. In a recent live test, none of the returned rows resolved to a /store/ profile URL - you get the email, the query and the listing context, but username is usually null and profileUrl is usually empty.

That is a Google indexing reality, not a defect, and it does not stop the emails from being usable. Supplier addresses published on AliExpress listings are exactly the trade and enquiry inboxes sourcing teams want. If a canonical store link matters more to you than the email itself, the eBay Email Scraper and Walmart Email Scraper resolve handles far more reliably.

The AliExpress Email Scraper does not log in, does not use AliExpress's API and never opens aliexpress.com itself. Every lead comes from Google's public index - titles, snippets and site labels - fetched through the Apify GOOGLE_SERP proxy. There is no browser, no JavaScript rendering, no authentication and no cookies.

What the AliExpress Email Scraper does

The AliExpress Email Scraper composes Google queries with the site: operator against aliexpress.com and aliexpress.us, then reads the result blocks. A generated query looks like site:aliexpress.com supplier wholesale "@gmail.com". Each block is parsed structurally, emails are pulled with a domain-filtered regex, and every unique address is pushed straight to the Apify dataset.

Because listing pages dominate the index, most of what the AliExpress Email Scraper reads is product-page text: titles, specification snippets and the contact lines suppliers put into their descriptions. Those contact lines are the payload. Store-page results do appear, and when one does the handle resolves to https://www.aliexpress.com/store/{username} - it is simply the exception rather than the rule. Plan your workflow around the email, not the store URL.

Why sourcing teams use an AliExpress Email Scraper

Contacting an AliExpress supplier normally means the message centre, which is slow, threaded and hard to track across dozens of candidates. Suppliers know this, which is why many publish an email in the listing itself for trade enquiries, pricing requests and sample orders. The AliExpress Email Scraper collects those published addresses at scale so you can run a proper outreach sequence from your own inbox or CRM.

Emails published on AliExpress listings are almost always business addresses: sales aliases, trade-enquiry inboxes, customer-service accounts. That is what makes them appropriate for B2B sourcing, and it is also why the responsible-use section below matters. The AliExpress Email Scraper touches no private account data, no order data and nothing behind a login.

Key features of the AliExpress Email Scraper

Feature	What it means in practice
Google-index sourcing	Reads publicly indexed AliExpress results through the Apify GOOGLE_SERP proxy - no login, no cookies, no browser
Two-domain coverage	Searches aliexpress.com and aliexpress.us
Listing-first extraction	Pulls supplier emails out of product-listing snippets, which is where AliExpress publishes most of them
Query expansion	Base, quoted and intitle: variants plus one variant per query modifier; base queries run first
Domain filtering	Only emails on the domains listed in customDomains are kept
Global deduplication	Each address is emitted once per run, across every query and every page - important when one supplier appears on hundreds of listings
Obfuscation handling	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 never matches inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another email in the same result block
Async concurrency	An asyncio worker pool with a shared stop signal on maxEmails
Retries and block detection	Up to 3 attempts per page with exponential backoff, a fresh proxy session per request, and CAPTCHA / "unusual traffic" / consent pages detected and retried rather than counted as empty
Blocked-query requeue	Blocked or failed queries are re-queued once at the end of the run
Resumable state	Key-value-store progress keyed by a hash of the input, with throttled saves plus saves on PERSIST_STATE, MIGRATING and ABORTING
Layout fallback	A whole-page fallback parser means a Google markup change degrades to "emails without account details", not "no emails"
Run summary	Logs pages fetched, blocked pages, retries and emails per page

Global deduplication deserves a note of its own here. A single AliExpress supplier can appear across hundreds of indexed listings with the same contact line. The AliExpress Email Scraper emits that address once, which is what keeps a listing-heavy platform from producing a listing-heavy dataset.

How the AliExpress Email Scraper works

1. It reads your input - keywords, location, email domains and limits.
2. It builds Google queries with the site: operator against aliexpress.com and aliexpress.us.
3. It fetches result pages asynchronously through the Apify GOOGLE_SERP proxy using aiohttp.
4. It locates each result's <h3> title and the smallest surrounding block, so it never depends on Google's CSS class names.
5. It extracts emails from that block text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead to the dataset immediately.

That immediate push means leads land while the AliExpress Email Scraper is still running, so an early abort keeps everything collected so far. State is resumable and keyed by a hash of your input, so a migrated or restarted run continues from where it stopped. Nothing is buffered until the end.

AliExpress Email Scraper input reference

Field names, types and defaults below are exactly what the Actor accepts.

Field	Type	Default	Meaning
keywords	array (required)	["supplier", "store"]	Search terms describing the AliExpress suppliers you want (product, category, niche)
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com","@yahoo.com"]	Only emails on these domains are kept; the leading @ is optional
maxEmails	integer 1-10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email","contact","wholesale","customer service","inquiries"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1-50	30	Page cap per query
maxConcurrency	integer 1-20	5	Parallel queries

Tuning the AliExpress Email Scraper

Product-specific keywords beat generic ones by a wide margin on this platform, because the index is full of listings. silicone baby bibs supplier will out-perform supplier every time, and the keyword field on each row lets you prove which phrasing worked. Add factory, OEM, MOQ, sample order or distributor to queryModifiers when you are sourcing manufacturing rather than resale stock.

This config targets two domains, so countryCode is a moderate lever - lighter than on the Amazon Email Scraper with its five domains, but US does bias results toward aliexpress.us. Widening customDomains matters more here: many suppliers publish on @163.com, @qq.com, @hotmail.com or @outlook.com rather than the @gmail.com / @yahoo.com defaults. Keep expandQueries on: Google caps a single query at roughly 300 results, and expansion is how the AliExpress Email Scraper gets past that ceiling.

Example input for the AliExpress Email Scraper

{
  "keywords": ["led strip lights supplier", "silicone kitchenware factory"],
  "location": "",
  "customDomains": ["@gmail.com", "@163.com", "@outlook.com"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "wholesale", "customer service", "inquiries"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

AliExpress Email Scraper output fields

Every dataset item carries all fourteen fields below - no more, no fewer.

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 (handle or display name)
fullName	Display name parsed from a profile-style title; empty for listing captions
username	URL-safe handle when AliExpress exposes one; otherwise null
profileUrl	Canonical store URL when a handle is known; otherwise empty
url	Direct AliExpress link when exposed, else the profile URL
description	Bio or listing 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

Example output from the AliExpress Email Scraper

This is what real output looks like: usable supplier emails from listing snippets, with username: null and an empty profileUrl because the result was a product page rather than a store page.

[
  {
    "network": "AliExpress",
    "keyword": "led strip lights supplier",
    "query": "site:aliexpress.com led strip lights supplier wholesale \"@gmail.com\"",
    "title": "5m RGB LED Strip Light Kit 5050 Waterproof - AliExpress",
    "accountName": "AliExpress",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Wholesale and OEM enquiries: ledstrip.trade@gmail.com. MOQ 100pcs, CE certified, custom lengths.",
    "email": "ledstrip.trade@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T13:15:22Z"
  },
  {
    "network": "AliExpress",
    "keyword": "silicone kitchenware factory",
    "query": "site:aliexpress.us silicone kitchenware factory contact \"@163.com\"",
    "title": "Food Grade Silicone Spatula Set 6pcs Heat Resistant - AliExpress",
    "accountName": "AliExpress",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "",
    "description": "Factory direct, custom colours and packaging. Sales contact: sales.kitchenware@163.com",
    "email": "sales.kitchenware@163.com",
    "emailDomain": "@163.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T13:16:47Z"
  }
]

When a /store/ result does surface, the AliExpress Email Scraper fills username and builds profileUrl as https://www.aliexpress.com/store/{username}. Treat those rows as a bonus and design your CRM import so an empty profileUrl is normal. The email, keyword, query and description fields are always populated enough to work with.

Use cases for the AliExpress Email Scraper

Who	How they use the AliExpress Email Scraper
Dropshippers	Reach suppliers directly for pricing, stock and shipping terms instead of using the message centre
Importers	Build a per-product supplier shortlist before requesting samples
Product-sourcing agents	Assemble a category contact list for a client brief
Private-label brands	Find factories that advertise OEM, custom packaging or MOQ terms in their listings
Wholesale buyers	Request trade pricing from multiple suppliers in one sequence
Freight and fulfilment providers	Reach suppliers with logistics, consolidation and 3PL offers
Market researchers	Measure how many suppliers in a category publish a direct contact
Quality and compliance teams	Open a documented channel with a supplier before placing an order

A productive pattern is to run the AliExpress Email Scraper once per product line, with narrow keywords, then merge datasets. Narrow runs keep attribution clean, because keyword and query record which phrasing produced each lead. That turns your sourcing language into something you can iterate on rather than guess at.

If AliExpress is one lane in a wider sourcing plan, the same engine covers the rest - the DHgate Email Scraper and Taobao Email Scraper sit closest to the same supplier base. For the retail side of the funnel, the Amazon Email Scraper covers five Amazon domains including Amazon Business, and the Etsy Email Scraper covers the handmade market.

AliExpress Email Scraper limitations - stated honestly

• Store handles are rare. AliExpress indexes product listings far more than store pages, so most rows carry a supplier email from a listing without a store handle. In a recent live test no returned row resolved to a store profile URL. Expect username: null and profileUrl: "" on the majority of rows.
• Publicly indexed emails only. If an address is not visible in Google's index, the AliExpress Email Scraper cannot find it. It does not crawl aliexpress.com.
• Google's result ceiling. A single query returns roughly 300 results at most, which is exactly why expandQueries and queryModifiers exist.
• possiblyTruncated. Rows where Google's snippet ellipsis touched the address are flagged true. This is worth watching on AliExpress, where contact lines often sit late in a long listing description. Verify those before sending.
• Apify GOOGLE_SERP proxy required. The AliExpress Email Scraper cannot run without Apify proxy credentials.
• Free-plan cap. Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
• username and profileUrl are conditional. They are filled only when Google's result exposes a handle. This is a Google indexing limitation, not a bug.
• No volume guarantee. Results vary with keywords, domains, country and location. No count is promised.

Responsible use

Emails published on AliExpress listings and store pages are usually business or sales addresses posted for trade enquiries. Treat them as B2B contact points, keep outreach relevant and specific, honour opt-outs, and record a lawful basis if you operate under GDPR, PECR or similar rules. Review AliExpress's terms and your local marketing law before you send - the AliExpress Email Scraper collects public data, but what you do with it is your responsibility.

This Actor is not affiliated with, endorsed by or officially supported by AliExpress or Alibaba Group.

FAQ about the AliExpress Email Scraper

Why is profileUrl empty on almost every row? AliExpress indexes product listings far more than store pages, so most rows carry a supplier email from a listing without a store handle. The email, keyword, query and listing snippet are still there.

Is the tool broken if username is null? No. username and profileUrl are only populated when Google's result exposes a handle. On AliExpress that is uncommon, which is a Google indexing limitation rather than a bug.

Does the AliExpress Email Scraper log into AliExpress? No. It never logs in, never uses AliExpress's API and never opens aliexpress.com. Everything comes from publicly indexed Google search results.

Which domains does it search? aliexpress.com and aliexpress.us.

How do I get better results on AliExpress? Use narrow product keywords rather than the generic defaults, and widen customDomains to include @163.com, @qq.com, @hotmail.com and @outlook.com alongside the defaults.

Can it find emails on any domain? Only the domains you list in customDomains. The default is @gmail.com and @yahoo.com.

How many emails can one run return? Up to maxEmails, which accepts 1 to 10000. Free Apify plans are capped at 100 emails per run; paid plans are uncapped.

What does possiblyTruncated: true mean? Google's snippet ellipsis touched that address, so it may be cut off. On listing-heavy platforms this happens more often - verify before adding to a send list.

Does it need proxies? Yes - the Apify GOOGLE_SERP proxy. The AliExpress Email Scraper cannot run without Apify proxy credentials.

Can I resume an interrupted run? Yes. Progress lives in the key-value store, keyed by a hash of your input, and is saved on PERSIST_STATE, MIGRATING and ABORTING events.

Will I get the same supplier hundreds of times? No. Deduplication is global across every query and page, so an address that appears on hundreds of listings is emitted once.

Can the AliExpress Email Scraper be used with an Apify schedule or the API? Yes. It is a standard Apify Actor, so it can be started from the Apify API, the JavaScript or Python client, or a schedule, and it writes to a normal dataset.

Are the emails verified? No. The AliExpress Email Scraper extracts what is published in the index. Run your own verification before a campaign.

Getting started with the AliExpress Email Scraper

1. Open the AliExpress Email Scraper on Apify and press Try for free.
2. Replace the default keywords (supplier, store) with narrow product terms.
3. Widen customDomains beyond the defaults - Chinese suppliers often publish on @163.com or @qq.com.
4. Raise maxEmails and run it.
5. Export the dataset from the Storage tab when the AliExpress Email Scraper finishes.

Start small - a maxEmails of 20 to 50 - to confirm your product keywords and domains are pulling real supplier contacts. Once a keyword set is producing useful rows, re-run the AliExpress Email Scraper with a higher cap and more pages per query.

Exporting AliExpress Email Scraper results

Every AliExpress Email Scraper run writes to a standard Apify dataset, so you can download CSV, JSON, XML or Excel, or pull the rows through the Apify API and the JavaScript or Python clients. The default dataset view surfaces the fields most people need first: email, account, name, username, profile, keyword, bio snippet and the truncation flag - and on this platform the username and profile columns will mostly be blank. Deduplication is per run, so keep your own master list when you merge several AliExpress Email Scraper datasets together.

Related Actors

The AliExpress Email Scraper belongs to a 41-Actor E-commerce & Marketplaces family sharing this engine.

Actor	What it collects
AliExpress Email and Phone Number Scraper	Emails and phone numbers from AliExpress
AliExpress Phone Number Scraper	Public phone numbers from AliExpress
Allegro Email Scraper	Public contact emails from Allegro
Amazon Email Scraper	Public contact emails from Amazon
Best Buy Seller Email Scraper	Public contact emails from Best Buy
BigCommerce Store Email Scraper	Public contact emails from BigCommerce Store
Cdiscount Email Scraper	Public contact emails from Cdiscount
Coupang Email Scraper	Public contact emails from Coupang
Depop Email Scraper	Public contact emails from Depop
DHgate Email Scraper	Public contact emails from DHgate
eBay Email Scraper	Public contact emails from eBay
Ecwid Store Email Scraper	Public contact emails from Ecwid Store
Etsy Email Scraper	Public contact emails from Etsy
Faire Email Scraper	Public contact emails from Faire
Flipkart Email Scraper	Public contact emails from Flipkart
Home Depot Seller Email Scraper	Public contact emails from Home Depot
JD.com Email Scraper	Public contact emails from JD.com
Lazada Email Scraper	Public contact emails from Lazada
Lowe's Seller Email Scraper	Public contact emails from Lowe's
MercadoLibre Email Scraper	Public contact emails from MercadoLibre
Mercari Email Scraper	Public contact emails from Mercari
Newegg Email Scraper	Public contact emails from Newegg
Otto Email Scraper	Public contact emails from Otto
Overstock Email Scraper	Public contact emails from Overstock
Poshmark Email Scraper	Public contact emails from Poshmark
Rakuten Email Scraper	Public contact emails from Rakuten
Shopee Email Scraper	Public contact emails from Shopee
Shopify Store Email Scraper	Public contact emails from Shopify Store
Taobao Email Scraper	Public contact emails from Taobao
Target Seller Email Scraper	Public contact emails from Target
Temu Email Scraper	Public contact emails from Temu
Tmall Email Scraper	Public contact emails from Tmall
Vinted Email Scraper	Public contact emails from Vinted
Walmart Email Scraper	Public contact emails from Walmart
Wayfair Email Scraper	Public contact emails from Wayfair
Wish Email Scraper	Public contact emails from Wish
Wix Stores Email Scraper	Public contact emails from Wix Stores
WooCommerce Email Scraper	Public contact emails from WooCommerce
Zalando Email Scraper	Public contact emails from Zalando
Allegro Email and Phone Number Scraper	Emails and phone numbers from Allegro
Amazon Email and Phone Number Scraper	Emails and phone numbers from Amazon
Best Buy Email and Phone Number Scraper	Emails and phone numbers from Best Buy

Support

Questions, a bug, or need a custom build? Email neurodata.apify@gmail.com.