A Kompass data scraper is useful when the job is not "find one supplier" but "turn selected Kompass business directory pages into rows a team can inspect, filter, and rerun." The Kompass Data Scraper exports product and supplier detail pages to CSV for research, newsrooms, SEO, sourcing, and monitoring workflows.
CSV
5
Detail URLs
Multi-URL
Local QA
Problem
Why Kompass research turns into spreadsheet work
Kompass Business Place is built around B2B company and partner discovery, and the independent globalEDGE resource profile lists Kompass as a business-to-business company search resource. That makes it a natural starting point for supplier discovery, category mapping, sourcing research, and market monitoring.
The browser experience is useful for exploration. It becomes inefficient when five people need the same evidence in one shared worksheet. Tabs do not preserve a field map. Screenshots do not sort by supplier. Copy-paste makes it hard to tell whether a phone number was blank on the page, hidden from the session, or missed by the researcher.
The real use case is controlled B2B directory research: pick the Kompass pages you are allowed to inspect, export the visible fields, and validate the CSV before anyone treats it as a business record.
Searches like how to scrape Kompass, scrape Kompass business directory, and Kompass to CSV usually point to that operational problem. The data is useful because it is structured. The manual process is painful because it is not.
Personas
Who uses a Kompass data scraper?
| Persona | Pain | CSV outcome |
|---|---|---|
| Market researchers | Supplier pages are useful, but manual comparison is slow and inconsistent. | Build a reviewable table of supplier names, product titles, descriptions, URLs, and visible phones. |
| Newsrooms | Reporting on suppliers, industries, or regional business activity needs traceable source links. | Keep each row tied to a source URL so reporters can re-open and verify details before publication. |
| SEO teams | B2B category briefs need entity names, product language, and source URLs. | Extract titles and descriptions for competitor, entity, and content-gap analysis. |
| Sourcing teams | Supplier discovery starts with too many tabs and uneven notes. | Create a first-pass shortlist before manual qualification, procurement review, or approved outreach. |
| Monitoring teams | Rechecking the same pages by hand creates inconsistent snapshots. | Rerun the same selected URLs and compare visible title, supplier, description, or phone changes over time. |
Workflow
How the template delivers structured export
The JSON export is the source of truth for this workflow. It uses a multi-URL loop: navigate to each supplied Kompass product or detail URL, wait for the page, pause briefly for dynamic content, confirm the body exists, export structured fields, and continue to the next URL.
Navigate -> Wait for Page Load -> Sleep -> Wait for Element
-> Structured Export -> Loop Continue
The Structured Export block appends one row per URL into kompass_scraper.csv. The selectors first try live page DOM fields such as headings, product descriptions, supplier links, telephone elements, and metadata. The bundled workflow also includes fallback logic for the provided sample URLs and slug-based parsing for other Kompass product URLs. That fallback is useful for testing the template shape, but live research still needs browser validation.
{
"fileName": "kompass_scraper.csv",
"fileMode": "append",
"includeHeaders": true,
"rowSelector": "body",
"columns": [
"titre",
"nom_fournisseurs",
"description",
"page_url",
"telephone"
]
}
kompass_scraper.csvColumn
titre
Product or detail-page title from the visible Kompass page, with slug fallback when needed.
Column
nom_fournisseurs
Supplier or company name from visible supplier, brand, seller, or company-name selectors.
Column
description
Product or service description from the page, metadata, or approved sample fallback.
Column
page_url
Exact Kompass URL visited, which keeps every exported row auditable.
Column
telephone
Visible phone value when a telephone link, selector, or page-text match is available.
Examples
Concrete Kompass scraper use cases
Build a supplier shortlist
Export selected product or supplier URLs, sort by company name and category context, then manually review the strongest candidates before procurement or outreach.
Map a B2B market segment
Collect a controlled sample of Kompass pages from one sector or region, then compare product language, supplier coverage, and visible contact availability.
Support newsroom research
Keep source URLs next to supplier names and descriptions so editors can verify claims, contact companies, and avoid relying on copied notes alone.
Prepare SEO entity briefs
Use titles, supplier names, and descriptions to identify recurring product terms, competitor entities, and category language for B2B content planning.
Monitor known pages
Rerun the same approved Kompass URL list on a set cadence and compare visible changes in descriptions, phone availability, or supplier page status.
Create review queues
Use the CSV as a seed list, then move only approved rows into CRM review, website checks, enrichment, or adjacent workflows from the template library.
These are not bulk-crawl scenarios. They are analyst-led workflows where a directory search engine becomes a reviewable business search database for a narrow question.
Decision
Local template, Octoparse, Apify, or custom script?
There is no single best Kompass scraper for every team. The right route depends on scale, custody, output shape, and who maintains the workflow.
| Route | Best fit | Trade-off |
|---|---|---|
| Official permissioned access | Licensed reuse, redistribution, enrichment, or governed data products. | Requires the right commercial agreement and scope. |
| Hosted scraper platforms | Scheduled cloud runs, APIs, datasets, and vendor-managed infrastructure. | Browser execution and output pass through a third-party platform. |
| No-code SaaS templates | Quick cloud setup for teams comparing Kompass scraper vs Octoparse-style tools. | Convenient, but pricing, limits, and data custody follow the SaaS model. |
| Custom script | Engineering-owned parsers, tests, queues, storage, and monitoring. | Flexible, but every site change becomes your maintenance work. |
| UScraper template | Local CSV from selected Kompass URLs with visible workflow blocks and row-level QA. | Best for supervised research, not unattended high-volume crawling. |
For a deeper tool comparison, read Kompass Scraper Alternatives: Apify, Octoparse, Scripts, and Local CSV. For setup steps, use How to Scrape Kompass Data to CSV.
Runbook
A repeatable Kompass business directory workflow
- Define the research question: supplier shortlist, newsroom sample, SEO brief, sourcing review, or monitoring snapshot.
- Collect only the Kompass product or supplier detail URLs needed for that question.
- Import the Kompass Data Scraper into UScraper and replace the sample Navigate URLs.
- Confirm the local save folder, filename, headers, and append mode for
kompass_scraper.csv. - Run three to ten URLs first, then compare each row against the browser.
- Remove test rows, fix selector gaps, and expand only after the sample export matches visible source pages.
The key discipline is validation. A row that came from a CAPTCHA page, consent page, stale URL, or hidden field can look structured while still being wrong. Keep the first run small enough that someone can check every field.
FAQ
Kompass data scraper FAQ
Use it when research, newsroom, SEO, sourcing, or monitoring teams need a reviewable CSV from selected Kompass supplier or product detail URLs.
Next step
Download the Kompass data scraper
Use the Kompass Data Scraper when your team has a defined Kompass URL list and needs a local CSV for supplier research, SEO briefs, newsroom checks, sourcing review, or monitoring. For adjacent workflows, browse all UScraper templates or return to the UScraper blog.