Asking the ChatGPT and Gemini apps
What it is
Everything else on the AI Visibility page asks the AI engines through their APIs: the same companies' models, called directly on your own AI keys. That is repeatable, and it is how your visibility score is measured, but it is not the ChatGPT app or the Gemini app a person types into. The apps decide for themselves whether to search the web, run their own searches and show their own sources. This lets you ask the apps themselves. Switch it on for a project and each of its tracked prompts is also put to the ChatGPT app, the Gemini app, or both. We do not ask them ourselves: DataForSEO, a data provider, asks the apps through their own web pages, so each answer is the one a person using the app would be given, asked from the place you set for the project. DataForSEO does not say whether it asks signed in or signed out, so someone signed in with their own history may be shown something different. It is for tracked prompts only. Your visibility runs, your visibility score and your engines' tracked-prompt figures stay exactly as they are.
Before you switch it on: two things to set up
1. YOUR DATAFORSEO LOGIN, IN SETTINGS. The apps are asked on your own DataForSEO account, never ours. Open Settings (your account's Settings, not AI Settings) and go to API Keys. In the DataForSEO box - headed "DataForSEO — AI Overviews and the ChatGPT and Gemini apps" - fill in your DataForSEO account email and your DataForSEO API password, then press Save API Keys. Use the API password from your DataForSEO dashboard, not the base64 string in their welcome email. If you already watch Google AI Overviews, it is the same login and there is nothing more to add. You need an account at dataforseo.com with credit on it: their minimum deposit is $50, and their credit does not expire. 2. A LOCATION ON THE PROJECT, IN MANAGE PROJECT. Open the project and press Settings - the project's own settings page, which the switches call Manage Project. In the Target keywords section, fill in Target location - a town, region or country, for example "Leeds, UK" - and press Save keywords. Saving checks the place against DataForSEO's own list of places, on your DataForSEO login, so add the login first. Under the field we say how it reads; where it fits several places, pick the one you mean, and your own wording stays as you typed it. What each app takes from the location: • THE CHATGPT APP is asked from the COUNTRY your location is in. DataForSEO can ask ChatGPT only from countries (and a few regions), not from towns, so a project in Leeds is asked from the United Kingdom. • THE GEMINI APP is asked from the PLACE ITSELF. DataForSEO can ask Gemini from towns as well as countries, so a project in Leeds is asked from Leeds. No location means nothing is asked. There is no default place: we ask the apps from the place you choose, never one we pick. AI Overview checks work differently - with no location they are read from the United States - but the apps never are.
The two switches, and what each line says
They are on the AI Visibility page (Reports & Tracking → Visibility), on the Tracked prompts card, under the box where you add a prompt: "Also ask the ChatGPT app" and "Also ask the Gemini app". Each is off until you tick it, and each belongs to one project: switching an app on for one project does not switch it on for any other. Beside a switch you can tick, the line says where the app is asked from and about what it costs you a month, for example: "Also ask the ChatGPT app - through DataForSEO, from United Kingdom, on your DataForSEO credit: about 10 cents a month." The monthly figure is worked out from this project's tracked prompts as they stand - how many, how often each is asked, and leaving out any you have paused - so it moves when you add, remove or pause a prompt. With no prompts it says so.
Why a switch is greyed out
When a switch cannot be ticked, the reason is written under it in amber. These are the reasons, in the words the card uses, and what to do about each: • "Add your DataForSEO login in Settings first: app answers run on your own DataForSEO account." - add the login (step 1 above). • "This project has no location set. We ask the apps from the place you choose, never one we pick." - set a Target location (step 2 above). • "This project's location "..." has not been checked against DataForSEO's list of places yet." - open Manage Project and press Save keywords: saving checks it. You see this when the location was saved before the DataForSEO login was added. • "This project's location "..." is not a place on DataForSEO's list. Edit it under Manage Project." - change the wording, or pick one of the places offered under the field. • "DataForSEO refused this project's location "...". Edit it under Manage Project." - DataForSEO turned the place down when it was sent. Save the location again, or choose another. • "ChatGPT app cannot be asked from (the country): it is not on DataForSEO's list of places for ChatGPT." - DataForSEO cannot ask ChatGPT from that country. The Gemini app may still be asked. • "ChatGPT app: DataForSEO's list of places for ChatGPT could not be read, so it is not asked this time." - usually passing. When DataForSEO was only slow to send it, opening the page again in a few minutes is enough. When it could not be read at all, it is not asked for again for 30 minutes, so the switch can stay greyed out for up to half an hour. The Gemini app does not need this list. • "DataForSEO does not take (the place) for the ChatGPT app [or Gemini app]. Edit the location under Manage Project." - DataForSEO refused that place for that app when we asked. We do not send it again until you change the location (after 40 days it is tried once more, in case DataForSEO has started taking it). While your account is active, a switch that is already on can always be switched off, even while it is greyed out.
After you switch one on
QUESTIONS GO OUT FROM THE NEXT CHECK. We check every 15 minutes, and from the next check each tracked prompt of the project that is not paused is sent to the app. A check sends a set number of questions across everyone's projects, so when many are waiting at once - for example just after several projects are switched on - some of yours go out at the checks that follow. After that, each prompt is asked again on its own schedule - daily, weekly or monthly, the same as you chose for it - counted from when that app last asked it. The apps keep their own schedule: your engines' answers and the apps' answers never wait for each other. A prompt you add later is sent to the app from the next check. ANSWERS COME IN AS DATAFORSEO RETURNS THEM. The questions are queued with DataForSEO, which is what keeps the price down, and DataForSEO does not promise a time. We collect every 15 minutes, and until an answer is in, the prompt's line says "answer not in yet". AFTER 12 HOURS WITHOUT AN ANSWER, IT IS WRITTEN OFF. The prompt's line then says "no answer last time:" with the reason - "DataForSEO had not answered after 12 hours." - and the history lists it with the same reason. The question was paid for when it was sent, so it counts as asked and is not sent again before its next turn. OTHER REASONS. Anything else after "no answer last time:" is the reason in DataForSEO's own words - for example when your DataForSEO account has run out of credit - or in ours, such as "The app's answer was empty." When DataForSEO turns a question down because of your account (the login, or no credit), nothing more is sent for your account for six hours, so a lapsed account is not refused four times an hour. A question turned down before DataForSEO took it was not paid for, and is tried again after six hours.
Reading the answers
Each app has a line of its own under the prompt, with a dashed edge, apart from your engines. For example: "ChatGPT app, via DataForSEO, from United Kingdom: named in 1 of 4 answers, cited in 0 (1 more asked a question back) · last asked 4 Oct" • NAMED is how many of the app's answers named your business; CITED is how many cited a page of your site. Both are counts out of the number of answers, never a percentage: a percentage of four answers would claim more than four answers can say. • A small chip shows the latest answer, for example "ChatGPT app (asked 4 Oct): named #2" - the number is where your name came in the answer. Point at the chip to see the model, as DataForSEO reported it. • Open the prompt's history (the clock button, "Answers so far") and the apps' answers have their own section, "The ChatGPT and Gemini apps, through DataForSEO", under your engines' answers. Each opens to show the model as DataForSEO reported it, the whole answer, WHAT IT CITED (your own pages marked "your site"), and, for the ChatGPT app, the pages its search LOOKED AT and did not cite - with yours named - and the SEARCHES IT RAN. The Gemini app reports only what it cited. • Each answer keeps the place it was asked from, shown beside it. The counts on the line take in all of an app's answers to the prompt, so if you change the location, the history says which answer came from where. • Search every answer, at the foot of the card, finds the apps' answers too, labelled "App (via DataForSEO)". Each answer is read by the same rules as your engines' answers - whether you were named and where, whether your site was cited - so "named" and "cited" mean the same thing on both. Reading it is done by those rules, not by an AI model, so nothing is spent on your AI keys. What the apps' answers are never part of: your visibility score, your visibility runs, the tracked-prompt figures from your engines (the "named in X of Y answers" on the prompt's own line), any rate and any trend. Each app is its own line: the ChatGPT app is never added to the OpenAI engine, nor the Gemini app to the Gemini engine, because they are different products answering in different ways.
When an app asks a question back
Sometimes an app does not answer. It asks something back, or offers to answer a narrower question instead - "If by entity SEO you mean platforms for ..., I can compare the leading options." An answer like that named nobody because it answered nothing, so calling it "not named" would count against you for no reason. So it is counted apart. It is left out of the answers the counts are out of, and the line says how many there were: "(1 more asked a question back)". In the history it reads "asked a question back instead of answering", with the text, and it is left out of Search every answer. An answer is set aside only when it is short (under 400 characters), cited nothing, ran no search, and either ends with a question or has words anywhere in it that ask or offer something back - "if you mean", "if by", "would you like", "do you want", "can you tell me" and the like. So a short answer that begins "If you mean ..." and then names only other businesses is set aside too. It is never set aside when it names your business: an answer that names you counts as an answer, whatever words it uses.
What it costs
About $0.0012 a question, on your own DataForSEO credit, billed by DataForSEO. Each tracked prompt is one question to each app you switched on, every time it is asked: • 20 weekly prompts, one app: about 80 questions a month - about 10 cents. • 20 daily prompts, one app: about 600 questions a month - about 72 cents. • Both apps: twice that. The card shows each app's estimate for the project beside its switch before you tick it. It is NOT part of your AI Overview budget. The monthly budget on the AI Overview page covers AI Overview checks only. The apps are extra, on the same DataForSEO credit, and they stop when you switch them off, pause the prompts or remove them, and while your account is read-only (see "Switching it off"). Nothing is spent on your AI keys for the apps.
One answer is one moment: read them over weeks
The apps' answers change from one asking to the next. The same question asked twenty minutes apart can name different businesses and cite different sites, and the app decides for itself each time whether to search. So one answer tells you little, and the counts are what to read - over weeks, not days. A weekly prompt gives each app about four answers a month: give it a month or two before reading a change into it. If you want more readings, ask the prompt daily; that is more questions, and the card's estimate says how many cents more. The model behind each app also changes whenever OpenAI or Google change it. Each answer shows the model as DataForSEO reported it, so you can see when it moved.
Switching it off
Untick the switch on the Tracked prompts card. Nothing more is sent from the next check, and the answers so far are kept: the line and the history stay. A question already sent before you switched off may still come in, and is filed like any other. You can also pause a single prompt with the pause button on its row: a paused prompt is asked of neither your engines nor the apps, and the monthly estimate leaves it out. Removing a tracked prompt removes its app answers with it. WHILE YOUR ACCOUNT IS READ-ONLY - after a trial ends without a subscription, or once a cancelled subscription has run out - nothing more is sent to either app, whatever the switches say, so nothing more is spent on your DataForSEO credit. A question already sent is still collected and filed. A read-only account cannot change the switches or the prompts, so they stay as they were, and once the account is active again the questions that are due go out from the next check.
Set the DataForSEO login first and the location second: saving the location is what checks it against DataForSEO's list of places. Then switch an app on. An answer DataForSEO has not returned within 12 hours of its question going out is written off with the reason; one that came back but could not be read is tried again at each check and written off after 24 hours.