CTR far below the site's own benchmark for its position (Navboost proxy)

Trial testimony and the 2024 opinion describe Navboost as memorising which results users click for each query over 13 months. A result that is shown but rarely chosen, or chosen then abandoned, is the pattern that signal records. This check measures CTR in Search Console as a proxy; it cannot observe Navboost or Google's click quality judgements.

Rewrite the title and meta description to match the dominant intent of the queries the page ranks for, move the direct answer into the first screen, and remove misleading promises. Re-measure after 8 to 12 weeks against the same position bucket.

1. Export 3 months of Search Console performance data by page and query, excluding branded queries.
2. Group rows into position buckets (1, 2, 3, 4 to 5, 6 to 10) and compute the site's median CTR per bucket.
3. Flag page and query pairs with at least 500 impressions whose CTR is below half the bucket median.
4. Review each flagged result in a live SERP: compare title, snippet and SERP features against competitors to find the cause.

Written for the Navboost page (evidence: Trial or leak evidence). Google has not documented this system in a way a site can test directly, so this check measures a proxy for it, not the system itself.

Indirect. Better CTR at equal position is a direct traffic gain; any ranking effect through Navboost is an estimate only.

Judge Mehta's August 2024 opinion (findings 96 and 102), Pandu Nayak's 18 October 2023 testimony, PXR0357 call notes, and the QualityNavboostCrapsCrapsData model in the May 2024 leak.