Catch every query the day it first appears.

Search Console has no “new query” view, and its bulk export has no backfill — so the only way to know a query is genuinely new is to keep your own history. We track every query’s first-seen date in your warehouse and surface the ones just starting to get impressions.

Maps
Queries → first-seen date
Lives in
Your own BigQuery
Source
Search Console

A new query looks exactly like an old one

In Search Console every query is just a row with clicks and impressions for the range you picked. Nothing tells you whether this is the first week it has ever appeared or its hundredth — so a query that just broke through sits buried among thousands that have been there all along.

The UI caps at 1,000 rows, and the bulk export has no backfill — the day you turn it on is day zero, with no earlier history to compare against. Without a baseline, “is this query new?” has no answer.

Measured against your own history

Not a snapshot you eyeball each session — a running record of every query that lets the first-time ones stand out on their own.

  1. Step 1

    Keep a running query history

    Every query, every day, is stored in your own BigQuery from day one — so each one carries a first-seen date that never resets when an export turns over.

  2. Step 2

    Flag the first appearances

    Each period we compare against your full history and mark the queries with no prior impressions — genuinely new demand, not a query that simply moved up the page.

  3. Step 3

    Surface them where you report

    New queries roll up into the reporting you already get, ranked by the impressions they’re already pulling — so the breakout shows up without a manual diff.

The queries that just showed up

Each period, the first-time queries collect into one readable list — what’s new, when it first appeared, and the impressions it’s already pulling.

First appeared this period first_seen
  • bigquery search console export This week 1,240
  • gsc data warehouse setup This week 860
  • search console 1000 row limit This week 540
  • track new keywords automatically This week 310

Example list. Your new queries are detected against your own warehouse history.

What first-seen tracking changes

Because the history lives in your data layer, the first appearances show up everywhere your numbers do.

  1. Catch demand while it’s still uncontested

    A query with no history and real impressions is a topic the market just started searching. Seeing it early is the window to publish before the page anyone else writes ranks first.

  2. History that survives the export gap

    Because first-seen dates live in your warehouse, you’re not stuck with the day you switched the bulk export on. Your baseline keeps growing, so “new” keeps meaning new.

  3. New queries come to you

    Instead of scrolling the Performance report hoping to spot something unfamiliar, the first-time queries surface in the reports and digest you already read.

The difference from doing it by hand

You can try to spot new queries in Search Console — until you hit the row cap or the missing history. Here’s what changes when the first-seen date is managed in your warehouse instead.

Knowing a query is new
Guess from memory
First-seen date on every query
Row depth
Capped at 1,000 in the UI
Every query in your warehouse
History before the export
Bulk export has no backfill
Continuous history from day one
Spotting first appearances
Scroll and compare by eye
Flagged automatically each period
In your reporting
A manual diff every time
Joined into every report

Frequently asked questions

Still wondering about something? A discovery call clears it up fast.

A query that has no prior impressions in your history and starts getting impressions in the current period. It’s genuinely new demand — distinct from a query that already existed and simply improved its position or click-through.

See what’s new before anyone else does.

Talk to us

Free discovery call · No commitment