Europages Scraper

Turn Europages (europages.com) into a clean, ready‑to‑use B2B supplier lead list.

This actor is built to help agencies and sales teams turn Europages search results into usable lead data — without fighting pagination limits, inconsistent exports, or brittle scrapers.

---

🚀 Built for agencies

This scraper focuses on what agencies actually need: clean company rows, predictable structure, and data that drops straight into outreach workflows.

• One company = one row Results are deduplicated at company level using Europages’ stable company identifiers, so you get a clean dataset — no manual cleanup required.

• Outreach‑ready data Emails, phone numbers, websites, locations, company size, certificates, and response signals — flattened for Excel, Google Sheets, or direct CRM imports.

• What they actually sell Product names, keywords, and structured portfolio entries make it easy to segment leads and personalize outreach without additional research.

• Scales beyond Europages’ UI limits An optional experimental partitioning mode allows broader searches when Europages’ page limit gets in the way.

• Built for unattended runs Rate‑limited, resilient, and designed to run reliably on large queries.

• Clean exports by default Works out of the box with CSV, Excel, JSON, and Apify’s table view.

---

🎯 Typical use cases

• B2B Lead Generation – Build supplier lists by industry, country, and size
• Procurement Research – Identify and compare manufacturers and vendors
• Market Mapping – Understand competitive landscapes in specific niches
• Sales Ops / CRM Enrichment – Add verified contact and portfolio data
• Automation Agencies – Feed Europages data directly into enrichment or outreach pipelines

---

⚙️ Input

Parameter	Type	Default	Description
query	string	—	Search term you’d type on Europages (required).
region	string	—	Country filter (alpha‑2, e.g. DE, FR, IT).
verifiedOnly	boolean	false	Include only verified Europages companies.
maxPages	number	—	Max number of result pages to scrape (Europages hard‑limit ≈ 100).
enableExperimentalPartitioning	boolean	false	Attempts to exceed Europages’ page limit. Advanced / experimental.

Example:

{
  "query": "CNC machining",
  "region": "DE",
  "verifiedOnly": false
}

---

📦 Output: built for spreadsheets & CRMs

Each dataset row represents one unique company with flattened, spreadsheet‑friendly fields.

⭐ Recommended columns for outreach

If you just want leads, these columns are usually sufficient:

• name
• website
• email
• phone
• address_countryCode
• address_city
• tags_employeeCount
• tags_supplierTypes
• portfolio_productNames
• portfolio_productKeywords

For a complete, field‑by‑field description of all available properties, see the Detailed output schema section below.

---

🔍 About result counts

Europages sometimes displays approximate totals in its UI.

This actor returns canonical companies, deduplicated by Europages’ internal company ID. As a result, your final dataset may contain fewer rows than the UI estimate — but no duplicated companies.

This ensures the dataset represents unique suppliers rather than repeated listings.

---

🧪 Experimental partitioning (advanced)

Europages enforces a hard limit of 100 pages per search (roughly equal to 3000 results).

When enableExperimentalPartitioning is enabled, the actor attempts to split the search space using Europages’ own filters (region, supplier type, company size) to collect larger datasets.

• May issue significantly more requests
• May generate overlapping queries
• Overlaps are automatically deduplicated

Recommended only for broad searches.

---

🛡️ Reliability & maintenance

• Automatic retries and rate limiting
• Schema‑validated output
• Continues scraping even if some fields are missing or change shape

If Europages changes their structure, just re‑run and attach the log — fixes are rolled out quickly.

---

📘 Detailed output schema

Below is a high‑level explanation of the available output fields. All fields are optional unless stated otherwise.

Source & identifiers

• source – Always "europages"
• source_companyId – Stable Europages company ID (primary deduplication key)
• source_listingId – Listing‑level identifier (if available)
• source_epId, source_epSlug, source_uuid, source_slug – Europages internal references for traceability

Core company identity

• name – Official company name
• shortName – Shortened or alternative company name (if available)
• description – Company profile description
• logoUrl – Company logo URL

Location & geography

• address – Full formatted address
• address_street, address_postalCode, address_city, address_countryCode – Parsed address components
• geo_latitude, geo_longitude – Geographic coordinates (if available)

Contact channels

• website – Company website
• email – Public contact email
• phone – Public contact phone number

Business classification & filters

These fields are especially useful for segmentation and prioritization.

• tags_supplierTypes – Supplier / business type labels
• tags_employeeCount – Employee count range (as shown on Europages)
• tags_distributionArea – Distribution or service area

Trust & quality signals

Helpful for lead scoring and prioritization.

• signals_isCustomer – Indicates Europages customer status
• signals_certificatesCount – Number of certificates
• signals_responseRate – Response rate percentage
• signals_averageResponseTime – Typical response time
• signals_foundingYear – Year the company was founded
• signals_packageName – Europages package / tier

Portfolio summary

• portfolio_productCount – Number of listed products
• portfolio_productNames – Flattened list of product names
• portfolio_productKeywords – Aggregated product keywords

Portfolio products (structured)

Each entry in portfolio_products may contain:

• name – Product name
• description – Product description
• keywords – Associated keywords
• flags_isMatching – Matches the current search query
• flags_isShowcased – Highlighted product
• imageUrls – Product images with optional captions

Media

• media – Images or media assets with title and description

Metadata

• meta.scrapedAt – Timestamp of the scrape
• meta.query – Search query used for this run

---

💬 Support

Questions, edge cases, or feature requests?

Open a support ticket or attach a failing run log — we’ll take care of it.