How Votebeat appears in ChatGPT, Perplexity, Claude, and Google AI Overviews
A free AI-visibility snapshot for Votebeat (votebeat.org) — a nonprofit newsroom based in New York, NY.
Overall AI visibility
votebeat.org
51/100
Grade F
Across the four AI engines we audit (ChatGPT, Perplexity, Claude, and Google AI Overviews), Votebeat is rarely cited by the engines we tested, with an overall 51/100 score. The largest open lift is on the engines below where Votebeat's articles are missing structured signals other nonprofit newsroom sites of the same size already publish.
ChatGPT
32
Crawler: GPTBot
GPTBot likely blocked or pages return JS-only shells.
Perplexity
76
Crawler: PerplexityBot
PerplexityBot ingests the archive; bylines and datelines are extracted.
Claude
57
Crawler: ClaudeBot
ClaudeBot allowed; speakable schema would lift answer-engine reuse.
Google AI Overviews
38
Crawler: Google-Extended
Site rarely appears in AI Overviews — Google-Extended likely blocked.
What Votebeat can ship this week
- Cross-link each article from at least two evergreen topic pages so AI engines can find it after the homepage rotates it off.
- Publish a `/llms.txt` at the root that maps your beats, reporter bios, and the canonical URL for each topic.
- Mark paywalled body content with `cssSelector` exclusions but leave the lede + first 200 words free — that's what answer engines quote.
- Server-render every article. JS-only shells fail GPTBot's HTML fetch and quietly drop you out of citations.
- Add `<script type="application/ld+json">` NewsArticle schema with `speakable`, `dateline`, and `isAccessibleForFree` to every story page.
If you work at Votebeat — 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.