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

A free AI-visibility snapshot for Berkeleyside (berkeleyside.org) — a nonprofit newsroom based in Berkeley, CA.

Overall AI visibility
berkeleyside.org
54/100
Grade F

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

ChatGPT
35
Crawler: GPTBot
GPTBot likely blocked or pages return JS-only shells.
Perplexity
79
Crawler: PerplexityBot
PerplexityBot ingests the archive; bylines and datelines are extracted.
Claude
60
Crawler: ClaudeBot
ClaudeBot allowed; speakable schema would lift answer-engine reuse.
Google AI Overviews
41
Crawler: Google-Extended
Site rarely appears in AI Overviews — Google-Extended likely blocked.

What Berkeleyside can ship this week

  1. Mark paywalled body content with `cssSelector` exclusions but leave the lede + first 200 words free — that's what answer engines quote.
  2. Server-render every article. JS-only shells fail GPTBot's HTML fetch and quietly drop you out of citations.
  3. Add `<script type="application/ld+json">` NewsArticle schema with `speakable`, `dateline`, and `isAccessibleForFree` to every story page.
  4. Add an XML sitemap entry for every article within an hour of publish so crawl latency for AI bots stays under 60 minutes.
  5. Add a public reporter bio page for every byline with `Person` schema, beats, and a sample of recent articles.
If you work at Berkeleyside — or any other nonprofit 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