Directory · Site crawler
Oncrawl — what a crawler receives from oncrawl.com
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 79/100, measured 2026-09-03 08:17 UTC from outside its network, as fifteen named crawler identities and one unnamed client. 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
6
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; 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.
The stage to fix first is quote, because the three run in order.
What to fix, in order
Findings first: each one holds the grade down until it is gone. Then headroom: each one lifts the score by the points shown. Open a card for what we saw, why it matters and how to fix it.
Files, generated from this scan
Each file says at its top exactly what was changed or filled and what was left as a TODO. Publish, then re-scan: done is measured.
1HTTPS is served without a Strict-Transport-Security headerThe homepage answered over HTTPS (200) with no Strict-Transport-Security header.Note
What we saw
The homepage answered over HTTPS (200) with no Strict-Transport-Security header.
Why it matters
Strict-Transport-Security tells a browser that has visited once to use HTTPS for every later request without trying HTTP first. Without it, a typed or linked http:// address makes one plaintext request before the redirect. It does not change what crawlers receive or how the site ranks; it is a small, reversible hardening step, and it is listed at the lowest severity for that reason.
How to fix it
Send Strict-Transport-Security: max-age=15552000; includeSubDomains on HTTPS responses (Cloudflare: SSL/TLS, Edge Certificates, HSTS). Leave preload off unless you intend a change that takes months to undo.
HSTS_MISSING · full transcript
2A business record gives an address but no coordinates1 business node declare a street address with no latitude/longitude.Note
What we saw
1 business node declare a street address with no latitude/longitude.
Why it matters
A resolver must geocode a text address rather than read a point, which is where ambiguity between similarly-named or nearby businesses is introduced.
How to fix it
Add latitude and longitude to the LocalBusiness node's geo property so an engine can place the business on a map without guessing.
ENTITY_NO_COORDINATES · full transcript
Headroom +21 points if every row passes
Nothing here is broken. Each row is a measure that currently fails its optimal range, and what fixing it is worth to the score.
Watch this domain
Twice-daily scans, the date each finding first appeared, and a change receipt when something moves. Free for 30 days, no card.
Start watching oncrawl.comGet this fixed for you
Every finding above fixed on your site, then re-measured - done is measured, not asserted. One-time, from $750.
See the fix serviceThe chain a crawler follows
The chain breaks at entity graph. 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 76,779 decompressed bytes the homepage delivers, 9.3% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 9.3% · 7,152 B
- Markup & attributes 58.8% · 45,134 B
- Structured data (JSON-LD) 4.8% · 3,687 B
- Inline CSS 21.4% · 16,465 B
- Inline JavaScript 5.2% · 4,001 B
- HTML comments 0.4% · 340 B
What changed
- 2026-09-03a new finding appeared: https is served without a strict-transport-security headerappeared
- 2026-09-02score moved 82 → 79score-down
- 2026-09-01a new finding appeared: an entity is missing geographic coordinatesappeared
- 2026-08-18resolved: the cache is still serving a file the origin no longer hasresolved
- 2026-08-18a new finding appeared: the cache is still serving a file the origin no longer hasappeared
6 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 oncrawl.comDispute or re-scan
If a reading here is wrong, it is our instrument that is wrong, and we want to know. Email hello@crawlcheck.io and the site is re-measured; the result is published as measured. Nothing about a listing, a payment or a request changes a number.
Category “Site crawler” is our label for what the product is primarily sold as; it is not scored. Back to the directory.