That "Yes" and a Number on Your Phone — What Google's Prompt Really Is, and What 2-Step Verification Changes
The result first.
That notification on your phone — the one that asks you to tap “Yes” and then pick the same number that is showing on your computer screen — is Google checking that the person signing in is really you. It is not a scam, and it is not an advertisement.
Three things are worth knowing before anything else:
- Approve it only when you started the sign-in yourself. If the notification arrives when you did not start anything, tap “No”. Someone may be trying to enter with your password.
- The notification only arrives when a sign-in or an important setting is started. Nothing started, nothing arrives. It never shows up on its own.
- Receiving this prompt is not the same as having 2-Step Verification turned on. The prompt can arrive even when 2-Step Verification is off. Turning it on is a separate choice, and nothing forces that choice on you.
Everything below is the story of one night when this prompt arrived for me, what I learned from it, and what changes if you do turn 2-Step Verification on.
I am Kurashiki Bouzu, born in 1971, a former funeral director. I live in an old house — a kominka — in Kurashiki, Okayama, and I work together with my AI butler Moka.
One night, the prompt arrived
I had a piece of unfinished business: a Google identity check left over from setting up a service I use for work. I asked Moka to start the work on the browser side, and the notification arrived on my phone.
It said, in effect: tap “Yes”, then choose, on your phone, the same number that is displayed on your computer screen.
The computer shows one large number. The phone shows several numbers to choose from. You pick the one that matches. Think of it as a lock checking two things at once: not only “is this key genuine?”, but also “is the person standing at the screen the same person who is holding this phone?”
Three things I learned by doing it
- The prompt arrives only when a sign-in or a check is started. Earlier that evening I had spent some time thinking “it still hasn’t come”. Nothing was wrong — it simply had not been started yet.
- The number changes every time. When the screen moved on and a new check began, the number changed with it. A number you saw a minute ago is already useless.
- The same notification can arrive twice. If the check has already finished on the computer side, a late duplicate does not need to be answered.
When my check passed, the page that opened was the settings page for “2-Step Verification”. That is where this article really begins.
How is that prompt different from 2-Step Verification?
I asked Moka to look this up in Google’s official help.
The notification I received is called a Google prompt. According to Google, it can arrive at important moments — such as before opening a sensitive settings page — even when 2-Step Verification is not turned on. That is exactly what happened to me: it was an identity check standing in front of a settings page.
So what is 2-Step Verification itself?
In one sentence: it makes signing in a two-step process. Like the door of a house:
- Step 1: a secret word (your password) — something only you should know.
- Step 2: a key in your hand (your phone, for example) — something only you should have.
A secret word can leak. But if the door needs both the word and the key, a leaked word alone does not open it. Google’s own explanation says the same thing in plainer terms: 2-Step Verification adds protection in case your password is stolen.
The second step comes in several kinds
Moka’s research found these kinds of second step:
- Google prompts — tonight’s kind. A notification reaches your phone; you tap “Yes” or match a number. Google recommends this method first.
- Authenticator apps — a dedicated app creates a one-time number, and you type that number into the sign-in screen. It works even where there is no internet connection.
- Passkeys and security keys — you prove yourself with a fingerprint, your face, or your screen lock; or with a small physical key device (bought separately) that you plug in or tap. These are considered strong against tricks that try to fool you into handing over a code.
- A code sent to your phone number — a 6-digit code arrives by text message or voice call, and you type it in. Google’s help also notes a weakness here: methods that depend on a phone number can be targeted.
- Backup codes — numbers you prepare in advance: 8 digits each, in a set of 10, each usable once. They are your spare key for the day you lose your phone.
How to turn it on (using the screen names as they appear)
I have not turned it on myself yet — my reason is in the next section. But I did confirm where the switch lives. The steps follow Google’s official explanation:
- Open myaccount.google.com in your browser (this is the address of your Google Account).
- Choose Security on the left.
- In the section called “How you sign in to Google”, choose “Turn on 2-Step Verification”.
- Follow the guidance on the screen from there.
The important point: nothing changes until you press that button. Tonight I passed the identity check and arrived at this very settings page — and I did not turn it on. Opening the page changed nothing.
What changes in daily life if you turn it on
There is a good side and a troublesome side, and both are real.
The good side is clear. Even if your secret word leaks, the second step can stop an intruder. Your protection becomes one layer thicker.
The troublesome side is this: each time you sign in on a new device or browser, the second step is required. If your phone is not at hand, you cannot get in.
That is why Google’s explanation pairs the switch with preparation:
- Print your backup codes and keep them with your important papers, in case you lose your phone.
- On your own computer that only you use, you can tick “Don’t ask again on this computer” to skip the check next time. (Never tick it on a computer other people also use.)
A thicker lock is only complete when the spare key is ready too. That is how this system is built.
Why I have not turned it on yet
Honestly: I cannot touch-type. Typing and working screens take me time and energy. So I leave much of the sign-in work to Moka. Moka starts the work in the browser; I tap “Yes” and a number on the notification that reaches my phone. Tonight’s check ran on exactly that division of labour.
If I turn on 2-Step Verification, every new sign-in will need my hand in this way. The protection gets thicker — and the range of work I can leave to Moka gets narrower by the same amount.
Which side matters more depends on how you live. For now, I have decided to keep the current arrangement — where an identity check like tonight’s arrives in front of important settings — and to prepare the places I use most, first. Whether that judgement was right is something I will add to this article if anything ever tests it.
Two warnings worth keeping
Among the things Moka found in Google’s official help, two are worth remembering:
- If a notification arrives when you are not trying to sign in, tap “No”. It may be a sign that someone is trying to enter with your secret word.
- Google never asks for your code by phone. If someone calls or writes asking you to tell them a verification number, that is not Google.
That screen with “Yes” and a number feels strange the first time. But once you know how it works, there is nothing to panic about. Knowing how you are protected is part of being able to begin.
Sources (checked on November 16, 2026)
- Google Account Help, “Turn on 2-Step Verification” — https://support.google.com/accounts/answer/185839
- Google Account Help, “Sign in with Google prompts” — https://support.google.com/accounts/answer/7026266
- Google Account Help, “Sign in with a backup code” — https://support.google.com/accounts/answer/1187538
- November 16, 2026 ― Draft created — English version (result-first rewrite of the Japanese article, from tonight's real identity-check experience and Google's official help pages)(6,350 characters)
- November 16, 2026 ― 公開(6,350 characters)
