Answer Radar / Search Console

Ground your AI visibility prompts in what buyers actually typed

Every tracker asks you to pick the prompts it measures. Answer Radar reads your own Google Search Console first, so the prompt set starts from the questions that already carry impressions rather than the ones you imagined.

Start tracking The recorded playbook

Updated 2026-09-04

What Search Console grounding is

First-party demand data, next to what the engines said.

Connecting Search Console gives Answer Radar the queries real buyers used to reach your site, with impressions, clicks and average position. It is first-party demand rather than a guess. The connection is not a Google login: you add Linkeddit's read-only service-account address as a user on your own property, and Answer Radar verifies it can read it. The gsc_queries_get tool then returns the queries ranked by impressions, so you can decide which buying questions are worth measuring, strike proposed prompts nobody types, and find high-impression questions where the site ranks poorly.

The real response, run on 4 September 2026 on our own project

Our linkeddit.com project was not connected to Search Console when we ran this. The tool refused to guess, and that refusal is the point.

gsc_queries_get({
  project_id: "<your project id>",
  days: 28,
  limit: 50
})

Through the Linkeddit MCP connector. project_id is your project.

gsc_queries_get, verbatim

connected: false
queries: []
explanation: This project has no Google Search Console connection, so there is no first-party search data to report. This says nothing about the site's search demand. Connect it from the project's page in Linkeddit, which asks you to add Linkeddit's address as a user on the property in Google Search Console.
when connected: From the tool contract: the query, its impressions and clicks, and its average position, ranked by impressions, over the number of days you ask for (28 by default).

An empty list plus connected false plus a sentence saying it says nothing about demand is what an honest data tool returns. Zero rows without the flag would let a client conclude nobody searches for you.

Connecting it, in four steps

No OAuth redirect, no stored credential, one address added as a user on your own property.

Step 1

Copy the address

On the project's Overview, the Search Console panel shows Linkeddit's service-account address. It begins linkeddit-search-console, so it reads as unmistakably us in your Google account.

Step 2

Add it as a user in Google

In Search Console, open the property for the domain the project tracks, then Settings, then Users and permissions, and add the address. Restricted permission is enough for reading.

Step 3

Check for properties

Back in Linkeddit, press Check for properties and choose the one for this project. Answer Radar verifies it can actually read the property with the read-only scope before it reports anything.

Step 4

Ask for the queries

gsc_queries_get returns the queries real buyers used to reach the site, with impressions, clicks and average position, ranked by impressions. Use them to decide which buying questions are worth measuring.

Why a service account and not a Google login

The decision that makes this connection boring, which is what a connection to your search data should be.

Search Console scopes are sensitive in Google's terms. Using them through a Google login for external customers would require Google's OAuth app verification and would leave Linkeddit holding and encrypting a refresh token for every customer. A service account needs none of that: you add our address as a user on your own property, which is what most SEO and AEO tools already ask for, and we never take custody of a customer credential. The scope requested is read-only. A credential that cannot write cannot be abused into writing, and a customer inspecting the grant in Google sees read only.

What it does not do

So the connection is judged on what it is.

It does not report AI Overview or ChatGPT impressions. Search Console reports Google web search; Answer Radar measures the engines separately and shows the two side by side.
It does not estimate prompt volume. No engine publishes how often a private assistant is asked a question, and the proposer will not invent a number to rank suggestions by.
It does not take custody of a credential. The grant lives in your Google account, is read-only, and is removed there.
It does not connect itself. A property has to be chosen for each project after the address has been added as a user.

Frequently asked questions

What does Google Search Console have to do with AI visibility?+

It is the only first-party record of what buyers actually typed to reach your site. Every AI visibility tracker asks you to pick the prompts it measures, and a prompt set picked from imagination measures the wrong things confidently. Search Console shows the questions that already carry impressions, where you rank poorly on them, and which phrasings are real. Answer Radar reads that through gsc_queries_get and uses it to sanity-check a prompt set before you spend credits on it.

Why did the tool return no data on your own project?+

Because we had not connected Search Console to our linkeddit.com project when we ran it. The response was connected false, an empty list, and a sentence saying this says nothing about the site's search demand. We printed that rather than a connected example from another account, because a tool that returned zero rows without the flag would let you conclude nobody searches for you.

Do I have to give Linkeddit my Google login?+

No. There is no OAuth redirect and Linkeddit never holds a customer credential. You add our service-account address as a user on your own property inside Google, with the read-only Search Console scope, and you can remove it at any time from the same screen. That is the same grant most SEO tools ask for.

Does Search Console show how I appear in AI Overviews or ChatGPT?+

Not as a separate report you can read through this tool. Search Console reports Google web search queries, impressions, clicks and position. What Answer Radar adds is the measurement of what ChatGPT, Gemini, Perplexity and Claude actually answered on those same questions, so the two sit side by side: what buyers typed, and what the engines said.

What does the connected response contain?+

Per query: the query text, impressions, clicks and average position over the window you ask for, 28 days by default, ranked by impressions. Use a high-impression, low-position query as a candidate prompt; use the list to strike proposed prompts nobody types.

Can I do this from Claude or Cursor?+

Yes. gsc_queries_get is a tool in the Linkeddit MCP connector, and the recorded playbook walks the whole sequence from any client: ask for the queries, get the honest not-connected answer, connect, and check the prompt set against the result.

Start from the questions buyers already ask

Search Console grounding is part of Answer Radar, included with the Compete plan, in the browser and through the MCP connector.

See pricing How Answer Radar works