Skip to main content
Card class: Non-HeroCategory: Keyword Performance

At a glance

New Queries is a table of search terms that began earning your site impressions or clicks during the selected period and were not present in the prior comparison window. Each row is a query with its current impressions, clicks, CTR and average position. It is your early-warning radar for emerging demand: the topics, products and questions people have just started finding you for.

What it tracks

The card compares the current period’s query set against the prior period and lists, row by row, the queries that appear now but did not before. These newcomers fall into a few useful patterns: terms you just started ranking for after publishing or optimising content, seasonal or trend-driven searches entering their window, long-tail variants Google has begun matching you to, and brand-adjacent or question-style queries that signal new audience intent. Reviewing new queries regularly tells content and SEO teams which fresh topics are gaining traction so they can double down with dedicated pages or on-page optimisation before competitors do. Note that Search Console anonymises rare queries, so genuinely tiny-volume newcomers may not surface here even when they exist.

Reconciling against the source

Approximate this in Search Console by opening the Performance report, setting a date comparison, sorting by Queries, and looking for terms with impressions in the current period but none in the prior one; the card automates that diff. Note Search Console data is typically 2 to 3 days delayed, rare queries are anonymised (so very low-volume newcomers may be hidden), and the UI caps at 1,000 rows.

Tracked live in Vortex IQ Nerve Centre

New Queries is one of hundreds of KPI pulses Vortex IQ tracks across Google Search Console and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.