How Hartford Courant appears in ChatGPT, Perplexity, Claude, and Google AI Overviews

A free AI-visibility snapshot for Hartford Courant (courant.com) — a regional daily based in Hartford, CT.

Overall AI visibility
courant.com
51/100
Grade F

Across the four AI engines we audit (ChatGPT, Perplexity, Claude, and Google AI Overviews), Hartford Courant is rarely cited by the engines we tested, with an overall 51/100 score. The largest open lift is on the engines below where Hartford Courant's articles are missing structured signals other regional daily 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 Hartford Courant 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 Hartford Courant — or any other regional daily — 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