Vercel Web Analytics and Speed Insights, on the page row.
For sites hosted on Vercel, RankSage reads Web Analytics and Speed Insights and joins them to the same page rows as Search Console, content scores and AI citations — so a slow page that AI engines never cite is one row, not two dashboards.
What Vercel gives RankSage
- Web Analytics per page for the projects you connect.
- Speed Insights per page, joined to the same row as content and visibility.
- The performance half of a technical-readiness finding, next to the content half.
How to connect
- 1
Install the RankSage integration on Vercel
Choose the projects RankSage may read.
- 2
Match projects to sites
Each Vercel project maps to one tracked site.
- 3
Read and join
Analytics and Speed Insights fill in per page on the next sync.
What it unlocks
Agent Readiness
robots.txt, llms.txt, agents.md and your structured data — whether AI agents can reach you at all, and what to publish if not.
One ranked queue
Playbooks, recommendations and tasks merged into one what-do-I-fix-next list, ordered by a weighting you can read.
Frustration Report
Find the pages where visitors visibly struggle and the content is thin — the only place both signals point at the same URL.
What it does not do
- Only for sites hosted on Vercel; other hosts use GA4 and first-party tracking instead.
- Read-only; RankSage never deploys, redeploys or changes a project setting.
- Disconnecting removes the cached copy of that source's data from RankSage.
Questions
Does RankSage touch my deployments?
No. It reads analytics and performance data only. Deployment checks on pull requests are a separate GitHub integration.
Do I still need first-party tracking?
Vercel Web Analytics gives page-level traffic; RankSage's own script adds rage clicks, dead clicks, scroll depth and form abandonment, which no host analytics records.
Start with the two that matter.
Google Analytics and Search Console, read-only, about five minutes. Add Vercel whenever it earns its place.