CrawlCheck

Directory · AI visibility monitoring

Athena — what a crawler receives from athenahq.ai

Website measurement, not a product review. This page records what machine clients received from athenahq.ai. It does not evaluate Athena software, features, pricing or support.

77
Bgrade

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

AI visibility 77/100, measured 2026-10-15 07:11 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can reach and read this site. What is left is giving it something specific to say.

Open the full report athenahq.ai ↗

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

3

findings

✓

llms.txt on its host

✗

entity map on its host

19

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, and one that cannot read it never quotes it.

98

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.

73

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.

54

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

3 findings on this site. Every one is named below; the top one is shown in full, free. What we saw, why each matters, how to fix it and the bytes behind it are what a licence buys — or we implement the whole list for you.

1 Low 2 Note

1The sitemap does not say when anything changed232 URLs across 1 child sitemap all carry the same lastmod (2026-10-14T20:30:20.685Z), which is a build stamp rather than a change date. Read from every child oLowContent

What we saw

232 URLs across 1 child sitemap all carry the same lastmod (2026-10-14T20:30:20.685Z), which is a build stamp rather than a change date. Read from every child of the sitemap index. /sitemap-0.xml

Why it matters

The sitemap lists URLs but carries no lastmod dates, so it says what exists and not what changed. A crawler with a budget uses lastmod to decide what to re-fetch; without it, the choice is made for you — usually by re-crawling little and late. This is the change signal every crawler already understands, and unlike a push protocol it needs no key, no account and no participation from the search engine.

How to fix it

Add <lastmod> dates to sitemap entries so a crawler can prioritise pages that changed.

Content: words, markup or images on a page — no deploy

Fix it with a coding agent

Paste into Claude Code, Cursor or Codex, opened on the code that serves this site.

Show prompt
You are working in the codebase (or server/CDN configuration) that serves athenahq.ai. A crawler audit found the problem below. Fix it at the source, keep the change as small as possible, and do not change anything a visitor sees unless the fix requires it.

Finding: The sitemap does not say when anything changed (SITEMAP_NO_LASTMOD, low severity)
Page: https://athenahq.ai/sitemap-0.xml
What was measured: 232 URLs across 1 child sitemap all carry the same lastmod (2026-10-14T20:30:20.685Z), which is a build stamp rather than a change date. Read from every child of the sitemap index.
Why it matters: The sitemap lists URLs but carries no lastmod dates, so it says what exists and not what changed. A crawler with a budget uses lastmod to decide what to re-fetch; without it, the choice is made for you — usually by re-crawling little and late. This is the change signal every crawler already understands, and unlike a push protocol it needs no key, no account and no participation from the search engine.
How to fix it: Add <lastmod> dates to sitemap entries so a crawler can prioritise pages that changed.

Rule and examples: https://crawlcheck.io/rules/SITEMAP_NO_LASTMOD
Full report (markdown): https://crawlcheck.io/r/mdbfpcen9a.md

When you are done:
1. Tell me which files or settings you changed and why.
2. If the fix is a server, CDN or cache setting you cannot change from the code, say exactly where it is set.
3. After deploying, re-scan at https://crawlcheck.io/?url=athenahq.ai . The fix counts when SITEMAP_NO_LASTMOD is gone from the new report.
Why this was decided
RuleSITEMAP_NO_LASTMOD · rule pack sv32 · scope route
Evaluated2026-10-15 07:11:48 UTC
Decisiond1:e7aafefbfc7c69747e9d · finding f1:6ba7cf27a850c431f471 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build fa0d1b5a · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /sitemap.xml2001983c55920e67ccalready_held
read: /sitemap_index.xml40466,58358e63c2bf6b5already_held
read: /wp-sitemap.xml40466,58358e63c2bf6b5already_held

19 more in the manifest.

Artifacts: manifest:da72810498d6c272ca01f07585f150567e2cbb06ba0860ca466fa8c4abd35724

Grade effect Does not cap the letter: only medium, high and critical findings do. Moves no points either; the score is built from the measured rows.

Rule SITEMAP_NO_LASTMOD under scoring rules v32 · fingerprint SITEMAP_NO_LASTMOD|/sitemap-0.xml · persisting (2 scans)

Verify the fix Re-scan after the change. This finding is cleared when SITEMAP_NO_LASTMOD is no longer reported at /sitemap-0.xml; if it comes back after clearing, it is marked a regression, not a new finding.

SITEMAP_NO_LASTMOD · full transcript

2The homepage is reached through a chain of redirects🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
3A missing agent file answers with a full page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 2

What we saw, why it matters, how to fix it, and the evidence bytes for every finding — on this report and every re-scan. From $29 a month.

Unlock the findings

Or have them fixed

We implement the list on your site and re-measure, with a sealed before and after. One site, $749 once.

Get this fixed — $749

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 204,731 decompressed bytes the homepage delivers, 8.3% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 8.3% · 16,915 B
  • Markup & attributes 67.7% · 138,689 B
  • Inline CSS 5.2% · 10,620 B
  • Inline JavaScript 4.9% · 9,942 B
  • Inline SVG 12.6% · 25,878 B
  • HTML comments 1.3% · 2,687 B

The individual blocks that weigh the most, so the fix is a search rather than a hunt:

  • Inline CSS · 8,761 B (4.3%) — unnamedopens .btn-icon--star[data-astro-cid-vzkia6wc]{display:inline-flex;margin-le
  • Inline SVG · 3,512 B (1.7%) — .before-after-arrowopens <mask id="mask0_content-marketing" style="mask-type:alpha" maskUnits="
  • Inline SVG · 3,498 B (1.7%) — .before-after-arrowopens <mask id="mask0_brand-marketing" style="mask-type:alpha" maskUnits="us
  • Inline JavaScript · 3,479 B (1.7%) — unnamedopens (()=>{var A=Object.defineProperty;var g=(i,o,a)=>o in i?A(i,o,{enumera
  • Inline SVG · 3,414 B (1.7%) — .before-after-arrowopens <mask id="mask0_aeo" style="mask-type:alpha" maskUnits="userSpaceOnUse
Section average over 2 scans on this score version · held at 80 since 2026-10-15
0501002026-10-15 03:02 · 79/100 · 4 findings2026-10-15 07:11 · 80/100 · 3 findings2026-10-152026-10-15

What changed

  1. 2026-10-15score moved 79 → 80score-up
  2. 2026-10-15the stale edge copy clearedresolved
  3. 2026-10-15a new finding appeared: the sitemap does not say when anything changedappeared
  4. 2026-10-15the homepage began taking more than one redirect to reachappeared
  5. 2026-09-25a stale edge copy was served againreturned
  6. 2026-09-24the stale edge copy clearedresolved
  7. 2026-09-19a stale edge copy was served againreturned
  8. 2026-09-18the stale edge copy clearedresolved
  9. 2026-09-16a new finding appeared: the machine files cost more than the pageappeared
  10. 2026-09-15a stale edge copy was served againreturned
  11. 2026-09-13the stale edge copy clearedresolved
  12. 2026-09-10a stale edge copy was served againreturned

19 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

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If athenahq.ai is yours you can prove it in a minute and for nothing — a DNS TXT record or one meta tag on the home page, both checkable by anyone.

Claiming marks you as the verified owner and lets you correct the category and the company name. It moves no score, no rank and no position.

Claim this listing — free or ask about a verified profile

Dispute or re-scan

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

By email instead: hello@crawlcheck.io. Category “AI visibility monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.