Directory · AI coding tools
Poolside — what a crawler receives from poolside.ai
Website measurement, not a product review. This page records what machine clients received from poolside.ai. It does not evaluate Poolside software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 77/100, measured 2026-10-12 00:03 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
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?
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 signals25
- Linked datan/a
- Quotable content80
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, because the three run in order.
What to fix
5 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 3 Note
1www and the apex both serve the site instead of one redirectingwww.poolside.ai answers 200 and stays there: 288,551 bytes against 288,551 on the apex. Every page exists at two addresses.MediumSetting
What we saw
www.poolside.ai answers 200 and stays there: 288,551 bytes against 288,551 on the apex. Every page exists at two addresses.
Why it matters
Both www and the bare domain answer 200 with the same pages, so every URL on this site exists at two addresses and a crawler fetches the whole site twice. A canonical tag does not prevent this: it is read after the response arrives, so the second fetch has already been spent. Nothing looks broken from a browser, which is why this survives for years. The fix is a 301 from one host to the other so there is one address per page.
How to fix it
Pick one host (apex or www) and redirect the other to it with a 301 so there is one copy of every page.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Why this was decided
| Rule | HOST_DUPLICATE_200 · rule pack sv31 · scope core |
|---|---|
| Evaluated | 2026-10-12 00:03:44 UTC |
| Decision | d1:58924d9a080048c69625 · finding f1:4abe592171571686a94e resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build a0b27a0e · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 288,551 | 8c2c902e7d38 | write_unconfirmed |
23 more in the manifest.
Artifacts: manifest:53d88c2ac8fb646850942b01f70a9174457bde36024e86c7f605aa9541a43db5
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 HOST_DUPLICATE_200 under scoring rules v31 · fingerprint HOST_DUPLICATE_200|/ · persisting (5 scans)
Verify the fix Re-scan after the change. This finding is cleared when HOST_DUPLICATE_200 is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
HOST_DUPLICATE_200 · 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, $749 once.
Get this fixed — $749The main product
We fix the 5 findings on poolside.ai. $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 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 288,505 decompressed bytes the homepage delivers, 1.2% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 1.2% · 3,479 B
- Markup & attributes 14.3% · 41,259 B
- Inline JavaScript 0.8% · 2,368 B
- Inline SVG 80.8% · 233,135 B
- HTML comments 2.9% · 8,264 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline SVG · 81,279 B (28.2%) — unnamedopens
<path fill="var(--color-mono-400)" class="dark:fill-mono-300" d="M1160 - Inline SVG · 19,235 B (6.7%) — unnamedopens
<g opacity="0.1" filter="url(#filter0_f_586_23199)"><path d="M53.7173 - Inline SVG · 19,235 B (6.7%) — unnamedopens
<g opacity="0.1" filter="url(#filter0_f_586_23199)"><path d="M53.7173 - Inline SVG · 18,295 B (6.3%) — unnamedopens
<g fill="var(--color-mono-400)"><rect x="524" y="186" width="34" class - Inline SVG · 15,607 B (5.4%) — unnamedopens
<mask id="mask0_75_1170" style="mask-type:alpha" maskUnits="userSpaceO
What changed
- 2026-09-19a 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 poolside.aiIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If poolside.ai 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 “AI coding tools” is our label for what the product is primarily sold as; it is not scored. Back to the directory.