← All posts

Google Search Console dashboard: what the built-in one shows, and how to build your own

What the Search Console Overview page shows, how to build a Search Console dashboard in Looker Studio step by step, and the three things every dashboard built on Search Console still cannot show you.

QueryScope team · · 7 min read · search console gsc dashboard looker studio

A Google Search Console dashboard is one screen that shows how your site is doing in Google Search without clicking through six reports. Search Console ships one, the Overview page, and it is a health check. When you want your own charts, the usual route is Looker Studio, Google's free reporting tool, which reads Search Console through a built-in connector. Both read the same data, so both share its limits: 16 months of history, query rows that leave out rare searches, and no idea which change you made caused which line to move.

TL;DR:

  • The Overview page in Search Console is a summary of your property's health: clicks, indexed pages, enhancement errors, and any manual action or security issue.
  • For a dashboard you design yourself, connect Looker Studio to Search Console. It takes eight steps and gives you two tables, Site Impression and URL Impression, one per data source.
  • Any dashboard on Search Console data can only show the last 16 months, under-counts queries, and cannot tell you whether a change worked.
  • If you need the history kept and every change measured, store your own snapshots or use a tool that does.

What does the Search Console dashboard show?

The built-in dashboard is the Overview page, the first screen after you pick a property. Google describes it as a page that "shows a summary of your property's health, including any manual actions or security issues applied to your site". In practice that means a clicks chart from the Performance report, a chart of indexed and not-indexed pages, summaries of enhancement errors, and a banner if Google has flagged a manual action or a security problem.

Read it as a smoke alarm. It tells you something is wrong (traffic fell off a cliff, pages dropped out of the index, a structured-data error spread across the site) and links you to the report where you can find out why. It does not show you which pages or searches moved, and it gives you no way to rearrange or combine its charts.

For anything past that first glance, the real work happens in the Performance report. It shows the last three months by default and up to 16 months if you widen the date range. You filter it by query, page, country, device and search appearance, one view at a time.

How do you build a Search Console dashboard in Looker Studio?

Looker Studio (formerly Data Studio) has a native Search Console connector. Google's connector guide lists the steps:

  1. Sign in to Looker Studio.
  2. On the home page, click Create, then Data source.
  3. Pick the Search Console connector.
  4. Authorize Looker Studio to read your Search Console data if it asks.
  5. In the Sites panel, choose your property. If it is missing, sign in with the same Google account you use in Search Console; you need at least view permission on the property.
  6. In the Tables panel, choose Site Impression or URL Impression.
  7. In the Search type panel, choose the default search type (web is the one most sites want).
  8. Click Connect, then build a report on the new data source.

Most people then add a scorecard row (clicks, impressions, CTR, average position), a time-series chart of clicks and impressions, and two tables: top queries and top pages. That covers what most people mean by a Search Console dashboard.

Site Impression or URL Impression?

Search Console counts performance two ways, by site and by page, and the connector exposes each as its own table. Google's guide says a data source can only use one of them. To see both, create two data sources and add both to the same report.

  • Site Impression counts at the site level. Use it for the headline numbers and the trend line.
  • URL Impression counts at the page level. Use it for the per-page table. It also supports the Discover and Google News search types, which Site Impression does not.

The two will not match each other, and that is expected. A page-level count credits each page that appeared for a search, while a site-level count credits the site once. Which one you read decides the number you report, so label the charts.

Try it

Point an SEO agent at your own site, not just an essay about one.

QueryScope holds the plan for your site, reads your real Search Console, and hands the coding agent you already have one change at a time to rank for the searches you decided to win. From $49/month, everything included.

What can't a Search Console dashboard show?

Any dashboard on Search Console data, the Overview page or one you build, inherits three limits from the source.

History stops at 16 months. Google keeps "data for the last 16 months" and deletes the oldest day every day. A Looker Studio report reads the same store, so a chart covering two years shows a line that starts 16 months back. More on why, and on what you can still keep, in how to keep Search Console data older than 16 months.

Query rows under-count. Google's connector guide says it plainly: "To protect user privacy, Search Analytics doesn't show all data." Rare searches are left out of the query breakdown, so a top-queries table never adds up to the site total. Take volume from the page level and read queries for what people are looking for, not how many of them there are. Anonymized queries covers how much goes missing.

It cannot tell you whether a change worked. A dashboard draws the line. When the line moves, it has no record of what you changed that week, which pages Google had read since, or what the rest of the site did over the same days. Search Console's annotations let you pin a dated note to the chart, but a note marks a date. It does not compare a before window with an after window, and it does not take out the movement the whole site saw anyway.

When is a template enough, and when is it not?

A Looker Studio template is enough when the job is reporting: a monthly view for a client or a team, the same five charts every time, no decisions hanging off it. Copy one, point it at your property, and you are done.

It stops being enough when the dashboard has to answer what to do next. That needs three things a chart does not hold: the searches you decided to win, a record of each change you made against them, and a measurement of each change once Google has recrawled the page. Without the record, every dip turns into a guessing game about which of last month's edits caused it.

A dashboard that keeps the history and the changes

QueryScope is built for that second job. It reads your own Search Console over a read-only grant and stores a daily snapshot from the day you connect, so the history keeps growing after Google's 16-month window has moved on. Its dashboard is organised around the searches you chose to win: which are on page 1, which rank below it, which are not ranking yet, and how each one's position has moved. Next to it, a changes ledger lists every edit recorded against those searches and what Google did after it, measured against the rest of your site.

The same data reaches your AI coding agent over MCP, so the agent that edits the page can read where it ranks and record what it changed. It stops at the click: it does not see signups or sales, and does not claim to.

Sources

  • Google Search Console Help, Reports at a glance (the Overview page "shows a summary of your property's health, including any manual actions or security issues applied to your site").
  • Google Cloud documentation, Connect to Search Console (connector steps; Site Impression and URL Impression tables; one table per data source; search types per table; "Search Analytics doesn't show all data").
  • Google Search Console Help, Performance report (Search results) (three-month default view, full 16-month range).
  • Google Analytics Help, Connect Search Console to Google Analytics ("Search Console keeps data for the last 16 months").

Try it

Put an SEO agent in your editor.

Ask your coding agent what to work on. QueryScope reads your real Search Console, holds the searches you decided to win, and hands back one move at a time with the proof it worked. From $49/month, everything included. 1, 3 or 10 sites.