Directory · Search and discovery infrastructure
Elastic — what a crawler receives from elastic.co
Website measurement, not a product review. This page records what machine clients received from elastic.co. It does not evaluate Elastic software, features, pricing or support.
AI assistants like ChatGPT can read your site, but find little to quote about your product.
AI visibility 77/100, measured 2026-10-27 05:04 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
10
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.
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.
- Structured data38
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals75
- Linked data67
- Quotable content100
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, the lowest of the three.
What to fix
5 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 4 Note
1Almost nothing a machine receives from this page is readable text1.9% of 887,956 decompressed bytes is visible text, and the largest single block is inline javascript at 254,167 bytes (a framework state payload)MediumDeveloper
What we saw
1.9% of 887,956 decompressed bytes is visible text, and the largest single block is inline javascript at 254,167 bytes (a framework state payload)
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)
- 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.
- Check View Source, not the browser inspector: the text must be in the HTML the server sends.
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 elastic.co. 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://elastic.co/ What was measured: 1.9% of 887,956 decompressed bytes is visible text, and the largest single block is inline javascript at 254,167 bytes (a framework state payload) 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/g89orsusyz.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=elastic.co . 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 sv34 · scope route |
|---|---|
| Evaluated | 2026-10-27 05:04:05 UTC |
| Decision | d1:0445e570aa087b3d9db5 · finding f1:796bc5e34f04ffa9126d resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 367c5507 from EWR · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 889,419 | 0d7a07afed86 | kept |
21 more in the manifest.
Artifacts: manifest:c63a536b5c5d0b785e0a1f66a30eaf68fb3f2336f5212fb417439e25c7818dbd
Grade effect Caps the letter at C. Without it the letter would be B (score 77). 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 (11 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, $100 once.
Get this fixed — $100The main product
We fix the 5 findings on elastic.co. $100, once.
1 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 887,956 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% · 17,243 B
- Markup & attributes 9.4% · 83,501 B
- Structured data (JSON-LD) 0% · 177 B
- Inline CSS 6.2% · 54,976 B
- Inline JavaScript 28.8% · 255,838 B
- Inline SVG 53.6% · 476,173 B
- HTML comments 0% · 48 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline JavaScript · 254,167 B (28.6%) — a framework state payloadopens
{"props":{"pageProps":{"entry":{"uid":"bltfdd4d3eaa4af83b4","_version" - Inline SVG · 230,737 B (26%) — unnamedopens
<g opacity="0.3"><path d="M566 0H568V2H566V0Z" fill="#ABB4C4"></path>< - Inline SVG · 230,737 B (26%) — unnamedopens
<g opacity="0.3"><path d="M566 0H568V2H566V0Z" fill="#ABB4C4"></path>< - Inline CSS · 54,976 B (6.2%) —
#__jsx-2677802404opens@charset "UTF-8";html,body{-webkit-font-smoothing:antialiased;position
What changed
- 2026-10-15the homepage began taking more than one redirect to reachappeared
- 2026-10-04resolved: the hsts header asks for browser preloading but does not qualify for itresolved
- 2026-10-04score moved 72 → 74score-up
- 2026-10-04a new finding appeared: the hsts header asks for browser preloading but does not qualify for it againreturned
- 2026-10-03score moved 72 → 73score-up
- 2026-09-19resolved: the hsts header asks for browser preloading but does not qualify for itresolved
10 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 elastic.coIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If elastic.co 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 “Search and discovery infrastructure” is our label for what the product is primarily sold as; it is not scored. Back to the directory.