Directory · AI security and governance
Lakera — what a crawler receives from lakera.ai
Website measurement, not a product review. This page records what machine clients received from lakera.ai. It does not evaluate Lakera software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 76/100, measured 2026-10-07 09: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.
3
findings
✗
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.
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.
- Structured data43
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals75
- Linked datan/a
- Quotable contentn/a
- Entity corroborationn/a
- Page subjectn/a
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 changed481 URLs listed, none carrying a lastmod date.LowContent
What we saw
481 URLs listed, none carrying a lastmod date. /sitemap.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
On Webflow (detected)
- Site settings → SEO → Sitemap: turn on auto-generate, then publish. It is served at /sitemap.xml.
- Pages excluded from search (page settings) are left out.
Why this was decided
| Rule | SITEMAP_NO_LASTMOD · rule pack sv28 · scope core |
|---|---|
| Evaluated | 2026-10-07 09:19:06 UTC |
| Decision | d1:70739325d8f4eac0d743 · finding f1:cd39e6cc3f7572ba601f resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 9a18d6c8 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /sitemap.xml | 200 | 47,339 | ac2249cf47fb | already_held |
| read: /sitemap_index.xml | 404 | 33,504 | 00f2a4889ee3 | already_held |
| read: /wp-sitemap.xml | 404 | 33,504 | 00f2a4889ee3 | already_held |
21 more in the manifest.
Artifacts: manifest:da933d245cdc4cf0658ac327cca933833602c4626e397ecaa8eba47e7b1ab9ab
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 v31 · fingerprint SITEMAP_NO_LASTMOD|/sitemap.xml · persisting (5 scans)
Verify the fix Re-scan after the change. This finding is cleared when SITEMAP_NO_LASTMOD is no longer reported at /sitemap.xml; if it comes back after clearing, it is marked a regression, not a new finding.
SITEMAP_NO_LASTMOD · full transcript
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 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 3 findings on lakera.ai. $749, once.
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 llms.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 102,898 decompressed bytes the homepage delivers, 6% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 6% · 6,216 B
- Markup & attributes 43.7% · 44,988 B
- Inline CSS 7% · 7,242 B
- Inline JavaScript 7.5% · 7,727 B
- Inline SVG 35.3% · 36,294 B
- HTML comments 0.4% · 431 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 5,357 B (5.2%) — unnamedopens
/* Focus state style for keyboard navigation for the focusable element - Inline JavaScript · 3,638 B (3.5%) — jQueryopens
window._vwo_code || (function() { var account_id=974355, version=2.1, - Inline SVG · 3,283 B (3.2%) — unnamedopens
<path d="M11.3333 0C11.1565 0 10.987 0.0702379 10.8619 0.195262C10.736 - Inline SVG · 2,669 B (2.6%) — unnamedopens
<path d="M7.33325 3.00001H12.1999C12.9467 3.00001 13.32 3.00001 13.605
What changed
- 2026-10-03score moved 78 → 80score-up
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 lakera.aiIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If lakera.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.