Directory · Vertical AI: enterprise, legal, health, bio
Owkin — what a crawler receives from owkin.com
Website measurement, not a product review. This page records what machine clients received from owkin.com. It does not evaluate Owkin software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 79/100, measured 2026-09-18 21:17 UTC from outside its network, as twelve named crawler identities plus an unnamed client and two mobile-browser controls. An engine can reach and read this site. What is left is giving it something specific to say.
Held at C A medium-severity finding sets the letter.
2
findings
✓
llms.txt on its host
✗
entity map on its host
2
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.
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.
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?
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
2 findings on this site, 1 of them scored serious. The top one is below in full, free. Which the other 1 is, what we saw, and the bytes behind each one are what a licence buys — or we implement the whole list for you.
1 Medium 1 Note
1Visitors and crawlers are being served an old copy of this pagethe copy served to us was built 21 hours 18 min ago, and a fresh read differs from the cached copy at byte 44,211 (59,758 bytes cached vs 59,772 fresh)MediumSetting
What we saw
the copy served to us was built 21 hours 18 min ago, and a fresh read differs from the cached copy at byte 44,211 (59,758 bytes cached vs 59,772 fresh)
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.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Evidence bytes
[object Object]STALE_CACHE_SERVED · full transcript
See the other 1
Every finding, what we saw, why it matters, how to fix it, and the evidence bytes — on this report and every re-scan. From $29 a month.
Unlock the findingsOr 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 — $749The main product
We fix the 2 findings on owkin.com. $749, once.
1 of them are scored serious. One site. You keep the grade for free — this is the part where the list stops being a list.
- Every finding implemented on the site itself: machine files, schema, NAP, the lot
- An entity map authored for your business, not a template with the name swapped
- Measured again afterwards — the before and the after, sealed, so it is evidenced rather than claimed
- Thirty days of monitoring included
- Work starts within two business days
What it covers · one payment, nothing recurring
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.
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 59,730 decompressed bytes the homepage delivers, 8.7% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 8.7% · 5,224 B
- Markup & attributes 67.2% · 40,152 B
- Structured data (JSON-LD) 5.2% · 3,112 B
- Inline CSS 9.2% · 5,513 B
- Inline JavaScript 6.9% · 4,127 B
- Inline SVG 2% · 1,165 B
- HTML comments 0.7% · 437 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 4,012 B (6.7%) — unnamedopens
/* Make text look crisper and more legible in all browsers */ body { t - JSON-LD · 2,116 B (3.5%) — unnamedopens
{ "@context": "https://schema.org", "@type": "Organization", "name": "
What changed
- 2026-09-18a stale edge copy was servedappeared
2 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 owkin.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If owkin.com 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 “Vertical AI: enterprise, legal, health, bio” is our label for what the product is primarily sold as; it is not scored. Back to the directory.