vercel.com
Strong technical baseline
This is an internal technical-readiness score, not a measure of AI mentions, citations or rankings. Test real prompts separately. How we score.
Homepage returned HTTP 200 with about 4,664 characters of server-rendered text to our checker.
How to fix: AI crawler access →No homepage disallow found for GPTBot, ClaudeBot, PerplexityBot, Google-Extended or CCBot. Other paths and actual crawler access can differ.
How to fix: AI crawler rules →/llms.txt is present with an H1 (5,538 bytes). Use the dedicated validator for a full format check; presence does not measure citations.
How to fix: llms.txt playbook →Parsable JSON-LD found: Organization, Service, SoftwareApplication. Required properties and factual accuracy still need validation.
How to fix: Answer Engine Optimization →H1, 17 H2 sections and a short paragraph detected. Review relevance and answer quality manually.
How to fix: GEO playbook →You are an engineer working on the website vercel.com. All five technical checks passed at the recorded run. Review any remaining page-level issues below; the result does not establish AI visibility. This is an internal technical-readiness score, not a measure of AI mentions, citations or rankings. Test real prompts separately. ## Audit findings ### Sitewide signals - [PASS] AI-crawler reachability: Homepage returned HTTP 200 with about 4,664 characters of server-rendered text to our checker. - [PASS] GPTBot / ClaudeBot access: No homepage disallow found for GPTBot, ClaudeBot, PerplexityBot, Google-Extended or CCBot. Other paths and actual crawler access can differ. - [PASS] llms.txt: /llms.txt is present with an H1 (5,538 bytes). Use the dedicated validator for a full format check; presence does not measure citations. - [PASS] JSON-LD schema: Parsable JSON-LD found: Organization, Service, SoftwareApplication. Required properties and factual accuracy still need validation. - [PASS] Answer-first structure: H1, 17 H2 sections and a short paragraph detected. Review relevance and answer quality manually. ## Implementation rules - Prioritize confirmed access problems and content quality. Check that stored findings still apply; a PASS is limited to what this probe tested. - Crawler access: check robots.txt AND the WAF/CDN layer. Distinguish training crawlers, search crawlers and user-triggered fetchers; preserve intentional opt-outs. - llms.txt is optional. If useful for the site's agents, create a curated Markdown index per https://llmstxt.org; its absence is not proof of search invisibility. - JSON-LD: use types and properties that accurately describe the visible content; link entities with absolute @id references. Do not add FAQPage or other types solely to raise a score. - Answer-first structure: under each question-shaped H2, place a self-contained 40–80-word answer paragraph before any elaboration. - Do not fabricate content; restructure what exists. ## Acceptance criteria - Re-run the free checker at https://geoplaybooks.com/check/ for vercel.com; record resolved findings and any intentional exclusions instead of forcing every signal to PASS. - If llms.txt is published, validate it at https://geoplaybooks.com/tools/llms-txt-validator/ (0 errors). - Validate JSON-LD syntax, applicable schema requirements and accuracy against visible content. Passing validation does not guarantee citations.
Share your technical baseline
This domain scores 100/100 on five technical checks. The badge links to this stored result and updates after a new check. It does not certify AI visibility.
⚔ Compare vercel.com with a competitor side by side →
Is this your site?
Scores move as you ship fixes. Re-run the check anytime — or get a human to run the deep version with cross-engine prompt-sampling.