Vercel Analytics scorecard: a grade per landing page
Grade every landing page A to D on traffic trend, pages per visit, conversion, Core Web Vitals and visitors sent onward, with a fix prompt for weak ones.
Last updated October 21, 2026
Which landing pages are pulling their weight?
Most teams on Vercel run one main site and a ring of landing pages around it: a pricing page, a launch page, a page per campaign or per event. Vercel Web Analytics shows each one on its own, so “which of these works?” turns into a spreadsheet. Lookout’s Scorecard answers it on one screen: every landing page on a board gets a grade from A to D, against the board’s other landing pages, for the range you pick.
The main site is the board’s busiest site, the one the others send visitors to. It isn’t graded; the pages around it are. Sites with no visitors in the range are left out.
The five factors
Each landing page is scored on five things, each good, fair or weak:
| Factor | What it measures | Good | Weak |
|---|---|---|---|
| Trend | Visitors against the previous period | Up 10% or more | Down 10% or more |
| Pages / visit | Page views per visitor, against the board’s median | 1.15× the median or more | 0.85× the median or less |
| Conversion | Goal conversion rate, against the board’s median | 1.2× the median or more | 0.6× the median or less |
| Web Vitals | Core Web Vitals from Speed Insights (p75) | Passing | Poor |
| Sends visitors onward | Share of visitors who go on to your other sites | 15% or more | Under 8% |
Pages per visit stands in for bounce rate, which Vercel’s API doesn’t return (why). Conversion needs a goal on the site, and Web Vitals needs Speed Insights; a page without one of them is marked “not fully graded” and is scored on the rest. Sending visitors onward comes from Flow: the visitors whose next site was another site on the board.
Reading the card
- The header counts the A grades (keep them as templates), the D grades (fix or retire them) and the pages not fully graded.
- Each row shows the grade, the page’s visitors, the five factors and one line on why it got that grade, for example “Traffic is falling and it’s a dead end”.
- Sort by best first, needs work first, or most traffic.
- Open a row for the reason in full, a card per factor with the page’s value next to the board’s, the next step to take, and a link to the site’s own page.
A fix prompt for every weak page
When a factor is weak, the row offers Copy prompt to fix this page. The prompt carries the page’s real numbers (its grade, each factor with its value, the Core Web Vitals that fail, the main site to link to) and the page’s framework, with the steps to take for each weak factor. Paste it into Claude Code, Cursor or another AI agent working in that site’s repository, or send it to the developer who owns it.
From the API and MCP
The same grades come from GET /v1/boards/{id}/scorecard in the Lookout API, so an assistant connected through the MCP server can answer “which landing pages need work this month?” with the board’s real grades. The live demo has a board of Northwind’s landing pages to try it on.