Measurement
SEO Dashboard: Templates, Metrics and How to Build One (Looker Studio, Sheets, Custom)
An SEO dashboard is a single report that shows how a site performs in search: clicks, impressions, click-through rate and position from Search Console, plus what those visitors did next from your analytics. A good one answers the three questions a stakeholder actually asks (are we growing, where, and did it produce anything) on one screen, without anyone opening Search Console.
This guide covers what belongs on an SEO dashboard, where templates help, and three ways to build one. The main walkthrough is Looker Studio (now called Data Studio again), followed by a client reporting setup, a Google Sheets route and a custom build on the Search Console API.
Key takeaways
- An SEO dashboard is a decision tool, not a data dump. Report the four metrics Search Console defines (clicks, impressions, CTR, average position), a small set of business outcomes from GA4, and nothing you would not act on.
- Looker Studio is the default build. It is a no-cost tool with built-in Search Console and GA4 connectors, and Google’s template gallery has a Search Console category to start from.
- For client dashboards, credentials and sharing matter more than chart design. Public link sharing also exposes the report’s embedded data sources, and a data control lets one report serve every client property you have access to.
- Sheets is a staging layer, not a warehouse. It works for small sites, but a daily page-and-query pull on a busy site fills a spreadsheet within weeks.
- Build your own on the Search Console API when you need history, custom segments or numbers you can defend. The API returns up to 25,000 rows per request, and the daily-increment pattern is how you keep data the interface discards.
/assets/screenshots/looker-studio-seo-dashboard.png What an SEO dashboard is, and which kind you need
An SEO dashboard pulls search performance and on-site outcomes into one view so that the people who fund SEO can see whether it is working. It is different from an SEO tool’s own interface, which is built for the person doing the work rather than the person reading the report.
Most dashboards do one of two jobs. A reporting dashboard is monthly, for stakeholders or clients: trends, outcomes, a short commentary. A monitoring dashboard is daily or weekly, for the person running SEO: recent data and sudden drops. Trying to make one page do both is the most common reason dashboards go unread, so build the reporting view first and give monitoring its own page.
The three ways to build one
| Build route | Best for | Data freshness | Effort | Main limitation |
|---|---|---|---|---|
| Looker Studio (Data Studio) with native connectors | Most sites, most teams, client reporting | As fresh as the connectors | Low | Query data is capped and anonymised; blends are fragile |
| Google Sheets as a staging layer, charted in Looker Studio | Small sites, custom calculated columns, manual annotations | Whenever your script or import runs | Medium | Spreadsheet size limit; you own the refresh |
| Custom: Search Console API or BigQuery export into your own store | Large sites, long history, custom segments, several data sources | You decide | High | You maintain a pipeline |
Commercial SEO dashboard software sits alongside these. Geckoboard, for example, connects to Google Analytics and Google Sheets for a live SEO view, and SEO platforms ship their own dashboards. They earn their cost when that platform’s rankings or backlink data are the core of the report. For Search Console and GA4 alone, the free route does the same job.
The metrics that belong on an SEO dashboard
The metric decision comes before the build. I cover how to choose them by business model in SEO KPIs: how to choose the five that matter. The short version for a dashboard is three layers, top to bottom.
Outcome metrics (the top row). Organic conversions or revenue from GA4, and non-branded clicks from Search Console. These are what the report exists to show.
Visibility metrics (the trend charts). Search Console defines exactly four metrics: Clicks, Impressions, CTR and Average position, and groups them by six dimensions: Queries, Pages, Countries, Devices, Search appearance and Dates. A dashboard that reports those cleanly beats one that reports thirty things badly.
Diagnostic metrics (a second page). Pages losing impressions, queries sitting at positions 8 to 20, CTR outliers against position. These are for the person doing the work, not the executive summary.
Two things to handle carefully:
- Average position is not a rank. Google defines it as the average position of the topmost result from your site, and in a table it is averaged per row. Show it as a trend, never as “we rank 4th”.
- AI traffic needs its own line. Visits from ChatGPT, Perplexity and similar assistants land in GA4 as referrals or direct traffic unless you separate them. Tracking AI referral traffic in GA4 sets up the channel group that makes an “AI assistants” row possible on this dashboard.
What to leave off: third-party authority scores, bounce rate on its own, raw keyword counts from a tool, and any number nobody has ever changed a decision because of.
SEO dashboard templates: where to start
You do not need to start from a blank canvas. For Search Console, Google points you to the template gallery, where you select the Search Console category. Use a template “as is” or strip it down to your layers.
Templates become more useful with a data control. A data control lets a viewer switch the report to a different dataset they have access to without editing the data source, and Search Console and Google Analytics are both supported. One template can then show any property you own.
With any template, delete first, then add. Keep the headline tiles, one trend, the query and page tables and the GA4 outcomes, and remove the rest until someone asks for it.
How to build an SEO dashboard in Looker Studio
This is the build most sites should do first. One housekeeping note before you open the product. In April 2026, Google returned Looker Studio to its original name, Data Studio, and the URL is now datastudio.google.com (the old lookerstudio.google.com redirects). It is the same product most people still search for as “Looker Studio”. The interface just says Data Studio now.
Step 1: Connect Search Console
The Search Console connector is the foundation. The steps Google documents:
- Sign in to Data Studio, and in the top left click Create, then Data Source.
- Select the Search Console connector.
- Click AUTHORIZE if prompted.
- In the Sites panel, choose the property. If a property you own is missing, check you are signed in to Data Studio and Search Console with the same Google Account and have at least view permission on it.
- In the Tables panel, choose either Site Impression or URL Impression.
- Choose a default Search Type, then click CONNECT.
Step 5 is the one people miss. Search Console uses two aggregation methods, and a single data source can only use one of them. Site Impression aggregates by property and suits headline trends. URL Impression aggregates by page, enables page-level tables, and adds the discover and googleNews search types. To show both, create two data sources and add both to one report. That is the supported pattern, not a workaround.
Step 2: Connect GA4
The Google Analytics connector follows the same shape: Create, Data Source, Google Analytics, AUTHORIZE, then pick an account and property and click CONNECT. Three things to know before relying on it:
- You need at least Read & Analyze permission on the GA4 property. An empty picker is almost always a permissions problem.
- It mirrors GA4 reports, not Explorations. Google states that Data Studio will match the data, but not the explorations, and GA4 segments and comparisons are not available through the connector.
- It is subject to the GA4 Data API quotas. A heavily used report on a large property may display an error when it exceeds them.
Step 3: Build the reporting page
My default reporting page, top to bottom:
- A summary row. Clicks, impressions, CTR and average position as scorecards, each with a comparison to the previous period. Add organic conversions from GA4 as a fifth tile.
- A clicks and impressions trend. A time series on the Date dimension. This is the “are we growing” chart that executives actually read.
- Top queries. A table on the Query dimension, sorted by clicks, with impressions, CTR and position alongside.
- Top pages. A table grouped by page, built on the URL Impression source. Put commercial pages where people will see them, not only the blog.
- A GA4 outcomes panel. Landing page sessions, engagement and key events from organic search, so the dashboard answers “did that traffic do anything”.
Add a date range control and set the default range to end a few days before today, for the reason in the next step.
Step 4: Bake in the data caveats
Three behaviours will generate support questions unless the dashboard explains them.
Query data is deliberately incomplete. To protect privacy, Google might not show some queries that are made a small number of times, or those that contain personal or sensitive information, and Data Studio may group them into a single blank row. Your query table will never add up to total clicks. You can filter the Query dimension to exclude null values so the blank row stops distracting people.
The newest days are provisional. In Search Console, the newest data can be preliminary, meaning it’s still being collected and might change in the next few hours. A cliff on the last day is usually that, not a traffic collapse.
Charts and tables are aggregated differently. Chart data is aggregated by property, while table data grouped by Pages or Search appearance is aggregated by page, so totals legitimately differ. Put a one-line note on the page and move on.
Step 5: Blend Search Console and GA4, sparingly
The tempting move is one table keyed by page with impressions, clicks and conversions in a single row. Data Studio lets you blend data from up to five data sources without writing SQL. For an SEO dashboard you would join the Search Console URL Impression page field to the GA4 landing page field.
Know how the join behaves first:
- Pick the operator deliberately. Data Studio supports inner, left outer, right outer, full outer and cross joins. For “Search Console pages, enriched with GA4 where it exists”, a left outer join from the Search Console table is usually right.
- Joins are equality-only. Data Studio only supports equality between the fields in the join condition. Check that both fields use the same format (full URL or path, trailing slash or not, query string or not) and build a calculated field to normalise them before you join.
- Rows can collapse. Before joining, identical rows are collapsed during this pre-grouping phase unless each table includes a unique identifier. If counts look short, this is why.
- Blends live in one report. You can’t make a blend reusable across reports, so a rebuilt dashboard means a rebuilt blend.
Blend only for the one or two charts that need both sources in the same row. Everywhere else, two honest charts side by side beat one fragile blend.
SEO client dashboards and reporting
A client dashboard is the same build with three extra decisions: whose credentials the data runs on, how the client gets in, and what they receive without logging in.
Credentials: owner’s or viewer’s
Every data source has a credentials setting. Owner’s credentials let other people view or create reports that use this data without requiring them to have their own access. Viewer’s credentials require each viewer to have their own access to the Search Console property or GA4 property.
For client reporting, owner’s credentials are the usual choice, because the client should not need a Search Console seat to read their own report. Anyone who can open the report then sees the data, so the sharing settings carry the access control.
One report for many clients
If you manage several properties, the data control is the tool. It lets a report switch to a different dataset without editing the data source, and it stores the selected account in the URL, so each client can get a bookmarked link to their version. Two limits: a data control only shows accounts the viewer has access to, and data controls don’t work in embedded reports.
For clients who should never see another client’s property name, the safer pattern is one copy of the report per client, each with its own data sources. It is more to maintain, and it cannot leak.
Sharing without leaking data
You can invite specific people or Google Groups, or turn on link sharing. The details that matter for clients:
- Viewers invited by email need a Google login. No login is required to view a report shared with public link sharing, but a login is required for email or group sharing.
- Public links expose embedded data sources. Google warns that when you share by public link, any embedded data sources within that report will also be accessible to anyone who has the link. Make the data sources reusable if the link will travel.
- There is a ceiling. You can share with a maximum of 1,500 principals, counting individual addresses and Google Groups.
What the client receives
Most clients will not open a dashboard every month. Two features close that gap. You can send a PDF of your report on a regular basis by setting up a delivery schedule, and you can embed a report in Google Sites or any iframe-enabled website, such as a client portal.
Add a text box at the top of the first page with three sentences of commentary: what changed, why, and what happens next. The numbers without that paragraph are the reason clients ask for a call.
Build your own: Search Console API, Sheets or a warehouse
The connectors cover most dashboards. You outgrow them when you need query history longer than the interface keeps, segments the connector cannot express (brand versus non-brand across thousands of queries, for example), or when a stakeholder asks how complete the numbers are and you need an answer.
The foundation is the Search Analytics query method. I go through its parameters and failure modes in the Search Console API guide. For a dashboard, four facts decide the design:
- 25,000 rows per request.
rowLimithas a valid range of 1 to 25,000, default 1,000, andstartRowpages through the rest. - 50K rows per day per search type. The method exposes a maximum of 50K rows of data per day per search type, sorted by clicks. Paging will not get past it.
- Query one day at a time, every day. Google recommends running a query each day for one day’s worth of data and notes data is typically available after 2 to 3 days.
- Dates are in Pacific Time.
startDateandendDateare in PT time (UTC - 7:00/8:00). If your warehouse runs on UTC, label the date column so nobody joins it to GA4 days blindly.
Route 1: Google Sheets with Apps Script
This is the lightest custom build: a script bound to a Google Sheet pulls one day of Search Console data into a tab, and Data Studio charts the tab through the Google Sheets connector. That connector checks for changed data values and new rows every time a query is run, so the dashboard picks up each day’s rows without a manual refresh.
In the Sheet, open Extensions, then Apps Script. Show the manifest file and set the scopes explicitly in appsscript.json:
{
"timeZone": "America/Los_Angeles",
"runtimeVersion": "V8",
"exceptionLogging": "STACKDRIVER",
"oauthScopes": [
"https://www.googleapis.com/auth/webmasters.readonly",
"https://www.googleapis.com/auth/spreadsheets.currentonly",
"https://www.googleapis.com/auth/script.external_request"
]
}
Then the script. It pulls one day, three days back, pages through every row the API returns, and writes them in one batch:
const SITE_URL = 'sc-domain:example.com'; // or 'https://www.example.com/'
const SHEET_NAME = 'gsc_daily';
const DIMENSIONS = ['page', 'query'];
const ROW_LIMIT = 25000; // the API's maximum per request
const LAG_DAYS = 3; // finalised data is typically 2 to 3 days behind
function pullSearchConsoleDay() {
const day = daysAgoPT_(LAG_DAYS);
const props = PropertiesService.getScriptProperties();
if (props.getProperty('lastLoaded') === day) return; // already loaded
const out = [];
for (let startRow = 0; ; startRow += ROW_LIMIT) {
const rows = querySearchConsole_({
startDate: day,
endDate: day,
dimensions: DIMENSIONS,
type: 'web',
rowLimit: ROW_LIMIT,
startRow: startRow,
});
if (rows.length === 0) break;
rows.forEach(function (r) {
out.push([day].concat(r.keys, [r.clicks, r.impressions, r.ctr, r.position]));
});
}
const sheet = getOrCreateSheet_();
if (out.length > 0) {
sheet.getRange(sheet.getLastRow() + 1, 1, out.length, out[0].length).setValues(out);
}
props.setProperty('lastLoaded', day);
}
function querySearchConsole_(body) {
const url = 'https://www.googleapis.com/webmasters/v3/sites/' +
encodeURIComponent(SITE_URL) + '/searchAnalytics/query';
const res = UrlFetchApp.fetch(url, {
method: 'post',
contentType: 'application/json',
headers: { Authorization: 'Bearer ' + ScriptApp.getOAuthToken() },
payload: JSON.stringify(body),
muteHttpExceptions: true,
});
if (res.getResponseCode() !== 200) {
throw new Error('Search Console API ' + res.getResponseCode() + ': ' + res.getContentText());
}
return JSON.parse(res.getContentText()).rows || [];
}
function daysAgoPT_(n) {
const d = new Date(Date.now() - n * 24 * 60 * 60 * 1000);
return Utilities.formatDate(d, 'America/Los_Angeles', 'yyyy-MM-dd');
}
function getOrCreateSheet_() {
const ss = SpreadsheetApp.getActiveSpreadsheet();
let sheet = ss.getSheetByName(SHEET_NAME);
if (!sheet) {
sheet = ss.insertSheet(SHEET_NAME);
sheet.appendRow(['date'].concat(DIMENSIONS, ['clicks', 'impressions', 'ctr', 'position']));
}
return sheet;
}
Run pullSearchConsoleDay once by hand to authorise it, then add a daily time-driven trigger from the Triggers panel. If the call fails because the API is not enabled for the script’s project, link the script to a standard Google Cloud project with the Search Console API turned on. I ran the paging and write logic against a stubbed API before publishing: a 30,001-row day produced three requests (startRow 0, 25,000 and 50,000) and 30,001 sheet rows, and a second run on the same day wrote nothing.
The limit is the spreadsheet itself. Google Sheets holds up to 20 million cells. A site that hits the 50K-row daily ceiling writes 350,000 cells a day at seven columns, which fills a sheet in under two months. For a site that size, drop query from DIMENSIONS (page-level rows only) or move to the next route.
Route 2: A warehouse (API pipeline or BigQuery export)
For larger sites, write the same daily rows into a database instead of a sheet. The Search Console API guide has the Python paging loop, and the logic is identical to the script above: one day per run, page until an empty response, store once, never re-request.
If the data can live in BigQuery, Search Console can do the pipeline for you. Its bulk data export will schedule a daily export of your Search Console performance data to BigQuery, with all performance data available to Search Console except anonymised queries. Data Studio connects to databases including BigQuery, so the dashboard layer stays the same.
A warehouse is also where you can join Search Console, GA4 and CRM data properly in SQL rather than in a blend. What else in SEO reporting is worth automating is covered in SEO automation.
SEO monitoring dashboards: catching drops early
A monitoring page needs different defaults: the last 28 days by day, a previous-period comparison, and page and query tables sorted by the change in clicks rather than the total. Two additions make it useful:
- Fresh data from the API. The
dataStateparameter set to"all"includes fresh data, and when you group by date the response can carry afirst_incomplete_datefield so a chart can mark where the numbers are still moving. That is the difference between an alert that fires on real drops and one that fires every morning. - A second surface. Search performance does not explain crawling or indexing problems. If pages drop out, the evidence is in server logs, which is log file analysis rather than a dashboard fix.
If you track AI Overviews, give them their own page too; the method is in how to track AI Overviews.
What I would skip, and the mistakes I see most
- One data source for both Site and URL impressions. Add the connector twice and label each source.
- A query table presented as complete. Anonymised queries are withheld by design.
- Blends where two side-by-side charts would do. Every blend is a join you now have to trust.
- A public link to a report with embedded data sources. Anyone with the link can reach the data.
- Building before deciding the KPIs. The dashboard is downstream of the metric decision, not a substitute for it.
If the dashboard keeps exposing tracking gaps (conversions that do not attribute, AI visits hiding in direct traffic), that is a measurement build rather than a reporting fix, and it is what full-funnel tracking sets up.
Frequently asked questions
What should an SEO dashboard include?
Start with the four Search Console metrics (clicks, impressions, CTR and average position), a trend over time, top queries and top pages, and organic conversions from GA4. Add AI assistant referrals as a separate row if you track them. Leave out anything nobody would act on, such as third-party authority scores.
Is there a free SEO dashboard template?
Yes. Looker Studio, now called Data Studio, is free, and Google’s template gallery has a Search Console category. Add a data control so the template can switch to any Search Console or Google Analytics property the viewer has access to.
Is Looker Studio the same as Data Studio?
They are the same product. In April 2026 Google returned Looker Studio to its original name, Data Studio, and moved it to datastudio.google.com; the old lookerstudio.google.com address redirects. Reports did not need to change.
How do I make an SEO dashboard for clients?
Build the report on data sources that use owner’s credentials, so clients do not need their own Search Console access, and share it by email invitation rather than a public link. Use a data control or one report copy per client, schedule a monthly PDF, and add a short written commentary at the top.
Can I build an SEO dashboard in Google Sheets?
Yes, with Apps Script pulling Search Console API data into a sheet and Data Studio charting it through the Google Sheets connector. It suits small sites. A spreadsheet holds up to 20 million cells, so a busy site with page and query rows will outgrow it within weeks.
Why don’t my dashboard numbers match Search Console?
Usually aggregation: Search Console aggregates chart data by property but page tables by page, so totals differ. Anonymised queries are withheld from query tables, and the most recent days are preliminary. The API also uses Pacific Time dates, which shifts day totals against reports that run on UTC.