How should you read the result?
Twenty measurements return sixty subquery occurrences. One measurement can return several phrases. This is not total public search demand.
Inspect returned subqueries associated with measured questions and the observable search intents behind them.
An advance subscription is required to use the service. Send your request using the form below.
API measurements and separately measured interfaces can produce different results. Measurements describe the configured prompts and retrieval context.
Inspect returned subqueries associated with measured questions and the observable search intents behind them. Stored provider results must contain subquery data. Coverage varies. The feature does not invent missing subqueries or expose the complete internal reasoning of an AI system.
Northstar · illustrative project · comparable 30-day periods. These examples explain how to use and interpret the measurements.
Measurements returning subqueries
20Subquery occurrences
60Shown phrases
4Figures shown are illustrative sample data.
Sixty occurrences overall. Review measurement counts and results returning subquery data alongside the trend.
Figures shown are illustrative sample data.
| Metric / scope | Sample value | Interpretation |
|---|---|---|
| Main prompt | Choosing an SEO agency | Observation starting point |
| Prices | 24 occurrences | Recurring search direction |
| References | 18 occurrences | Trust-related sub-intent |
| All occurrences | 60 | Not sixty unique prompts or users |
Figures shown are illustrative sample data.
Twenty measurements return sixty subquery occurrences. One measurement can return several phrases. This is not total public search demand.
Recurring pricing and reference phrases help focus review of the corresponding service page.
More subqueries do not automatically mean better performance. Retrieval counts and provider coverage affect the chart.
A supplier-selection prompt returns subqueries about prices, references, and services. These observable signals help investigate whether your page addresses the relevant sub-intents.
An illustrative scenario, not a customer result or a promise of results.
Stored provider results must contain subquery data. Coverage varies. The feature does not invent missing subqueries or expose the complete internal reasoning of an AI system.
No. Suggestions help select new questions to measure; fan-out describes subqueries returned for questions already measured.
No. Only available returned data is shown. Missing data does not prove that the provider performed no search.
It collects stored subqueries for the selected prompt or topic context to help compare the page with the observed search intents.
Check the selected question or URL, filters, sample size, source coverage, and data freshness. Different scopes can produce differences unrelated to a real change.
No. A source connection, retrieval, or processing step may be missing. Check availability before interpreting an empty block.
The feature supports evidence-based investigation. It does not control provider answers or guarantee recommendations or citations.
Investigate a specific page in the context of a selected question or topic, combining technical checks, available performance data, and observed query fan-out.
Explore this feature →: URL analysisBuild a measurement set from buyer questions with domain- or topic-based suggestions, intent classification, demand context, and scheduled answer analysis.
Explore this feature →: Prompt management and suggestionsExplore one question’s measured answers, owned mentions, competitors, and connected owned or external URLs.
Explore this feature →: Prompt 360Tell us which brand and website you want to measure and what question you need to answer. We will discuss the subscription and data connections your project requires.