How Chicago Reader appears in ChatGPT, Perplexity, Claude, and Google AI Overviews

A free AI-visibility snapshot for Chicago Reader (chicagoreader.com) — a alt-weekly based in Chicago, IL.

Overall AI visibility
chicagoreader.com
59/100
Grade D

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

ChatGPT
56
Crawler: GPTBot
GPTBot is allowed but article-level structured data is thin.
Perplexity
37
Crawler: PerplexityBot
PerplexityBot blocked or paywalled before the lede.
Claude
81
Crawler: ClaudeBot
ClaudeBot crawls clean HTML; Anthropic citations appear for evergreen pieces.
Google AI Overviews
62
Crawler: Google-Extended
AIO surfaces the site occasionally; missing FAQ + speakable hurts.

What Chicago Reader can ship this week

  1. Publish a `/llms.txt` at the root that maps your beats, reporter bios, and the canonical URL for each topic.
  2. Mark paywalled body content with `cssSelector` exclusions but leave the lede + first 200 words free — that's what answer engines quote.
  3. Server-render every article. JS-only shells fail GPTBot's HTML fetch and quietly drop you out of citations.
  4. Add `<script type="application/ld+json">` NewsArticle schema with `speakable`, `dateline`, and `isAccessibleForFree` to every story page.
  5. Add an XML sitemap entry for every article within an hour of publish so crawl latency for AI bots stays under 60 minutes.
If you work at Chicago Reader — 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