Directory · Data and database infrastructure
QuestDB — what a crawler receives from questdb.io
Website measurement, not a product review. This page records what machine clients received from questdb.io. It does not evaluate QuestDB software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 75/100, measured 2026-10-04 16:19 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.
2
findings
✗
llms.txt on its host
✗
entity map on its host
4
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?
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 quote, because the three run in order.
What to fix
2 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
1The homepage sends crawlers to a different hostnameA request for https://questdb.io/ answered HTTP 301 with a redirect to questdb.com. That host is neither questdb.io nor its www/apex peer, so the scan did not fMediumSetting
What we saw
A request for https://questdb.io/ answered HTTP 301 with a redirect to questdb.com. That host is neither questdb.io nor its www/apex peer, so the scan did not follow it; every section that needs the homepage is unmeasured below.
Why it matters
An answer engine resolving this domain is handed a page on another host. Content, schema and entity signals it finds there are attributed to questdb.com, and questdb.io itself reads as a site with no homepage. Geo-routed storefronts and locale redirects are the usual cause; the fix is to serve a canonical page at the root and redirect by link, not by host.
How to fix it
Point the domain at the site it is meant to serve, or make the redirect a single permanent hop to the canonical host.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Why this was decided
| Rule | HOMEPAGE_REDIRECTS_OFF_HOST · rule pack sv27 · scope route |
|---|---|
| Evaluated | 2026-10-04 16:19:32 UTC |
| Decision | d1:d7319fe9eaa642e001b6 · finding f1:772a268d7f486e449e03 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 | 716,742 | aba8861333a8 | kept |
21 more in the manifest.
Artifacts: manifest:c6d0ed7e8059332b09acb8185193d9b3ed3b83993dc0126c0079550f8d204aa3
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 HOMEPAGE_REDIRECTS_OFF_HOST under scoring rules v28 · fingerprint HOMEPAGE_REDIRECTS_OFF_HOST|/ · persisting (4 scans)
Verify the fix Re-scan after the change. This finding is cleared when HOMEPAGE_REDIRECTS_OFF_HOST is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
HOMEPAGE_REDIRECTS_OFF_HOST · full transcript
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 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 2 findings on questdb.io. $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 robots.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 716,683 decompressed bytes the homepage delivers, 4.7% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 4.7% · 33,803 B
- Markup & attributes 30.1% · 216,063 B
- Structured data (JSON-LD) 0.3% · 2,230 B
- Inline JavaScript 18.5% · 132,305 B
- Inline SVG 46.3% · 331,994 B
- HTML comments 0% · 288 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline SVG · 305,023 B (42.6%) —
#three-tier-chart-groupedopens<g id="Container"><g id="Container_2"><g id="Tier 1 Group"><g id="Spee - Inline JavaScript · 10,871 B (1.5%) — unnamedopens
self.__next_f.push([1,"# QuestDB 10.0.1\n\nQuestDB 10.0.1 is a mainten - Inline JavaScript · 8,103 B (1.1%) — unnamedopens
self.__next_f.push([1,"2:[\"$\",\"html\",null,{\"lang\":\"en\",\"class
What changed
- 2026-10-04the stale edge copy clearedresolved
- 2026-09-19a stale edge copy was servedappeared
4 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 questdb.ioIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If questdb.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 “Data and database infrastructure” is our label for what the product is primarily sold as; it is not scored. Back to the directory.