Looker Studio for SEO + GEO: One Dashboard for Search and AI

What changed in SEO reporting

The rules of search visibility have split in two. One half still lives in Google's traditional index - rankings, clicks, impressions. The other half now lives inside AI-generated answers from ChatGPT, Perplexity, Gemini, and Google's own AI Overviews. Your dashboard needs to track both, or stakeholders are reading half a report.

Analytics dashboards make it quick and easy to understand real-time business performance in a particular area. This means stakeholders can track progress toward goals without having to dig through lots of data. Or ask colleagues for custom reports. Semrush - semrush.com/blog/analytics-dashboard

AI Overviews now appear in 25.11% of Google searches, up from 13.14% in March 2025, based on Conductor's analysis of 21.9 million queries. ChatGPT reaches over 800 million weekly users. If your reporting dashboard only tracks traditional SEO metrics, you are measuring half the picture.

Most dashboards fail not because they lack data but because they lack structure. They either overload stakeholders with vanity metrics, mix incompatible data sources, or hide the signals that actually matter. An effective SEO dashboard is not about showing more data - it is about structuring the right data so you can act on it. What follows is the practitioner's architecture for a Looker Studio dashboard that unifies traditional SEO performance with Generative Engine Optimization (GEO), giving you a single reporting surface for both channels.

Looker Studio remains the best free tool for this job for three reasons. It ingests data from any source - Google or third-party. Cross-data-source filtering now lets one filter override field IDs across all sources, which was previously impossible. And Gemini AI for Looker Studio introduces a Formula Assistant for calculated fields in natural language plus Conversational Analytics for querying data in plain English. These remove the two biggest friction points that once pushed teams toward paid BI tools.

When and how to set up the dashboard

This is current best-practice architecture as of late 2025. The connectors, calculated fields, and GA4 channel grouping logic described below are all in production and available today. No private beta required.

• Looker Studio platform: Free tier covers everything in this dispatch. Pro plan ($9/month) adds scheduled email delivery and team management - useful for agencies but not required.
• GSC Search Console connector: Native, free, and live. Has two modes (Site Impression for query data; URL Impression for page data) - you need both data sources.
• GA4 connector: Native, free, and live. Pair with a custom channel group for AI referral tracking.
• Third-party data via Google Sheets: For rank tracking from Ahrefs, Semrush, or SE Ranking. Export weekly to Sheets, connect Sheets to Looker Studio. Refreshes automatically.
• GEO-specific data: Profound, Peec.ai, Frase AI Visibility, and SE Ranking's AI visibility module can feed citation data into Google Sheets and then into Looker Studio.

The dashboard needs three conceptual layers, not 30 charts. The executive summary at the top is a row of scorecards - organic sessions, revenue, AI referral traffic, trend arrows - readable in five seconds. The middle layer is the blended SEO performance detail (GSC query data, ranking distributions, CTR by position band, GA4 engagement). The bottom layer is the GEO visibility section: AI referral traffic volume and trend, landing pages cited by AI platforms, branded search as an AI awareness proxy.

Who needs this dashboard most

The value scales with the complexity of your reporting audience and the diversity of your traffic mix. Agencies and in-house teams with multiple stakeholders gain the most; solo SEOs operating one site can run a lighter version.

One caveat across all segments: you must start by defining what success looks like before you touch a chart. What results do you want to see after investing in SEO? What does a win look like in AI search? If you cannot articulate either, you are not ready to build the dashboard - you are ready to write the brief.

What to build this week

Priority order: get the data sources connected correctly, set up the AI referral channel before you touch any chart, blend GSC and GA4 on Landing Page, then drop scorecards at the top. Five actions, in order:

1. Connect GSC with both data tables, not just one. In Looker Studio, click Create > Report > Add Data > Google Search Console. Select your property, then add "Site Impression" (gives you query-level data). Repeat the connector setup and add "URL Impression" (gives you page-level data). Most tutorials only show one. You need both, or you cannot combine queries and landing pages in the same view.
2. Add GA4 and immediately filter to organic only. Your SEO dashboard should not be polluted with paid social, referrals, or PPC. Apply a default Session medium filter of "organic" at the data source level. This also gives you the engagement metrics GSC cannot provide: sessions, engaged sessions, key events, engagement rate, average engagement time per session.
3. Create the AI Traffic custom channel group in GA4 before doing anything else. In GA4, go to Admin > Data Display > Channel Groups. Create a new channel called "AI Traffic" with a regex condition: chatgpt\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|chat\.openai\.com|bard\.google\.com|meta\.ai. Critically: drag your new channel to the TOP of the list, above Organic Search and Referral. GA4 processes rules sequentially - if you skip this step, AI traffic gets swallowed by earlier rules.
4. Blend GSC and GA4 on Landing Page with a calculated field. GSC returns full URLs (https://example.com/page/); GA4 returns path-only values (/page/). The join will fail until you create a calculated field in GA4 that concatenates hostname + landing page path. Then blend the two sources. The output table - Landing Page, GSC Clicks, GSC Impressions, GSC CTR, Average Position, GA4 Sessions, Engagement Rate, Key Events - will drive 80% of your optimization decisions.
5. Drop scorecards across the top with comparison periods. Use the scorecard component for organic sessions, revenue, AI referral traffic, and total key events. Set comparison to "previous period" (MoM) or "previous year" (YoY). Every number needs context. A scorecard without comparison is a number on a billboard.

What to build this quarter

Once the core dashboard is live, the quarter-long work is layering on the GEO visibility section, the calculated fields that turn raw data into strategy, and the dark-AI-traffic transparency annotations that build stakeholder trust.

Build the GEO visibility layer

Traditional SEO optimizes for rankings and clicks. GEO optimizes for mentions, citations, and recommendations inside AI-generated answers. Your dashboard needs both. Track AI referral traffic volume and trend (from the channel group you set up in Chapter 4), AI referral landing page analysis (which specific pages get cited - this is the most actionable finding in the entire exercise), and a conversion comparison scorecard showing rates for Organic vs AI Referral vs Direct. AI traffic converts at roughly 4.4x the rate of traditional organic visitors based on cross-account observation, so isolating that channel for reporting changes how executives perceive AI search.

Annotate the dark AI traffic problem on the dashboard itself

Be honest with stakeholders about measurement limitations. ChatGPT began appending utm_source=chatgpt.com to citation links in June 2025, making some attribution automatic - but Google AI Overviews, AI Mode, and mobile app referrals from most LLMs still pass no attribution at all. Your GA4 AI traffic numbers are a floor, not a ceiling. True AI referral traffic is likely 2-3x higher than what GA4 reports. Build a text annotation on the dashboard stating this clearly. Transparency about data limits builds stakeholder trust faster than inflated absolute numbers.

Add four calculated fields that change how stakeholders read the data

Brand vs non-brand classification using CASE WHEN with REGEXP_MATCH on your GSC query dimension. Rising branded query volume is one of the strongest AI visibility proxies you can build without external tools. Content type grouping (Blog, Product, Category, Landing Page) using CASE WHEN with REGEXP_MATCH on page paths - this reveals which content types earn AI citations vs traditional clicks. Ranking tier buckets (1-3, 4-10, 11-20, 21-50, 50+) trended over time as a stacked bar chart - momentum that raw position averages hide. And Revenue per Click for ecommerce (GA4 revenue divided by GSC clicks) to identify the highest-leverage pages for optimization investment.

Respect visualization discipline

Not every data point deserves a chart. Scorecards at the top, scatter charts (Average Position on X axis, Clicks on Y axis, CTR as bubble size) to identify low-hanging-fruit opportunities, and a small number of trend lines for the metrics that actually drive decisions. One performance note: calculated fields in Looker Studio run in the reporting layer, not in BigQuery. Complex calculations on large datasets get slow. If a calculated field is making the dashboard sluggish, move the calculation to a BigQuery view instead and let Looker read the precomputed result.

What we're seeing in real accounts

Note: the patterns below are aggregated from Looker Studio audits we have run for ecommerce and B2B clients over the past two quarters. The dominant finding: most dashboards we inherit are technically functional but strategically inert - they show data without surfacing the decisions that data should drive.

A second pattern across multiple accounts: AI referral traffic hiding in the generic "Referral" bucket. On three different ecommerce dashboards we audited in Q3 2025, ChatGPT and Perplexity were collectively driving 3 to 8 percent of total sessions but none of it had been surfaced - the AI channel grouping was simply absent. Once we added the regex-based AI channel group and dragged it above Organic Search in GA4 priority order, the conversion-rate comparison scorecard immediately showed AI traffic converting at multiples of organic. That single chart changed how leadership talked about AI search budget allocation.

Counterexample: a B2B SaaS client with strong content marketing had implemented the AI channel grouping correctly but never trended branded search alongside it. After adding the branded-versus-generic split using CASE WHEN with REGEXP_MATCH on GSC queries, the team discovered branded queries had grown 28% over six months - a strong AI visibility proxy that had never been reported to leadership. The dashboard architecture problem was not data quality. It was that the right metric was not on the page.

What we're still watching

Four open questions are driving how we sequence Looker Studio + GEO build work into 2026.

• AI Overviews attribution: Google currently passes no referrer attribution for clicks originating from AI Overviews or AI Mode. Whether Google introduces native attribution (or a paid utm-style parameter equivalent) will determine how much of the "dark AI traffic" problem actually closes vs requires permanent proxy metrics.
• LLM mobile-app utm coverage: ChatGPT began appending utm_source=chatgpt.com to citation links in June 2025, but mobile app referrals still pass no attribution. Whether Perplexity, Gemini, and Claude follow suit - and whether mobile coverage lands - will reshape how much trust the GA4 AI Traffic channel deserves.
• Native AI channel category in GA4: Whether Google introduces a built-in "AI Search" or "Generative AI" channel category in GA4, or whether custom channel groupings remain the only path. A native category would standardize reporting across the industry; the custom approach keeps configuration in operator hands.
• GEO data feed consolidation: Profound, Peec.ai, Frase AI Visibility, and SE Ranking are all maturing as GEO citation trackers. Which becomes the consensus data feed for Looker Studio - via Sheets or a native connector - will determine whether AI citation data becomes table-stakes in dashboards or remains a premium add-on.