Directory · Vector databases and retrieval

Milvus — what a crawler receives from milvus.io

Website measurement, not a product review. This page records what machine clients received from milvus.io. It does not evaluate Milvus software, features, pricing or support.

Bgrade

AI assistants like ChatGPT can read your site, but find little they can quote from your pages.

AI visibility 75/100, measured 2026-10-31 08:48 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 milvus.io ↗

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?

At least one answer engine was refused, challenged or served less than a browser.

What each crawler getsn/a
Crawler permissions100
Machine-file chainn/a
Speed100
Server & hosting50
Internal linksn/a
Mobilen/a
exposuren/a

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.

Page weight & textn/a
Machine files60
Sitemapn/a
Crawl wasten/a
Accessibility structuren/a
Image signalsn/a
Instructions for agentsn/a
URL naming67
errpagesn/a

Stage 3 · 30% of the score

Quote

Is there a specific fact it can state and attribute?

Not measured on this scan; left out rather than counted as zero.

Structured datan/a
Local presence & NAPn/a
Claim consistencyn/a
Authors & trust signalsn/a
Linked datan/a
Quotable contentn/a
Entity corroborationn/a
Page subjectn/a

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

What to fix

4 findings on this site. 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 Low 3 Note

1The site refuses plain automated requests; it was measured through a real browserThe plain request for the homepage was answered with HTTP null; a real browser was served the site (HTTP 200, 164,685 bytes), so this report was measured througLowSetting

What we saw

The plain request for the homepage was answered with HTTP null; a real browser was served the site (HTTP 200, 164,685 bytes), so this report was measured through the browser.

Why it matters

The site’s security layer refused CrawlCheck’s plain HTTP request but served the page to a real browser. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) make plain HTTP requests and do not run JavaScript, so a shield that tells the two apart this way is likely refusing them too, which keeps the site out of AI answers no matter what robots.txt allows. The rest of this report was measured through the browser, so its findings describe the site, not the wall.

How to fix it

Decide which automated readers you want. If AI and search crawlers should reach the site, allow verified bots in the bot-protection settings (Cloudflare, Akamai and others have a verified-bot or signed-agent allow list) instead of challenging every client that does not run JavaScript.

Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing

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 milvus.io. 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: The site refuses plain automated requests; it was measured through a real browser (SCANNER_REFUSED_BROWSER_READ, low severity)
Page: https://milvus.io/
What was measured: The plain request for the homepage was answered with HTTP null; a real browser was served the site (HTTP 200, 164,685 bytes), so this report was measured through the browser.
Why it matters: The site’s security layer refused CrawlCheck’s plain HTTP request but served the page to a real browser. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot and others) make plain HTTP requests and do not run JavaScript, so a shield that tells the two apart this way is likely refusing them too, which keeps the site out of AI answers no matter what robots.txt allows. The rest of this report was measured through the browser, so its findings describe the site, not the wall.
How to fix it: Decide which automated readers you want. If AI and search crawlers should reach the site, allow verified bots in the bot-protection settings (Cloudflare, Akamai and others have a verified-bot or signed-agent allow list) instead of challenging every client that does not run JavaScript.
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/SCANNER_REFUSED_BROWSER_READ
Full report (markdown): https://crawlcheck.io/r/6xocudasvp.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=milvus.io . The fix counts when SCANNER_REFUSED_BROWSER_READ is gone from the new report.

Why this was decided

Rule	`SCANNER_REFUSED_BROWSER_READ` · rule pack `sv34` · scope core
Evaluated	2026-10-31 08:48:47 UTC
Decision	`d1:91ccf59c068beec93ca1` · finding `f1:bc78795ca5103fc9dd84` resolve either at `/api/graph/<id>` with a key
Observer	crawlcheck-worker build `77ae0f18` from LAX · audit v4

What it rests on

Identity	Status	Bytes	sha256	Kept
crawlcheck	—	0	`—`	no_body

5 more in the manifest.

Artifacts: manifest:0856dadf5a64ff66bd77235842cdcc8f0143dd4113b4d477340a178fd03fce59

Grade effect Does not cap the letter: only medium, high and critical findings do. Moves no points either; the score is built from the measured rows.

Rule SCANNER_REFUSED_BROWSER_READ under scoring rules v34 · fingerprint SCANNER_REFUSED_BROWSER_READ|/ · persisting (3 scans)

Verify the fix Re-scan after the change. This finding is cleared when SCANNER_REFUSED_BROWSER_READ is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.

SCANNER_REFUSED_BROWSER_READ · full transcript

2The homepage is reached through a chain of redirects🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

3HTTPS is served without a Strict-Transport-Security header🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

4A missing agent file answers with a full page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 3

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

What changed

2026-10-31a new finding appeared: the site refuses plain automated requests; it was measured through a real browserappeared
2026-10-31the homepage began taking more than one redirect to reachappeared
2026-10-31a new finding appeared: the machine files cost more than the pageappeared
2026-10-31a new finding appeared: https is served without a strict-transport-security headerappeared

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 milvus.io

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If milvus.io 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 “Vector databases and retrieval” is our label for what the product is primarily sold as; it is not scored. Back to the directory.