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

A free AI-visibility snapshot for DigBoston (digboston.com) — a alt-weekly based in Boston, MA.

Overall AI visibility
digboston.com
66/100
Grade C

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

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

What DigBoston 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://digboston.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 DigBoston — 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