This Kompass scraper tutorial shows how to turn approved Kompass Recherche detail URLs into a local CSV export with the Kompass Recherche Scraper for Company Data Export. You will prepare inputs, import the workflow, set the export path, run a small validation batch, and read the output before scaling.
Before you start
Prerequisites for a Kompass Recherche scraper
You need the UScraper local desktop app, the Kompass Recherche Scraper template, a folder for CSV exports, and a short list of Kompass company detail URLs your team is allowed to process. This workflow is not a broad crawler. It is best for known detail pages where one source URL should become one company row.
Prepare a small input list before importing the template. Include the Kompass URL, market, owner, and reason for collection so each exported row has an audit trail.
Automation is a collection method, not permission. Review the current Kompass terms of use, robots guidance, database-rights risk, privacy obligations, and your internal data policy before using exported rows commercially.
Workflow
How the Kompass Recherche Scraper works
The JSON export is the authoritative workflow definition. The graph follows a simple supervised path: set the browser size, open a supplied URL, wait for page load, check for known challenge assets, wait for the body when the page is accessible, sleep briefly so dynamic content can settle, export structured fields, then continue to the next URL.
Set Window Size -> Navigate -> Wait for Page Load -> DataDome check
-> if challenged: Structured Export with blocked/sample handling
-> if accessible: Wait for body -> Sleep -> Structured Export
-> Loop Continue
The template includes defensive logic because Kompass pages can vary by country, profile completeness, session state, and access prompts. Accessible pages are read from the live DOM. If the bundled TotalEnergies sample page is blocked, the workflow uses preview-style fallback values so the first test is not empty. For your own URLs, treat blocked-page messages as a signal to pause and review access.
kompass-recherche-scraper.csvColumn
nom_de_l_entreprise
Company name from headings, company-name selectors, or cleaned page title fallback.
Column
lieu
Location text such as city and country when visible on the profile.
Column
presentation
Company presentation text or a blocked-session note when the page is not accessible.
Column
fournisseur
Supplier category, activity label, products, services, or sector text.
Column
telephone
Visible phone number from tel links or matching page text.
Column
site_de_l_entreprise
External company website, excluding Kompass and challenge domains.
Column
url_de_la_page_detaillee
The exact Kompass detail URL visited by the workflow.
Runbook
How to scrape Kompass Recherche detail URLs to CSV
Prepare source URLs
Build a short list of approved Kompass France company detail pages. Open several manually and confirm that normal company content appears in the same browser session you plan to automate.
Import the template
Open the Kompass Recherche Scraper template, download the JSON workflow, and import it into UScraper.
Replace the Navigate list
In the Navigate block, replace the bundled sample URL with your source URLs. Keep the wait, challenge-check, and loop blocks unchanged for the first run.
Confirm the export path
In Structured Export, set a project-specific save folder, keep headers enabled, and keep append mode if you want one combined CSV for all detail URLs.
Run and validate
Run a small batch, compare every column against the live profile, then increase the URL list only after company names, URLs, phones, and website fields look clean.
Append mode puts every visited URL in one file, but it can mix test and production rows. Before a real run, clear the previous CSV or use a dated folder such as kompass-recherche-2026-06-25.
Validation
Validate the Kompass CSV before using it
The first pass should answer one question: does each row mean what the column says it means? Open the CSV beside the live Kompass pages before importing it into a CRM, enrichment workflow, or research workbook.
| Check | What to inspect | Why it matters |
|---|---|---|
| Source page | url_de_la_page_detaillee opens the expected Kompass profile | Keeps every row auditable. |
| Company name | nom_de_l_entreprise is the company, not a navigation label | Heading selectors can drift when layouts change. |
| Location | lieu matches the visible city or country context | Mixed country pages can format addresses differently. |
| Presentation | presentation contains company copy, not CAPTCHA or cookie text | Block pages and consent pages can pollute exports. |
| Activity | fournisseur captures supplier, activity, or services text | This field is useful for segmentation and dedupe. |
| Contact fields | telephone and site_de_l_entreprise appear only when visible | Blank cells are normal when the profile does not expose contact data. |
If Kompass returns a challenge page, do not build around bypassing it. Reduce volume, use a smaller approved list, solve legitimate manual access steps in the visible browser, or move to an approved data agreement when the project needs guaranteed access.
Alternatives
Kompass scraper alternative choices
There is no single best Kompass scraper for every workflow. Octoparse publishes Kompass templates, Apify actors can fit hosted runs and API calls, and managed services can deliver finished datasets. Kompass France also offers official web-service access for teams that need contracted database access and integration.
UScraper is a different fit: supervised local desktop extraction where you can inspect blocks, keep the CSV on your machine, and validate rows yourself. That makes sense for supplier shortlists, market research, B2B list cleanup, and company profiling.
| Approach | Good fit | Tradeoff |
|---|---|---|
| UScraper local desktop app | Approved detail URL lists, local CSV review, visible no-code workflow | You own URL quality, pacing, selector maintenance, and compliance review. |
| Octoparse Kompass template | Users who prefer a hosted no-code template catalog | Platform pricing, run mode, and export behavior depend on the vendor. |
| Apify actor or API workflow | Developers who want hosted execution and programmatic runs | Inputs and outputs are handled in a cloud actor environment. |
| Official Kompass web service | Contracted access, CRM integration, and agreed data rights | Requires a commercial route and technical integration planning. |
| Manual copy-paste | Tiny one-off checks | Slow, inconsistent, and hard to audit. |
Troubleshooting
Common Kompass scraping issues
| Symptom | Likely cause | Fix |
|---|---|---|
| A row says blocked by DataDome | The session saw challenge assets | Pause, reduce pace, review access, and rerun a smaller batch. |
| Company name is blank | Heading selectors or metadata changed | Inspect the current page and update the nom_de_l_entreprise JavaScript column. |
| Phone is empty | The field is hidden, absent, or not exposed to the session | Treat it as optional unless the live profile clearly shows it. |
| Website points to the wrong domain | A generic link was selected before the company website | Update the website selector to exclude navigation, Kompass, and challenge domains. |
| Old and new rows are mixed | Append mode reused an existing CSV | Clear the file or use a dated export folder before production runs. |
Keep a simple run log: source URL list, run date, Kompass country domain, export filename, selector edits, and any access notes. That audit trail saves time when you rerun the same research later.
FAQ
Kompass Recherche scraper FAQ
Kompass pages may include publicly visible B2B information, but automated access can still be limited by terms of use, robots guidance, database rights, privacy rules, and local law. Use approved URLs, avoid bypassing access controls, keep runs modest, and get legal review before commercial reuse.
Next step
Download the Kompass Recherche Scraper template
Use Kompass Recherche Scraper for Company Data Export as the download path, then keep this tutorial open while you validate your first CSV. For adjacent workflows, browse the UScraper template library or return to the UScraper blog for more scraping tutorials and comparison guides.