ai-referrals: let the caller ask for the tail, not just the top 25
The landing-page report was hardcoded to 25 rows. That is a dashboard view, and it was being used as a measurement: GDA's AI sessions (1,016/28d) run ~10x its GSC blog clicks (104/28d across 273 pages), so any per-page traffic ranking
The landing-page report was hardcoded to 25 rows. That is a dashboard view, and it was being used as a measurement: GDA's AI sessions (1,016/28d) run ~10x its GSC blog clicks (104/28d across 273 pages), so any per-page traffic ranking of the blog is really a ranking on this number. With ~640 of those sessions sitting below the 25th page, a top-decile cutoff over ~715 blog pages lands squarely inside the truncated region and cannot be computed at all.
pageLimit is additive and defaults to the old 25, so every existing caller is unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>