openai.com
Partial visibility
AI engines can reach you, but 3 signals need work to get you into most generated answers. Fix the WARN and FAIL items below.
Homepage returns HTTP 200 with ~3,117 chars of server-rendered text. Retrieval bots can read you.
How to fix: AI crawler access →No blanket Disallow for the major AI crawlers — GPTBot, ClaudeBot and PerplexityBot can fetch your key pages.
How to fix: AI crawler rules →No /llms.txt found. Engines have no curated map to your best content — they're guessing.
How to fix: llms.txt playbook →No JSON-LD schema on the homepage. Engines can't tell what type of entity you are.
How to fix: Answer Engine Optimization →Some structure, but too few sections — add question-shaped H2s with a short answer capsule under each.
How to fix: GEO playbook →You are an engineer working on the website openai.com. Below is an AI-visibility (GEO) audit of the site — the signals that decide whether AI answer engines (ChatGPT, Perplexity, Google AI Overviews) can crawl, understand and cite it. Implement the fixes. ## Audit findings ### Sitewide signals - [PASS] AI-crawler reachability: Homepage returns HTTP 200 with ~3,117 chars of server-rendered text. Retrieval bots can read you. - [PASS] GPTBot / ClaudeBot access: No blanket Disallow for the major AI crawlers — GPTBot, ClaudeBot and PerplexityBot can fetch your key pages. - [FAIL] llms.txt: No /llms.txt found. Engines have no curated map to your best content — they're guessing. - [FAIL] JSON-LD schema: No JSON-LD schema on the homepage. Engines can't tell what type of entity you are. - [WARN] Answer-first structure: Some structure, but too few sections — add question-shaped H2s with a short answer capsule under each. ## Implementation rules - Work through the failing signals in the order above; PASS items need no changes. - Crawler access: check robots.txt AND the WAF/CDN layer for blocks on GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended. - llms.txt: create a curated Markdown index at /llms.txt per https://llmstxt.org — one H1, a > summary, ## sections, every link with a one-line description. - JSON-LD: add Organization (+ logo, sameAs) sitewide and Article/FAQPage on content pages; link entities with absolute @id references. - 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 openai.com until all 5 signals are PASS. - Validate llms.txt at https://geoplaybooks.com/tools/llms-txt-validator/ (0 errors). - Verify JSON-LD parses in Google's Rich Results Test.
⚔ Compare openai.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.