Europages Supplier Scraper avatar

Europages Supplier Scraper

Pricing

Pay per event

Go to Apify Store
Europages Supplier Scraper

Europages Supplier Scraper

Extract public Europages supplier leads with company profiles, locations, descriptions, badges, products, and contact entry URLs.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Categories

Share

Extract supplier leads from Europages category and company search result pages.

What This Actor Does

Europages Supplier Scraper collects public B2B supplier listings from Europages.

It is built for lead generation, supplier discovery, market mapping, sourcing research, and competitor monitoring.

The actor reads Europages result pages with HTTP requests and parses the server-rendered HTML plus embedded structured data.

Data Source

The actor targets public Europages pages such as:

https://www.europages.co.uk/companies/electronics.html

It supports category pages, search-result pages, and generated company search URLs from keywords.

Input Sources

You can provide direct URLs.

You can provide search terms.

You can provide category names.

You can combine all three modes in one run.

Start URLs

Use startUrls when you already have Europages URLs.

Example:

[
{ "url": "https://www.europages.co.uk/companies/electronics.html" }
]

Search Terms

Use searchTerms to search for supplier topics.

Example:

["electronics", "metal machining", "industrial packaging"]

The actor converts terms into Europages company search URLs.

Categories

Use categories for category-style scraping.

Example:

["electronics", "industrial machinery"]

Categories are normalized into Europages URL slugs.

Limits

maxItems controls the total number of supplier rows saved.

maxPagesPerSearch controls pagination for each source.

Small test runs should use 5 to 20 items.

Large sourcing exports can increase the limit.

Proxy Settings

Europages can expose WAF and CAPTCHA configuration.

The actor supports Apify Proxy.

Residential proxy is the safest default for challenged runs.

Direct HTTP can work for many small category pages.

Output Fields

Each dataset row represents one supplier listing.

The actor exports:

  • supplier name
  • Europages profile URL
  • source URL
  • source type
  • source value
  • search term or category
  • page number
  • result position
  • city
  • country
  • combined location
  • public description
  • badges
  • supplier types
  • employee count
  • founding year
  • product count
  • sample product names
  • public contact-entry URLs
  • public website URLs when present
  • area served
  • scrape timestamp

Supplier Name

name is the supplier or company name shown by Europages.

The field is normalized for extra whitespace.

Profile URL

profileUrl is the public Europages company profile URL from the result card.

This is useful for deduplication and manual review.

Location

The actor extracts city and country from structured JSON-LD when available.

It also emits a combined location string.

Description

description is the public supplier summary shown on the result page.

Some descriptions are truncated by Europages.

Badges

badges captures visible trust and feature hints.

Examples include certificate hints, verified markers, and manufacturing badges.

Supplier Types

supplierTypes captures visible role tags.

Examples include manufacturer, producer, distributor, service provider, and wholesaler.

Products

productCount captures the visible number of listed products when present.

productNames includes sample product names shown in the result card.

Contact Entry URLs

contactEntryUrls contains public Europages URLs that lead to contact, portfolio, or profile actions.

The actor does not bypass login, forms, or protected contact reveal flows.

Website URLs

websiteUrls contains external website links when they are directly visible in public HTML.

Many Europages cards do not expose an external website link on the search result page.

Pagination

The actor follows the next-page link when it is present.

It stops at maxPagesPerSearch.

It also stops when maxItems is reached.

Deduplication

The actor deduplicates by profileUrl during a run.

If the same supplier appears across multiple sources, only the first occurrence is saved.

Example Input

{
"startUrls": [
{ "url": "https://www.europages.co.uk/companies/electronics.html" }
],
"searchTerms": ["electronics"],
"maxItems": 20,
"maxPagesPerSearch": 1,
"maxRequestRetries": 3,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}

Example Output

{
"name": "Frezamet Bis Sp. z o.o",
"profileUrl": "https://www.europages.co.uk/en/company/frezamet-bis-sp-z-oo-22294309",
"sourceUrl": "https://www.europages.co.uk/companies/electronics.html",
"sourceType": "startUrl",
"sourceValue": "https://www.europages.co.uk/companies/electronics.html",
"positionOnPage": 1,
"pageNumber": 1,
"city": "Orzesze",
"country": "PL",
"location": "Orzesze, PL",
"description": "Frezamet Bis is a Polish company specializing in precision machining of metals and plastics.",
"badges": ["Certificates: 1"],
"supplierTypes": ["Manufacturer/Producer"],
"employeeCount": "20-49",
"productCount": 39,
"productNames": ["Turning on CNC lathes"],
"contactEntryUrls": ["https://www.europages.co.uk/en/company/frezamet-bis-sp-z-oo-22294309"],
"websiteUrls": [],
"areaServed": "europe",
"scrapedAt": "2026-05-15T08:17:25.388Z"
}

Use Cases

Use this actor to build supplier prospect lists.

Use it to compare suppliers across countries.

Use it to collect sourcing candidates for a product category.

Use it to monitor competitor or distributor presence on Europages.

Use it to enrich internal CRM research with public supplier metadata.

Persona Workflows

Sourcing teams can collect candidates for a product category, keep the Europages profile URL as the source of truth, and shortlist suppliers by country, supplier type, employee count, and product count.

B2B sales teams can create focused prospect lists from category pages, export the rows to CSV, and enrich only the companies that match their ideal customer profile.

Procurement analysts can run the same category every week or month, compare scrapedAt timestamps, and detect new or changed supplier listings without manually reviewing every result page.

Market researchers can map how many suppliers appear in a category, which countries dominate the visible listings, and which role tags are common across the market.

Who Is It For

This actor is for sourcing teams, B2B sales teams, procurement analysts, market researchers, distributor managers, and lead-generation operators who need structured supplier lists from public Europages pages.

Use it when you need repeatable exports instead of manually opening category pages, copying supplier names, and preserving source context by hand.

  1. Start with one Europages category URL or one search term.

  2. Set maxItems to 20 and maxPagesPerSearch to 1 for the first validation run.

  3. Inspect the dataset columns you care about: name, profileUrl, country, supplierTypes, productCount, contactEntryUrls, and websiteUrls.

  4. Remove source URLs or terms that produce irrelevant suppliers.

  5. Increase maxPagesPerSearch and maxItems for a production export.

  6. Export the dataset to CSV or Excel for review, or JSON for enrichment.

  7. Use Apify Proxy if direct requests start returning WAF or challenge responses.

Sales Workflow

  1. Enter one category such as electronics or a direct Europages category URL.

  2. Export name, profileUrl, country, supplierTypes, productCount, and websiteUrls.

  3. Remove suppliers that do not match your territory or product focus.

  4. Send the remaining profiles to a website-contact or CRM enrichment workflow.

  5. Keep sourceValue, pageNumber, and positionOnPage so each lead can be traced back to the original Europages result.

Procurement Workflow

  1. Create one run per category, product family, or sourcing region.

  2. Use country, employeeCount, supplierTypes, and productNames to shortlist candidates.

  3. Review the public Europages profile before contacting a supplier.

  4. Schedule refreshes for key categories and compare exports over time.

  5. Use scrapedAt to separate new supplier research from older sourcing snapshots.

Market Mapping Workflow

  1. Run several related categories with a shared maxItems limit.

  2. Group exported rows by country, supplierTypes, and sourceValue.

  3. Compare product counts and badge fields to identify mature supplier clusters.

  4. Review duplicates by profileUrl to see which companies appear across multiple categories.

  5. Feed the dataset into BI tools or spreadsheets for category-level reporting.

Data Freshness

Rows reflect the public Europages page at run time.

The actor includes scrapedAt so you can track when a row was collected.

Respectful Scraping

The actor uses HTTP requests and conservative pagination.

Keep limits aligned with your business need.

Avoid repeated large runs over the same category when a smaller refresh is enough.

Limitations

Europages may hide some contact details behind interactive flows.

The actor only exports publicly available URLs and text found in the initial HTML.

Some result cards do not contain external websites.

Some descriptions are truncated by Europages.

Upstream page layout changes can affect selectors.

Troubleshooting

If output is empty, check that the URL is a Europages company search or category page.

If the run fails with a challenge message, enable Apify Proxy.

If pagination stops early, raise maxPagesPerSearch.

If you see repeated suppliers, lower overlapping input sources or rely on profileUrl deduplication.

Cost Control

Every saved supplier result is charged as a result event.

Use small limits for tests.

Raise limits only after confirming that the source returns the fields you need.

How much does it cost to scrape Europages supplier leads?

This actor uses pay-per-event pricing. Each run has a small start event and each saved supplier row is charged as a result event.

Current configured BRONZE pricing is:

EventWhen it is chargedPrice
Run startedOnce per run$0.005
Result extractedEach saved supplier row$0.00014896

Example estimates at BRONZE rates:

Run sizeEstimated actor charge
20 supplier rowsAbout $0.0080
100 supplier rowsAbout $0.0199
1,000 supplier rowsAbout $0.1540

If you are testing with a $5 monthly platform credit, these event prices are low enough for thousands of small validation rows before normal Apify platform usage costs are considered. Actual total spend depends on your account plan, proxy usage, and run volume.

Use maxItems and maxPagesPerSearch to control spend before scaling to larger exports.

Dataset Export

The default dataset can be exported as JSON, CSV, Excel, XML, or RSS through Apify.

Use CSV or Excel for sales workflows.

Use JSON for enrichment pipelines.

Integration Ideas

Send exported rows to a CRM.

Join profileUrl against existing supplier records.

Filter by country and supplier type.

Use productNames to identify relevant supplier capabilities.

Use badges and employeeCount to prioritize outreach.

Integration Workflows

CRM teams can export CSV rows and import name, profileUrl, country, supplierTypes, and websiteUrls as new lead records.

Data teams can call the actor through the Apify API, read the default dataset, and push JSON rows into a warehouse or enrichment queue.

Automation teams can schedule weekly category runs, then trigger downstream workflows only when new profileUrl values appear.

AI-agent workflows can call the actor through Apify MCP and ask the model to summarize suppliers by country, product focus, or supplier type.

API Usage

Use the Apify API when you want to run the actor from scripts, scheduled jobs, enrichment workflows, or backend services.

Node.js example:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/europages-supplier-scraper').call({
startUrls: [{ url: 'https://www.europages.co.uk/companies/electronics.html' }],
maxItems: 20,
maxPagesPerSearch: 1,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python example:

from apify_client import ApifyClient
import os
client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("automation-lab/europages-supplier-scraper").call(
run_input={
"startUrls": [{"url": "https://www.europages.co.uk/companies/electronics.html"}],
"maxItems": 20,
"maxPagesPerSearch": 1,
}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

cURL example:

curl "https://api.apify.com/v2/acts/automation-lab~europages-supplier-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"startUrls": [{"url": "https://www.europages.co.uk/companies/electronics.html"}],
"maxItems": 20,
"maxPagesPerSearch": 1
}'

MCP

Use this actor through Apify MCP when an assistant needs supplier leads as structured data. The hosted Apify MCP endpoint uses HTTP transport at https://mcp.apify.com, and the actor can be exposed as a tool with the tools query parameter.

Keep inputs narrow for interactive workflows, then increase limits for scheduled sourcing jobs.

Claude CLI setup example:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/europages-supplier-scraper"

Claude Desktop or Cursor JSON configuration:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=automation-lab/europages-supplier-scraper",
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}

VS Code MCP JSON configuration:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=automation-lab/europages-supplier-scraper",
"headers": {
"Authorization": "Bearer ${input:apify-token}"
}
}
}
}

Example prompts:

  • "Find up to 20 electronics suppliers from Europages and return their names, countries, profile URLs, and supplier types."
  • "Scrape the Europages industrial machinery category and summarize which suppliers mention CNC or machining."
  • "Create a supplier lead table from this Europages category URL and include the source URL for each result."

Legality

This actor extracts public information from Europages pages.

You are responsible for using the output in line with applicable laws, platform terms, privacy rules, and your own outreach obligations.

The actor does not bypass authentication, paywalls, form protections, or private contact reveal flows.

Related supplier and lead-generation workflows from automation-lab:

Combine this dataset with enrichment actors when you need extra company websites, emails, or firmographic fields that are not visible on Europages result pages.

Field Notes

sourceType tells you which input mode produced the row.

sourceValue keeps the original category, term, or URL context.

pageNumber and positionOnPage preserve pagination metadata.

areaServed comes from structured data when Europages publishes it.

Support

If a valid Europages URL returns no results, include the input and run URL when reporting the issue.

If a field is missing for a supplier, verify that Europages shows that field publicly in the result card.

FAQ

Can it scrape every contact detail from Europages?

No. It exports public text and URLs visible in the initial HTML, not protected contact details hidden behind interactive flows.

Why are some website URLs empty?

Many Europages result cards do not expose an external website link. In those cases the actor keeps the public Europages profile URL.

Can I scrape multiple categories in one run?

Yes. Provide several startUrls, searchTerms, or categories; the actor deduplicates suppliers by profileUrl during the run.