> ## Documentation Index
> Fetch the complete documentation index at: https://cloro.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use only the endpoint paths in https://cloro.dev/docs/skill.md. Do not derive a path from a docs page URL.
> For many requests, use the async API (POST /v1/async/task or POST /v1/async/task/batch). It has no sync surcharge.
> To call cloro as tools, use the MCP server at https://mcp.cloro.dev/mcp.
> Plan prices are at https://cloro.dev/pricing/. Credits for each request are at https://cloro.dev/docs/guides/providers.md.

# Google Search changelog

> All cloro changelog entries for Google Search, newest first.

See [every entry](https://cloro.dev/docs/changelog.md).

**19th November 2026**

**Google Search: hotel cards inside text ads are now in `ads`**

Some text ads show a carousel of hotel cards, often 20 per ad. The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) did not return these cards. Each card is now an item in `ads[]`:

```json theme={null}
{
  "position": 1,
  "blockPosition": "bottom",
  "type": "SHOPPING_CARD",
  "category": "Sponsored",
  "title": "DoubleTree by Hilton London ExCeL",
  "url": "https://www.google.com/aclk?sa=L&ai=...",
  "page": 1,
  "price": { "value": 84, "currency": "£", "raw": "£84" },
  "store": "Hilton",
  "rating": 4.3,
  "reviews": "3.3k"
}
```

`blockPosition` is the block of the text ad, and `store` is its advertiser. See [Sponsored ads](https://cloro.dev/docs/api-reference/endpoint/google/sponsored-ads.md#ad-types).

**17th November 2026**

**Google Search: expand the AI Overview in the HTML page**

You can now expand the AI Overview in the `include.html` page. Send [`include.aioverview.expand: true`](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview#example-request) and the stored page shows the full AI Overview, as if **Show more** were clicked. This works on desktop only: on phones, Show more opens AI Mode. `result.aioverview` does not change.

**16th November 2026**

**Google Search: resolving redirect links is free for paying customers**

[`POST /v1/monitor/google/goto`](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto#resolve-a-link) now costs 0 credits if you have an active subscription or bought credits. Before, it cost 1 credit per resolved link.

When Google changes how it serves its links, responses can have an empty `link` for some hours. You can now backfill those links at no cost: send each `redirectLink` to the endpoint.

**16th November 2026**

**Google Search: 17 more SERP features**

The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now returns 17 more blocks that Google shows on the results page. A key is omitted when its block is not on the page. No flag, no extra cost.

| Key | Block |
| - | - |
| [`sportsResults`](https://cloro.dev/docs/api-reference/endpoint/google/sports-results) | Standings, games, squads and stat leaders |
| [`relatedWebsites`](https://cloro.dev/docs/api-reference/endpoint/google/related-websites) | Carousels of site cards ("Related websites", "Find results on") |
| [`inlineImages`](https://cloro.dev/docs/api-reference/endpoint/google/inline-images) | The Images block |
| [`videos`](https://cloro.dev/docs/api-reference/endpoint/google/videos) | The Videos carousel, with key moments |
| [`shortVideos`](https://cloro.dev/docs/api-reference/endpoint/google/short-videos) | The Short videos carousel |
| [`weather`](https://cloro.dev/docs/api-reference/endpoint/google/weather) | Current conditions, hourly and daily forecast |
| [`latestPosts`](https://cloro.dev/docs/api-reference/endpoint/google/latest-posts) | An entity's own social posts |
| [`financeQuote`](https://cloro.dev/docs/api-reference/endpoint/google/finance-quote) | Market summary of a stock, fund, index, future or crypto currency |
| [`events`](https://cloro.dev/docs/api-reference/endpoint/google/events) | Event cards and ticket offers |
| [`discussionsAndForums`](https://cloro.dev/docs/api-reference/endpoint/google/discussions-and-forums) | Forum threads, with their answers |
| [`thingsToKnow`](https://cloro.dev/docs/api-reference/endpoint/google/things-to-know) | The "Things to know" facets |
| [`transitResults`](https://cloro.dev/docs/api-reference/endpoint/google/transit-results) | Train and bus routes, departures and fares |
| [`flights`](https://cloro.dev/docs/api-reference/endpoint/google/flights) | The flights blocks, with prices, stops and booking sites |
| [`hotelResults`](https://cloro.dev/docs/api-reference/endpoint/google/hotel-results) | The hotel pack and hotel carousels, with prices and booking sites |
| [`stores`](https://cloro.dev/docs/api-reference/endpoint/google/stores) | The merchants of the Stores block |
| [`comparisonShoppingSites`](https://cloro.dev/docs/api-reference/endpoint/google/comparison-shopping-sites) | In the EEA, the products of each comparison shopping site |
| [`topSights`](https://cloro.dev/docs/api-reference/endpoint/google/top-sights) | The top sights of a city or place |

Organic results also have a [`readMore`](https://cloro.dev/docs/api-reference/endpoint/google/organic-results#read-more-link) link when Google ends the snippet with "Read more".

**12th November 2026**

**Perplexity is discontinued**

Perplexity blocks access for logged-out sessions. Each workaround we found stopped working within days, so we discontinued the endpoint. `POST /v1/monitor/perplexity` and async tasks with `taskType: "PERPLEXITY"` return `400` (`MODEL_UNAVAILABLE`) and cost no credits. See [unsupported providers](https://cloro.dev/docs/guides/providers.md#unsupported-providers).

**Google Search: responses about 2x faster**

The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now returns a 1-page response in about 1.7 seconds at the median, against about 3.7 seconds before 7 November. These times are for requests without `include.html` and `include.aioverview`.

**9th November 2026**

**Google: EU places unit in `localResults`**

In the EU, Google often replaces the local pack with a list of suppliers (Google, TheFork, UberEats, …). The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now returns the places of every supplier in `result.localResults`, each with a new [`supplier`](https://cloro.dev/docs/api-reference/endpoint/google/local-pack#eu-places-unit) field. Places also gain `ratingScale` (5 or 10) where Google shows one. No flag, no extra cost.

**6th November 2026**

**Google Search: redirect links resolve again**

On 6 November Google closed the method cloro used to resolve organic result redirects (`/goto?url=…`). We deployed a new method a few hours later, and the [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) returns resolved links again.

If a response from those hours has an empty `link`, pass its `redirectLink` to [`POST /v1/monitor/google/goto`](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto#resolve-a-link) to get the destination. It costs 1 credit, charged only when the destination comes back. The endpoint also resolves `/goto` links that you did not get from cloro.

**30th October 2026**

**Google Search: resolving a redirect link now costs 1 credit**

[`POST /v1/monitor/google/goto`](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto#resolve-a-link) now costs 1 credit per request, with no sync surcharge. You pay only when the call returns the destination, so a failed call costs nothing.

Demand for this endpoint has grown very fast, because the industry has not been able to solve these links, and each link takes significant processing to resolve. We have to charge for it to sustain this demand.

**30th October 2026**

**Google Search: add a fallback for unresolved links**

Google now puts most organic result redirects (`/goto?url=…`) behind a verification page, so resolving them can take longer. This affects every SERP provider we track. cloro used to fail a page when a link stayed unresolved, so from 01:40 to 06:50 UTC on 30 October about 94% of requests to the [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) failed. Failed requests were not charged.

The endpoint now returns the page, and a link that is not resolved yet has an empty `link`:

```json theme={null}
{
  "position": 3,
  "title": "Understand the basics of Roth IRAs",
  "link": "",
  "redirectLink": "https://www.google.com/goto?url=CAESaAHrOzAVev0pi_wnTxm1..."
}
```

We still try to resolve each link in the response, but you should always have a fallback. When `link` is empty, pass `redirectLink` to [`POST /v1/monitor/google/goto`](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto#resolve-a-link) to get the destination. If the call returns `502`, retry it later.

**27th October 2026**

**Google Search: degraded results are back**

Since 26 October, about 20:10 UTC, Google again gives most sessions a [degraded SERP](https://cloro.dev/blog/google-poisoned-serps/), across every provider we track. The organic results then show pages that are similar to the query but are not the sites that usually rank for it. Requests to the [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) can return this degraded page until it is fixed.

We're working on it, and we'll post here when full results are back.

**21st October 2026**

**Async: the idempotency `409` returns the existing task ID**

When you reuse an `idempotencyKey`, the `409 RESOURCE_ALREADY_EXISTS` from [`POST /v1/async/task`](https://cloro.dev/docs/api-reference/endpoint/create-async-task) now has `error.details.taskId`: the ID of the task that already holds the key. If your submit request timed out before you received the `taskId`, resubmit with the same key and poll the returned ID. The [batch endpoint](https://cloro.dev/docs/api-reference/endpoint/create-batch-tasks.md) returns it too, except for a key repeated inside the same batch.

**Google: the AI Overview is expanded in the HTML**

When a [Google Search](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) request sends `include.aioverview` and `include.html`, the stored HTML now shows the AI Overview expanded, as it looks after a click on "Show more". Before, it was collapsed. The cost does not change.

**19th October 2026**

**Google: new `recipes` field for the Recipes carousel**

The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now returns the cards of Google's Recipes carousel as [`result.recipes`](https://cloro.dev/docs/api-reference/endpoint/google/recipes), on desktop and mobile, with no flag and at no extra cost. Each card has `position`, `title` and `link` plus, when Google shows them, `source`, `rating`, `reviews`, `totalTime`, `ingredients` and `thumbnail`. The field is omitted when the SERP has no Recipes carousel.

On desktop these cards were returned in `result.peopleAreSaying` by mistake. `peopleAreSaying` now has only the cards of the "What people are saying" module.

**14th October 2026**

**Google Search: fewer degraded results**

Google gives some sessions a degraded SERP: fewer pages, and fewer of the sites that usually rank for the keyword. A site can then drop out of the results even though its rank did not change. The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now sends a request only through a session that a test confirms gets Google's full results, so ranks are more stable from one request to the next.

**12th October 2026**

**Google: `localResults` on mobile**

The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now returns the [local pack](https://cloro.dev/docs/api-reference/endpoint/google/local-pack.md) for `device: "mobile"` in all the layouts Google shows. Before, most mobile responses had no `localResults`. On mobile, `phone` is the number from the card's Call button, such as `"+17027773777"`.

On desktop and mobile, a price in a currency that has no symbol in the text, such as `"20–40 zł"` or `"100-200 kr."`, is now in `price`. Before, it was in `type` and the category was lost.

**8th October 2026**

**Google Search: get the product panel behind a shopping card**

A Google shopping card opens a product panel, so its `productLink` is usually empty. Each desktop first-page card now has a `productResultToken`. Send it to the new [`POST /v1/monitor/google/product`](https://cloro.dev/docs/api-reference/endpoint/google/product) endpoint to get the panel as `productResults`: merchant offers with links and prices, specifications, reviews, videos, variants and related products.

```json theme={null}
{
  "productResultToken": "nuzK-QgAV8BqrZdwQJYZopzdoFhpvKr-N2_YDZevwzg"
}
```

A token expires five minutes after the search. The search costs no more than before. The product request costs 1 credit (3 sync), and only when it succeeds. It is also available async as `taskType: "GOOGLE_PRODUCT"`. Set a high `priority` on an async product request, so that the token does not expire in the queue.

**14th September 2026**

**Google shopping cards ship the discount badge as `promoLabel`**

A discounted card renders a badge above the product name. That badge was reaching you as `title`, in the SERP language — `LOW PRICE`, `OFERTA`, `PROMOÇÃO` — and the name was dropped. `title` now always carries the name, and the badge comes back beside it:

```json theme={null}
{
  "title": "Dove Jabón Barra Original 135 g",
  "promoLabel": "OFERTA",
  "price": { "value": 8.79, "currency": "$", "raw": "$8.79" },
  "oldPrice": { "value": 11, "currency": "$", "raw": "$11" }
}
```

Omitted on a card without a badge. See the [shopping cards schema](https://cloro.dev/docs/api-reference/endpoint/google/shopping-cards.md).

**8th September 2026**

**Every redirect link now ships beside its destination as `redirectLink`**

Google serves many result links as an encrypted `/goto?url=<token>` redirect. cloro resolves them, and now returns the redirect too, so you no longer choose between the two:

```json theme={null}
{
  "position": 1,
  "title": "24 best SEO tools I'm using in 2026 (free + paid)",
  "link": "https://www.marketermilk.com/blog/best-seo-tools",
  "redirectLink": "https://www.google.com/goto?url=CAESaAHrOzAVev0pi_wnTxm1qpiZTmMyAllabLr1or10ZCfvJKPk",
  "page": 1
}
```

It appears on any link field Google served as a redirect, across [Google Search](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md), [Google News](https://cloro.dev/docs/api-reference/endpoint/monitor-google-news.md) and [AI Mode](https://cloro.dev/docs/api-reference/endpoint/monitor-aimode.md), and is the absolute form [`POST /v1/monitor/google/goto`](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto) takes.

Every field now holds a destination, including the ones that still returned a raw token until early September: `peopleAlsoAsk[].sources[].url`, `newsResults[].link`, `productResults[].stores[].link`, and the links inside `markdown`.

The key is omitted when Google served a plain link, so its absence means there was no redirect. Sponsored results are the exception: an ad's `/aclk` URL is a tracking link, not a redirect, and following it registers a click against the advertiser — so ads carry no `redirectLink` on Google Search.

> [!WARNING]
>
> **`include.googleGoto` is now ignored.** The flag returned raw `/goto` links *instead of* destinations. Requests still sending it get a normal response, with the destination in `link` and the redirect in `redirectLink` — more than the flag gave you, so nothing needs to change. One exception: links inside `markdown` and `text` are resolved destinations and no longer carry the raw token. Read `redirectLink` from the structured fields instead. `POST /v1/monitor/google/goto` is unaffected.

> [!NOTE]
>
> A redirect we cannot resolve now omits the link field rather than returning a token you cannot fetch. `redirectLink` is still there, so a missing `link` or `url` means "unresolved". Pass it to [`POST /v1/monitor/google/goto`](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto) to get the destination.

**31st August 2026**

**Google and AI Mode: keep the raw `/goto` links, and a new endpoint to resolve one**

cloro resolves Google's encrypted `/goto?url=<token>` redirect links for you, so result links are real destinations. If you run your own resolution, set `include.googleGoto: true` on a [Google Search](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) or [AI Mode](https://cloro.dev/docs/api-reference/endpoint/monitor-aimode.md) request and the links come back raw instead, as absolute `https://www.google.com/goto?url=<token>` URLs:

```json theme={null}
{
  "position": 1,
  "title": "24 best SEO tools I'm using in 2026 (free + paid)",
  "link": "https://www.google.com/goto?url=CAESaAHrOzAVev0pi_wnTxm1qpiZTmMyAllabLr1or10ZCfvJKPkFqExEIHEAXuQnnehHEAZpxrNEFuDMonO8o90rlyWkWC8xN5NiVm7zj9JUmedJUe_ZXVVrJ1rr520I5PZ5XAZpQplL4bp",
  "page": 1
}
```

`POST /v1/monitor/google/goto` resolves one of those links to its destination. It charges no credits and uses no concurrency slot.

The flag is off by default, so requests that do not send it behave exactly as before. See [Google redirect links](https://cloro.dev/docs/api-reference/endpoint/google/resolve-goto.md).

> [!WARNING]
>
> Superseded on 8th September 2026: `include.googleGoto` is ignored. Every redirect now ships as `redirectLink` beside its destination, so you get both without the flag.

**30th August 2026**

**Google Search: sponsored-ad coverage roughly doubled**

cloro now targets geography on [Google Search](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) requests in a way that no longer suppresses Google's ad auction, so sponsored results that were previously withheld come through. In a paired A/B test on commercial-intent US queries, ads roughly double the coverage.

Nothing changes in your integration. The `country` request parameter (and its `gl` alias) targets the same geography as before, `hl` still controls the interface language, and [sponsored ads](https://cloro.dev/docs/api-reference/endpoint/google/sponsored-ads.md) keep arriving in `result.ads` with the same schema. You should simply see ads on more commercial queries.

**27th August 2026**

**Google `/goto` tracking links: your results keep real URLs**

Google now serves many result links as relative `/goto?url=<token>` redirects instead of the destination URL. The token is encrypted on Google's side, so the raw HTML gives no usable link.

cloro resolves them before the response leaves us. The `/goto` links stay in the HTML, but the parsed JSON holds the real destination:

```json theme={null}
{
  "organicResults": [
    {
      "position": 1,
      "title": "Best laptops for programmers",
      "link": "https://example.com/best-laptops-2026",
      "displayedLink": "example.com › best-laptops"
    }
  ]
}
```

For the few links we cannot resolve this way, we follow the `/goto` link to its destination. This adds a small delay to those requests only.

Nothing changes in your integration. `link` and the video and local-pack link fields stay absolute `https://` URLs, as before. If a Google organic link cannot be resolved at all, we retry the request instead of giving you a `/goto` value.

**25th August 2026**

**Google family: interface language with `hl`**

[Google Search](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md), [Google News](https://cloro.dev/docs/api-reference/endpoint/monitor-google-news.md), and [AI Mode](https://cloro.dev/docs/api-reference/endpoint/monitor-aimode.md) take a new optional `hl` parameter for the interface language, independent of the country:

```json theme={null}
{
  "prompt": "beste laptops für programmierer",
  "country": "US",
  "hl": "de"
}
```

Before this, the language came from the country, so a German interface meant asking for Germany, and multilingual countries such as `CH`, `BE`, and `CA` picked one dominant language. AI Mode had no override at all.

The same three endpoints also accept `gl` as an alternative name for `country`, matching Google's own parameter. Both work, and `gl` takes either case; sending `country` and `gl` with different values is a `400`. Nothing changes for existing requests.

**Perplexity pricing increases to 4 credits per request**

Perplexity continues to restrict access. To hold the same success rate and source coverage, our cost to serve this endpoint increased by 70%. The [Perplexity endpoint](https://cloro.dev/docs/guides/providers.md#unsupported-providers) now costs **4 credits per request**, up from 3. That is an increase of 33% against a cost increase of 70%. All other provider prices, addons, and the sync surcharge do not change. See the full [providers pricing table](https://cloro.dev/docs/guides/providers.md) for context.

**10th August 2026**

**Google Search and Google News: `device` now accepts `ios` and `android`**

The `device` parameter on the [Google Search](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) and [Google News](https://cloro.dev/docs/api-reference/endpoint/monitor-google-news.md) endpoints takes two new values: `ios`, which runs the search as Safari on an iPhone, and `android`, which runs it as Chrome on Android. Both return the mobile SERP layout, so the response shape is unchanged and there is no extra credit cost.

`mobile` still works and is now an alias for `android`, so existing requests behave exactly as before. Use `ios` when you need to see what Google serves iPhone users specifically.

**Merchant offers on Google Search and AI Mode: `result.productResults`**

Both Google surfaces can now return the merchant offers behind a product — direct merchant URL, price, installment terms, and stock, delivery and returns badges — as a new `productResults` array, in the same shape on both.

On [Google Search](https://cloro.dev/docs/api-reference/endpoint/google/product-results.md) it appears whenever Google's right-rail product panel does, with no flag and no extra credits; [`shoppingCards`](https://cloro.dev/docs/api-reference/endpoint/google/shopping-cards) is unchanged. On [Google AI Mode](https://cloro.dev/docs/api-reference/endpoint/aimode/product-results.md) it is opt-in via `include.expandProducts` and costs **+1 credit per product cluster returned**, capped at +6.

**9th July 2026**

**Google: new `localResults` (local pack / "3-pack") field**

The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now exposes a `localResults` array on `result` for local-intent queries (e.g. "best pizza in new york city", "plumbers in houston"). Each entry is a place from Google's map-backed local pack, carrying `position` and `title` plus, when Google renders them, `placeId`, `rating`, `reviews`, `price`, `type`, `yearsInBusiness`, `address`, `phone`, `hours`, a `description` snippet, and a `links` object with the place's `website` and `directions` URLs (typical on business/service packs). When the pack shows a "More places" / "More businesses" control, `result.localResultsMoreLink` carries the URL of Google's expanded Local Finder for the query. The field is additive and omitted when no local pack appears on the SERP; extraction is desktop only. See the [Local Pack schema](https://cloro.dev/docs/api-reference/endpoint/google/local-pack.md).

**30th June 2026**

**Google Search and AI Mode now pin to the requested country by default**

Requests to [`/v1/monitor/google`](https://cloro.dev/docs/api-reference/endpoint/monitor-google) and [`/v1/monitor/aimode`](https://cloro.dev/docs/api-reference/endpoint/monitor-aimode) that pass `country` but omit both `location` and `uule` now auto-default `location` to the country's canonical name (e.g. `"Portugal"` for `country: "PT"`). Previously, with no UULE set, Google geolocated by the proxy's exit IP — so identical sequential requests could swing between different result locations as each scrape leased a different proxy session.

No request changes are needed. Existing calls will see more stable, country-pinned results. Defaulting is country-level only — cloro never auto-picks a city. If you need city- or region-level precision, keep passing `location` (Google canonical name) or `uule` (pre-encoded UULE) explicitly. Unknown country codes leave UULE unset, preserving prior behavior.

```json theme={null}
{
  "query": "best restaurants",
  "country": "PT"
}
```

**29th June 2026**

**Google Knowledge Graph panel now extracted**

The Google Search endpoint now returns a `knowledgeGraph` object when a Knowledge Graph panel appears on the SERP. The panel covers people, places, organizations, films, local businesses, and other well-known entities — surfacing structured data like entity type, description, attributes, profiles, ratings, and panel-type-specific fields (streaming options, admission prices, social posts, and more).

No request changes needed — the field is included automatically when a panel is present, and omitted from `result` when it is not.

```json theme={null}
{
  "result": {
    "knowledgeGraph": {
      "title": "Eminem",
      "type": "American rapper",
      "description": "Marshall Bruce Mathers III, known professionally as Eminem...",
      "website": "https://www.eminem.com",
      "attributes": [
        { "key": "Born", "value": "October 17, 1972" },
        { "key": "Genre", "value": "Hip hop" }
      ]
    }
  }
}
```

See the [Knowledge Graph reference](https://cloro.dev/docs/api-reference/endpoint/google/knowledge-graph.md) for the full schema.

**13th May 2026**

**Google Search now returns sponsored shopping-card ads**

The Google Search endpoint now extracts every sponsored shopping surface Google renders on the SERP, alongside the existing text ads. Each entry in `ads[]` carries a new `type` discriminator:

* **`type: "RESULT"`** — classic text ads at the top or bottom of the page (unchanged).
* **`type: "SHOPPING_CARD"`** — shopping-style sponsored cards from the right-hand-side carousel (`blockPosition: "rhs"`) and the top-of-page carousels (`blockPosition: "top"`). Categories observed include `"Sponsored products"`, `"Sponsored vehicles"`, and `"Sponsored hotels"`.

`SHOPPING_CARD` ads include `category` (the carousel header label), `price`, optional `oldPrice` (MSRP / sale), `store`, and `imageUrl`. For shopping-card ads, the existing `description` field carries category-specific subtitle fragments joined with `·` (e.g. `Used - 94k miles · Greeley` on a vehicle card).

The `ads[]` `blockPosition` enum widens to `"top" | "bottom" | "middle" | "rhs"`. The new fields are emitted whenever the SERP renders the corresponding surface — no opt-in, no additional credit charge.

In the organic `shoppingCards[]` field, the `product_link` and `old_price` keys are now emitted as camelCase `productLink` and `oldPrice` to match the rest of the Google response.

Learn more in the [sponsored ads documentation](https://cloro.dev/docs/api-reference/endpoint/google/sponsored-ads.md).

**11th May 2026**

**Google Search and Google News multi-page pricing is now linear**

Multi-page requests are now billed at **+2 credits per additional page** instead of the previous tiered structure. Single-page requests are unchanged.

| Request | Old cost | New cost |
| - | - | - |
| 1 page | 3 credits | 3 credits (unchanged) |
| 1 page + AI Overview | 5 credits | 5 credits (unchanged) |
| 3 pages | 4 credits | 7 credits |
| 3 pages + AI Overview | 6 credits | 9 credits |
| 10 pages | 5 credits | 21 credits |
| 10 pages + AI Overview | 7 credits | 23 credits |

The same per-page rate applies to [Google News](https://cloro.dev/docs/api-reference/endpoint/monitor-google-news.md). See [providers](https://cloro.dev/docs/guides/providers.md#google-search-multi-page-pricing) for the full pricing breakdown.

**Why the change.** Pages 2-10 are materially harder to serve than page 1: the failure rate climbs as Google ramps up scrutiny on deep pagination. In our infrastructure, fetching pages 1-10 of a single query costs roughly **6× more** than fetching 10× page 1 alone — the per-page cost scales near-exponentially with depth. The old tiered pricing absorbed that cost and under-charged deep-pagination requests; the new per-page rate aligns billing with the actual cost of serving each page and keeps single-page Google requests — the dominant use case — unchanged.

**7th May 2026**

**Google Search now returns shopping cards and "people are saying" cards**

The Google Search endpoint now extracts two additional SERP modules:

* **Shopping cards**: product cards from the organic shopping grids ("Popular products" and "More products") in a new optional `shoppingCards` array. Learn more in the [shopping cards documentation](https://cloro.dev/docs/api-reference/endpoint/google/shopping-cards.md).
* **People are saying**: community-thread cards from Google's "What people are saying" / "Trending posts and discussions" module in a new optional `peopleAreSaying` array. Learn more in the [people are saying documentation](https://cloro.dev/docs/api-reference/endpoint/google/people-are-saying.md).

Both fields are omitted from `result` when their corresponding module is absent — treat them as optional. No additional credit charge.

**22nd April 2026**

**Geo-targeting for Google Search**

The Google Search endpoint now supports two parameters for precise geo-targeting of search results:

* **`location`**: City-level targeting using [Google canonical location names](https://developers.google.com/google-ads/api/reference/data/geotargets) (e.g., `New York,New York,United States`). Choose from \~100,000 supported locations worldwide
* **`uule`**: Advanced targeting using pre-encoded Google UULE strings for users who generate their own UULE values

Both parameters work alongside `country` for precise localization. They are mutually exclusive -- provide one or the other, not both. No additional credits required.

Learn more in our [Google Search documentation](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md#uule-geo-targeting).

**9th February 2026**

**Sponsored ad extraction for Google Search**

Google Search endpoint now automatically extracts sponsored ad results from search results pages.

**Features**:

* **Ad placement tracking**: Ads are extracted from both top and bottom of search results with `blockPosition` indicating placement
* **Complete ad details**: Title, URL, displayed URL, domain, description, and position within ad block
* **Ad sitelinks**: Extended ad sitelinks with titles, URLs, and descriptions when available
* **Multi-page support**: Ads are extracted across all requested pages

**Response structure**:

```json theme={null}
{
  "result": {
    "ads": [
      {
        "position": 1,
        "blockPosition": "top",
        "title": "Best Programming Laptops - Shop Now",
        "url": "https://example.com/programming-laptops",
        "page": 1,
        "displayedUrl": "example.com/laptops",
        "domain": "example.com",
        "description": "Shop our selection of high-performance laptops...",
        "sitelinks": [
          {
            "url": "https://example.com/gaming-laptops",
            "title": "Gaming Laptops",
            "description": "High-performance laptops for gaming"
          }
        ]
      }
    ]
  }
}
```

No additional parameters required. Ads are automatically included when present on search results pages.

Learn more in our [Google Search documentation](https://cloro.dev/docs/api-reference/endpoint/google/sponsored-ads.md).

**5th February 2026**

**Updated Google Search pricing structure**

We've updated the Google Search endpoint baseline pricing to a more predictable tiered structure for multi-page requests.

**What's changed:**

* **Multi-page pricing** is now tiered instead of per page:
  * 2-3 pages: +1 credit (was +2-4 credits)
  * 4-10 pages: +2 credits (was +6-18 credits)
* **Base cost and AI Overview** remain unchanged:
  * Base request: 3 credits
  * AI Overview addon: +2 credits

**New pricing examples:**

* 1 page, no AI Overview: **3 credits** (unchanged)
* 1 page, with AI Overview: **5 credits** (unchanged)
* 3 pages, with AI Overview: **6 credits** (was 9 credits)
* 10 pages, with AI Overview: **7 credits** (was 23 credits)

Costs are more predictable, with reduced pricing for bulk multi-page extraction.

**23rd January 2026**

**Google Search and AI Mode updates**

We've updated the Google Search and AI Mode endpoints:

**Removed parameters:**

* `city` parameter temporarily removed from Google Search and AI Mode endpoints
* No customers were using this parameter, and `country`-level localization was sufficient for all use cases

**New parameter:**

* `device` parameter added to AI Mode endpoint
* Options: `desktop` (default) or `mobile`
* Same device targeting available in Google Search

**11th January 2026**

We've expanded our geographical coverage across all Google endpoints:

* **Google Search**: Now available in all 250 countries worldwide
* **AI Mode**: Expanded from 58 to 211 countries
* **AI Overview**: Expanded from 59 to 230 countries

Remember to check the [model-specific country list](https://cloro.dev/docs/api-reference/endpoint/countries.md) before deploying to ensure availability for your target endpoint.

**17th November 2025**

**New Google Search endpoint**

We're excited to announce the launch of our Google Search endpoint (`/v1/monitor/google`) for extracting structured data from Google search results.

**Features**:

* **Organic results** - Extract titles, links, snippets, and positions from search results
* **People Also Ask** - Capture questions and answers with page tracking
* **Related searches** - Get related search query suggestions
* **AI Overview** - Extract Google's AI-generated summaries with source attribution (optional)
* **Multi-page scraping** - Scrape up to 10 pages per request with the `pages` parameter
* **Country-specific results** - Localized search results across many countries
* **Hyperlocal targeting** - City-specific search results using canonical city names with automatic UULE conversion
* **Raw HTML access** - Option to retrieve full page HTML for custom parsing

**Usage example**:

```json theme={null}
{
  "query": "best laptops for programming",
  "pages": 3,
  "country": "US",
  "include": {
    "aioverview": {
      "markdown": true
    }
  }
}
```

Learn more in our [Google search documentation](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.