This tutorial shows how to scrape Chefkoch recipes from recipe detail URLs into CSV with the Chefkoch Recipe Scraper template for UScraper. You will import the workflow, replace sample URLs, set the export folder, run a validation batch, and troubleshoot common blanks.
Before you start
Prerequisites for a Chefkoch scraper tutorial
You need UScraper installed as a local desktop app, a short list of Chefkoch.de recipe detail URLs, and a folder where CSV exports can be written. Start with two to five URLs because pages can differ by recipe type, consent state, hidden modules, and anti-abuse checks.
This guide covers visible recipe detail pages, not member dashboards, login-only features, comments behind interaction walls, or CAPTCHA bypassing. Before automated collection, review the current Chefkoch.de robots.txt and Chefkoch terms. For republishing, resale, or model training, get legal review.
A scraper is a collection method, not a rights grant. Keep the dataset narrow, keep pacing modest, and document why each field is needed.
Workflow anatomy
What the Chefkoch recipe scraper exports
The companion template is built for detail pages, not search listings. It opens each recipe URL, waits for page load, checks for common cookie consent buttons, waits for the visible h1, and uses Structured Export to read fields from the rendered page body.
| Output group | CSV columns | Use it for |
|---|---|---|
| Recipe identity | rezept_url, titel, beschreibung | Dedupe rows, review page titles, and preserve source URLs. |
| Social proof | kundenbewertung, anzahl_der_bewertungen, anzahl_der_kommentare | Compare which recipes have stronger visible engagement. |
| Cooking metadata | gesamtzeit, arbeitszeit, schwierigkeitsgrad, veroeffentlichungszeit | Segment recipes by effort, recency, and difficulty. |
| Recipe body | details_der_zutaten, vorstellung_der_zubereitung | Review ingredient structure and preparation language. |
| Attribution and discovery | rezept_von, rezept_von_name, weitere_rezepte | Track author profile links and related recipe URLs. |
There is no CSV sample bundled with this post. Use the export shape above together with the JSON workflow from the Chefkoch Recipe Scraper template. The JSON defines the block graph, sample URLs, waits, export file name, append mode, and JavaScript-backed columns.
Runbook
How to scrape Chefkoch recipes to CSV
Import the template
Open Chefkoch Recipe Scraper for Recipe Details, download the JSON, and import it into UScraper.
Replace sample URLs
In the Navigate block, replace the Bauerntopf and Filettopf examples with Chefkoch.de recipe detail URLs you are allowed to process.
Set the export path
Confirm the Structured Export save folder and file name. The stock workflow writes chefkochde-rezepte-detail-scraper.csv with headers and append mode.
Run one recipe
Start with a single URL. Watch for cookie prompts, verification pages, slow loading, and whether the page reaches a visible recipe heading.
Validate, then batch
Open the CSV, compare the row against the browser, fix blanks, and only then reconnect the loop for the rest of the URL list.
The important detail is append mode. If you rerun the same URL after a failed test, the file may contain duplicate rows. For clean validation, delete the test CSV first or save a new file name.
Validation
Validate Chefkoch recipe exports before analysis
Recipe pages mix structured metadata, visible text, and dynamic modules. Validate before the CSV feeds ingredient normalization, SEO research, translation, internal search, or recommendation experiments.
| Symptom | Likely cause | Practical fix |
|---|---|---|
Empty titel | The recipe heading never became visible | Extend the wait, handle consent, and rerun one URL. |
| Blank ingredient details | Chefkoch changed the ingredient table markup | Inspect the live page and update the details_der_zutaten selector. |
| Missing preparation text | The page structure or visible labels changed | Test the JavaScript extraction against one rendered recipe. |
| Rating count differs | Locale text or rating markup changed | Recheck the rating selector and number parsing pattern. |
| Repeated rows | The same URL was supplied twice or a loop was rerun | Sort by rezept_url and dedupe before analysis. |
API choice
Chefkoch API vs scraper: which path fits?
Searches for chefkoch api vs scraper usually come from two teams: developers who want an integration and analysts who want recipe rows in a spreadsheet.
Chefkoch has public API-style endpoints and community wrappers in JavaScript, Python, and PHP ecosystems. Those can help engineering teams that want code, tests, retries, and storage. The trade-off is ownership: you maintain the wrapper and handle schema changes.
UScraper fits a narrower job: a reviewed list of Chefkoch recipe pages, a visible browser run, and a local CSV for QA. Hosted tools such as Octoparse, Apify, Thunderbit, Spider, or Scrapebit may fit cloud scheduling better. For small recipe research exports, the local desktop workflow keeps the block graph and CSV destination easy to inspect.
FAQ
Chefkoch recipe scraper FAQ
Is it legal to scrape Chefkoch.de recipes?
Chefkoch.de recipe pages may be publicly visible, but automated collection can still be limited by terms, robots rules, copyright, database rights, privacy law, and local regulations. Keep runs modest and get legal review before republishing or selling recipe data.
Do I need a Chefkoch API key for this tutorial?
No. The UScraper workflow opens normal recipe detail URLs in a browser session and exports visible page fields to CSV. API wrappers are useful for developer-led integrations; this tutorial is for reviewable local CSV exports.
What does the Chefkoch recipe scraper export?
The workflow writes chefkochde-rezepte-detail-scraper.csv with recipe URL, title, description, rating fields, times, difficulty, publication date, ingredients, preparation text, author fields, and related recipe URLs.
Why are some Chefkoch fields blank after export?
Blank cells usually mean the layout changed, the field was not visible, the page did not finish rendering, consent interrupted the run, or Chefkoch.de showed verification. Inspect one URL before scaling.
How many Chefkoch recipe URLs can I scrape?
The template is a multi-URL loop, so you can add more approved detail URLs to Navigate. Practical limits depend on permission, pacing, CAPTCHA frequency, selector maintenance, and your local machine.
Next step
Download the Chefkoch recipe scraper template
When you are ready to run the tutorial, download the workflow from Chefkoch Recipe Scraper for Recipe Details and keep this article open for validation. For adjacent workflows, browse the UScraper template library or return to the UScraper blog for more scraping tutorials.