How The Village Voice appears in ChatGPT, Perplexity, Claude, and Google AI Overviews

A free AI-visibility snapshot for The Village Voice (villagevoice.com) — a alt-weekly based in New York, NY.

Overall AI visibility
villagevoice.com
75/100
Grade B

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

ChatGPT
88
Crawler: GPTBot
GPTBot reaches the site and recent articles surface in citations.
Perplexity
69
Crawler: PerplexityBot
PerplexityBot allowed but author entities aren't strongly linked.
Claude
50
Crawler: ClaudeBot
ClaudeBot allowed; speakable schema would lift answer-engine reuse.
Google AI Overviews
94
Crawler: Google-Extended
Google AI Overviews include the site for breaking and explainer queries.

What The Village Voice 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://villagevoice.com/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 The Village Voice — or any other alt-weekly — 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