CrawlCheck

Directory · AI security and governance

Credo AI — what a crawler receives from credo.ai

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

82
Bgrade

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

AI visibility 82/100, measured 2026-10-06 11:19 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 credo.ai ↗

1

finding

✓

llms.txt on its host

✗

entity map on its host

5

scans on record since 2026-09-18

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.

83

Stage 1 · 40% of the score

Reach

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

At least one answer engine was refused, challenged or served less than a browser.

83

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.

78

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

1 finding on this site. Every one is named below; the top one is shown in full, free. Want it fixed for you? We implement it and re-measure.

1 Note

1Visitors and crawlers are being served an old copy of this pagethe copy served to us was built 21 hours 43 min ago, and byte-identical to a fresh read, so the cache is old but not wrongNoteSetting

What we saw

the copy served to us was built 21 hours 43 min ago, and byte-identical to a fresh read, so the cache is old but not wrong

Why it matters

The page handed to us carried a cache age older than an hour. The detail says whether the copy still matches what the origin produces now: if it matches, nothing is broken today; if it differs, an edit is already waiting behind the cache. 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.

Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing

On Webflow (detected)

  1. Republish the site; Webflow clears its CDN on publish. If Cloudflare is in front, purge there too.

All Webflow fixes

Why this was decided
RuleSTALE_CACHE_SERVED · rule pack sv27 · scope route
Evaluated2026-10-06 11:19:06 UTC
Decisiond1:4f28d315b093d932cfe6 · finding f1:09107f85b3c4a74c9c7d resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 71386c1f · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /200169,4746ab9cfd66e96kept
read: /200169,4746ab9cfd66e96kept
read: /200169,4746ab9cfd66e96kept

21 more in the manifest.

Artifacts: manifest:755ec97f44c8ad2e0ddcfd7f99a2b9f5a87ad1aab6b09104a7f1f78b0709267f

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 STALE_CACHE_SERVED under scoring rules v31 · fingerprint STALE_CACHE_SERVED|/ · persisting (4 scans)

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

STALE_CACHE_SERVED · full transcript

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

  • Readable text 7.5% · 12,673 B
  • Markup & attributes 46.8% · 79,262 B
  • Structured data (JSON-LD) 1.1% · 1,836 B
  • Inline CSS 0.3% · 552 B
  • Inline JavaScript 4.2% · 7,132 B
  • Inline SVG 39% · 66,110 B
  • HTML comments 1% · 1,776 B

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

  • Inline SVG · 7,025 B (4.1%) — unnamedopens <path d="M4.84235 3.61829C4.84235 4.64101 4.01327 5.4701 2.99054 5.470
  • Inline SVG · 5,911 B (3.5%) — unnamedopens <mask id="path-1-inside-1_1322_819" fill="white"> <path fill-rule="eve

What changed

  1. 2026-10-02score moved 80 → 81score-up
  2. 2026-09-20a stale edge copy was servedappeared

5 scans on record, first 2026-09-18. 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 credo.ai

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If credo.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 security and governance” is our label for what the product is primarily sold as; it is not scored. Back to the directory.