GEMINI LABJP
0918 — The Gemini API changelog has no entries after September 18. For new projects the recommendation is still 3.5 Flash-Lite or 3.8 Flash09/30 — gemini-omni-flash-preview shuts down on September 30, six days away. Its successor is gemini-omni-1.1-flashENTCLI — An open question asks why Gemini 3.5 and 3.6 Flash have not reached Gemini CLI on Enterprise accounts, and the gap with personal accounts is still unexplainedNEW — The day I first removed a connected MCP server, and how I now pick the tools that stay onCONFIG — Since Antigravity 2.17.0, repository settings load from .gemini/config.json, the same .gemini/ folder Gemini CLI already usesPICKER — When a familiar model disappears, check what your own model picker actually lists first. It keeps an access limit from being mistaken for an outage0918 — The Gemini API changelog has no entries after September 18. For new projects the recommendation is still 3.5 Flash-Lite or 3.8 Flash09/30 — gemini-omni-flash-preview shuts down on September 30, six days away. Its successor is gemini-omni-1.1-flashENTCLI — An open question asks why Gemini 3.5 and 3.6 Flash have not reached Gemini CLI on Enterprise accounts, and the gap with personal accounts is still unexplainedNEW — The day I first removed a connected MCP server, and how I now pick the tools that stay onCONFIG — Since Antigravity 2.17.0, repository settings load from .gemini/config.json, the same .gemini/ folder Gemini CLI already usesPICKER — When a familiar model disappears, check what your own model picker actually lists first. It keeps an access limit from being mistaken for an outage
Articles/Gemini Basics
Gemini Basics/2026-09-24Beginner

Before You Send a Gemini Draft, Run Double-Check and Fix Only the Orange Sentences

A short routine for using the Gemini app's double-check feature right before you send an email or reply: what green, orange, and unhighlighted sentences mean, the order I use to fix orange ones, and when even green deserves a second look.

Gemini appdouble-checkfact-checkingGoogle Search3

It was a Sunday morning when a support email arrived from someone using my wallpaper app. When they set an image on the lock screen, they wrote, it looked slightly shifted.

I asked the Gemini app to draft a reply, and a polite English answer came back in seconds: an apology, a guess at the cause, and one iPhone setting to try. I pasted it into my mail client, and my finger was already over the send button when I stopped.

I had never checked, on my own device, the one sentence that told the user where to find that setting.

On a whim I opened the menu under the response and ran double-check. That exact sentence, and only that one, came back highlighted in orange. When I walked through the steps on my own iPhone, the path was off by one screen. Had I sent it, I would have sent a frustrated person on a second detour.

Double-check is one tap from the menu under a response

Double-check compares the sentences in a Gemini response against Google Search results and marks them with color. There's nothing to set up.

  1. Open the response you want to verify in the Gemini app (web or mobile)
  2. Among the icons under the response, open the more menu (the three dots)
  3. Choose the option that checks the response with Google Search. The label may read "Double-check response" or something close to it, depending on your screen and when you read this
  4. Wait a few seconds, and some sentences will be highlighted
  5. Tap a highlighted sentence to see the search result it was compared against

On some work or school accounts, or with certain language settings, the option may not appear at all. If you can't find it, trying the same prompt on a personal account is the quickest way to tell whether it's your account or the feature.

What green, orange, and no color actually mean

There are only three states. I made the mistake of memorizing them as "green is right, orange is wrong," and that shortcut cost me more time than it saved.

HighlightWhat happened in Google SearchHow I treat it
GreenA page with similar content was foundOpen the link and check only the date and who wrote it
OrangeContent that is likely different was found, or nothing relevant was foundVerify it myself before sending, then fix it or cut it
No colorNot enough information to evaluate, or the sentence isn't a factual claimIf it contains a number, a name, or a step, treat it like orange

Orange mixes two different situations: "this looks wrong" and "this couldn't be checked." And no color does not mean "fine." Greetings and apologies naturally stay unhighlighted, but a step or a figure with no color is Search telling you it couldn't back that sentence up either.

The order I use to fix an orange sentence

When something turns orange, the tempting move is to ask Gemini, "Is this correct?" I did that at first. What usually came back was the same claim in different words, which didn't help much.

These days I work through it like this:

  1. Tap the orange sentence and open the page it was compared against. Often the disagreement is obvious right there
  2. Decide whether the sentence is a fact about the world, or a fact about my own product or situation
  3. If it's about the world, confirm it against an official help page or primary source and rewrite it
  4. If it's about my own product or setup, Search can't confirm it. I walk through it on the real device or in the real dashboard and rewrite from what I see
  5. If I can't confirm a sentence, I delete it. A reply still works with one sentence fewer; a wrong sentence can't be taken back once it's sent

That Sunday email was a step-four case. The screens in my own app, and the exact path through a particular iOS settings flow, simply don't have much for Search to match against. The orange wasn't Gemini lying so much as Gemini saying something Search had no way to confirm.

When even green deserves a second look

There are also times I slow down on green. Three of them, mostly.

The first is anything tied to a date: prices, availability, supported versions. An old page can match an outdated claim perfectly and still turn it green. Glancing at the page's last-updated date catches most of these.

The second is when the linked page isn't a primary source. If several roundup articles have copied the same mistake from each other, Search sees agreement where there's really just repetition. I check whether I can trace the claim back to an official help page or the provider's own announcement.

The third is anything about my own product. Nobody knows how my app behaves better than I do. If a sentence about it turns green, the evidence is still just someone else's page.

Facts about the world go to Search; facts about my own product go to my own hands. Double-check makes the first kind faster. It was never meant to carry the second kind for me, and that's the line I keep.

Making the thirty-second check a habit

What finally made this stick was deciding in advance how little I would check. Rereading the whole draft every time never lasted. Now I look at just these four lines before I send a reply:

[Before sending]
1. I ran double-check (or, if the option wasn't there, I marked every step, number, and name myself)
2. Every orange sentence is fixed or deleted
3. Unhighlighted sentences with steps, numbers, or names have been verified
4. Green sentences involving dates: I looked at the linked page's update date

I keep those four lines in a notes app and run a finger down them right before I hit send. Once it's familiar, it takes about thirty seconds, and I've been surprised how many small mix-ups those thirty seconds catch.

When what you need to verify is Gemini's own judgment, such as a classification or a tag rather than a factual claim, matching against Search isn't the right tool. I wrote about a different approach for that in I Stopped Asking Gemini 'Is This Right?' and Started Hiding My Answer Instead, in case you want to build the check into a workflow rather than do it by hand.

For now, the next time you're about to send a reply that Gemini helped you draft, try tapping double-check once from the menu. If nothing turns orange, you can send it with a lighter heart. Since that Sunday morning, it's the one small step I haven't skipped.

Share

Thank You for Reading

Gemini Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • Copy-paste ready implementation code
  • New advanced guides published daily
  • $5/mo or $15 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

Gemini Basics2026-09-20
Three Lines Decide Who Gets Images in the Gemini App: 13, 18, and Your Administrator
When the image entry point is missing from the Gemini app, a bug is rarely the reason. Here is how the two separate age thresholds and the work or school account rules line up, and who you should actually contact.
Gemini Basics2026-09-18
Before You Split That PDF: Three Different Limits in the Gemini App
When the Gemini app refuses your PDF, file size is rarely the real problem. Here is how I tell storage, rate limits, and reading capacity apart, and what I trim before I ever reach for a splitter.
Gemini Basics2026-09-13
I edited the Drive doc, asked Gemini again, and it quoted the old sentence back
When Gemini answers from an outdated version of a Drive file, the file usually isn't the problem — the conversation is. Here's how sources stay attached for the whole conversation, why you can't remove one mid-thread, and what to do about partial reads.
📚RECOMMENDED BOOKS
Build a Large Language Model (From Scratch)
Sebastian Raschka
LLM Dev
Prompt Engineering for LLMs
Berryman & Ziegler
Prompting
AI Engineering
Chip Huyen
AI Eng
* Contains affiliate links