Directory · AI visibility monitoring
Rankscale — what a crawler receives from rankscale.ai
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 83/100, measured 2026-09-02 17: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.
Held at C A medium-severity finding sets the letter.
2
findings
✓
llms.txt on its host
✗
entity map on its host
3
scans on record since 2026-09-01
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 read, because the three run in order.
What to fix, in order
Findings first: each one holds the grade down until it is gone (the top one sets the letter). 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.
1Almost nothing a machine receives from this page is readable text4.1% of 549,111 decompressed bytes is visible textMedium
What we saw
4.1% of 549,111 decompressed bytes is visible text
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.
PAGE_IS_MOSTLY_CODE · 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 +14 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 rankscale.aiGet 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 549,111 decompressed bytes the homepage delivers, 4.1% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 4.1% · 22,621 B
- Markup & attributes 68.2% · 374,740 B
- Structured data (JSON-LD) 2.8% · 15,628 B
- Inline CSS 0.7% · 3,706 B
- Inline JavaScript 2.1% · 11,420 B
- Inline SVG 21.8% · 119,829 B
- HTML comments 0.2% · 1,167 B
What changed
No change recorded between the readings on file yet.
3 scans on record, first 2026-09-01. 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 rankscale.aiDispute 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 “AI visibility monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.