Every query, dated the day it first appears
From day one we stamp each query with a first-seen date in your warehouse. So a first-ever appearance is something you can sort and filter on, not a row you have to spot by eye.
Catch every query the day it first appears
A query that just broke through looks identical to one that's been there for years — Search Console has no first-seen date.
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.
New
—
New
—
New
—
New
—
Illustration. Each new query carries a first-seen date, then its own clicks and impressions, computed from your own history.
Open Search Console in another tab. Can you answer these right now?
- Which queries are appearing for the first time this week — not ones that merely moved up?
- When a brand-new way of searching for what you sell shows up, how long before you notice — if nothing flags it as new?
- Can you separate genuinely new demand from queries that have been there all along?
If you hesitated on any of these, the answer is already in your data — just not in a shape Search Console will show you.
Built for teams who own their data
- Northpeak
- Datawise
- Quantly
- Meridian
- Brightline
- Corewave
Why you can trust the data
-
Read-only access
We only ever read your data. Nothing on your site or in Search Console is ever changed.
-
Your warehouse
All data lives in your own Google Cloud project. It is never copied into a tool you do not control.
-
Your rules
Grouping and classification are tailored to your site, and stay fully editable as it changes.
-
Yours to keep
Leave and the tables stay. Export on your terms, with no rolling deletion window and no lock-in.
-
Founder pedigree
Built by a team that has run analytics for high-traffic platforms, with a Google Product Expert among the founders.
-
Built on Google’s stack
BigQuery storage and the full Search Console API, not a third-party scrape.
You have said one of these, but could not catch it in time
A brand-new query is the market telling you what it wants — before your competitors have noticed. But Search Console shows you what moved up, not what just appeared, and its export has no backfill, so a query that just broke through looks identical to one that's been there for years.
You find out once it's already big and contested — arriving late to demand you could have owned first.
In-house, measured on traffic
Finding the next thing to rank for is half my job. But I am scrolling thousands of rows hoping something unfamiliar jumps out. There is no way to tell a query appearing for the first time from one that has been there for months. The new queries I do catch, I catch too late to be first.
The real problem Every query is just a row of clicks and impressions for the range you picked. Nothing marks the day it first appeared. So genuinely new demand stays buried among the queries that have always been there.
Editorial / content marketing
We plan the calendar weeks ahead from keyword tools and instinct. Then a competitor ranks for a term our own audience was already searching. I learn it was an opportunity only after someone else owns the page. The signal was sitting in our own Search Console the whole time.
The real problem The freshest demand is what the market just started searching on your own pages. It never surfaces in time to brief a writer. So the calendar runs on lagging third-party tools instead of your own first-party signal.
Reporting to clients
Catching a trend before the client does is half of what they pay for. But I am spotting new queries by eye, one account at a time. When I miss one, the client is the one who flags it and asks why we do not have a page up for this yet. I never have a good answer.
The real problem There is no systematic way to surface first-time queries. So catching something early rests on noticing by hand. A missed new query makes the agency look slow.
Exec, owns the budget
I want to put budget where demand is forming, not where it already landed. But everything that reaches me is a lagging number. By the time a trend shows up in the topline it is no longer new. I cannot separate a real emerging market from ordinary week-to-week noise.
The real problem With no first-seen date to tell new demand apart from existing queries that merely moved up, every signal that reaches the exec arrives after the fact. So the team reacts to trends instead of getting ahead of them.
How working with us works
A managed setup, scoped to your site. It is not a plan you configure yourself.
- 01
Discovery call
We look at your Search Console setup together, and agree on what counts as a new query for you.
- 02
We build it in your BigQuery
We set up query-history tracking and start dating every query’s first appearance inside your own warehouse, read-only.
- 03
It runs every day
New queries are flagged automatically each period and surface in every report. Nothing for you to maintain.
A managed setup: you give read-only access, we run it, and your data stays in your own warehouse.
The queries that just showed up
Each period, the first-time queries collect into one readable list: what is new, when it first appeared and the impressions it is already pulling.
Query First seen Impressions
-
bigquery search console exportThis week 1,240 -
gsc data warehouse setupThis week 860 -
search console 1000 row limitThis week 540 -
track new keywords automaticallyThis week 310
Example list. Your new queries are detected against your own warehouse history.
What you actually do with it
In the order you’ll use it, from the first-seen date to the report that flags it.
New queries flagged automatically
Each period, queries with no prior history are marked new. This is genuinely fresh demand, not a query that simply moved up the page.
Ranked by the impressions they are already pulling
New queries arrive sorted by the demand behind them. So the one worth acting on sits at the top, not buried in the tail.
A baseline that grows from day one
Because first-seen dates live in your warehouse, your history keeps building past the export gap. So new keeps meaning new.
In every report and your digest
The new-query flag lives in your data layer, so it joins Looker Studio, your BI and the digest email. It reaches everywhere your numbers already go.
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 is what changes when the first-seen date is managed in your warehouse instead.
By hand in Search Console
Manual, session-bound
- Knowing a query is new
- By hand Guess from memory
- Insightlytics First-seen date on every query
- Row depth
- By hand Capped at 1,000 in the UI
- Insightlytics Every query in your warehouse
- History
- By hand Only the last 16 months
- Insightlytics Continuous history from day one, no limit
- Spotting first appearances
- By hand Scroll and compare by eye
- Insightlytics Flagged automatically each period
- In your reporting
- By hand A manual diff every time
- Insightlytics Joined into every report
Pricing
Priced to your site, not a plan you pick
No tiers to choose between. Pricing depends on your site's size and data. We scope it with you on a quick call, and your data is always yours.
Frequently asked questions
If something is still unclear, 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 is genuinely new demand. This is distinct from a query that already existed and simply improved its position or click-through.