Looker Studio (formerly Data Studio) is the free report builder most SEO teams already know. Connect Search Console, drop a time series, ship a client dashboard. That workflow is fine inside Google's live Performance window. It fails the moment someone asks for last year's same week and the chart empties.
This page is the limits guide. Wider option set: Best Google Search Console history tools. Deeper warehouse decision: BigQuery vs hosted Search Console archive. Retention maths: 16-month limit and year-over-year when the prior year is gone.
Quick verdict
- Use Looker Studio on the native Search Console connector for charts of the current ~16-month window, blended with Ads or Sheets you already trust.
- Do not treat that connector as backup. Saving a report does not snapshot row-level history into a warehouse you control.
- When you need month 17 and beyond, point Looker at data you already stored (BigQuery, Sheets you maintain carefully, or a hosted archive), or stop promising YoY from Looker alone.
What the connector actually does
Google's Looker Studio Search Console connector queries Search Console's live Performance data on refresh. It is a visualisation layer on Google's API window, not a second copy of your clicks and queries.
| Limit | What it means in practice |
|---|---|
| Retention | Same rolling ~16 months as Search Console UI and Search Analytics API |
| Freshness | Marketing / measurement connectors refresh about every 12 hours; you cannot tighten that for Search Console |
| History past month 16 | Empty — not a traffic crash |
| Anonymised queries | Still withheld; blank query rows are privacy filtering, not a Looker bug |
| Row completeness | Same caps as Google's live path (UI ~1,000; API / connector scale toward Google's daily row ceilings) |
| Site vs URL impression | One data source = one aggregation method; pick deliberately |
Empty prior-year ranges after month 16 are retention, not a ranking collapse. Zero-filling them lies to the deck — same rule as YoY.
The five walls people hit
1. “Last year is blank”
Cause: the day aged out of Search Console. Looker asked Google again and Google had nothing. Fix: store days before they age out (API schedule, BigQuery from enable day onward plus a backfill, or a hosted archive). Point Looker at that stored copy.
2. “The number disagrees with Search Console”
Cause: different date ranges, Site vs URL impression, filters, cached freshness, or summing query rows in Looker the way you never should in the UI. Site totals belong in a totals query — how to export more than 1,000 rows and the 1,000-row limit cover why table sums lie.
3. “I saved the report, so I have history”
Cause: confusion between a dashboard definition and a data warehouse. The .looker report remembers charts and filters. It does not freeze Performance rows. Refresh after month 16 and the old day is gone.
4. “Blended data will invent the missing year”
Cause: hope. Blending GA4, Sheets, and Search Console cannot recreate clicks Google already deleted. Sheets only help if you exported in time — and UI CSV is still ~1,000 representative rows.
5. “Quota / sample weirdness”
Cause: Google's live path has daily row and privacy filters. Looker does not lift them. Very large properties feel this first; most sites feel retention first.
What Looker Studio is still good for
- Client-facing charts of the current window without building a BI stack.
- Combining Search Console with Ads or CRM tables you already land elsewhere.
- Teaching stakeholders the difference between impressions and clicks with a familiar UI.
If that is the whole job, stop here. You do not need SiteLine or BigQuery to draw last quarter.
Paths that actually keep history
- BigQuery bulk export — first-party forward archive. No automatic backfill of the ~16 months already in Search Console on enable day. Details: BigQuery vs hosted.
- DIY Search Analytics API warehouse — you schedule pulls, store site totals and breakdowns, own retention. Engineering time is the price.
- Hosted archive (e.g. SiteLine) — OAuth connect with
webmasters.readonly, backfill of what Google still holds on connect, ongoing imports, retention while you subscribe, UI, and read-only MCP for agents.
Then connect Looker Studio to that store if you still want Looker's charts. Looker becomes the presentation layer. The archive becomes the source of truth.
Where SiteLine fits (and where it does not)
SiteLine is a hosted Search Console archive plus cookieless on-site analytics. On connect it copies up to about 16 months of what Google still holds (capped by how long the property has been verified), imports up to 25k rows/day/report, and keeps imported days while you subscribe. Agents can query the same warehouse over read-only MCP — /mcp.
It does not recover days Google already deleted. It does not replace Looker Studio as a free chart builder. It does not submit sitemaps or request indexing (scope is webmasters.readonly).
Register — 7-day trial, no card. Pricing from $4.99/mo. Prefer agents on signup? Register with MCP intent. Connect walkthrough: Connect Google Search Console to SiteLine.
FAQ
Does Looker Studio store Search Console history?
No. The native connector re-reads Google's live window on refresh. Past ~16 months, those days are gone from Looker too.
Can I change Search Console freshness in Looker Studio?
No. Google's marketing and measurement connectors refresh on a fixed ~12-hour cadence. You cannot set a tighter interval for Search Console.
Should I stop using Looker Studio?
Only if you expected an archive. Keep Looker for charts; add a real store if you need YoY past Google's window.
Is BigQuery enough on its own?
For the future, often yes. For the past already sitting in Search Console on enable day, usually no — pair with a backfill. See BigQuery vs hosted.
Will SiteLine fill my Looker YoY chart automatically?
Only after you connect and import, and only for days SiteLine stored. Point Looker at an export or warehouse you control, or use SiteLine's own UI/MCP for history questions.