CrawlCheck

Directory · Content and GEO

Koala — what a crawler receives from koala.sh

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

87
Agrade

Answer engines can reach and read this site. It needs more it can quote.

AI visibility 87/100, measured 2026-10-11 04:17 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.

Open the full report koala.sh ↗

2

findings

✗

llms.txt on its host

✗

entity map on its host

6

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.

91

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.

86

Stage 2 · 30% of the score

Read

Once it has the bytes, can it find the words?

The delivered HTML is mostly content, and the machine files point at the rest.

81

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. 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 1 Note

1The HSTS header asks for browser preloading but does not qualify for itThe header sends the preload token but max-age is 2592000 (30 days), the list requires 31536000.LowSetting

What we saw

The header sends the preload token but max-age is 2592000 (30 days), the list requires 31536000.

Why it matters

The header carries the `preload` token, which is a request to be compiled into the HTTPS-only list shipped inside browsers. That list only accepts a header with max-age of at least 31536000 (one year) AND includeSubDomains AND preload. As sent, the token is ignored: the site is declaring an intent it does not meet, and if it ever was on the list, this header is what gets it removed. The rest of the HSTS header still works.

How to fix it

Either raise max-age to 31536000 and keep includeSubDomains so the preload token qualifies, or remove the preload token. As sent it does nothing.

Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing

On Next.js (detected)

  1. next.config.js headers(): source '/(.*)' with Strict-Transport-Security: max-age=63072000; includeSubDomains. Some hosts send it already; check the live response before adding a second copy.

In Cloudflare (this site is behind it)

  1. SSL/TLS → Edge Certificates → HTTP Strict Transport Security (HSTS) → Enable: max-age 12 months; include subdomains and preload only when every subdomain is on HTTPS for good.

All Next.js fixes

Why this was decided
RuleHSTS_PRELOAD_INELIGIBLE · rule pack sv31 · scope core
Evaluated2026-10-11 04:17:29 UTC
Decisiond1:2fd7ef62690a090588f4 · finding f1:065ad81dec443ffe15fd resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build be8a9372 · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /20073,602e09fa0ec29c2write_unconfirmed

21 more in the manifest.

Artifacts: manifest:909aca76d6421f1946981f7d280a86741fe56312af874f374b601d3e96922f7f

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 HSTS_PRELOAD_INELIGIBLE under scoring rules v31 · fingerprint HSTS_PRELOAD_INELIGIBLE|/ · persisting (6 scans)

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

HSTS_PRELOAD_INELIGIBLE · full transcript

2No llms.txt/llms.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

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 findings

Or 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 — $749

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.

✓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 73,506 decompressed bytes the homepage delivers, 12.7% is text a reader or a model can actually use. Workable, with room to trim.

  • Readable text 12.7% · 9,321 B
  • Markup & attributes 48.3% · 35,518 B
  • Structured data (JSON-LD) 2.1% · 1,534 B
  • Inline JavaScript 1.7% · 1,231 B
  • Inline SVG 35.2% · 25,846 B
  • HTML comments 0.1% · 56 B

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

  • Inline SVG · 2,275 B (3.1%) — .h-8opens <g id="Layer_1-2"><path d="M140.75 148.45c-27.58 13.31-26.26 20.59-32.
  • Inline SVG · 2,275 B (3.1%) — .h-8opens <g id="Layer_1-2"><path d="M140.75 148.45c-27.58 13.31-26.26 20.59-32.

What changed

  1. 2026-10-03score moved 85 → 86score-up

6 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 koala.sh

Is this your company?

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