Gelbe Seiten Scraper - German Business Directory & Leads avatar

Gelbe Seiten Scraper - German Business Directory & Leads

Pricing

from $3.00 / 1,000 results

Go to Apify Store
Gelbe Seiten Scraper - German Business Directory & Leads

Gelbe Seiten Scraper - German Business Directory & Leads

Scrape Gelbe Seiten, the German yellow pages, in bulk. Extract business name, trade, full address, postcode, phone and profile URL for any trade in any German city. B2B lead data at source. No login, no API key.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Logiover

Logiover

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

10 days ago

Last modified

Share

Scrape Gelbe Seiten, the German yellow pages, in bulk. Extract business name, trade, full address, postcode, phone and profile URL for any trade in any German city. B2B lead data at source. No login, no API key.

✨ What this Actor does

  • Build a B2B prospect list for a trade in a German city, with phone numbers.
  • Size a local market by counting registered businesses per trade.
  • Enrich a CRM with verified addresses and postcodes.
  • Find businesses in a trade that have no website yet.

🚀 Quick start

  1. Fill in the input below — the example is already prefilled, so you can just press Start.
  2. Watch the log: it names every source it reaches and how many rows each returned.
  3. Export from the Storage tab as JSON, CSV, Excel or feed it straight into your own tools.

📥 Input

{
"queries": [
"Zahnarzt",
"Friseur"
],
"cities": [
"Berlin",
"Hamburg"
],
"maxItems": 500
}

Every field is documented in the input form. Nothing here needs an API key or a login.

📤 Output

One row per record, with these columns:

FieldTypeDescription
namestringRegistered trading name.
tradestringPrimary trade category.
addressstringStreet address as published.
postalCodestringGerman five-digit postcode.
citystringCity searched.
phonestringContact number where published.
openingStatusstringWhether the business is open now, as shown in the results.
websitestringBusiness website where published.
ratingnumberAverage rating where published.
participantIdstringGelbe Seiten' internal participant number.
realIdstringStable identifier of the directory record.
profileUrlstringPublic directory page for the business.
querystringTrade searched for this row.
pagenumberResult page the row came from.
scrapedAtstringWhen this row was collected.

A column that is empty means the source did not publish that value for that record — it is never a silent substitute for zero or for "unknown".

❓ Frequently asked questions

Do I need an API key or an account? No. This Actor reads a public feed.

What happens if the source blocks the run? Requests go out directly first; one that is refused or stalls is retried on German residential and then Apify proxy exits, with a hard time limit on every attempt. If nothing gets through, the run fails with the reason — it never reports success with zero rows, because "there is no such data" and "the source would not answer" are very different answers and you should not have to guess which one you got.

How do I schedule this? Use the Schedules tab. Daily is usually enough; the sources here do not change by the minute.

Can I get the results into Google Sheets or a database? Yes — use the dataset export, or the Apify API and integrations. Every run writes a SUMMARY record to the key-value store with the outcome and counts, which is handy for monitoring an automated pipeline.

💰 Pricing

Pay per result. You are charged for the rows you receive and nothing else, so a run that finds nothing costs nothing.

This Actor collects publicly available information only. It does not log in, does not bypass access controls, and collects no private data. You are responsible for using the output in line with the source's terms and with applicable law, including GDPR where personal data is involved.

⭐ Support

Found something wrong, or want a field that is not here? Open an issue on the Actor's page — include the run ID and I will look at it.

How much Gelbe Seiten data can you extract in one run?

A single run returned 570 business records in 93 seconds on the example input. That is roughly 367 business records a minute. Widen the search — more queries, more pages, a broader location — and the same run goes deeper.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Gelbe Seiten itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

Gelbe Seiten scraping — frequently asked questions

Do I need a Gelbe Seiten API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Gelbe Seiten data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Gelbe Seiten scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the business records you care about really do change that fast.

How many business records can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

This Actor collects only information that Gelbe Seiten publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Gelbe Seiten blocks the run or changes its layout?

A request that is refused or stalls is retried on another route — German residential, then Apify proxy — on a fresh IP each time, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

Who uses this Gelbe Seiten scraper, and what for

  • Market and pricing analysts tracking how business records on Gelbe Seiten move week to week.
  • Sales and growth teams building prospect lists from what Gelbe Seiten publishes.
  • Data and ML teams who need a structured corpus rather than screenshots.
  • Researchers and journalists who need a dataset they can cite and re-run.
  • Operations teams feeding business records into a CRM, a warehouse or a dashboard on a schedule.

Same output format, same pay-per-result billing, so they combine cleanly in one pipeline:

📝 Changelog

2026-09-25

  • First release.