Most teams already report marketing performance in Looker Studio, and a number that lives in a separate tool is a number that quietly stops being discussed. The Cituna community connector puts AI visibility beside your Search Console, Analytics and ads data in the report your stakeholders already open. You deploy the connector once through Apps Script, add it in Looker Studio, and paste an API key on its key screen. After that it is ordinary Looker Studio: overall, SEO, GEO and authority scores per scan, per-engine cited counts and citation rates, share of voice, and open gaps, all filterable by brand and date range.
1. Deploy the community connector once
Open the setup guide linked on the Looker Studio card in Cituna. It walks every click for both routes: clasp from a terminal, or pasting the files into the Apps Script editor if you would rather not install anything.
This is a one-time deployment per Google account. Once it exists, every future report reuses it.
2. Add the connector in Looker Studio
In Looker Studio, create a data source and choose your deployed connector from Build your own. Looker Studio will ask to authorise it against your Google account.
3. Paste your Cituna API key
The connector asks for a key on its own key screen. Generate one under Integrations → Claude / MCP access if you have not already. It is shown once, so copy it before leaving the page.
The key is stored by Looker Studio against your data source, not in the report, so sharing a report does not share the key.
4. Filter to a brand and a date range
Optionally scope the data source to one brand and a date range. Agencies usually make one data source per client so a report can be shared without exposing the rest of the workspace (see AI visibility reports for agency clients and a sample client report).
5. Build on the fields
Available fields include overall, SEO, GEO and authority scores per scan, per-engine cited counts and citation rates, share of voice, and open gaps.
A trend of the overall score with per-engine citation rate underneath it answers the two questions stakeholders actually ask: are we improving, and where is the movement coming from.
Troubleshooting
The connector returns no rows.
Usually the date range predates the first scan for that brand, or the data source is filtered to a brand with no scans yet. Widen the range first, then check the brand filter. A brand added yesterday has one day of history, not thirty.
Looker Studio says the key is invalid.
Keys are shown once and cannot be recovered, so a partially copied key is the common cause. Generate a fresh one, paste it into the data source credentials, and refresh the fields.
Can I share the report with a client who has no Cituna account?
Yes. Looker Studio reports are shared through Google, and the viewer never needs a Cituna login. Scope the data source to that client's brand so the report cannot show anyone else's.
How fresh is the data?
It reflects your stored scans, and tracked brands re-scan daily, so a report refreshed in the morning shows yesterday's completed scan. It is not a live query against the engines.
Drafted with AI assistance from our own research and Search Console data, and reviewed by Rahul A before publishing. Rules and prices change; check the linked official source before you act.