Skip to content

Gelbe Seiten Business Listings, Reliably Scraped

Gelbe Seiten is the German yellow-pages directory, and its public listing pages are a common source for service-provider records, customer feedback, and business ratings.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a managed scraping API handles the request for you: you supply the URL, and the service renders the page, rotates proxies, and returns HTML or structured JSON. Below you will find the fields that come back, the request parameters that change behavior, a worked credit example, and a checklist for deciding whether this fits your job.

What a Gelbe Seiten request returns

A single request to the API takes a Gelbe Seiten URL and returns the rendered page. By default you receive HTML; with extraction rules you receive structured JSON. The listing fields the service describes as available include business name, category, address, phone, website, opening hours, ratings, and customer reviews. Contact info, categories, and locations are also returned when present on the page.

If a field you need is not in the default output, you have two options. You can supply CSS selectors through extract_rules, or you can describe the data you want in natural language through ai_extract_rules and let the AI-driven extraction return JSON. Both approaches are documented in the API reference; the choice depends on whether you already know the page structure or want the service to infer it.

Request parameters that change behavior

Four parameters cover most Gelbe Seiten jobs:

  • render_js=true runs the page in a real headless browser and returns the post-render HTML. Use this when listings are loaded by JavaScript after the initial response.
  • stealth_proxy enables the stealth proxy pool. The service already rotates residential proxies and uses a headless browser by default; turn this on when a target is aggressive about blocking.
  • country_code routes the request through a residential IP in the specified country. Useful when content varies by geography.
  • ai_extract_rules (or extract_rules) converts the rendered page into structured JSON instead of raw HTML.

The dashboard request builder lets you paste a URL, set these parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby, or cURL. That is the fastest way to confirm a parameter combination before wiring it into a codebase.

How credits are counted

Credits are consumed per successful request, and the cost depends on which features you enable. The base rate is 1 credit per request. Enabling JavaScript rendering raises the cost to 5 credits per successful request. Enabling premium proxies costs 10 credits when JS rendering is off, or 25 credits when it is on. Credits are valid for one month and do not roll over.

A worked example: a job that needs JavaScript rendering and premium proxies costs 25 credits per successful request. At the Startup plan's 1,000,000 monthly credits, that is roughly 40,000 successful requests per month before you hit the cap. A job that needs only JavaScript rendering costs 5 credits per request, so the same plan covers roughly 200,000 requests. Use these figures to size a plan against your expected page count, not against a guess about how many pages exist.

Plan tiers at a glance

The service publishes five standard plans and five enterprise plans. The standard tiers are Hobby at $19/month with 75,000 credits and 25 concurrent requests; Freelance at $49/month with 250,000 credits and 50 concurrent requests; Startup at $99/month with 1,000,000 credits and 100 concurrent requests; Business at $249/month with 3,000,000 credits and 200 concurrent requests; and Business + at $599/month with 8,000,000 credits and 400 concurrent requests. The enterprise tiers run from Enterprise 14 at $999/month with 14,000,000 credits and 500 concurrent requests up to Enterprise 120 at $5,799/month with 120,000,000 credits and 900 concurrent requests.

Every standard and enterprise plan includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules. Priority email support, a dedicated account manager, and team management are included only from the Business tier upward. All prices are exclusive of VAT. A free trial with 1,000 credits is available without a credit card.

The full plan table with every tier and feature is delivered as a separate structured module; refer to it for exact figures rather than relying on this summary.

Blocked request vs. empty render vs. missing selector

Three failure modes look similar in a log but need different fixes. A blocked request returns an error or a challenge page instead of listing content; the fix is to enable stealth_proxy or adjust the request rate. An empty render returns a page shell with no listings because the JavaScript did not finish; the fix is to confirm render_js=true and, if needed, add a wait or a JavaScript scenario. A missing selector returns a page with content but an empty field in your JSON; the fix is to inspect the rendered HTML and update the extract_rules selector or the ai_extract_rules description. Checking which of the three you are seeing before changing parameters saves credits.

Decision checklist before you sign up

Use these questions to decide whether a managed API fits your Gelbe Seiten job:

  1. Do you need the data on a recurring schedule, or is this a one-off pull? Recurring jobs benefit most from managed proxy rotation and rendering.
  2. Which fields do you actually need? If the default listing fields cover your use, you can skip extraction rules and save setup time.
  3. Does the target require JavaScript rendering? If yes, budget 5 credits per request; if you also need premium proxies, budget 25.
  4. Do you need geo-targeted requests? If content varies by country, plan for country_code.
  5. Do you need team access, priority support, or a dedicated account manager? Those start at the Business tier.
  6. Have you confirmed the parameter combination in the dashboard request builder before writing production code?

If you answered yes to recurring jobs, JavaScript rendering, and geo-targeting, the Startup plan is the smallest tier that covers all three with headroom. If you only need occasional pulls, the free trial credits are enough to validate the approach.

Standard and enterprise plan comparison
PlanPriceAPI CreditsConcurrent requestsPriority Email SupportDedicated Account ManagerTeam Management
Hobby$19 /mo75,00025Not includedNot includedNot included
Freelance$49 /mo250,00050Not includedNot includedNot included
Startup (Recommended)$99 /mo1,000,000100Not includedNot includedNot included
Business$249 /mo3,000,000200IncludedIncludedIncluded
Business +$599 /mo8,000,000400IncludedIncludedIncluded
Enterprise 14$999 /mo14,000,000500IncludedIncludedIncluded
Enterprise 24$1,599 /mo24,000,000600IncludedIncludedIncluded
Enterprise 41 (Recommended)$2,399 /mo41,000,000700IncludedIncludedIncluded
Enterprise 69$3,599 /mo69,000,000800IncludedIncludedIncluded
Enterprise 120$5,799 /mo120,000,000900IncludedIncludedIncluded

All prices are exclusive of VAT. Credits are valid for one month and do not roll over. Requests start at 1 credit each; JavaScript rendering costs 5 credits per successful request; premium proxies cost 10 or 25 credits per successful request depending on whether JavaScript rendering is enabled. Plan figures are the service's published rates at the time of capture and should be checked on the current pricing page before purchase.

Frequently asked questions

What data can I extract from Gelbe Seiten?

Any content visible on the public listing page is fair game. To get structured JSON back, either target specific elements with CSS selectors through extract_rules, or describe the fields you want in plain language with ai_extract_rules and let AI-driven extraction assemble the output.

How do I get started scraping Gelbe Seiten?

Sign up, grab your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. 1,000 free credits are available to test.

Will I get blocked when scraping Gelbe Seiten?

Out of the box, requests go out through rotating residential proxies driven by a genuine headless browser, so they blend in with ordinary visitor traffic. When a target starts pushing back harder, turn on stealth_proxy for that request.

Can I scrape Gelbe Seiten without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby, or cURL.

How do I handle JavaScript when scraping Gelbe Seiten?

Pass render_js=true on the request. The service runs the page in a real headless browser, executes the JS server-side, and returns the post-render HTML.

Can I scrape Gelbe Seiten from a specific country?

Yes. Add country_code to the request and traffic exits through a residential IP located in that country, which matters when the directory serves different content by location.