Skip to main content
Page Performance is available on active paid plans. Each source contributes only when its own connection and entitlement requirements are met.
Open Measure > Page Performance to compare several page-level data sources in one table. A tracked page is a normalized path present in at least one source, not a separate list of configured pages. The page can combine:
  • recorded source mentions in monitored AI answers;
  • GA4 sessions classified from recognized AI referrers;
  • observed crawler occurrences from retained daily rollups;
  • Google Search Console and Bing Webmaster Tools clicks, impressions, and position.
The table exposes source connection states. Read a missing source as unavailable, not as an observed zero. The score has a documented exception below: disconnected non-crawler sources currently remain zero-valued in its percentile inputs.

​
Summary and table

The summary can show tracked paths, GA4 AI-referral sessions, observed crawler occurrences, and combined Google plus Bing clicks. The table keeps the underlying units separate and shows source-specific trends where comparison data is available. Use source-state indicators to distinguish connected, disconnected, empty, and unavailable data. Sort by the metric relevant to the current question rather than treating every column as the same type of evidence.

​
About the score

The score compares each page with the site’s other pages using site-wide percentiles:
  • AI-answer source mentions: 40%;
  • GA4 AI-referral sessions: 25%;
  • crawler occurrences: 20%;
  • Google plus Bing clicks: 15%.
If crawler detail is not measured, its component is null and the remaining 80% is normalized to 100%; the score is marked partial. Other disconnected sources currently remain zero-valued rather than having their weights removed. A folder filter does not recalculate the site-wide percentiles. The score is a relative Qwairy summary for the current site dataset. It is not an absolute quality grade, a search-engine ranking, or a forecast of AI visibility.

​
Scope and coverage

Crawler page detail is queried only for windows of 30 days or less. The dashboard reads at most 250 crawler page identities; it marks crawler detail as bounded when pagination, count precision, or occurrences without a retained 2xx page identity prevent an exact page-level match. Missing delivery is not inferred as zero. When crawler detail is not measured, the crawler occurrence value is null. Paths pseudonymized by Crawler Analytics are excluded from matching with GA4, Search Console, and Bing.

​
Reconcile URLs

Cross-source matching removes query strings and fragments and lowercases paths. It does not reliably merge trailing-slash variants, redirects, or canonical alternatives. Confirm those mappings before comparing totals.

​
Page Performance in MCP

The dashboard and the MCP tool answer different questions:
  • Measure > Page Performance combines page-level signals from the connected product surfaces listed above.
  • MCP get_page_performance returns retained Crawler Analytics rollups only. It does not return answer citations, referral sessions, Search Console metrics, or raw HTTP events.
The MCP page-detail window covers at most 30 completed UTC days. period: "all" means 30 days, not lifetime history. Read the coverage caveats in the returned text before interpreting counts. The tool does not render a measured zero when no supported public occurrence exists. Pseudonymized paths are labelled as such in the rendered result and do not receive a page title. The tool also separates current pages from up to 10 neglected page identities and reports lifecycle states such as new, hot, and neglected.