How Willamette Week appears in ChatGPT, Perplexity, Claude, and Google AI Overviews
A free AI-visibility snapshot for Willamette Week (wweek.com) — a alt-weekly based in Portland, OR.
Overall AI visibility
wweek.com
73/100
Grade C
Across the four AI engines we audit (ChatGPT, Perplexity, Claude, and Google AI Overviews), Willamette Week is inconsistently cited by the engines we tested, with an overall 73/100 score. The largest open lift is on the engines below where Willamette Week's articles are missing structured signals other alt-weekly sites of the same size already publish.
ChatGPT
86
Crawler: GPTBot
GPTBot reaches the site and recent articles surface in citations.
Perplexity
67
Crawler: PerplexityBot
PerplexityBot allowed but author entities aren't strongly linked.
Claude
48
Crawler: ClaudeBot
ClaudeBot blocked or anthropic-ai variant disallowed in robots.txt.
Google AI Overviews
92
Crawler: Google-Extended
Google AI Overviews include the site for breaking and explainer queries.
What Willamette Week can ship this week
- 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.
- Add an XML sitemap entry for every article within an hour of publish so crawl latency for AI bots stays under 60 minutes.
- Add a public reporter bio page for every byline with `Person` schema, beats, and a sample of recent articles.
If you work at Willamette Week — 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.