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

A free AI-visibility snapshot for KQED (kqed.org) — a public-radio newsroom based in San Francisco, CA.

Overall AI visibility
kqed.org
64/100
Grade D

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

ChatGPT
77
Crawler: GPTBot
GPTBot reaches the site and recent articles surface in citations.
Perplexity
58
Crawler: PerplexityBot
PerplexityBot allowed but author entities aren't strongly linked.
Claude
39
Crawler: ClaudeBot
ClaudeBot blocked or anthropic-ai variant disallowed in robots.txt.
Google AI Overviews
83
Crawler: Google-Extended
Google AI Overviews include the site for breaking and explainer queries.

What KQED can ship this week

  1. Add an XML sitemap entry for every article within an hour of publish so crawl latency for AI bots stays under 60 minutes.
  2. Add a public reporter bio page for every byline with `Person` schema, beats, and a sample of recent articles.
  3. Allow `GPTBot`, `PerplexityBot`, `ClaudeBot`, `anthropic-ai`, `Google-Extended`, and `Applebot-Extended` in `https://kqed.org/robots.txt`.
  4. Cross-link each article from at least two evergreen topic pages so AI engines can find it after the homepage rotates it off.
  5. Publish a `/llms.txt` at the root that maps your beats, reporter bios, and the canonical URL for each topic.
If you work at KQED — or any other public-radio newsroom — 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