Scrape search results on lidl.com

Measured on Crawlbase

Success rate over every request from every account in August 2026: 97.9%. Patterns, countries and failures come from the request log since 14 Aug 2026; 1.1% of successful calls used the JavaScript token and the median answer took 3.7s.

Among the 9 grocery sites in the Cookbook, lidl.com sits at 6 of 9 by success rate; the category median is 98.8%. Its median answer of 3.7s is slower than the category median of 2.6s. 5 of the 9 accept the plain token, this one among them.

The call

Search result pages are the shape the accounts fetch most here, with the country and token that succeed most often. Replace the placeholder query with your own.

curl "https://api.crawlbase.com/?token=YOUR_TOKEN&country=US&url=https%3A%2F%2Fwww.lidl.com%2Fs%2Fexample-page%2Fexample-page"

from crawlbase import CrawlingAPI
api = CrawlingAPI({'token': 'YOUR_TOKEN'})

r = api.get('https://www.lidl.com/s/example-page/example-page', {'country': 'US'})
html = r['body']

const { CrawlingAPI } = require('crawlbase');
const api = new CrawlingAPI({ token: 'YOUR_TOKEN' });

const r = await api.get('https://www.lidl.com/s/example-page/example-page', { country: 'US' });

Parameters that matter

URL patterns accounts fetch

Fields you get

A search page carries a list of results, each with a title, a link and usually a price or a snippet. Paginate with the site’s own page parameter and stop when a page repeats.

What breaks, and the fix

Of the failures since 14 Aug 2026, the site answered:

Run it on a schedule

Search is the expensive side of a site. Keep the query list short, run it on a cadence through the Crawler with a callback, and fetch afterwards only the result pages you need. The median answer on this site is 3.7s.

Questions