How should you read the result?
Citations, sessions, bot requests, and search clicks count different events. They describe one page from different perspectives and cannot be summed.
Connect one owned page’s AI citations and prompts with technical, indexing, crawler, search, and analytics signals where available.
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.
Connect one owned page’s AI citations and prompts with technical, indexing, crawler, search, and analytics signals where available. An owned URL and associated project data are required. Each connected source has its own coverage and update timing; missing data does not mean zero performance.
Northstar · illustrative project · comparable 30-day periods. These examples explain how to use and interpret the measurements.
AI citations
60Related prompts
4Sample readiness
90 / 100Figures shown are illustrative sample data.
Sixty citations in total, not sixty unique users or visits.
Figures shown are illustrative sample data.
| Metric / scope | Sample value | Interpretation |
|---|---|---|
| northstar.example/guide | 60 citations | Selected URL occurrences |
| GA4 AI traffic | 45 sessions | Separate identifiable visit metric |
| Crawler logs | 120 requests | Bot activity, not visitors |
| Search performance | 320 clicks | Separate Google search scope |
Figures shown are illustrative sample data.
Citations, sessions, bot requests, and search clicks count different events. They describe one page from different perspectives and cannot be summed.
A frequently cited page warrants review of access and available visit outcomes. Related prompts identify relevant questions.
Check freshness, URL matching, and data availability before connecting signals. Co-occurrence does not establish causation.
An often-cited guide also shows access errors in connected logs. URL 360 brings these distinct signals together around the same page.
An illustrative scenario, not a customer result or a promise of results.
An owned URL and associated project data are required. Each connected source has its own coverage and update timing; missing data does not mean zero performance.
URL 360 organises connected page data. URL analysis starts a targeted investigation and can use selected prompt or topic context.
No. Connected aggregates provide context, not individual click-level causal proof.
Sources observed for the same prompts provide alternatives for comparing the owned page’s role.
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 analysisExplore one question’s measured answers, owned mentions, competitors, and connected owned or external URLs.
Explore this feature →: Prompt 360Connect your investigation of AI presence with measurable visits to your website.
Explore this feature →: Visits from AI sourcesTell 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.