Vercel

← board · vercel.com · #14 of 33

Ready with a few material gaps

81/ 100
B
Grade
82
Agent readiness
Board average 73
Scanned 2 hours ago

Every outstanding fix in one prompt for your coding agent. Rescan →

Task

What does vercel.com do and how do I use it? A fetch-only agent finds out.

12 fetches7 found5 missing

home
  • /robots.txt/sitemap.xml
  • /llms.txt/llms-full.txt
  • /pricing
  • /docs
  • /openapi.json
  • mcp.jsonMCP initialize
  • /privacy · /terms
404 probe

every path the scanner fetched · replayed deterministically, no LLM

Evaluator notes

A fetch-only agent reached vercel.com over HTTPS in 155 ms and identified it from its title as “Agentic Infrastructure - Vercel”. The copy is readable without JavaScript (338,267 chars of visible text, 56.1% of HTML). It found pricing, docs and an OpenAPI spec. It looked for an MCP server and found none.

Critical access needs attention

Whether an ordinary agent can enter, read, and operate the public site.

  • Agents can reach the site

    Crawler access and bot defenses.

    4 / 4 passed
  • Core content is available

    Useful content remains accessible without a fragile browser-only path.

    2 / 2 passed
  • ~
    Navigation fails safely

    Redirects and missing pages give agents a recoverable path.

    1 / 2 passed
  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    3 / 3 passed

Fix these gaps first

Critical access gaps come first, then the biggest remaining points.

  1. 01
    Analytics installedMeasured

    Install analytics (PostHog, Plausible, GA4) before spending on traffic.

    +6 pts
  2. 02
    Meta description 50–160 charactersMetadata

    Add a meta description between 50 and 160 characters.

    +5 pts
  3. 03
    Spec parses and declares a versionAPI

    Serve valid JSON with an openapi or swagger version field.

    +4 pts
  4. 04
    Agent manifest (MCP, A2A or ai-plugin)Agent-ready

    Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.

    +2 pts
  5. 05
    Agent-friendly 404sCritical access

    Return a real 404 for paths that do not exist; a 200 app shell makes every wrong guess look like a page.

    +2 pts

Audit the checks behind the score

Grouped by what they measure. Not-applicable checks are excluded from scoring.

Crawlable5 of 5 passed · 19/19 pts
  • Served over HTTPS5/5

    https://vercel.com/

  • Responds in under 1.5s5/5

    155 ms to first byte

  • robots.txt present2/2

    User-Agent: * Content-Signal: search=yes, ai-input=yes, ai-train=no # Allow robo…

  • sitemap.xml present2/2

    /sitemap.xml → 200

  • Homepage is indexable5/5

    HTTP 200

Metadata6 of 7 passed · 19/24 pts
  • Title tag 10–70 characters5/5

    "Agentic Infrastructure - Vercel" (31)

  • Meta description 50–160 characters0/5

    "The autonomous stack for every app and agent." (45)

    Add a meta description between 50 and 160 characters.

  • Canonical URL set3/3

    https://vercel.com

  • Exactly one H14/4

    1 × <h1>: "Agentic Infrastructure"

  • Mobile viewport set3/3

    width=device-width, initial-scale=1, maximum-scale=1

  • Language declared2/2

    <html lang="en">

  • Favicon declared2/2

    https://assets.vercel.com/image/upload/q_auto/front/favicon/vercel/favicon.ico

Shareable3 of 3 passed · 14/14 pts
  • Open Graph title, description and image8/8

    title, description, image

  • Twitter/X card type set3/3

    twitter:card = summary_large_image

  • Links to X or LinkedIn3/3

    2 social link(s)

Converts3 of 3 passed · 17/17 pts
  • Clear call to action8/8

    3 CTA(s), e.g. "Download Brand Assets"

  • Pricing page linked6/6

    → /pricing

  • HTML under 2 MB3/3

    589 KB of HTML

Measured0 of 1 passed · 0/6 pts
  • Analytics installed0/6

    no analytics tag detected

    Install analytics (PostHog, Plausible, GA4) before spending on traffic.

Agent-ready16 of 19 passed · 41/46 pts
  • Structured data (JSON-LD)4/4

    @type: Organization, Service, SoftwareApplication

  • Machine-readable pricing3/3

    Offer / Product in JSON-LD

  • llms.txt present1/1

    /llms.txt → 200, 3507+ chars

  • llms-full.txt present0/1

    no /llms-full.txt

    Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.

  • AI crawlers allowed in robots.txt2/2

    none of 9 known AI crawlers blocked

  • No noai / TDM reservation2/2

    no opt-out signals

  • Serves markdown on request1/1

    Accept: text/markdown → text/markdown; charset=utf-8

  • OpenAPI spec discoverable7/7

    application/json; charset=utf-8 at /openapi.json or /.well-known/openapi.json

  • Agent manifest (MCP, A2A or ai-plugin)0/2

    no manifest at /.well-known/{mcp,agent,ai-plugin}.json

    Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.

  • Docs or API link from the homepage3/3

    homepage links to docs / API

  • Content readable without JavaScript3/3

    338,267 chars of visible text, 56.1% of HTML

  • Semantic landmarks (main, single H1)3/3

    <main> present, 1 × <h1>

  • Images have alt text2/2

    17/17 images have alt

  • Form fields are labelled2/2

    3/3 fields have a label, name or aria-label

  • Descriptive link text2/2

    0/166 links say "click here" / "learn more"

  • Agent-friendly 404s0/2

    a nonexistent path returned HTTP 200

    Return a real 404 for paths that do not exist; a 200 app shell makes every wrong guess look like a page.

  • Trust pages (privacy, terms, security)n/a
  • Organization schema complete2/2

    Organization has name, url, logo, sameAs, description

  • llms.txt says what you are and links out2/2

    3507+ chars, has H1, has links

  • Contact route discoverable2/2

    mailto:, /contact or /support link found

API0 of 1 passed · 0/4 pts
  • Spec parses and declares a version0/4

    spec fetched but is not valid JSON

    Serve valid JSON with an openapi or swagger version field.

  • Operations have summaries and operationIdsn/a
  • Error responses documentedn/a
  • Auth scheme declaredn/a
  • Versioned paths or serversn/a
  • Spec within a model context budgetn/a
MCPn/a
  • Server answers initializen/a
  • Tools listedn/a
  • Tools carry descriptionsn/a
  • Tool parameters have schemasn/a

AI visibility

Do AI assistants actually recommend Vercel? Grounded LLM checks plus ecosystem presence, folded into the score.

  • Category share of voice0/6

    not in the shortlist; assistants name: Here, Visual, Studio, Code, VS, It

    Publish comparison and use-case content so AI assistants have grounds to recommend vercel.com for its category.

  • Brand name discoverability3/3

    Vercel is a cloud platform that provides infrastructure and developer tools for building, deploying, and scaling web applications and AI age

  • Wikipedia / Wikidata presence2/2

    article: Vercel

  • SDK package on npm1/1

    npm: vercel

  • Listed in the MCP registry0/1

    not listed

    Publish your MCP server to registry.modelcontextprotocol.io so agents can find it.

Vercel is not consistently named by AI assistants in its category and is absent from the MCP registry. However, its brand is discoverable with a clear description, a Wikipedia article, and an npm SDK package.

AI-analyzed 2 hours ago · cached 7 days · grounded via web search

The report is free. Visibility is the bid.

Vercel sits at #14 of 33. $1 moves it above Dub.

Bid $1

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-25T11:39:30.239Z.

← Back to the board