Skip to content

vercel.com

Record E4zsbLg1x · May 31, 2026

for “deploy next.js app”

This week’s fixes. The 5 fixes that add the most to this page’s readiness, in the order to ship them. Roughly a day of work, by our estimate.

36/100to52/100

+16 points of readiness if you ship them all

Dark is today, light is the gain. Readiness, not a citation count.

Re-scored with the rubric’s current weights; the record itself shows 42.

Ship these, in this order

Ranked by the points each fix adds to readiness, using the rubric’s own weights. Each card’s points assume the fixes above it are already done.

  1. Direct answer in the lead

    Fix 1 · Content · +5 points

    Now: 0 of 4 query terms appear in the first paragraph.

    Do this: Open the page with a direct, complete answer to the buyer query: engines extract their citation snippet from the lead paragraph.

    Effort: 2 to 4 hours · Signal score now 0/100

  2. Outbound links to authoritative sources

    Fix 2 · Authority · +3 points

    Now: 0 links to authoritative domains (.edu, .gov, named sources).

    Do this: Add 2-3 outbound citations to .edu / .gov / known publishers. The GEO paper measured this as the #2 citation-lift factor.

    Effort: 2 to 4 hours · Signal score now 0/100

  3. Inline citations and attributions

    Fix 3 · Authority · +3 points

    Now: 0 bracketed citations + 0 attribution phrases (per 200 words: 0%).

    Do this: Add inline citations ([1], [2]) or attribution phrases ("according to X"). GEO factor #1 for credibility-weighted citation.

    Effort: 2 to 4 hours · Signal score now 0/100

  4. Statistic density

    Fix 4 · Authority · +3 points

    Now: 0 numerical facts (~0 per 100 words).

    Do this: Add concrete statistics with sources. AI engines preferentially cite paragraphs containing numbers: a GEO paper §4.1 finding.

    Effort: 2 to 4 hours · Signal score now 0/100

  5. Content freshness

    Fix 5 · Authority · +2 points

    Now: No parseable date: engines treat undated content as stale.

    Do this: Add a parseable date: `<time datetime="2026-01-15">` or `<meta property="article:modified_time">`.

    Effort: 2 to 4 hours · Signal score now 0/100

After you ship these, check they’re live.

The schema verifier reads your page again and confirms every JSON-LD block parses. Then run the audit again to see what moved.