Build a Search Console dashboard in Looker Studio

#01Which questions should this dashboard answer?

#02How do you connect Search Console?

1. Create data source > Search Console connector.
2. Authorise the Google account that owns or is a full user of the property.
3. Select the property (URL-prefix or Domain).
4. Choose Site Impression for query/country/device rollups.
5. Repeat for URL Impression for page-level rows.
6. Set owner credentials. Accept 12-hour freshness.
7. Name them GSC Site — Brand (owner) and GSC URL — Brand (owner).

If you manage many properties, prefer a property-per-source naming pattern over one overloaded source you cannot debug.

#03What belongs on each page?

Page 1 — Overview

• Scorecards: Clicks, Impressions, Average CTR, Average position (label average position carefully — it is not a rank you bid on).
• Time series of clicks and impressions for last 28 days.
• Device split bar.
• Footer: "Search Console data refreshes every 12 hours in Data Studio."

Page 2 — Queries and pages

• Query table: Query, Clicks, Impressions, CTR, Position. Default sort by Clicks. Filter control for Query (contains).
• Page table from URL source: Landing page, Clicks, Impressions, CTR.
• Optional: branded vs non-branded filter using a calculated field or Sheets classification. See Search Console branded queries filter.

Page 3 — Generative AI honesty

Google rolled the Generative AI performance report in Search Console more broadly in 2026. Dashboard it like this:

1. Weekly export (or BigQuery bulk export when you use it) into a Sheet with Date, Surface, Impressions, Clicks (use the columns your property actually shows).
2. Connect that Sheet as GSC GenAI export — Brand.
3. Scorecards for AI Mode / AI Overviews impressions and clicks if those dimensions exist in your export.
4. Text box: "Source: Search Console Generative AI performance export. Not the same as GA4 AI Assistant sessions."

Do not invent connector fields. If your connector already lists Generative AI metrics, prefer them and note the date you verified. Cross-link Search Console AI visibility connection and measurement: what Search Console AI Overviews data shows.

#04How should you talk about CTR and position?

#05Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Walkthrough

1. SEO connected Site and URL sources on day one.
2. They kept the Generative AI page on a Sheet export until connector fields were confirmed in-account.
3. A VP tried to average position across all queries; the team filtered to the money cluster first.
4. Weekly routine followed Search Console monthly routine with this report open.
5. Competitor B's dashboard mixed GSC clicks and GA4 sessions in one "organic" scorecard — Ledgerline kept them separate and won trust.

#06Property types and filters

Apply country and device filters deliberately. A global average CTR hides a broken mobile template in one locale.

#07Regex and query groups

For advanced query grouping, see Search Console filters and regex and Insights query groups. In Data Studio, heavy regex on huge query tables can feel slow — pre-classify in Sheets/BigQuery when the list is long.

#08Bulk export path

When the property is large, Search Console BigQuery bulk export beats pulling years of data through the connector for every chart. Mart views keep Data Studio snappy.

#09Click vs session teaching box

Paste on Overview:

Search Console clicks ≠ GA4 sessions.
GSC counts clicks Google attributes to your property in Search.
GA4 counts sessions on your site with its own channel rules.
A gap is normal. Investigate only when the gap suddenly changes shape.

This box alone prevents recurring Slack archaeology.

#10Common mistakes

• One Search Console source used for both query and page grains without checking which table you picked.
• Dumping 50,000 query rows into a shared table.
• Calling Generative AI impressions "ChatGPT traffic".
• Ignoring the 12-hour freshness when someone screenshots at 10:00 and compares to the UI.
• Average position as a KPI without a query set.

#11Try it yourself

Connect Site and URL sources. Build Overview + Queries/Pages. Add a Sheet stub for Generative AI with three sample rows labelled illustrative, then replace with a real export next week.

#12Quick quiz

1. What is Search Console freshness in Data Studio?

Answer: Every 12 hours (fixed).

2. Why use both Site and URL tables?

Answer: Site is right for query/country rollups; URL is right for page-level rows.

3. Are Generative AI impressions the same as GA4 AI Assistant sessions?

Answer: No. Different products, different measurement.

#13What should you check before the next lesson?

• Site + URL sources named and on owner credentials.
• Generative AI page exists (connector or Sheet) with an honesty note.
• GSC vs GA4 comparison caption on Overview.

Previous: Build a Google Ads dashboard in Looker Studio. Next: Cross-channel ROI with blended Looker Studio data. Or return to the Looker Studio for Marketers track. Related: Search Console Data Studio reporting, Search Console generative AI performance report, Search Console for Marketers, Gemini Search Console AI reports.

#14Common questions

Which Search Console tables should I connect in Data Studio? Most marketing dashboards need the Site Impression table for query and country rollups and the URL Impression table for page-level work. Connect both as separate data sources when you need both grains.

Does the Search Console connector include the Generative AI performance report? Confirm in your account. Many teams still export Generative AI metrics to Sheets or BigQuery for dashboards. Do not invent connector fields. Link the Search Console UI report until the connector exposes what you need.

How fresh is Search Console data in Data Studio? Google documents Search Console freshness as every 12 hours. It is not configurable like GA4.