CrawlCheck

Directory · ML platforms and experiment tracking

Determined AI — what a crawler receives from determined.ai

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

46
Dgrade

Answer engines are being served something other than this site.

AI visibility 46/100, measured 2026-09-30 12:17 UTC from outside its network, as each named AI and search crawler and as a browser. An answer engine cannot use this site. Whatever else is true of the marketing, the machine layer is shut.

Open the full report determined.ai ↗

4

findings

✗

llms.txt on its host

✗

entity map on its host

4

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.

50

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.

40

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.

—

Stage 3 · 30% of the score

Quote

Is there a specific fact it can state and attribute?

Not measured on this scan; left out rather than counted as zero.

  • Structured datan/a
  • Local presence & NAPn/a
  • Claim consistencyn/a
  • Authors & trust signalsn/a
  • Linked datan/a
  • Quotable contentn/a
  • Entity corroborationn/a
  • Page subjectn/a

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

What to fix

4 findings on this site, 2 of them scored serious. 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.

2 High 1 Low 1 Note

1robots.txt is unreadableHTTP 500.HighSetting

What we saw

HTTP 500. /robots.txt

Why it matters

A 5xx on robots.txt tells a standards-following crawler to treat the whole site as disallowed (RFC 9309). A 401 or 403 is a 4xx, which the standard treats as no file and so allows everything, though some crawlers read it as a refusal. Either way the rules you wrote are not the rules a crawler read. This is the single most expensive file on the site to get wrong.

How to fix it

robots.txt could not be fetched. Allow it through the security layer; it is the one file every crawler reads first.

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

Why this was decided
RuleROBOTS_BLOCKED · rule pack sv26 · scope core
Evaluated2026-09-30 12:17:48 UTC
Decisiond1:479bdb583c5b170e0270 · finding f1:40aef96b905eb7e27cf7 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 38212f1a · audit v4

What it rests on

IdentityStatusBytessha256Kept
crawlcheck5000e3b0c44298fcalready_held

5 more in the manifest.

Artifacts: manifest:8cad58a04c7e5b9f35259c3a437326092e8cdada91aefd2a11aa5c2cc7dcf350

Grade effect Caps the letter at D together with 1 other high-severity finding; the letter rises only when all of them are gone. Moves no points.

Rule ROBOTS_BLOCKED under scoring rules v31 · fingerprint ROBOTS_BLOCKED|/robots.txt · new on this scan (1 scan)

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

ROBOTS_BLOCKED · full transcript

2No XML sitemap found🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.High
3The homepage refused this client, so every homepage section is unmeasured🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Low
4No llms.txt/llms.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 3

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

What changed

  1. 2026-09-30resolved: this origin refused crawlcheck, so the site was never measuredresolved
  2. 2026-09-30a new finding appeared: robots.txt is unreadableappeared
  3. 2026-09-30no sitemap could be foundappeared
  4. 2026-09-30no llms.txt was foundappeared
  5. 2026-09-30the homepage refused this clientappeared

4 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 determined.ai

Is this your company?

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