CrawlCheck

Directory · LLM observability and evaluation

Langfuse — what a crawler receives from langfuse.com

Website measurement, not a product review. This page records what machine clients received from langfuse.com. It does not evaluate Langfuse software, features, pricing or support.

72
Cgrade

AI assistants like ChatGPT can reach your site, but get very little they can use.

AI visibility 72/100, measured 2026-10-30 15:03 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.

Open the full report langfuse.com ↗

961. ReachCan a named answer-engine crawler get your pages at all?662. ReadOnce it has the bytes, can it find the words?463. QuoteIs there a specific fact it can state and attribute?

3

findings

✓

llms.txt on its host

✗

entity map on its host

8

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, and one that cannot read it never quotes it.

96

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.

66

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.

46

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, the lowest of the three.

What to fix

3 findings on this site, 1 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.

1 Medium 2 Note

1Almost nothing a machine receives from this page is readable text1.9% of 583,941 decompressed bytes is visible text, and the largest single block is inline javascript at 74,847 bytesMediumDeveloper

What we saw

1.9% of 583,941 decompressed bytes is visible text, and the largest single block is inline javascript at 74,847 bytes

Why it matters

A crawler pays for every byte it fetches and can only quote the text. Under 5% readable content means an answer engine downloads the whole page and comes away with almost nothing it can use — the difference between being quotable and being skipped. The content-ratio row above passes at 20%, so without this a page at 2% and a page at 19% were scored identically.

How to fix it

Move inline CSS and JavaScript into external files, drop unused page-builder styling, and make sure the words a visitor reads are in the HTML itself.

Developer: a template, theme or application change — a developer touches it

On Next.js (detected)

  1. Render content on the server: keep it in Server Components (the App Router default) or use getStaticProps / getServerSideProps; avoid "use client" at the page root and content fetched only in useEffect.
  2. Check View Source, not the browser inspector: the text must be in the HTML the server sends.

All Next.js fixes

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 langfuse.com. 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: Almost nothing a machine receives from this page is readable text (PAGE_IS_MOSTLY_CODE, medium severity)
Page: https://langfuse.com/
What was measured: 1.9% of 583,941 decompressed bytes is visible text, and the largest single block is inline javascript at 74,847 bytes
Why it matters: A crawler pays for every byte it fetches and can only quote the text. Under 5% readable content means an answer engine downloads the whole page and comes away with almost nothing it can use — the difference between being quotable and being skipped. The content-ratio row above passes at 20%, so without this a page at 2% and a page at 19% were scored identically.
How to fix it: Move inline CSS and JavaScript into external files, drop unused page-builder styling, and make sure the words a visitor reads are in the HTML itself.
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/PAGE_IS_MOSTLY_CODE
Full report (markdown): https://crawlcheck.io/r/cykflo48w9.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=langfuse.com . The fix counts when PAGE_IS_MOSTLY_CODE is gone from the new report.
Why this was decided
RulePAGE_IS_MOSTLY_CODE · rule pack sv34 · scope route
Evaluated2026-10-30 15:03:15 UTC
Decisiond1:4f0ac32da106a8e1bf54 · finding f1:a6a3da6de4439df99371 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 48134344 · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /200583,998097c6134af1bkept

22 more in the manifest.

Artifacts: manifest:b52991a355aae5efe6fe2375567ead33fc4d9a3dac53f63ca66080efffe976e7

Grade effect Caps the letter at C. Without it the letter would be B (score 72). Moves no points; the score is built from the measured rows.

Rule PAGE_IS_MOSTLY_CODE under scoring rules v34 · fingerprint PAGE_IS_MOSTLY_CODE|/ · persisting (8 scans)

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

PAGE_IS_MOSTLY_CODE · full transcript

2The homepage is reached through a chain of redirects🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
3A missing agent file answers with a full page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

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 findings

Or have them fixed

We implement the list on your site and re-measure, with a sealed before and after. One site, $100 once.

Get this fixed — $100

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.

✓robots.txtEvery crawler reads this first
✓sitemapNamed in robots.txt and resolves
✓llms.txtPoints onward, links stay on this host
✗entity graphParses as JSON and points home

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 583,941 decompressed bytes the homepage delivers, 1.9% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 1.9% · 11,270 B
  • Markup & attributes 44.1% · 257,791 B
  • Inline JavaScript 46.6% · 271,983 B
  • Inline SVG 7.3% · 42,560 B
  • HTML comments 0.1% · 337 B

The individual blocks that weigh the most, so the fix is a search rather than a hunt:

  • Inline JavaScript · 74,847 B (12.8%) — unnamedopens self.__next_f.push([1,"1:\"$Sreact.fragment\"\n2:I[593100,[\"/_next/st
  • Inline JavaScript · 71,323 B (12.2%) — unnamedopens self.__next_f.push([1,"5c:I[188109,[\"/_next/static/immutable/chunks/0
  • Inline JavaScript · 67,888 B (11.6%) — unnamedopens self.__next_f.push([1,"69:[\"$\",\"footer\",null,{\"className\":\"px-4
  • Inline JavaScript · 37,159 B (6.4%) — unnamedopens self.__next_f.push([1,"a4:[\"$\",\"div\",null,{\"className\":\"pb-px b
  • Inline JavaScript · 14,475 B (2.5%) — unnamedopens self.__next_f.push([1,"a3:I[125896,[\"/_next/static/immutable/chunks/0
Section average over 2 scans on this score version · held at 72 since 2026-10-30
0501002026-10-23 10:04 · 71/100 · 3 findings2026-10-30 15:03 · 72/100 · 3 findings2026-10-232026-10-30

What changed

  1. 2026-10-30score moved 72 → 74score-up
  2. 2026-10-16the homepage began taking more than one redirect to reachappeared
  3. 2026-10-03score moved 69 → 71score-up

8 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 langfuse.com

Is this your company?

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