Alibaba Email Scraper

Alibaba Email Scraper — Extract Supplier Emails and Leads

Alibaba Email Scraper finds public email addresses on Alibaba, AliExpress, and 1688 pages by running site: searches through Google and parsing the result snippets. Give it a list of keywords and it returns each match as a typed JSON row — email, page title, snippet, URL, source marketplace, and the keyword that found it. No HTML, no selectors, no manual parsing. After reading this README you'll know exactly what the actor extracts, how to configure it, and how to pull its output straight into a CRM, spreadsheet, or AI pipeline.

What is Alibaba Email Scraper?

Alibaba Email Scraper is an Apify Actor that discovers publicly indexed Alibaba, AliExpress, or 1688 pages containing an email address and returns them as structured data. It works by issuing Google site: search dorks for each keyword you provide, reading the public result snippets, and extracting any email address found. No Alibaba account, login, or API key is required — the actor never contacts Alibaba's servers directly.

• Search Alibaba, AliExpress, or 1688 pages indexed by Google, selected via the platform input
• Extract email addresses parsed directly from search-result snippets
• Filter results to specific email domains (e.g. @gmail.com)
• Bias results toward a location by adding a location term to the query
• Batch many keywords in a single run, each processed and paged independently
• Export results as JSON, CSV, or Excel from the Apify dataset

What data does Alibaba Email Scraper collect?

Every output row represents one Google search result that matched your keyword and platform filter and contained a parseable email address. The actor returns six fields per row, grouped below by what they represent.

Data Type	Key Fields	JSON Field Names
Contact email	Email address parsed from the result snippet	email
Search result metadata	Result title, snippet text, and page URL	title, description, url
Query context	Source marketplace and the keyword that produced the result	network, keyword

Need more Alibaba data?

API-Empire does not currently publish a separate Alibaba product, supplier-profile, or listing scraper — this actor is the account's only Alibaba/AliExpress/1688 tool. Its platform input already covers all three marketplaces from one Actor, so if you need broader coverage today, run it with platform set to each marketplace you're targeting.

Why not build this yourself?

Alibaba Email Scraper doesn't call Alibaba's own systems — it depends on Google's search-result markup, which is not a stable, documented API. Google's result page uses unversioned CSS classes (the actor parses div.MjjYud, h3, and .VwiC3b blocks) that change without notice, and search traffic gets rate-limited or shown a CAPTCHA page well before Alibaba is ever involved. A DIY script has to detect blocks reliably, rotate proxies, retry with fresh IPs, and re-fix selectors every time Google adjusts its markup. This actor already handles size-and-phrase-based block detection, jittered retries, and rotation across Apify's GOOGLE_SERP and RESIDENTIAL proxy groups, so you get parsed rows instead of maintaining a scraper.

Why do developers and teams scrape Alibaba?

For B2B sales and lead-generation teams

Sales teams targeting import/export or wholesale buyers use keyword batches (e.g. led lights supplier, electronics supplier) to surface Alibaba pages that expose a direct contact email, skipping inquiry forms that go unanswered. Each row pairs an email with the title and url it came from, so a rep can verify context before outreach instead of cold-emailing a bare address. Filtering with emailDomains narrows results to corporate-looking addresses over generic webmail, and running the same keyword against platform: "AliExpress" or "1688" extends the same workflow to adjacent marketplaces without a separate tool.

For sourcing and procurement researchers

Procurement teams evaluating a product category run a set of niche keywords to see which supplier pages Google has indexed with public contact details, giving a fast first pass before formal RFQs. The description field carries the snippet text (factory location, product line, MOQ mentions) that a buyer can scan without opening every URL. Because results stream to the dataset per keyword, a researcher can compare yield across keyword variants (broad vs. narrow) to see which terms actually surface sourcing-ready pages.

For market and competitive researchers

Researchers studying how a product niche is represented on Alibaba use this actor to sample which pages rank and expose contact information for a given search term, without scraping Alibaba's site directly. Because every result is grounded in a real, publicly returned Google snippet, this stays within a public-data-only research scope — no login, no scraping behind Alibaba's authentication wall. Aggregating keyword and network across a run shows how coverage differs between Alibaba, AliExpress, and 1688 for the same search term.

For developers building outreach or enrichment pipelines

Because the actor is a standard Apify Actor, it's callable over HTTP from any backend, script, or AI agent framework, and returns flat, typed JSON — no HTML to parse before loading into a CRM or vector store. A developer can chain keyword generation, this actor's run, and a downstream email-validation or enrichment step into one pipeline, using email and url as the join keys back into their own lead records.

How to scrape Alibaba (step by step)

1. Open Alibaba Email Scraper on its Apify Store listing and start a new run.
2. Provide the required input: keywords, an array of one or more search terms (e.g. ["led lights supplier"]).
3. Set platform (Alibaba, AliExpress, or 1688 — defaults to Alibaba), and optionally location, emailDomains, and maxEmails to narrow the search.
4. Click Start. The actor configures the proxy group for your chosen engine, then runs a site: search per keyword and streams matching rows to the dataset as it finds them.
5. Open the Dataset tab once the run finishes (or while it's still running) and export results as JSON, CSV, or Excel.

What to do when Alibaba changes its structure

This actor doesn't parse Alibaba's own site, so Alibaba redesigns don't break it directly — what matters is Google's search-result markup and Alibaba's indexing/robots policy, both of which the actor is built to tolerate. The output schema (network, keyword, title, description, url, email) stays stable, so downstream integrations keep working even when the underlying page markup shifts. No specific turnaround time is promised for maintenance updates.

⬇️ Input

Parameter	Required	Type	Description	Example Value
keywords	Yes	array	List of keywords to search for. Each keyword is run as a site:<platform> "<keyword>" Google search, and emails are extracted from the result snippets.	["led lights supplier", "electronics supplier"]
platform	No	string	Marketplace to target: Alibaba (alibaba.com), AliExpress (aliexpress.com), or 1688 (1688.com). Sets the Google site: filter and the network label on each row. Default Alibaba.	"Alibaba"
location	No	string	Optional location term added to the search query. Leave empty to search globally. Default "".	"London"
emailDomains	No	array	Optional filter — keep only emails ending in these domains. Leave empty to collect all domains.	["@gmail.com"]
maxEmails	No	integer	Maximum number of emails to collect per keyword. Minimum 1, maximum 5000. Default 20.	20
engine	No	string	Fetch engine — selects the Apify proxy group: legacy (GOOGLE_SERP proxy) or residential (RESIDENTIAL proxy). Default legacy.	"legacy"
proxyConfiguration	No	object	Proxy settings. Google requests run through the proxy group selected by engine and retry on a fresh IP if blocked.	{ "useApifyProxy": true }

Example input

{
  "keywords": ["led lights supplier", "electronics supplier"],
  "platform": "Alibaba",
  "location": "",
  "emailDomains": ["@gmail.com"],
  "maxEmails": 20,
  "engine": "legacy",
  "proxyConfiguration": { "useApifyProxy": true }
}

Common pitfall: maxEmails caps emails per keyword, not per run — if you submit 10 keywords with maxEmails: 20, you can get up to 200 rows total, not 20.

⬆️ Output

Results are written to the Apify dataset as flat JSON objects and can be exported as JSON, CSV, or Excel. Each dataset row is billed as one row_result event under Apify's pay-per-event pricing — rows are only pushed (and only charged) when a snippet yields a parseable email, so pages with no match are never billed.

Scraped email result

{
  "network": "Alibaba.com",
  "keyword": "led lights supplier",
  "title": "LED Lights - Wholesale Supplier of Outdoor Lighting - Alibaba.com",
  "description": "Shenzhen LED lighting factory offering outdoor and indoor fixtures. Contact sales@example-lighting.com for a quote and MOQ details ...",
  "url": "https://www.alibaba.com/showroom/led-lights-supplier.html",
  "email": "sales@example-lighting.com"
}

This is the only entity type the actor returns — there are no separate product, supplier-profile, or review objects, since the data source is a Google search snippet rather than the Alibaba page itself.

How many results can you scrape with Alibaba Email Scraper?

maxEmails sets a hard per-keyword ceiling between 1 and 5,000 (default 20), so a run with multiple keywords can return up to maxEmails × number of keywords rows. There's no separate cap on how many keywords you can submit in one run. Within a keyword, the actor pages through Google results 10 at a time and stops early once it hits five consecutive result pages with no new matching email, so actual yield depends on how many indexed pages expose an address for that search term — it can land well below maxEmails for narrow keywords. No benchmark run time is published, since this depends on keyword count and Google response behavior.

Integrate Alibaba Email Scraper and automate your workflow

Alibaba Email Scraper works with any language or tool that can send an HTTP request, since it runs as a standard Apify Actor with a documented REST API.

REST API integration

import requests

ACTOR_ID = "API-Empire~alibaba-email-scraper"
TOKEN = "<YOUR_APIFY_TOKEN>"

run_input = {
    "keywords": ["led lights supplier"],
    "platform": "Alibaba",
    "maxEmails": 20,
}

url = f"https://api.apify.com/v2/acts/{ACTOR_ID}/run-sync-get-dataset-items?token={TOKEN}"
response = requests.post(url, json=run_input)
for row in response.json():
    print(row["email"], row["url"])

Works in Python, Node.js, Go, Ruby, cURL — any client that can make an authenticated HTTPS request.

Automation platforms (n8n, Make)

In n8n, the Apify node can run this Actor by ID and pass its dataset items directly into downstream nodes (CRM upserts, Slack alerts, spreadsheets) without a code step. In Make, the Apify app's run-actor module starts the Actor with your keywords and other inputs, and a follow-up "Get Dataset Items" module retrieves the resulting rows for use in the rest of the scenario.

Is it legal to scrape Alibaba?

Yes — Alibaba Email Scraper only collects data already publicly exposed in Google's search-result snippets for indexed marketplace pages; it does not log in, bypass access controls, or query any private Alibaba system. Because the underlying data is public business and listing content, the primary legal framing is Alibaba's and Google's own Terms of Service and database-rights considerations, not personal-data law. That said, the actor's core output is an email address, which several jurisdictions treat as personal data regardless of source — so storing, filtering, or using extracted addresses for outreach can trigger GDPR/CCPA-style obligations depending on your use case and location. Consult legal counsel for commercial use cases involving bulk collection or storage of email addresses.

Frequently asked questions

Does Alibaba Email Scraper work without an Alibaba account?

Yes. The actor never logs into Alibaba, AliExpress, or 1688, and no account or API key from those platforms is needed — it only reads public Google search-result pages filtered with a site: query.

How often is the scraped data updated?

Every run performs a live Google search at execution time; nothing is served from a cache. Results reflect whatever Google has indexed at the moment the run executes.

What happens if a keyword returns no emails?

The actor pages through Google results for that keyword and stops once it hits five consecutive pages with zero new matching emails, then moves to the next keyword. This is expected for narrow or low-volume search terms — broader, contact-oriented keywords typically surface more addresses.

Can I scrape private or restricted Alibaba content?

No. The actor only returns what appears in a public Google search snippet. Supplier pages that require a login, an inquiry form, or aren't indexed by Google will not appear in the output at all.

Does Alibaba Email Scraper work for AI agent workflows and LLM pipelines?

Yes. It's callable as a standard HTTP endpoint by any agent framework or script. Every response is flat, typed JSON with stable field names, so it can be passed directly to an LLM context window or indexed into a vector store without a parsing step.

How does Alibaba Email Scraper handle blocking during search?

Requests run through Apify's GOOGLE_SERP or RESIDENTIAL proxy group (selected by the engine input), with randomized headers and jittered delays between requests. If a response is detected as blocked — based on response size and known block phrases — the actor retries on a fresh proxy IP up to three times per request before failing that page.

Does Alibaba Email Scraper return data in a format LLMs can use directly?

Yes. Output is a flat JSON object with six consistent keys (network, keyword, title, description, url, email) — no HTML and no selectors to strip before use.

Can I use Alibaba Email Scraper without managing proxies?

Yes. Proxy setup is handled automatically based on the engine input; the proxyConfiguration field is exposed only if you want to override the default Apify proxy behavior.

Why did my run collect fewer emails than my maxEmails setting?

maxEmails is a ceiling, not a guarantee. Yield depends on how many Google-indexed pages for that keyword and platform actually expose a parseable email in their snippet — once the actor exhausts available results (five empty pages in a row), it stops that keyword early.

What happens when Google or Alibaba changes its structure or blocks the scraper?

The actor is maintained, and its output schema — field names and types — stays stable on the user's end even if the underlying page markup changes. No specific turnaround time is promised for fixes.

Your feedback

Found a bug, or need a field this actor doesn't currently return? Let API-Empire know through the Issues tab on this Actor's Apify Store page, or use the Contact developer option on the listing. Bug reports and field requests are what keep this actor's output accurate as Google's result pages evolve.