Direct answer
Open Measure > Page Performance and inspect the score breakdown. The score combines site-wide percentiles for AI-answer source mentions (40%), AI referral visits from the selected analytics provider (25%), crawler occurrences (20%), and Google plus Bing clicks (15%). Use it as a relative Qwairy summary, then inspect each source column before prioritizing pages.Data required
Use normalized page paths, the current Page Performance scope, source connection states, recorded AI-answer source mentions, AI referral visits from the selected analytics provider, retained crawler occurrences, Google and Bing clicks, and the displayed score breakdown.Workflow
1
Validate source states
Confirm which integrations are connected, populated, empty, disconnected, or unavailable. Outside the score, missing data is not an observed zero.
2
Reconcile page URLs
Normalize protocol, hostname, path, parameters, redirects, and canonical variants before comparing page rows.
3
Inspect the score breakdown
Record which components are measured for the page. An unknown referral count removes its 25% weight, and an unknown crawler count removes its 20% weight. The score is normalized over the remaining weights. A measured zero keeps its weight.
4
Review source columns
Sort by the metric relevant to the decision and inspect answer mentions, AI referral visits, crawler occurrences, and Google plus Bing data as separate evidence.
Interpretation
The page score is relative to the site’s full path dataset, even when a folder filter is active. It is not an absolute quality grade, a search-engine ranking, a forecast, or proof of business impact. Answer mentions and search clicks keep their weights even when missing data contributes zero. Compare pages with the same measured signals.Possible next actions
- If a page score is unexpected, test URL reconciliation and source-state issues before changing the page.
- If one source column is weak, form a hypothesis specific to that source rather than treating the score as a diagnosis.
- If an important source is unavailable, connect or validate it before using the score for prioritization.
Limitations
Crawler page detail is limited to 30-day windows and can be bounded. Pseudonymized crawler paths are excluded from cross-source matching. Source coverage, refresh timing, and URL matching can change. The REST source-URLs endpoint is a separate contract and does not return this product score.Related pages
Source URLs in Looker Studio
Review documented URL-level reporting.
Page Performance
Understand page signals, source states, and score scope.
Source URLs API
Read the separate REST source-URL contract.
Pages cited by AI
Analyze recorded citation URLs separately.
AI traffic by page
Review recognized AI-referral landing pages.
Content pickup observations
Track publication milestones separately.

