Getting GIG's prices into Gemini

This follows straight from the thesis. Gemini and Google AI Overviews are grounded in Google's live index — where GIG already ranks. In Run 2, Google AI cited giggulf.ae 71% of the time. So unlike ChatGPT (which still leans on stale AXA-era priors), Gemini will surface GIG's own pages — if the price is on them in a form a machine can read. This is winnable.

The five moves

Make prices machine-readable. Gemini reads structured data. Add Product + Offer JSON-LD to the car-insurance pages — price / priceCurrency: AED / "starting from" for third-party and comprehensive. Insurance is quote-based, so you publish indicative "from AED X" pricing, not a live quote.
Answer the exact price question, in content. "How much is car insurance in Dubai?" is a top GIG search query. Publish a clear, structured price-range block (by car value, third-party vs comprehensive) plus FAQ schema. Gemini lifts direct, sourced answers like this almost verbatim.
Make sure a crawler can see the price. If your quote and prices only appear after a JavaScript form submit, GPTBot and Googlebot never see them. The numbers must be in server-rendered HTML. (Worth a crawl check on giggulf.ae.)
Be the cited source — or ride the ones that are. Gemini also pulls aggregators (YallaCompare, InsuranceMarket) that already publish GIG price comparisons. A feed or partnership there gets your prices in indirectly while the owned pages catch up.
Prove it with the tracker. Add price-intent prompts — "car insurance price Dubai", "cheapest third-party UAE cost" — and watch whether Gemini starts quoting GIG's numbers versus rivals'.

The honest limit

AI Overviews surface typical / range pricing from content, not live personalised quotes — and Google's own guidance is that this is standard SEO quality, not a magic schema switch. So the win is authoritative, structured, crawlable price-range content that Gemini trusts as the source — backed by the policy documents themselves (see the Motor cover comparison).