This tutorial shows how to scrape WLW.de supplier leads from approved company detail URLs into CSV with the WLW.de Lead Scraper template for UScraper. You will import the workflow, add supplier URLs, set the export path, and validate contact fields before scaling.
CSV
12
URLs
wlw.de
Local
Before you start
Prerequisites and WLW.de policy checks
You need UScraper installed as a local desktop app, a short list of WLW.de company detail URLs you are allowed to process, and a folder where CSV files can be written. Start with five URLs so you can prove that pages load, reveal buttons work, and each supplier creates one clean row.
WLW.de is a B2B marketplace for finding suppliers, products, and services. Its buyer help explains supplier and product search, which is useful when you move selected company detail pages into the scraper. Before automation, review the current WLW.de terms of use and robots.txt. Public visibility does not automatically mean unrestricted automated collection.
Compliance rule: scrape only pages you are permitted to access, avoid login-only data, do not bypass access controls, keep request rates modest, and document why the supplier dataset is being collected.
Workflow anatomy
What the WLW.de lead scraper workflow does
The JSON workflow is direct: Navigate -> Wait for Page Load -> accept common cookie prompts -> Wait for Element -> reveal contact buttons -> Structured Export -> Loop Continue. Navigate owns the input URLs. The reveal step clicks visible phone, website, email, or contact buttons. Structured Export reads the rendered browser state and writes the CSV.
| Workflow block | Purpose | What to verify |
|---|---|---|
| Navigate | Opens each WLW.de company detail URL | Replace sample URLs with approved supplier pages. |
| Wait for Page Load | Gives the page time to render | Keep this before any extraction or reveal step. |
| Consent click | Handles common cookie buttons | Confirm the page is visible after the first run. |
| Wait for Element | Waits for the company heading | Empty names usually mean this step failed. |
| Reveal contact buttons | Opens available website, phone, or email fields | If contact cells are blank, inspect this step first. |
| Structured Export | Appends supplier fields to CSV | Confirm filename, save folder, headers, and append mode. |
Runbook
How to scrape WLW supplier data to CSV
Import the template
Open WLW.de Lead Scraper, download the JSON workflow, and import it into UScraper.
Add company detail URLs
Replace the Navigate sample URLs with approved WLW.de /de/firma/ pages. Keep your first list small so QA is fast.
Check prompts and page load
Run one URL and watch the browser. Handle consent, verification, or language prompts before trusting the first CSV row.
Set the export path
In Structured Export, confirm wlw_de_lead_scraper_final.csv, headers, append mode, and a project-specific save folder.
Validate before batching
Compare the CSV against the source page, fix blank or shifted fields, then run the remaining URLs in modest batches.
WLW.de profiles vary. Some companies publish a website but no email, some require a reveal click, and some pages expose only a short overview. Validate what is visible on the page.
Output
CSV fields from the WLW data extractor
No sample CSV was included in the bundle, so the preview below mirrors the authoritative JSON export shape. The workflow writes one row per company detail URL and includes headers in append mode.
wlw_de_lead_scraper_final.csvColumn
seite_url
Current WLW.de company detail URL.
Column
name_der_firma
Company name from the page heading.
Column
standort
Parsed location and country from visible profile text.
Column
firmenueberblick
Company overview text or meta description fallback.
Column
ob_verifiziert
Verified badge indicator when present.
Column
lieferung
Delivery area such as regional, national, Europe-wide, or worldwide.
Column
gruendungsjahr
Founding year when visible or known from sample pages.
Column
mitarbeiteranzahl
Employee count or range when available.
Column
lieferantentyp
Supplier type such as manufacturer, wholesaler, or service provider.
Column
offizielle_webseite
Official company domain after filtering tracking and social domains.
Column
telefonnummer
Phone number from tel links or visible contact text.
Column
Email address from mailto links or visible text when available.
Sample rows
1 of many
| seite_url | name_der_firma | standort | firmenueberblick | ob_verifiziert | lieferung | gruendungsjahr | mitarbeiteranzahl | lieferantentyp | offizielle_webseite | telefonnummer | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Example Supplier GmbH | Hamburg, Deutschland | Industrial supplier overview | check | National | 1998 | 50-99 | Hersteller | example-supplier.de | +49401234567 |
Troubleshooting
Common issues when exporting WLW.de leads
| Symptom | Likely cause | Fix |
|---|---|---|
Empty name_der_firma | The page did not reach a visible heading state | Extend waits, handle prompts, and rerun the URL. |
| Blank website, phone, or email | Field is not visible, was not revealed, or is not published | Check the page manually and update the reveal button pattern if needed. |
| Wrong website domain | A tracking, social, or WLW-owned URL was picked up | Tighten the domain filter in the website column. |
| Duplicate rows | The same URL appears twice or the loop resumed after export | Deduplicate the input list and clear test rows before the final run. |
| Mixed languages in output | Source pages rendered with different locale text | Use a consistent browser locale and validate regex-based columns. |
Guardrails for supplier lead scraping
Review rules before reuse
Check WLW.de terms, robots guidance, privacy law, and outreach rules before resale, redistribution, enrichment at scale, or automated contacting.
Keep batches modest
Avoid aggressive repeated runs. Slow down if page load times climb, prompts appear, or contact reveal buttons stop responding.
Expect selector maintenance
Marketplace layouts change. If exports become empty, rerun a small browser test and adjust Structured Export columns before scaling.
Alternatives
Best WLW scraping tools and when to use each
The best WLW scraping tools depend on how you want to run the job. UScraper fits supervised local exports, visible browser QA, and editable no-code workflows. Hosted actors on platforms such as Apify or Bright Data can make sense for managed infrastructure, API scheduling, or larger cloud queues. Octoparse-style templates are useful for teams already standardized there. Browser extensions can be convenient for one-off extraction, but they are harder to audit across repeatable supplier research projects.
If you are looking for a WLW scraper alternative, decide on custody and repeatability first. A local desktop app keeps the workflow and CSV close to the analyst who validates the rows. A hosted service may be easier to schedule, but it usually adds vendor storage, usage pricing, and another place where lead data passes through.
FAQ
WLW.de lead scraper FAQ
WLW.de company profiles may be visible in a browser, but automated collection can still be limited by source terms, robots guidance, database rights, privacy law, and outreach rules. Review the current WLW.de terms and robots file, use modest pacing, avoid private or login-only data, and get legal review before resale or large-scale enrichment.
Next step
Download the WLW.de lead scraper template
When you are ready to run the tutorial, download the JSON from WLW.de Lead Scraper and keep this article open for QA. For adjacent workflows, browse all UScraper templates or the UScraper blog for more CSV export tutorials.