VectorCiteVectorCite
AEO audit · May 31, 2026

vercel.com

on the querydeploy next.js app
42AEO score
Behind the cited cohort
Not cited at top 0·simulated retrieval against 0 candidates

The 30-signal rubric

13 ok · 3 weak · 14 absent

Every signal is measurable from your page. Hover for the detail and a remedy.

Structure

59/100
JSON-LD structured data70
1 JSON-LD block found.
JSON-LD validity100
1 of 1 JSON-LD block parse cleanly.
Schema type matches query intent40
Schema types found (SoftwareApplication) don't match a informational buyer intent.
Fix: Add a Article JSON-LD block — the highest-leverage schema type for a "deploy next.js app" query.
FAQ / Q&A schema0
No FAQPage / QAPage schema — AI Overviews preferentially cite pages exposing structured Q&A.
Fix: Add a FAQPage schema with 3-5 questions buyers actually ask. The single most direct path to AI Overview citation.
H1 quality30
2 H1s — multiple H1s confuse the retrieval-anchor signal.
Fix: Reduce to a single H1. Demote secondary H1s to H2.
H2 subtopic coverage100
13 H2 headings — answer engines decompose a buyer query into subtopics and match each to an H2.
Lists (bulleted / numbered)100
25 lists found.
Comparison tables50
No tables. Comparison / specification tables are heavily cited for product and technical queries.
Image alt-text coverage0
0 of 1 images have alt text (0%).
Fix: Add descriptive alt text to every image — engines index alt text as part of page content.
Open Graph metadata100
Open Graph title, description, and image all present.

Authority

14/100
Outbound links to authoritative sources0
0 links to authoritative domains (.edu, .gov, named sources).
Fix: Add 2-3 outbound citations to .edu / .gov / known publishers. The GEO paper measured this as the #2 citation-lift factor.
Inline citations and attributions0
0 bracketed citations + 0 attribution phrases (per 200 words: 0%).
Fix: Add inline citations ([1], [2]) or attribution phrases ("according to X"). GEO factor #1 for credibility-weighted citation.
Statistic density0
0 numerical facts (~0 per 100 words).
Fix: Add concrete statistics with sources. AI engines preferentially cite paragraphs containing numbers — a GEO paper §4.1 finding.
Expert quotations0
0 blockquotes + 0 long inline quotes.
Fix: Include at least one direct quote from a named expert, ideally in a <blockquote>. Quote-rich pages are 28% more likely to be cited (GEO paper).
Author byline0
No author byline. E-E-A-T penalises anonymous content.
Fix: Add a visible author byline (a `<div class="byline">` or `[rel="author"]`) AND a `<meta name="author">` tag.
Publish + update date markup0
No structured publish date. Freshness ranking can't be applied.
Fix: Add `<time datetime="...">` for published date AND a `<meta property="article:modified_time">` for updates.
Content freshness0
No parseable date — engines treat undated content as stale.
Fix: Add a parseable date — `<time datetime="2026-01-15">` or `<meta property="article:modified_time">`.
Technical / domain vocabulary100
32 multi-syllable words (~32.0% of total).

Content

34/100
Direct answer in the lead0
0 of 4 query terms appear in the first paragraph.
Fix: Open the page with a direct, complete answer to the buyer query — engines extract their citation snippet from the lead paragraph.
Query-term coverage25
25% of query terms appear somewhere on the page.
Fix: Cover every term in the buyer query at least once. Missing terms make embeddings drift and competitor pages win retrieval.
Named-entity coverage100
12 distinct proper-noun entities mentioned.
Readability (Flesch Reading Ease)20
Reading-ease score: 27.2 (target 60-70).
Fix: Page reads too academic — shorter sentences and simpler vocabulary lift citation rate by ~12% (GEO §4.3).
Content depth0
100 words. Target 300-2500 — engines bias toward focused depth.
Fix: Page is too short. Expand to at least 500 words covering the query in depth.
Information density100
Unique-word ratio: 56.0% (target 40-60%).
Definitional sentences0
0 definitional sentences.
Fix: Include definitional sentences ("X is...", "X refers to..."). Engines specifically extract definitions for AI Overview snippets.

Trust

100/100
HTTPS100
Page served over HTTPS.
Canonical URL100
Canonical: https://vercel.com
Mobile-friendly viewport100
Viewport meta tag present.
Twitter Card100
Twitter Card metadata present.
Meta description100
Meta description: 111 chars (target 50-160).

The Fix Kit

Behind the cited cohort (42/100) — 10 structural patches needed

Ready-to-paste patches. Schema.org JSON-LD, meta tags, copy guidance. The first three below are unlocked; the rest are gated behind a free account.

Article JSON-LD

A Article schema is the strongest single AEO signal for a informational query. Paste this in the <head>.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Build and deploy on the AI Cloud.",
  "description": "Vercel gives developers the frameworks, workflows, and infrastructure to build a faster, more personalized web.",
  "url": "https://vercel.com/",
  "datePublished": "2026-05-31",
  "author": {
    "@type": "Person",
    "name": "Add author name"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Vercel",
    "logo": {
      "@type": "ImageObject",
      "url": "https://vercel.com/logo.png"
    }
  }
}
</script>

FAQPage JSON-LD

FAQPage is the single most-cited schema type by Google AI Overviews. Add 3-5 Q&A pairs covering what buyers ask.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Scale your?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add a 1-2 sentence answer here, mentioning the key entity / number / claim that buyers searching \"deploy next.js app\" would expect."
      }
    },
    {
      "@type": "Question",
      "name": "What is without compromising?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add a 1-2 sentence answer here, mentioning the key entity / number / claim that buyers searching \"deploy next.js app\" would expect."
      }
    },
    {
      "@type": "Question",
      "name": "What is Get Started?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add a 1-2 sentence answer here, mentioning the key entity / number / claim that buyers searching \"deploy next.js app\" would expect."
      }
    },
    {
      "@type": "Question",
      "name": "What is Build?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add a 1-2 sentence answer here, mentioning the key entity / number / claim that buyers searching \"deploy next.js app\" would expect."
      }
    }
  ]
}
</script>

Organization JSON-LD

Organization schema gives the engine an E-E-A-T anchor — pages without one are treated as anonymous.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Vercel",
  "url": "https://vercel.com",
  "logo": "https://vercel.com/logo.png",
  "sameAs": [
    "https://twitter.com/your-handle",
    "https://linkedin.com/company/your-org"
  ]
}
</script>
7 more patches locked
Free account unlocks the full Fix Kit + continuous monitoring.
Unlock →
VectorCite Pro

Close the gap. Get cited.

Weekly probing across your buyer-query portfolio, full Fix Kit, score-change alerts, and a single dashboard your team can act from.