CrawlCheck

Directory · AI visibility monitoring

Athena — what a crawler receives from athenahq.ai

80
Bgrade

Answer engines can reach and read this site. It needs more it can quote.

AI visibility 80/100, measured 2026-09-02 16:17 UTC from outside its network, as fifteen named crawler identities and one unnamed client. An engine can reach and read this site. What is left is giving it something specific to say.

Open the full report athenahq.ai ↗

1001. ReachCan a named answer-engine crawler get your pages at all?762. ReadOnce it has the bytes, can it find the words?563. QuoteIs there a specific fact it can state and attribute?

1

finding

✓

llms.txt on its host

✗

entity map on its host

3

scans on record since 2026-09-01

The three stages, in the order an engine hits a site

Each stage gates the next. An engine that cannot reach a page never reads it; one that cannot read it never quotes it. That is why reach is a ceiling and not just a weight.

100

Stage 1 · 40% of the score

Reach

Can a named answer-engine crawler get your pages at all?

Every named crawler was served the same page a browser gets.

76

Stage 2 · 30% of the score

Read

Once it has the bytes, can it find the words?

The content is buried in markup, or the files that guide a crawler are missing.

56

Stage 3 · 30% of the score

Quote

Is there a specific fact it can state and attribute?

An assistant would have to paraphrase your page instead of quoting a fact.

The stage to fix first is quote, because the three run in order.

What to fix, in order

Findings first: each one holds the grade down until it is gone. Then headroom: each one lifts the score by the points shown. Open a card for what we saw, why it matters and how to fix it.

Files, generated from this scan

entitymap.json, startedyour name, phone, coordinates and every declared service area as entities; TODOs marked

Each file says at its top exactly what was changed or filled and what was left as a TODO. Publish, then re-scan: done is measured.

1Visitors and crawlers are being served an old copy of this pagethe copy served to us was built 10 hours 37 min agoLow

What we saw

the copy served to us was built 10 hours 37 min ago

Why it matters

The page handed to us carried a cache age older than an hour. Nothing is broken today — the copy matches what the origin produces. It matters the moment you change something: an edit, a new price, a corrected phone number stays invisible to every visitor and every crawler for about that long, and nothing in your dashboard says so.

How to fix it

Lower the cache lifetime on HTML (an hour or less), or purge the edge and origin caches after every publish so crawlers see the current copy.

STALE_CACHE_SERVED · full transcript

Headroom +18 points if every row passes

Nothing here is broken. Each row is a measure that currently fails its optimal range, and what fixing it is worth to the score.

+3No hidden block over 50 wordsnow 9 block(s), 633 words · Instructions for agents+1.5A named person is declarednow none · Authors & trust signals+1.5Contact page or direct contact linkednow no · Authors & trust signals+1.5Cost of a missnow 2 missing file(s) return >20KB of HTML · Machine files+1.5Homepage links are declared in the sitemapnow 1 linked but undeclared · Sitemap+1.5entitymap.jsonnow absent (404) · Machine files+1.2Content rationow 8.6% · Page weight & text+0.8Entity nodesnow 0 · Structured data+0.8Lead paragraph defines the subjectnow does not name it, no defining verb · Quotable content+0.8Paragraphs an engine can quote wholenow 7 of 55 (13%) · Quotable content+0.8Sentences with a checkable factnow 11 of 90 (12%) · Quotable content+0.8Stable @id coveragenow 0% · Structured data

Watch this domain

Twice-daily scans, the date each finding first appeared, and a change receipt when something moves. Free for 30 days, no card.

Start watching athenahq.ai

Get this fixed for you

Every finding above fixed on your site, then re-measured - done is measured, not asserted. One-time, from $750.

See the fix service

The chain a crawler follows

The chain breaks at entity graph. Everything after that point is only reachable by a crawler guessing the conventional path.

✓robots.txtEvery crawler reads this first
✓sitemapNamed in robots.txt and resolves
✓llms.txtPoints onward, links stay on this host
✗entity graphParses as JSON and points home

A machine file that does not parse is worth less than one that is absent, because it looks present. Rows behind this.

Where the bytes go

Of the 195,052 decompressed bytes the homepage delivers, 8.6% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 8.6% · 16,836 B
  • Markup & attributes 66.2% · 129,089 B
  • Inline CSS 5.4% · 10,620 B
  • Inline JavaScript 5.1% · 9,942 B
  • Inline SVG 13.3% · 25,878 B
  • HTML comments 1.4% · 2,687 B

What changed

  1. 2026-09-02a stale edge copy was servedappeared

3 scans on record, first 2026-09-01. Score movements are shown only between readings taken under the same score version; finding codes are comparable across all of them.

Is this your site?

This listing reads the public record. Claim it and Watch keeps that record on your terms: every list this page holds back, finding age, and twice-daily re-measurement. Free for 30 days, no card.

Claim the record for athenahq.ai

Dispute or re-scan

If a reading here is wrong, it is our instrument that is wrong, and we want to know. Email hello@crawlcheck.io and the site is re-measured; the result is published as measured. Nothing about a listing, a payment or a request changes a number.

Category “AI visibility monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.