Infobel Email Scraper

Infobel Email Scraper - public business contact emails from infobel.com

The Infobel Email Scraper collects publicly indexed contact emails that appear in Google search results for infobel.com. Infobel is one of the oldest online business and telephone directories, with company records spanning a large number of countries.

One thing must be said before anything else, because it shapes every row you will see. Infobel indexes category and search pages more than company profiles, so most rows carry an email without a resolvable handle.

That is not a defect, and this README will not bury it. The Infobel Email Scraper is an email-rich, identity-poor Actor: you get the contact route, usually without a clean company page link attached.

For most local outreach that trade-off is workable, because the address is what you actually need. Local-services agencies, SMB SaaS vendors and franchise development teams are the people who get real value from it.

A measured live result, stated plainly

A live Google run of the Infobel Email Scraper returned 10 result blocks, 1 row with account identity, 1 resolvable profile URL and 9 unique emails. Those are observed figures, not estimates.

Nine unique emails from ten blocks is a very strong ratio. Infobel's category and search pages list contact details in bulk, and that is exactly the sort of page a snippet-level extractor reads well.

One identity resolution out of ten is equally real, and it is the direct consequence of the same fact. If you need a clean company URL on every record, the Infobel Email Scraper is not the Actor for that job.

Read that pair of numbers as a positioning statement rather than a scoreboard. The Infobel Email Scraper is a volume tool for local contact discovery, and it should be judged on the addresses it returns.

Features of the Infobel Email Scraper

Every feature below is genuinely implemented. Nothing here is aspirational.

Feature	What it means in practice
Google SERP parsing	Reads Google result pages through the Apify GOOGLE_SERP proxy. No browser, no JavaScript rendering
Structural block detection	Locates the <h3> title, then the smallest surrounding block. Does not depend on Google's CSS class names
Domain filter	Only emails ending in one of your customDomains values are kept
Query expansion	Base, quoted, intitle: and one variant per query modifier. Base queries run first
Global deduplication	An email seen once is never pushed twice, across every query and every page
Email normalisation	Understands name [at] domain [dot] com, name (at) domain, name @ domain.com, domain .com, zero-width characters and the full-width ＠ sign
Junk filter	Rejects placeholders such as 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
Concurrency	An asyncio worker pool with a shared stop signal on maxEmails
Retries	Up to 3 attempts per page, exponential backoff, a fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Re-queueing	Blocked or failed queries are retried once at the end of the run
Resumable run	State is stored in the key-value store, keyed by a hash of the input, and saved on PERSIST_STATE, MIGRATING and ABORTING
Fallback parser	If Google's markup changes, the run degrades to "emails without account details" rather than "no emails"
Run summary	Logs pages fetched, blocked pages, retries and emails per page
Dataset output	Rows push immediately and export to CSV, JSON, Excel or XML from the Apify dataset

Three of those features do most of the work in the Infobel Email Scraper. Soft-wrap repair, the junk filter and global deduplication all matter more on dense listing pages than they would on tidy one-company profiles.

How the Infobel Email Scraper works

The pipeline is six steps and there is nothing hidden inside it.

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google search queries with the site: operator against infobel.com, for example site:infobel.com company "@gmail.com" "Brussels".
3. It fetches Google result pages through the Apify GOOGLE_SERP proxy using aiohttp, asynchronously.
4. It parses each result block structurally, finding the <h3> title and the smallest block around it.
5. It extracts emails from that block's text with a domain-filtered regex.
6. It deduplicates globally and pushes each lead straight into the Apify dataset.

The Infobel Email Scraper does not log into Infobel, does not use any Infobel API, and does not open the directory in a browser. Every field comes from publicly indexed Google search results - titles, snippets and site labels, with no authentication and no cookies.

Who the Infobel Email Scraper is built for

This is a local and regional business directory Actor, so its audience is people selling to small and mid-sized companies rather than industrial buyers.

Local-services agencies use it to build outreach lists for web design, SEO, print and signage work in a defined town or region. SMB SaaS vendors use it to reach owner-operated businesses that still run on paper or spreadsheets.

Franchise development teams use it to find independent operators in a category they want to convert. Field sales teams use it to plan territory coverage before a route.

Because Infobel spans a large number of countries, it is also useful for anyone testing a new national market. If you need industrial suppliers rather than local businesses, use Kompass Email Scraper or Europages Email Scraper instead.

Input fields for the Infobel Email Scraper

Field	Type	Default	Meaning
keywords	array (required)	["company", "supplier"]	Search terms - 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 kept; the @ 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", "enquiries", "owner", "get a quote"]	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

How the Infobel Email Scraper input fields actually behave

location is the most important field in the Infobel Email Scraper. Because so many indexed pages are category and city pages, a location phrase such as "Brussels", "Antwerpen" or "Marseille" is what makes a query hit a dense listing page rather than a thin one.

keywords should name a trade, not a company type. plumber, hair salon, driving school and accountant all match the Infobel index better than the broad defaults company and supplier.

queryModifiers only fire when expandQueries is true. The defaults enquiries, owner and get a quote are tuned for local business pages, where those exact phrases sit beside published addresses.

customDomains is not the bottleneck it is on B2B platforms. Small local businesses genuinely do use Gmail and Yahoo, which is a large part of why the Infobel Email Scraper reached nine unique emails from ten blocks.

maxEmails is a hard stop shared across the worker pool, and on this email-dense Actor it is often the limit you hit first. maxConcurrency and maxPagesPerQuery trade speed against politeness; the defaults of 5 and 30 are sensible.

JSON input example for the Infobel Email Scraper

{
  "keywords": ["plombier", "coiffeur", "auto-ecole"],
  "location": "Bruxelles",
  "customDomains": ["@gmail.com", "@yahoo.com", "@skynet.be", "@telenet.be", "@hotmail.com"],
  "maxEmails": 300,
  "countryCode": "BE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "enquiries", "owner", "get a quote"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

That is a realistic configuration for the Infobel Email Scraper: three trades named in the local language, one city, a matching country code and national webmail domains.

Infobel is a genuinely multilingual directory, so native-language trade names are worth using. plombier reaches Belgian and French listings that plumber never surfaces, and Klempner or fontanero do the same for Germany and Spain.

The national webmail domains in that example are the other half of the recipe. @skynet.be and @telenet.be are common among Belgian small businesses and are invisible to the default filter.

Output fields of the Infobel 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 category and search results
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 snippet text, cleaned of labels and counters
email	Lower-cased email address
emailDomain	The matched domain, for example @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email - verify before sending
foundAt	ISO 8601 UTC timestamp

Reading Infobel Email Scraper output honestly

Expect the large majority of rows to arrive with username: null and an empty profileUrl. That follows directly from Infobel indexing category and search pages more than company profiles.

Use url, title and description for context when that happens. A city-and-trade category URL still tells you what the business does and roughly where it is, which is normally enough to qualify a local lead.

Check possiblyTruncated before sending. When it is true, Google's snippet ellipsis may have clipped the address and you should confirm it on the source page.

JSON output example from the Infobel Email Scraper

[
  {
    "network": "Infobel",
    "keyword": "plombier",
    "query": "site:infobel.com plombier contact \"@gmail.com\" \"Bruxelles\"",
    "title": "Plombiers a Bruxelles - Infobel",
    "accountName": "Plombiers a Bruxelles",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.infobel.com/fr/belgium/business/bruxelles/plombiers",
    "description": "Liste des plombiers a Bruxelles avec adresses, telephones et emails de contact.",
    "email": "sanitaire.dupont@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-08-29T15:02:44Z"
  },
  {
    "network": "Infobel",
    "keyword": "coiffeur",
    "query": "site:infobel.com coiffeur \"get a quote\" \"@telenet.be\"",
    "title": "Salon Elegance BVBA - Infobel",
    "accountName": "Salon Elegance BVBA",
    "fullName": "Salon Elegance BVBA",
    "username": "salon-elegance-bvba",
    "profileUrl": "https://www.infobel.com/salon-elegance-bvba",
    "url": "https://www.infobel.com/salon-elegance-bvba",
    "description": "Hair salon in central Brussels. Appointments and enquiries by email.",
    "email": "salon.elegance@telenet.be",
    "emailDomain": "@telenet.be",
    "possiblyTruncated": true,
    "foundAt": "2026-08-29T15:04:11Z"
  }
]

The first row is the common case on this platform and the second is the rare one. Any README that showed you only the second shape would be misrepresenting how Infobel is indexed.

Use cases for the Infobel Email Scraper

Audience	What they do with the data
Local-services agencies	Build outreach lists for web design, SEO, print or signage in a defined town
SMB SaaS vendors	Reach owner-operated businesses still running on paper or spreadsheets
Franchise development teams	Find independent operators in a category worth converting to a franchise
Field sales teams	Plan territory coverage before working a route
Payment and POS providers	Approach retail and hospitality businesses in a chosen city
Insurance and finance brokers	Prospect small businesses by trade and municipality
Market-entry consultants	Test the density of a trade in a new national market
Local data researchers	Map which trades publish contact routes in which countries

Every one of those jobs targets a business inbox that an owner published in a directory so customers could get in touch. That is the honest boundary of what the Infobel Email Scraper is for.

Targeting tips and multilingual keywords for the Infobel Email Scraper

location and countryCode are both real levers, and on the Infobel Email Scraper they matter more than anywhere else in this local set.

Set location to a city or municipality rather than a country. Infobel's index is organised around place-and-trade pages, so a city phrase is what puts your query on a page that actually lists businesses.

countryCode changes the country of the search proxy and therefore which national view Google prefers. Because Infobel is global, running the same trade keyword against BE, FR, ES and PL is a cheap way to compare markets.

Native-language trade names are essential here, not optional. plombier, Klempner, fontanero, idraulico and loodgieter each reach an entirely different slice of the directory than the English plumber does.

Keep expandQueries on so the owner and get a quote modifiers reach pages where addresses are printed. For overlapping multilingual local coverage, run Cybo Email Scraper with the same city and language settings.

Limitations of the Infobel Email Scraper

Read all of these before your first run.

• Infobel indexes category and search pages more than company profiles, so most rows carry an email without a resolvable handle. Expect username: null and an empty profileUrl on the large majority of rows.
• The Infobel Email Scraper only finds addresses that are publicly visible in Google's index. Anything Google has not indexed is invisible to it.
• Google caps a single query at roughly 300 results, which is exactly why query expansion exists and defaults to on.
• possiblyTruncated: true means Google's snippet ellipsis may have cut the email short. Verify it before sending.
• It 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. On this email-dense Actor you will reach that cap quickly.
• username and profileUrl are only populated when Google exposes a handle, which on Infobel is very much the minority case. That is a Google limitation, not a bug.
• Results vary with keywords, domains, language and location. No volume is guaranteed by the Infobel Email Scraper or by any Actor in this family.

Responsible use of Infobel Email Scraper output

The addresses the Infobel Email Scraper surfaces are business contacts that owners published in a directory so that customers and partners could reach them. Treat them as exactly that.

Under GDPR, a sole trader's or a named employee's address is personal data even when it is publicly listed, and much of Infobel's coverage is inside the EU. Record your legitimate interest, identify yourself in the first line, and make the relevance of your message obvious.

Honour opt-outs immediately and permanently, keep your list current, and follow the national marketing rules of every country you contact. Do not use this output for bulk unsolicited mail.

FAQ about the Infobel Email Scraper

How many results should I expect from the Infobel Email Scraper? A live Google run returned 10 result blocks, 1 identified account, 1 profile URL and 9 unique emails on default settings. Email density is the strength; identity coverage is the weakness. Volume scales with how many trade keywords, cities and domains you supply, but no specific number is guaranteed because it depends on what Google has indexed.

Why do so many rows have username: null and an empty profileUrl? Because Infobel indexes category and search pages more than company profiles, so most rows carry an email without a resolvable handle. Google prints no company slug on those pages, and the Infobel Email Scraper reports that honestly rather than inventing a link.

Is that an Infobel Email Scraper bug worth reporting? No. It is a Google indexing characteristic of this platform. If you need a resolvable company page on nearly every row, Fyple Email Scraper and Cybo Email Scraper are better suited.

Does the Infobel Email Scraper log into Infobel or use its API? No. It builds Google site:infobel.com queries, fetches result pages through the Apify GOOGLE_SERP proxy and parses them. There is no browser, no login, no API and no cookies.

Should I use non-English keywords with the Infobel Email Scraper? Yes, whenever you target a non-English market. Infobel is genuinely multilingual, so plombier, Klempner or fontanero reaches listings that plumber never surfaces.

What is the fastest way to increase Infobel Email Scraper yield? Set a specific city in location and use precise trade names. Adding national webmail domains such as @skynet.be, @orange.fr or @web.de to customDomains helps as well.

How do I qualify an Infobel Email Scraper lead when there is no profile URL? Use url, title and description. A city-and-trade category page still tells you the trade and the town, which is usually enough for local outreach.

Why does the Infobel Email Scraper turn expandQueries on by default? Google caps one query at roughly 300 results. Expansion runs base, quoted and intitle: variants plus one per modifier, reaching listing pages a single query cannot. Base queries always run first.

Can I run the Infobel Email Scraper on a free Apify plan? Yes, though the 100-email cap on free plans binds quickly here because email density is high. Paid plans are uncapped.

What happens if an Infobel Email Scraper run is interrupted? State is saved in the key-value store, keyed by a hash of your input, and written on Apify's PERSIST_STATE, MIGRATING and ABORTING events. Restarting with the same input resumes rather than starting over.

Which export formats does the Infobel Email Scraper support? Anything the Apify dataset supports - CSV, JSON, Excel and XML - plus the API for pushing rows straight into a CRM.

Is the Infobel Email Scraper affiliated with Infobel? No. It is an independent Actor that reads publicly indexed Google results, with no relationship to or endorsement from the platform.

Related Actors

More email scrapers from the same Business & Professional Directories family, built on the same Google SERP pipeline.

Actor	What it collects
Infobel Email and Phone Number Scraper	Emails and phone numbers from Infobel
Infobel Phone Number Scraper	Public phone numbers from Infobel
Angi Email Scraper	Public contact emails from Angi
Bark Email Scraper	Public contact emails from Bark
Better Business Bureau Email Scraper	Public contact emails from Better Business Bureau
Bizapedia Email Scraper	Public contact emails from Bizapedia
Brownbook Email Scraper	Public contact emails from Brownbook
Callupcontact Email Scraper	Public contact emails from CallUpContact
Capterra Email Scraper	Public contact emails from Capterra
Clutch Email Scraper	Public contact emails from Clutch
Crunchbase Email Scraper	Public contact emails from Crunchbase
Cybo Email Scraper	Public contact emails from Cybo
Cylex Email Scraper	Public contact emails from Cylex
EC21 Email Scraper	Public contact emails from EC21
Europages Email Scraper	Public contact emails from Europages
ExportHub Email Scraper	Public contact emails from ExportHub
FindUsLocal Email Scraper	Public contact emails from FindUsLocal
Foursquare Email Scraper	Public contact emails from Foursquare
Fyple Email Scraper	Public contact emails from Fyple
G2 Email Scraper	Public contact emails from G2
Hotfrog Email Scraper	Public contact emails from Hotfrog
Houzz Email Scraper	Public contact emails from Houzz
Kompass Email Scraper	Public contact emails from Kompass
Lacartes Email Scraper	Public contact emails from Lacartes
Manta Email Scraper	Public contact emails from Manta
MapQuest Email Scraper	Public contact emails from MapQuest
N49 Email Scraper	Public contact emails from N49
Porch Email Scraper	Public contact emails from Porch
Scoot Email Scraper	Public contact emails from Scoot
Thomasnet Email Scraper	Public contact emails from Thomasnet
Thumbtack Email Scraper	Public contact emails from Thumbtack
Touch Local Email Scraper	Public contact emails from Touch Local
TradeIndia Email Scraper	Public contact emails from TradeIndia
Trustpilot Email Scraper	Public contact emails from Trustpilot
Tupalo Email Scraper	Public contact emails from Tupalo
Yalwa Email Scraper	Public contact emails from Yalwa
Yellow Pages Email Scraper	Public contact emails from Yellow Pages
Angi Email and Phone Number Scraper	Emails and phone numbers from Angi
Bark Email and Phone Number Scraper	Emails and phone numbers from Bark
Better Business Bureau Email and Phone Number Scraper	Emails and phone numbers from Better Business Bureau
Bizapedia Email and Phone Number Scraper	Emails and phone numbers from Bizapedia
Brownbook Email and Phone Number Scraper	Emails and phone numbers from Brownbook