A Kompass leads scraper for Germany is useful when the job is not "get every company on the internet." The job is usually narrower: take a vetted list of Kompass Germany detail pages, extract consistent company fields, and give researchers, SEO teams, newsrooms, and monitoring analysts a CSV they can inspect. The Kompass Leads Scraper for Germany template is built for that controlled, reviewable workflow.
Use-case frame
When to extract leads from Kompass Germany
Kompass Germany and the global Kompass Business Place are useful discovery surfaces for B2B company and supplier research. Kompass also sells governed business-data paths, including CRM/API integrations and firmographic data products, which are often the cleaner route when the requirement is contracted enrichment.
A scraper fits a different moment. The team already has page URLs, needs a spreadsheet for review, and wants to compare visible company information across a small or medium batch. That could be a market map of precision manufacturing firms, a sourcing shortlist for a Germany supplier article, an SEO audit of directory profiles, or a monitoring file for company website changes.
The useful question is not "Can we scrape Kompass?" It is "Which visible fields do we need, why are we allowed to collect them, and what decision will this CSV support?"
Personas
Who uses Kompass lead exports?
| Persona | Research pain | CSV outcome |
|---|---|---|
| Market researchers | German supplier lists are scattered across browser tabs, notes, and screenshots. | One row per company with identity, website, source URL, and description fields for sorting. |
| Newsrooms | Reporters need a dated evidence file before naming companies or suppliers in a story. | A reviewable export that preserves the input URL beside every extracted company row. |
| SEO teams | Directory profile audits need structured checks, not manual copy-paste from each page. | Website, company name, Kompass ID, description, and membership signals in a repeatable sheet. |
| Monitoring analysts | Watchlists need periodic checks for changes in contact details or company descriptions. | Re-runnable CSV exports that can be compared across collection dates. |
| Sales operations | Lead research needs cleanup before it becomes CRM data. | A raw research file for qualification, deduplication, compliance checks, and manual review. |
Germany is a large and structured B2B market, and official sources such as Destatis enterprise statistics and Eurostat business demography are better for market sizing than a directory export. A Kompass scraper is more tactical: it helps you inspect specific companies and preserve what was visible at the page level.
Workflow
How the template turns pain into a structured export
The template uses a multi-URL detail-page loop. It sets the browser size, navigates through a list of Kompass Germany company URLs, waits for page load, pauses for dynamic content, tries a light contact reveal interaction, then runs Structured Export in append mode. Loop Continue moves to the next URL.
Set Window Size -> Navigate -> Wait for Page Load -> Sleep
-> Inject JavaScript -> Sleep -> Structured Export -> Loop Continue
That design matters because the workflow is intentionally not a broad directory crawler. It is a controlled extractor for page URLs your team supplies. The bundle has no CSV sample, so the JSON export definition is the authority for the intended output shape.
kompass-leads-scraper.csvColumn
Name_des_Unternehmens
Company name from structured data, a company-name selector, or the page heading.
Column
Adresse
Street, postal code, locality, and region when visible.
Column
Land
Country from schema, visible country fields, or page text.
Column
Fax
Visible fax link or fax-like text.
Column
Offizielle_Website
Official company website, excluding Kompass and challenge domains.
Column
Kompass_ID
Identifier parsed from the URL or page text.
Column
Telefon
Visible telephone link or telephone-like text.
Column
Firmenkurzbeschreibung
Short company description or activity summary.
Column
Input_url
The exact detail-page URL processed by the run.
Examples
Four concrete Kompass scraping workflows
Research: German supplier shortlist
A researcher starts with 40 Kompass company detail URLs for suppliers in a niche manufacturing category. The export gives them names, websites, addresses, phone fields, descriptions, and source URLs in one CSV. They can then tag companies by region, remove duplicates by Kompass_ID, and hand a smaller verified shortlist to the sourcing team.
Newsroom: company evidence file
A newsroom investigating a supply chain does not need an automated lead engine. It needs a dated worksheet that preserves the source page for editorial review. The scraper creates the first pass, then journalists verify any claim manually, archive screenshots where appropriate, and separate public company facts from personal data or contact-use decisions.
SEO: directory profile audit
An SEO agency can use a Kompass export to review whether client or competitor profiles show consistent company names, official websites, descriptions, and membership signals. This is not rank tracking. It is directory-profile QA with a cleaner audit trail than screenshots alone.
Monitoring: watchlist refresh
A monitoring analyst can run the same approved URL list periodically and compare CSV snapshots. The important fields are not only phone and website. Input_url, Kompass_ID, and description text make it easier to identify page drift, profile changes, and rows that failed because of access or selector changes.
Guardrails
Responsible use before the CSV becomes leads
Kompass publishes terms of use, and responsible scraping should also account for robots guidance, access controls, database rights, privacy law, and direct-marketing rules. Google's robots.txt guidance is a useful technical baseline for crawler behavior, while CNIL guidance on legitimate interest and web scraping and EDPB guidance on legitimate interest are useful privacy checkpoints for EU data work.
| Check | Practical rule |
|---|---|
| Source permission | Use approved URLs and stop when consent, login, CAPTCHA, or challenge screens appear. |
| Data minimization | Export only fields needed for the stated research, monitoring, SEO, or sourcing task. |
| Validation | Compare the first rows against the browser before trusting the file. |
| Reuse | Do not import rows into sales tools until legal basis, suppression, and outreach rules are reviewed. |
Tool choice
When UScraper is the right Kompass scraper
UScraper is a good fit when the deliverable is a local CSV, the URL list is known, and a non-engineer needs to inspect the workflow. It is less suitable when you need scheduled cloud runs, dataset APIs, managed proxy infrastructure, or a vendor-backed data contract.
| Option | Use when | Tradeoff |
|---|---|---|
| UScraper template | You need an inspectable local desktop app workflow and a reviewable CSV. | You own validation and selector maintenance. |
| Kompass CRM/API route | You need licensed enrichment, CRM sync, or production data rights. | Requires vendor evaluation, agreement, and integration. |
| Hosted scraper tools | You need schedules, APIs, cloud datasets, or shared workspaces. | Data custody, pricing, and debugging differ from local export. |
For implementation steps, read the Kompass Germany scraper tutorial. For tool selection, compare the Kompass leads scraper alternatives. The broader UScraper template library and UScraper blog cover adjacent directory, search, and lead research workflows.
FAQ
FAQ
Use it when a research, SEO, newsroom, sourcing, or monitoring team has approved Kompass detail-page URLs and needs a reviewable CSV with company identity, contact, website, description, and source URL fields.
Next step
Build the review file
If your use case is a controlled Germany lead list, start with the Kompass Leads Scraper for Germany template, replace the sample URLs with approved targets, run a small validation batch, and only then decide whether the CSV belongs in research, monitoring, SEO QA, or a governed sales workflow.