Directory · Site crawler
Lumar — what a crawler receives from lumar.io
Website measurement, not a product review. This page records what machine clients received from lumar.io. It does not evaluate Lumar software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 84/100, measured 2026-10-18 17:08 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.
2
findings
✗
llms.txt on its host
✗
entity map on its host
17
scans on record since 2026-08-14
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, and one that cannot read it never quotes it.
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?
The facts an assistant is asked for are declared and consistent.
The stage to fix first is read, because the three run in order.
What to fix
2 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.
2 Note
1No llms.txtNot present: /llms.txt answered HTTP 404.NoteContent
What we saw
Not present: /llms.txt answered HTTP 404. /llms.txt
Why it matters
Not a defect. llms.txt is an emerging convention for telling AI systems what a site is and which pages matter.
How to fix it
Publish /llms.txt: a short Markdown file naming the business, what it does, and the pages worth reading, served as text/plain or text/markdown.
Content: words, markup or images on a page — no deploy
On WordPress (detected)
- Upload llms.txt to the site root, the folder with wp-config.php, through your host's file manager or SFTP.
- Recent versions of Yoast SEO and Rank Math can generate llms.txt for you; use one source only.
Fix it with a coding agent
Paste into Claude Code, Cursor or Codex, opened on the code that serves this site.
Show prompt
You are working in the codebase (or server/CDN configuration) that serves lumar.io. A crawler audit found the problem below. Fix it at the source, keep the change as small as possible, and do not change anything a visitor sees unless the fix requires it. Finding: No llms.txt (NO_LLMS_TXT, note severity) Page: https://lumar.io/llms.txt What was measured: Not present: /llms.txt answered HTTP 404. Why it matters: Not a defect. llms.txt is an emerging convention for telling AI systems what a site is and which pages matter. How to fix it: Publish /llms.txt: a short Markdown file naming the business, what it does, and the pages worth reading, served as text/plain or text/markdown. Detected platform: WordPress. Make the change where this platform controls it. Rule and examples: https://crawlcheck.io/rules/NO_LLMS_TXT Full report (markdown): https://crawlcheck.io/r/q4rlbv8ouk.md When you are done: 1. Tell me which files or settings you changed and why. 2. If the fix is a server, CDN or cache setting you cannot change from the code, say exactly where it is set. 3. After deploying, re-scan at https://crawlcheck.io/?url=lumar.io . The fix counts when NO_LLMS_TXT is gone from the new report.
Why this was decided
| Rule | NO_LLMS_TXT · rule pack sv32 · scope core |
|---|---|
| Evaluated | 2026-10-18 17:08:45 UTC |
| Decision | d1:22217df66f5104dffb64 · finding f1:3f9053a2279cab1246a0 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build b3cf8c17 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /llms.txt | 404 | 102,884 | 72774dc15de7 | already_held |
21 more in the manifest.
Artifacts: manifest:4c32194d726575f7e99380e849b5a052dee6efd42036341ce878e9219c098efe
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 NO_LLMS_TXT under scoring rules v32 · fingerprint NO_LLMS_TXT|/llms.txt · persisting (26 scans)
Verify the fix Re-scan after the change. This finding is cleared when NO_LLMS_TXT is no longer reported at /llms.txt; if it comes back after clearing, it is marked a regression, not a new finding.
NO_LLMS_TXT · full transcript
Open the other 1
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 2 findings on lumar.io. $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 228,318 decompressed bytes the homepage delivers, 8.1% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 8.1% · 18,519 B
- Markup & attributes 50.9% · 116,231 B
- Structured data (JSON-LD) 1.4% · 3,285 B
- Inline CSS 10.5% · 23,924 B
- Inline JavaScript 7.9% · 17,964 B
- Inline SVG 20.5% · 46,907 B
- HTML comments 0.7% · 1,488 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 8,980 B (3.9%) — WordPress theme or block stylesopens
:root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio - Inline CSS · 6,899 B (3%) — WordPress theme or block stylesopens
.wp-block-image>a,.wp-block-image>figure>a{display:inline-block}.wp-bl - Inline SVG · 3,969 B (1.7%) — unnamedopens
<path d="M13.5332 9.05926L13.4262 10.0535L13.4262 10.0535L13.5332 9.05 - Inline CSS · 3,617 B (1.6%) — WordPress theme or block stylesopens
:root{--wp-block-synced-color:#7a00df;--wp-block-synced-color--rgb:122 - Inline SVG · 3,463 B (1.5%) — unnamedopens
<title>Lumar</title> <path fill-rule="evenodd" clip-rule="evenodd" d="
What changed
- 2026-10-18the homepage is reached in one redirect or noneresolved
- 2026-10-15the homepage began taking more than one redirect to reachappeared
- 2026-10-02score moved 83 → 84score-up
- 2026-09-17a new finding appeared: the machine files cost more than the pageappeared
17 scans on record, first 2026-08-14. 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 lumar.ioIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If lumar.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 “Site crawler” is our label for what the product is primarily sold as; it is not scored. Back to the directory.