Directory · Site crawler
Botify — what a crawler receives from botify.com
Website measurement, not a product review. This page records what machine clients received from botify.com. It does not evaluate Botify software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 86/100, measured 2026-10-18 17:10 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.
Held at C A medium-severity finding sets the letter.
5
findings
✗
llms.txt on its host
✗
entity map on its host
21
scans on record since 2026-08-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.
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
5 findings on this site, 2 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.
2 Medium 3 Note
1Almost nothing a machine receives from this page is readable text4.9% of 136,808 decompressed bytes is visible text, and the largest single block is inline css at 14,019 bytesMediumDeveloper
What we saw
4.9% of 136,808 decompressed bytes is visible text, and the largest single block is inline css at 14,019 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 Webflow (detected)
- Remove unused interactions and custom code embeds; Webflow's own runtime cannot be reduced.
- Put the main text in the page itself, not in elements filled by script.
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 botify.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://botify.com/ What was measured: 4.9% of 136,808 decompressed bytes is visible text, and the largest single block is inline css at 14,019 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: Webflow. 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/4z7go5u7mr.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=botify.com . The fix counts when PAGE_IS_MOSTLY_CODE is gone from the new report.
Why this was decided
| Rule | PAGE_IS_MOSTLY_CODE · rule pack sv32 · scope route |
|---|---|
| Evaluated | 2026-10-18 17:10:51 UTC |
| Decision | d1:077f5a4282c939f08a50 · finding f1:59475372852742f7b541 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: / | 200 | 136,873 | 3e48c37b0b60 | write_unconfirmed |
23 more in the manifest.
Artifacts: manifest:ed7efbd51c378178df6b95e9b53a891c9be5efd9e1eabd594f0e8a0fccac087b
Grade effect Caps the letter at C together with 1 other medium-severity finding; the letter rises only when all of them are gone. Moves no points.
Rule PAGE_IS_MOSTLY_CODE under scoring rules v32 · fingerprint PAGE_IS_MOSTLY_CODE|/ · persisting (27 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
Open the other 4
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 5 findings on botify.com. $749, once.
2 of them are scored serious. 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 136,808 decompressed bytes the homepage delivers, 4.9% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 4.9% · 6,639 B
- Markup & attributes 69% · 94,418 B
- Structured data (JSON-LD) 2% · 2,687 B
- Inline CSS 14.5% · 19,885 B
- Inline JavaScript 7.3% · 9,936 B
- Inline SVG 2.2% · 2,948 B
- HTML comments 0.2% · 295 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 14,019 B (10.2%) — unnamedopens
body { -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: g - Inline SVG · 2,948 B (2.2%) —
.botify-logoopens<g clip-path="url(#clip0_2340_12147)"> <path fill="currentcolor" class - JSON-LD · 2,687 B (2%) — unnamedopens
{ "@context": "https://schema.org", "@graph": [ { "@type": "WebPage", - Inline JavaScript · 2,402 B (1.8%) — unnamedopens
const checkpoint1 = document.querySelector('.c-checkpoint-first'); con - Inline CSS · 2,401 B (1.8%) — unnamedopens
/* Force hide text before JS runs */ .c-first-text, .c-second-text { d
What changed
- 2026-10-15the homepage began taking more than one redirect to reachappeared
- 2026-10-09resolved: links on this site point at pages that do not answerresolved
- 2026-10-05a stale edge copy was served againreturned
- 2026-10-01the stale edge copy clearedresolved
- 2026-10-01resolved: the machine files cost more than the pageresolved
- 2026-09-20a stale edge copy was served againreturned
- 2026-09-18the stale edge copy clearedresolved
- 2026-09-17a new finding appeared: the machine files cost more than the pageappeared
- 2026-09-17a new finding appeared: links on this site point at pages that do not answerappeared
- 2026-09-15a stale edge copy was served againreturned
- 2026-09-12the stale edge copy clearedresolved
- 2026-09-08score moved 82 → 81score-down
21 scans on record, first 2026-08-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 botify.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If botify.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 “Site crawler” is our label for what the product is primarily sold as; it is not scored. Back to the directory.