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.

Bgrade

AI assistants like ChatGPT can read your site, but find little to quote about your product.

AI visibility 82/100, measured 2026-10-25 19:05 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.

Open the full report yugabyte.com ↗

1. ReachCan a named answer-engine crawler get your pages at all?2. ReadOnce it has the bytes, can it find the words?3. QuoteIs there a specific fact it can state and attribute?

findings

✓

llms.txt on its host

✗

entity map on its host

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.

What each crawler gets100
Crawler permissions100
Machine-file chain57
Speed100
Server & hosting50
Internal links80
Mobile100
exposure100

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.

Page weight & text60
Machine files80
Sitemap83
Crawl waste100
Accessibility structure91
Image signals100
Instructions for agents100
URL naming100
errpages75

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 data89
Local presence & NAPn/a
Claim consistency100
Authors & trust signals64
Linked data100
Quotable content40
Entity corroboration100
Page subject0

The stage to fix first is quote, the lowest of the three.

What to fix

2 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 1 Note

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.

All WordPress fixes

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 yugabyte.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: Two business records on this page claim the same identity (ENTITY_COLLISION, medium severity)
Page: https://yugabyte.com/
What was measured: 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.
Detected platform: WordPress. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/ENTITY_COLLISION
Full report (markdown): https://crawlcheck.io/r/uygbsmnikh.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=yugabyte.com . The fix counts when ENTITY_COLLISION is gone from the new report.

Why this was decided

Rule	`ENTITY_COLLISION` · rule pack `sv34` · scope route
Evaluated	2026-10-25 19:05:06 UTC
Decision	`d1:d0c388d46905220ccb90` · finding `f1:c95c4d1ae609ead0aacd` resolve either at `/api/graph/<id>` with a key
Observer	crawlcheck-worker build `4e7ce319` from SIN · audit v4

What it rests on

Identity	Status	Bytes	sha256	Kept
read: /	200	245,918	`763e9389a4b0`	write_unconfirmed

23 more in the manifest.

Artifacts: manifest:887dd8a916887c488b68d7bc56eef13d62c517a62b0d8fd8b93d4fbb7192a0c7

Grade effect Would cap the letter at C, but the score (82) already reads B, so the letter is the same without it. Moves no points.

Rule ENTITY_COLLISION under scoring rules v34 · fingerprint ENTITY_COLLISION|/ · persisting (8 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

2Visitors and crawlers are being served an old copy of this page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 1

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 findings

Or 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 — $100

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.

✓robots.txtEvery crawler reads this first

✓sitemapNamed in robots.txt and resolves

✓llms.txtPoints onward, links stay on this host

✗entity graphParses as JSON and points home

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 245,875 decompressed bytes the homepage delivers, 5% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

Readable text 5% · 12,256 B
Structured data (JSON-LD) 1.6% · 3,891 B
Inline CSS 58.6% · 144,198 B
Inline JavaScript 2.4% · 5,850 B
Inline SVG 64% · 157,289 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-25the homepage no longer read as mostly markupresolved
2026-10-25no answer engine was refusedresolved
2026-10-14an answer engine was refused againreturned
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

8 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.com

Is 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.