Scrapingdog Weekly Changelog: Nov9-15, 2026

This week's release focuses on making your search requests more dependable. We improved success rates across several of our search APIs, restored a Google Lens mode you asked for, added language selection for Amazon, and launched a new lightweight option for image search. Here's everything that shipped.

At a Glance

• Feature: Google Images Light API

• Update: Amazon language selection in the Playground

• Bug fix: Google Lens all-results mode restored

• Improvements: Higher success rates for Google Lite, Google Advanced Search, DuckDuckGo, and Google Shopping

The headline of the week is the Google Images Light API, now available in both the API and the dashboard Playground.

You can now retrieve image search results by setting advance_search=false. Each standard request costs 5 credits, which makes it a simple, predictable option for projects that need image results without extra overhead. If you need the richer output, advanced image search is still available by setting advance_search=true.

The quickest way to try it is the Playground: open the dashboard, pick the Google Images Light API, and run a query to see the response before wiring it into your code.

Testing Amazon requests in different languages just got easier. The Amazon Search API and Amazon Product API request forms in the dashboard Playground now include a language field. Whatever language you select is sent along with the API request, so you can check how results look for different audiences without editing requests by hand.

This is especially handy if you serve customers in multiple regions and want to confirm that listings and product details come back the way you expect.

We've restored all-results searches in the Google Lens API. Requests now keep the all-results mode when visual matches aren't explicitly requested. Visual-match searches continue to use their own dedicated mode, so nothing changes if you rely on that behavior.

If you noticed reverse image searches returning something different from what you expected, this fix brings them back in line.

A big part of this week's work happened behind the scenes. We refined how requests are handled, retried, and routed so that intermittent failures are less likely to reach you.

We improved request handling, retries, and proxy selection to reduce intermittent failures. The goal is simple: return search results more consistently, even when conditions upstream are unpredictable.

The Advanced Search API received similar upgrades to retry handling and proxy selection. You should see fewer sporadic request failures and more consistent search results.

We updated request handling, retries, and proxy selection to improve success rates. There's also a nice bonus for anyone using the results downstream: the API now extracts destination URLs from DuckDuckGo redirect links. That means you get the actual page a result points to rather than an intermediary redirect, which makes the data cleaner and easier to use.

We improved retry handling and parallel requests so the API can recover from individual upstream failures. When one request stumbles, the others can carry on, helping product results come back more reliably.

If you already use any of these APIs, you don't need to change anything to benefit from the reliability improvements. They apply automatically. You may notice fewer failed requests and fewer retries on your side, which can simplify error handling and make your applications feel steadier.

If you're exploring new capabilities, the Google Images Light API and Amazon language selection are both ready to try in the Playground today.

Here is a video tutorial about our weekly updates.

1. Try the Light API first for images. Use advance_search=false for straightforward image results at 5 credits per request, and switch to advance_search=true only when you need more detail.

2. Test languages before you ship. Use the new Playground language field to preview Amazon results in each language you support.

3. Re-check your Lens workflows. If you use Google Lens, confirm that all-results queries behave as expected now that the mode is restored.

4. Review your DuckDuckGo parsing. With destination URLs now extracted, you may be able to remove custom redirect-handling code.

We'll keep investing in reliability and in the tools that make testing faster. As always, your feedback shapes what we build next, so let us know which APIs you'd like to see improved in the coming weeks.

Thanks for building with us, and see you in next week's update.