Directory · Vertical AI: enterprise, legal, health, bio
Lunit — what a crawler receives from lunit.io
Website measurement, not a product review. This page records what machine clients received from lunit.io. It does not evaluate Lunit software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 72/100, measured 2026-10-07 14:18 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can technically reach this site and would struggle to get anything quotable out of it.
Held at C A medium-severity finding sets the letter.
6
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.
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.
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
6 findings on this site, 3 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.
3 Medium 3 Note
1robots.txt declares no sitemapNo Sitemap: directive present.MediumSetting
What we saw
No Sitemap: directive present. /robots.txt
Why it matters
Adding one Sitemap: line lets crawlers enumerate the site instead of guessing at it.
How to fix it
Add a Sitemap: line to robots.txt pointing at the full sitemap URL, so crawlers find it without guessing.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
On WordPress (detected)
- WordPress serves a virtual robots.txt. Edit it in your SEO plugin: Yoast SEO → Tools → File editor; Rank Math → General Settings → Edit robots.txt; All in One SEO → Tools → Robots.txt Editor.
- A real robots.txt file in the site root (the folder with wp-config.php) overrides every plugin. If one exists, edit that file instead, through your host's file manager or SFTP.
- Keep one group per crawler: a crawler that has its own User-agent group ignores the * group entirely, so repeat any Disallow lines it still needs.
On WordPress (detected)
- WordPress 5.5 and later serve /wp-sitemap.xml; Yoast and Rank Math replace it with /sitemap_index.xml. Keep exactly one turned on.
- Core's wp-sitemap.xml has no lastmod dates; Yoast and Rank Math sitemaps do. If the finding is missing lastmod, use the plugin sitemap.
- Add the sitemap's address to robots.txt as Sitemap: https://yourdomain/sitemap_index.xml.
Why this was decided
| Rule | ROBOTS_NO_SITEMAP · rule pack sv28 · scope core |
|---|---|
| Evaluated | 2026-10-07 14:18:58 UTC |
| Decision | d1:ea2d7cfa48a0f6fb19a9 · finding f1:5fd3d47f97ce9d89f713 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 4c64f0e2 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /robots.txt | 200 | 0 | e3b0c44298fc | already_held |
21 more in the manifest.
Artifacts: manifest:8a28ca609c4bd65921673a3e89bc624055cffa088c5c0d3c37597b04d0ce5572
Grade effect Caps the letter at C together with 2 other medium-severity findings; the letter rises only when all of them are gone. Moves no points.
Rule ROBOTS_NO_SITEMAP under scoring rules v31 · fingerprint ROBOTS_NO_SITEMAP|/robots.txt · persisting (4 scans)
Verify the fix Re-scan after the change. This finding is cleared when ROBOTS_NO_SITEMAP is no longer reported at /robots.txt; if it comes back after clearing, it is marked a regression, not a new finding.
ROBOTS_NO_SITEMAP · full transcript
Open the other 5
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 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 6 findings on lunit.io. $749, once.
3 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 robots.txt. 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 190,870 decompressed bytes the homepage delivers, 3.3% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 3.3% · 6,280 B
- Markup & attributes 52.1% · 99,493 B
- Structured data (JSON-LD) 3.1% · 5,973 B
- Inline CSS 12.1% · 23,034 B
- Inline JavaScript 17.8% · 33,967 B
- Inline SVG 10.1% · 19,206 B
- HTML comments 1.5% · 2,917 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 17,179 B (9%) — WordPress theme or block stylesopens
:root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio - Inline JavaScript · 11,014 B (5.8%) — unnamedopens
(function() { var openYears = {}; // Store which years are open var is - Inline JavaScript · 4,468 B (2.3%) —
#ct_code_block_js_16opensdocument.addEventListener('DOMContentLoaded', function () { const TARG - Inline CSS · 4,321 B (2.3%) — WordPress theme or block stylesopens
:root{--wp-block-synced-color:#7a00df;--wp-block-synced-color--rgb:122 - Inline JavaScript · 4,036 B (2.1%) —
#ct_custom_js_14opensdocument.addEventListener('DOMContentLoaded', function () { const head
What changed
No change recorded between the readings on file yet.
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 lunit.ioIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If lunit.io 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.