How Semafor appears in ChatGPT, Perplexity, Claude, and Google AI Overviews

A free AI-visibility snapshot for Semafor (semafor.com) — a digital-native based in New York, NY.

Overall AI visibility
semafor.com
64/100
Grade D

Across the four AI engines we audit (ChatGPT, Perplexity, Claude, and Google AI Overviews), Semafor is rarely cited by the engines we tested, with an overall 64/100 score. The largest open lift is on the engines below where Semafor's articles are missing structured signals other digital-native sites of the same size already publish.

ChatGPT
92
Crawler: GPTBot
GPTBot reaches the site and recent articles surface in citations.
Perplexity
73
Crawler: PerplexityBot
PerplexityBot ingests the archive; bylines and datelines are extracted.
Claude
54
Crawler: ClaudeBot
ClaudeBot allowed; speakable schema would lift answer-engine reuse.
Google AI Overviews
35
Crawler: Google-Extended
Site rarely appears in AI Overviews — Google-Extended likely blocked.

What Semafor can ship this week

  1. Add a public reporter bio page for every byline with `Person` schema, beats, and a sample of recent articles.
  2. Allow `GPTBot`, `PerplexityBot`, `ClaudeBot`, `anthropic-ai`, `Google-Extended`, and `Applebot-Extended` in `https://semafor.com/robots.txt`.
  3. Cross-link each article from at least two evergreen topic pages so AI engines can find it after the homepage rotates it off.
  4. Publish a `/llms.txt` at the root that maps your beats, reporter bios, and the canonical URL for each topic.
  5. Mark paywalled body content with `cssSelector` exclusions but leave the lede + first 200 words free — that's what answer engines quote.
If you work at Semafor — or any other digital-native — the same audit, but live and continuous on every article you publish, is what Mani does.
Start a 7-day free trial →
$20/mo after trial. No card to start. See integrations.

Run the audit on your own domain