Directory · Data and database infrastructure
YugabyteDB — what a crawler receives from yugabyte.com
Website measurement, not a product review. This page records what machine clients received from yugabyte.com. It does not evaluate YugabyteDB software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 80/100, measured 2026-10-05 15:18 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.
3
findings
✓
llms.txt on its host
✗
entity map on its host
5
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.
Stage 1 · 40% of the score
Reach
Can a named answer-engine crawler get your pages at all?
At least one answer engine was refused, challenged or served less than a browser.
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.
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
3 findings on this site, 3 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.
3 Medium
1Two business records on this page claim the same identity1 identity collision in this page's structured data: two nodes share the same url.MediumDeveloper
What we saw
1 identity collision in this page's structured data: two nodes share the same url.
Why it matters
A system resolving which business this page is about has more than one candidate for one identity. Two LocalBusiness or Organization nodes sharing a phone number, an @id or a coordinate pair give a retrieval system no way to decide which record is the entity, so it may pick either or neither. This reads only what the page declares - it does not assert the business is duplicated or wrongly located.
How to fix it
Merge the duplicate business nodes into one, keep a single @id, and remove any plugin that emits a second empty LocalBusiness record.
Developer: a template, theme or application change — a developer touches it
On WordPress (detected)
- Keep one source of business markup: Rank Math → Titles & Meta → Local SEO, or Yoast Local SEO. Turn off the same block in your theme or any second plugin.
- Fill name, address, phone, geo coordinates and opening hours there, matching the Business Profile exactly.
Why this was decided
| Rule | ENTITY_COLLISION · rule pack sv27 · scope route |
|---|---|
| Evaluated | 2026-10-05 15:18:43 UTC |
| Decision | d1:bc8a74536f151eb7f1c0 · finding f1:c95c4d1ae609ead0aacd resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 71386c1f · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 246,239 | 9974368518ea | write_unconfirmed |
23 more in the manifest.
Artifacts: manifest:625871792d28178f299fae2744852ada9e9d86d3f70823ee4cd301ce6da8a11b
Grade effect Caps the letter at C together with 2 other medium-severity findings; the letter rises only when all of them are gone. Moves no points.
Rule ENTITY_COLLISION under scoring rules v31 · fingerprint ENTITY_COLLISION|/ · persisting (5 scans)
Verify the fix Re-scan after the change. This finding is cleared when ENTITY_COLLISION is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
ENTITY_COLLISION · full transcript
Open the other 2
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 3 findings on yugabyte.com. $749, once.
3 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 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 246,200 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% · 12,168 B
- Structured data (JSON-LD) 1.6% · 3,891 B
- Inline CSS 58.6% · 144,223 B
- Inline JavaScript 2.6% · 6,403 B
- Inline SVG 63.9% · 157,347 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline SVG · 37,495 B (15.2%) — WordPress theme or block stylesopens
<style>@font-face{font-family:Roobert;font-style:normal;font-weight:40 - Inline CSS · 37,462 B (15.2%) — WordPress theme or block stylesopens
@font-face{font-family:Roobert;font-style:normal;font-weight:400;font- - Inline SVG · 25,930 B (10.5%) — WordPress theme or block stylesopens
<style>.yugabyte-hero-section img,.yugabyte-cards-section img{width:au - Inline CSS · 25,897 B (10.5%) — WordPress theme or block stylesopens
.yugabyte-hero-section img,.yugabyte-cards-section img{width:auto;heig - Inline SVG · 22,843 B (9.3%) — unnamedopens
<defs> <clipPath id="__lottie_element_239"> <rect width="400" height="
What changed
- 2026-10-05the homepage read as mostly markupappeared
- 2026-10-02score moved 78 → 82score-up
- 2026-10-02no answer engine was refusedresolved
- 2026-09-24an answer engine was refused againreturned
- 2026-09-20no answer engine was refusedresolved
- 2026-09-20a stale edge copy was servedappeared
5 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 yugabyte.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If yugabyte.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 “Data and database infrastructure” is our label for what the product is primarily sold as; it is not scored. Back to the directory.