Wikipedia Contact Email Scraper

Wikipedia Contact Email Scraper - emails cited in Wikipedia articles, honestly labelled

The Wikipedia Contact Email Scraper searches Google's public index of wikipedia.org and extracts email addresses that appear in the indexed result text. Read this before your first run: Wikipedia articles rarely publish contact addresses, so most rows carry an email cited in a reference rather than an official contact. That distinction is the single most important thing to understand about the Wikipedia Contact Email Scraper.

Wikipedia is an encyclopedia, not a directory. Articles about organisations and institutes do not list a press inbox as a matter of style. What they do contain are citations: a press release, an annual report, a government notice, a letter, an archived page. Those sources sometimes carry an address, and that address gets indexed with the article.

So a row from the Wikipedia Contact Email Scraper is usually a third party's address quoted in a reference, not the subject's official contact. Treat it as a research lead to verify, never as a confirmed contact channel.

Our measured live run reflects that: 10 result blocks, 10 rows with identity data, 10 profile URLs and 6 unique emails.

Who uses the Wikipedia Contact Email Scraper

Desk researchers, due-diligence analysts and journalists run the Wikipedia Contact Email Scraper while mapping an organisation, to see which addresses appear in the public record around it. It is a paper-trail tool rather than a lead-generation tool.

Audience	How they use the Wikipedia Contact Email Scraper
Desk and archival researchers	Trace which addresses appear in the cited sources for a topic
Due-diligence and OSINT analysts	Map the public paper trail around an organisation or institute
Journalists	Follow citations to a reachable source
Academic researchers	Identify institutional sources referenced in an article
Knowledge-base and data teams	Audit what contact data leaks into encyclopedic citations
Non-profit and policy researchers	Find referenced bodies working in a policy area

How the Wikipedia Contact Email Scraper works

The Wikipedia Contact Email Scraper never logs into Wikipedia, never uses the MediaWiki API and never opens an article in a browser. There is no JavaScript rendering, no authentication and no cookie handling.

The run is a structured Google harvest:

1. Read the input: keywords, location, email domains and limits.
2. Build Google queries with the site: operator, for example site:wikipedia.org institute contact "@gmail.com".
3. Fetch result pages through the Apify GOOGLE_SERP proxy with async aiohttp requests.
4. Parse each result block structurally by locating the <h3> title and the smallest surrounding block.
5. Extract emails from the block text with a domain-filtered regular expression.
6. Deduplicate globally and push each lead to the Apify dataset immediately.

Everything the Wikipedia Contact Email Scraper returns comes from publicly indexed search text: titles, snippets and site labels. It does not read article wikitext, edit histories or user pages.

Key features of the Wikipedia Contact Email Scraper

Feature	What it does
Google site: scoping	Restricts every query to wikipedia.org, across language editions Google surfaces
Query expansion	Base, quoted and intitle: variants plus one variant per modifier; base queries run first
Query modifiers	email, contact, press, booking, submissions by default
Email domain filtering	Keeps only addresses on your customDomains list
Global deduplication	One unique email per run across every query and page
Obfuscated address handling	Reads name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and full-width ＠
Placeholder rejection	Filters email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com does not match inside @gmail.company or @gmail.com.br
Soft-wrap repair	Drops a hit that is only the tail of another email in the same block
Structural block parsing	No dependence on Google CSS class names
Whole-page fallback parser	A markup change degrades to "emails without account details", not "no emails"
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried
Retries and re-queueing	Up to 3 attempts per page with exponential backoff and a fresh proxy session; failed queries re-queued once
Resumable state	Key-value store state keyed by an input hash, saved on PERSIST_STATE, MIGRATING and ABORTING
Async concurrency	asyncio worker pool with a shared stop signal on maxEmails
Streaming dataset writes	Rows appear as they are found

The Wikipedia Contact Email Scraper also logs pages fetched, blocked pages, retries and emails per page in the run summary.

Input fields for the Wikipedia Contact Email Scraper

Field	Type	Default	Meaning
keywords	array (required)	["organisation", "institute"]	Search terms describing the articles or subjects you want
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com","@yahoo.com"]	Only emails on these domains are kept; @ 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","press","booking","submissions"]	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

Example input for the Wikipedia Contact Email Scraper

{
  "keywords": ["marine research institute", "heritage foundation", "organisation"],
  "location": "Portugal",
  "customDomains": ["@gmail.com", "@yahoo.com"],
  "maxEmails": 60,
  "countryCode": "PT",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "press", "booking", "submissions"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Set maxEmails conservatively. Given how rarely Wikipedia publishes addresses, a Wikipedia Contact Email Scraper run usually ends because matches run out, not because the cap is reached.

Output fields from the Wikipedia Contact Email Scraper

Every dataset item carries all fourteen fields.

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
fullName	Display name parsed from a profile-style title; empty for post captions
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 caption snippet, cleaned of labels and engagement counters
email	Lower-cased email address
emailDomain	The matched domain, for example @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email
foundAt	ISO 8601 UTC timestamp

On Wikipedia the exposed handle is the article slug, so the Wikipedia Contact Email Scraper builds profileUrl as https://en.wikipedia.org/wiki/{username}. That URL identifies the article, not the owner of the email.

Example output from the Wikipedia Contact Email Scraper

[
  {
    "network": "Wikipedia",
    "keyword": "marine research institute",
    "query": "site:wikipedia.org \"marine research institute\" contact \"@gmail.com\" \"Portugal\"",
    "title": "Algarve Marine Research Institute - Wikipedia",
    "accountName": "Algarve_Marine_Research_Institute",
    "fullName": "Algarve Marine Research Institute",
    "username": "Algarve_Marine_Research_Institute",
    "profileUrl": "https://en.wikipedia.org/wiki/Algarve_Marine_Research_Institute",
    "url": "https://en.wikipedia.org/wiki/Algarve_Marine_Research_Institute",
    "description": "Cited press release lists enquiries to coastalsurvey.press@gmail.com",
    "email": "coastalsurvey.press@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-31T17:05:12.338Z"
  },
  {
    "network": "Wikipedia",
    "keyword": "heritage foundation",
    "query": "site:wikipedia.org \"heritage foundation\" email \"@yahoo.com\"",
    "title": "Douro Heritage Foundation - Wikipedia",
    "accountName": "Douro_Heritage_Foundation",
    "fullName": "Douro Heritage Foundation",
    "username": "Douro_Heritage_Foundation",
    "profileUrl": "https://en.wikipedia.org/wiki/Douro_Heritage_Foundation",
    "url": "https://en.wikipedia.org/wiki/Douro_Heritage_Foundation",
    "description": "Reference 14 quotes a 2019 newsletter signed douro.newsletter...",
    "email": "douro.newsletter@yahoo.com",
    "emailDomain": "@yahoo.com",
    "possiblyTruncated": true,
    "foundAt": "2026-08-31T17:06:30.771Z"
  }
]

Both rows illustrate the pattern the Wikipedia Contact Email Scraper produces: the address came from a cited source, and the profile URL points at the article that cited it. The second row is flagged possiblyTruncated, so it needs verification before any use.

What results to expect from the Wikipedia Contact Email Scraper

Our measured live run returned 10 result blocks, 10 identity rows, 10 profile URLs and 6 unique emails. Identity resolution is excellent because every article has a stable slug, but email density is moderate for a structural reason.

Wikipedia articles rarely publish contact addresses, so most rows carry an email cited in a reference rather than an official contact. Volume from the Wikipedia Contact Email Scraper varies with keywords, customDomains, countryCode and location, and no number is guaranteed.

Tips for stronger Wikipedia Contact Email Scraper runs

Give the Wikipedia Contact Email Scraper the kind of body you want: "research institute", "foundation", "observatory", "heritage trust", "regional agency". Those article types cite reports and press material far more often than biographies do.

Widen customDomains beyond free-mail; cited sources often use institutional or .org addresses. Keep expandQueries on to work around Google's roughly 300-results-per-query ceiling, and do not expect concurrency to increase yield.

Researchers often pair this with the Internet Archive Email Scraper for archived source material and the Scribd Email Scraper for reports and grey literature.

Limitations of the Wikipedia Contact Email Scraper

• Wikipedia articles rarely publish contact addresses, so most rows carry an email cited in a reference rather than an official contact. This is the dominant limitation and it affects how every row should be read.
• An address found this way may belong to a third party quoted in a source, not to the subject of the article.
• The Wikipedia Contact Email Scraper only finds pages whose email is publicly visible in Google's index; it does not read wikitext, references sections in full, or edit histories.
• Cited material can be old, so an address may be out of date.
• Google caps a single query at roughly 300 results, which is exactly why query expansion exists.
• possiblyTruncated: true means Google's snippet ellipsis may have clipped the address; verify before use.
• username and profileUrl are only populated when a slug is exposed in the Google result, and that URL identifies the article rather than the address owner. Rows without a slug arrive with username: null and an empty profileUrl. This is a Google limitation, not a bug.
• The Actor requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
• Free Apify plans are capped at 100 emails per run; paid plans are uncapped.
• Results vary with keywords, domains and location; no volume is guaranteed.

Ethics and responsible use

The Wikipedia Contact Email Scraper needs a clearer conscience than most, because of whose addresses it surfaces. An email cited in a Wikipedia reference usually belongs to a third party - an author, a spokesperson, a signatory - who published it in a different context for a different purpose.

Verify who an address actually belongs to before you contact anyone, and never assume it is an organisation's official channel. Use these leads for relevant, respectful correspondence: source verification, research enquiries, corrections and permissions.

Do not build marketing lists from third-party addresses lifted out of citations, and honour any opt-out immediately. Respect GDPR and institutional norms, and check with your compliance or editorial team if you are unsure. This is not legal advice.

Related Actors

The Wikipedia Contact Email Scraper shares its engine with every Actor below in the Content, Media, Research and Entertainment category.

Actor	What it collects
Wikipedia Email and Phone Number Scraper	Emails and phone numbers from Wikipedia
Wikipedia Phone Number Scraper	Public phone numbers from Wikipedia
ArtStation Email Scraper	Public contact emails from ArtStation
arXiv Email Scraper	Public contact emails from arXiv
Blogger Email Scraper	Public contact emails from Blogger
Crunchyroll Email Scraper	Public contact emails from Crunchyroll
Digg Email Scraper	Public contact emails from Digg
Flipboard Email Scraper	Public contact emails from Flipboard
iHeartRadio Email Scraper	Public contact emails from iHeartRadio
IMDb Email Scraper	Public contact emails from IMDb
Internet Archive Email Scraper	Public contact emails from Internet Archive
iTunes Podcast Host Email Scraper	Public contact emails from Apple Podcasts
Netflix Shows Email Scraper	Public contact emails from Netflix
Rotten Tomatoes Email Scraper	Public contact emails from Rotten Tomatoes
Scribd Email Scraper	Public contact emails from Scribd
Spotify Email Scraper	Public contact emails from Spotify
Spotify Playlist Email Scraper	Public contact emails from Spotify
TuneIn Email Scraper	Public contact emails from TuneIn
WordPress Blog Email Scraper	Public contact emails from WordPress.com
ArtStation Email and Phone Number Scraper	Emails and phone numbers from ArtStation
arXiv Email and Phone Number Scraper	Emails and phone numbers from arXiv
Blogger Email and Phone Number Scraper	Emails and phone numbers from Blogger
Crunchyroll Email and Phone Number Scraper	Emails and phone numbers from Crunchyroll
Digg Email and Phone Number Scraper	Emails and phone numbers from Digg
Flipboard Email and Phone Number Scraper	Emails and phone numbers from Flipboard
iHeartRadio Email and Phone Number Scraper	Emails and phone numbers from iHeartRadio
IMDb Email and Phone Number Scraper	Emails and phone numbers from IMDb
Internet Archive Email and Phone Number Scraper	Emails and phone numbers from Internet Archive
Apple Podcasts Email and Phone Number Scraper	Emails and phone numbers from Apple Podcasts
Netflix Email and Phone Number Scraper	Emails and phone numbers from Netflix
Rotten Tomatoes Email and Phone Number Scraper	Emails and phone numbers from Rotten Tomatoes
Scribd Email and Phone Number Scraper	Emails and phone numbers from Scribd
Spotify Email and Phone Number Scraper	Emails and phone numbers from Spotify
Spotify Email and Phone Number Scraper	Emails and phone numbers from Spotify
TuneIn Email and Phone Number Scraper	Emails and phone numbers from TuneIn
ArtStation Phone Number Scraper	Public phone numbers from ArtStation
arXiv Phone Number Scraper	Public phone numbers from arXiv
Blogger Phone Number Scraper	Public phone numbers from Blogger
Crunchyroll Phone Number Scraper	Public phone numbers from Crunchyroll
Digg Phone Number Scraper	Public phone numbers from Digg
Flipboard Phone Number Scraper	Public phone numbers from Flipboard
iHeartRadio Phone Number Scraper	Public phone numbers from iHeartRadio

FAQ about the Wikipedia Contact Email Scraper

How many results should I expect from the Wikipedia Contact Email Scraper?

Our measured live run returned 10 result blocks, 10 identity rows, 10 profile URLs and 6 unique emails. Wikipedia articles rarely publish contact addresses, so moderate email volume with excellent identity data is the normal pattern.

Does the Wikipedia Contact Email Scraper return official organisation contacts?

Usually not. Most rows carry an email cited in a reference rather than an official contact, so verify ownership before contacting anyone.

Whose address am I actually looking at?

Often a third party quoted in a cited source - an author, spokesperson or signatory. The Wikipedia Contact Email Scraper reports where the address was found, not who controls it.

Does the Wikipedia Contact Email Scraper use the MediaWiki API?

No. It never uses the API, never logs in and never opens an article. All data comes from publicly indexed Google results.

Does the Wikipedia Contact Email Scraper read the full references section?

No. It reads only Google's indexed result text, so it sees whatever fragment Google surfaced.

Why does profileUrl point at an article?

Because the exposed handle is the article slug, and https://en.wikipedia.org/wiki/{username} is the canonical URL for it. It identifies the article, not the email owner.

Can I target a country with the Wikipedia Contact Email Scraper?

Yes. Set countryCode to a two-letter code such as US, GB or PT, and optionally add a location phrase.

Which email domains does the Wikipedia Contact Email Scraper collect?

Only those in customDomains. The default is @gmail.com and @yahoo.com, and the leading @ is optional.

What does possiblyTruncated mean?

Google's snippet ellipsis touched the address, so it may be incomplete. Verify those rows before use.

Could a Wikipedia Contact Email Scraper address be out of date?

Yes. Citations can be years old, so an address quoted in a reference may no longer be monitored.

Does the Wikipedia Contact Email Scraper handle obfuscated addresses?

Yes. It normalises [at]/[dot] spellings, (at) forms, spaced @, spaced .com, zero-width characters and the full-width ＠.

Do I need Apify proxy access?

Yes. The Wikipedia Contact Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

Is there a free-plan cap?

Free Apify plans are capped at 100 emails per run; paid plans are uncapped.

Leave a review

If the Wikipedia Contact 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 about the Wikipedia Contact Email Scraper, feature requests or a custom build? Email neurodata.apify@gmail.com.