Skip to main content
See every entry.
AI Mode: one ID links shopping cards, inline products and product resultsGoogle AI Mode shopping cards, inline products and product results now have a productDocid, which is Google’s ID for the product. Entries for the same product in one response have the same value, so you can join the three blocks without a match on title, store or price.Google can change the value between responses, so do not use it to identify a product over time. The field is absent when the link from Google has no ID.
AI Mode: product tokens replace include.expandProductsGoogle AI Mode shopping cards and inline products that link to Google’s product viewer now have a productResultToken, with no flag and at no extra cost. Send it to POST /v1/monitor/google/product within five minutes to get the product’s merchant offers. Each product request costs 1 credit (3 sync), so you pay only for the products you need.include.expandProducts is deprecated. From 23rd October 2026 the API ignores it: a request that sends it still succeeds, but returns no result.productResults. Use the token.
AI Mode product results report each market’s own currencyresult.productResults[].stores[].price.currency now returns the correct ISO code for Brazil, Mexico and the UAE. Before, Brazilian offers ("R$ 5.597,99") were mislabelled as "USD", and Mexican ("MXN 19,499.00") and Emirati ("3,399.00 د.إ") offers lost their price entirely. They now return "BRL", "MXN" and "AED".A bare $ now follows the request country, so country: "CA" returns "CAD" and country: "AU" returns "AUD". Other countries keep "USD". An explicit currency token always takes priority over the country. Google Search product results also return "BRL" for R$ prices. See currency codes.AI Mode ads carry the creative image as imageUrlAI Mode ad cards now return the creative as a public https://tpc.googlesyndication.com/simgad/... URL on imageUrl. Roughly a third of AI Mode ads carry a creative; text ads without one omit the field, so treat it as optional.
The change is additive; no request parameter is needed. See the AI Mode ads schema.
Place cards carry phone and website, and placeId is now a Google IDPlace cards render Call, Directions and Website buttons. places[] and map[] now read all three, on AI Mode and AI Overview alike:
address is the full postal address from the Directions link. It used to be the short line printed on the card — a street line, a “city, region” line, or nothing at all.placeId was a hash of the title and address. It is now the place’s Google Knowledge Graph ID, the same id its map entry carries, so the two join on it. Two things change for you: the value differs from what you stored before, and it is omitted on a card Google did not geo-tag.phone and website are omitted when the card renders no Call or Website button.See the places and map schemas.
Every redirect link now ships beside its destination as redirectLinkGoogle 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:
It appears on any link field Google served as a redirect, across Google Search, Google News and AI Mode, and is the absolute form POST /v1/monitor/google/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.
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.
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 to get the destination.
Google and AI Mode: keep the raw /goto links, and a new endpoint to resolve onecloro 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 or AI Mode request and the links come back raw instead, as absolute https://www.google.com/goto?url=<token> URLs:
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.
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.
Google family: interface language with hlGoogle Search, Google News, and AI Mode take a new optional hl parameter for the interface language, independent of the country:
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 requestPerplexity 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 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 for context.
Google Search and Google News: device now accepts ios and androidThe device parameter on the Google Search and Google News 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.productResultsBoth 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 it appears whenever Google’s right-rail product panel does, with no flag and no extra credits; shoppingCards is unchanged. On Google AI Mode it is opt-in via include.expandProducts and costs +1 credit per product cluster returned, capped at +6.
Google AI Mode: 33 newly-supported countriesThe Google AI Mode endpoint now accepts 33 additional countries and territories that Google has rolled out since the last update, bringing its supported list in line with the official AI Mode availability list. Every country accepted by AI Mode is also accepted by the Google Search endpoint, so you can now freely use the same country value across both.The additions are: BL, BV, BY, EH, ER, ET, GF, GP, GU, GW, IS, KM, KZ, LK, LR, MC, MF, MO, MQ, MR, NC, PF, PM, RE, SY, SZ, TF, TZ, VA, WF, XK, YE, YT. The /v1/countries endpoint now lists them under model=aimode.
Google AI Mode and AI Overview: France (FR) is now supportedYou can now send country: "FR" to the Google AI Mode endpoint and use include.aioverview on the Google endpoint for FR requests. Previously these were rejected as unsupported regions; regular Google Search already accepted FR. The /v1/countries endpoint now lists FR under model=aimode and model=aioverview.
Google Search and AI Mode now pin to the requested country by defaultRequests to /v1/monitor/google and /v1/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.
Structured citationPills array on Google AI Overview and AI ModeBoth Google AI surfaces now emit an additive citationPills array alongside the answer text and sources. Each entry is one (pill, source) pair carrying a per-source label (the source’s own page title from the sources rail), a citationPillId that groups entries from the same chip, and per-source url/domain/description/position. Cross-provider iteration over AI surface citation pills now uses one shape.
When a pill cites N sources, the array contains N entries sharing the same citationPillId but carrying distinct per-source label, url, and domain. Group by citationPillId to recover the pill-level structure.Markdown rendering is unchanged — inline [anchor](url) links remain the canonical in-text citation form. The citationPills array gives type-aware consumers per-source access without re-parsing markdown.Additive change — existing consumers are unaffected. Learn more in the AI Overview citation pills and AI Mode citation pills documentation.
AI Overview and AI Mode markdown citations now match ChatGPTWhen you opt into markdown output, in-text citations from Google AI Overview and Google AI Mode are now rendered as standard inline [anchor](url) links in the markdown field — the same shape ChatGPT already uses.
Anchor text resolves via a deterministic fallback chain: matched source title → Google’s pill-chip label → URL host. Multi-source pills (Google’s +N chips) expand to N adjacent stacked links at the citation point. result.markdown is now fully self-contained — no parallel index resolution needed to render citations.Learn more in the AI Overview and AI Mode documentation.
More Google AI Mode fieldsThe AI Mode endpoint now returns more structured data:
  • Map: GPS-enriched location results with gpsCoordinates (latitude/longitude), type, thumbnail, and a position index
  • Places: Inline place cards with rating, reviews, type, priceLevel, address, and status
  • Shopping cards: Shopping cards now include oldPrice for discount comparison, snippet for product descriptions, and snippetLinks for related links within snippets
  • Ads: Sponsored ad sections are now parsed into a structured ads object with individual ad details including title, URL, position, price, store, rating, and reviews
  • Inline products: Product cards embedded within the AI response text are now extracted as inlineProducts, separate from shopping card carousels
Breaking change: The price and description fields have been removed from the places object. The link field now points to Google’s viewer URL format instead of the previous search URL format.
All new data is included at no additional credit charge. Learn more in the AI Mode endpoint documentation.
Hyperlocal-targeting for AI Mode with UULEThe AI Mode endpoint now supports two parameters for precise geo-targeting of results:
  • location: City-level targeting using Google canonical location names (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 AI Mode documentation.
Google Search and AI Mode updatesWe’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
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 before deploying to ensure availability for your target endpoint.
More fields extracted for AI Mode and AI OverviewGoogle AI Mode and AI Overview endpoints now automatically extract rich structured data:
  • Places in AI Mode: Location information with ratings, reviews, price levels, addresses, Google Places IDs, and operating status
  • Shopping cards in AI Mode: Structured product data with currency-aware pricing, merchant details, ratings, and purchase links
  • Video content in AI Overview: Videos with thumbnails, titles, duration, platform info, and source attribution
No additional parameters required. All structured data is automatically detected and included when available in responses.Learn more in AI Mode and AI Overview.
New dedicated endpointsEach AI model now has its own dedicated endpoint for better performance and clearer documentation:
Added Google AI ModeGoogle’s AI Mode results are now supported. You can extract structured data from ChatGPT, Perplexity, Copilot, and AI Mode using the same unified interface.To monitor AI Mode, set "model": "AIMODE" in your API requests:
All existing features work with AIMODE, including:
  • Structured data extraction with sources & citations
  • Localization across different countries
  • Markdown format support
  • Citation grouping and processing
Learn more in our API Reference.