Directory · ML platforms and experiment tracking
Comet — what a crawler receives from comet.com
Website measurement, not a product review. This page records what machine clients received from comet.com. It does not evaluate Comet software, features, pricing or support.
AI assistants like ChatGPT can read your site, but find little to quote about your product.
AI visibility 79/100, measured 2026-11-05 22:32 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
10
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.
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 data89
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals43
- Linked data67
- Quotable content60
- Entity corroboration100
- Page subject100
The stage to fix first is read, the lowest of the three.
What to fix
3 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 2 Note
1The ARD manifest breaks the specification1 specification error in 0 entries: [Root] Malformed JSON in manifest: Unexpected token '<', "<!doctype "... is not valid JSONMediumDeveloper
What we saw
1 specification error in 0 entries: [Root] Malformed JSON in manifest: Unexpected token '<', "<!doctype "... is not valid JSON /.well-known/ard.json
Why it matters
The site's ARD manifest (/.well-known/ard.json or the source it advertises) fails the rules every entry must meet: a urn:air:<publisher>:<name> identifier, a displayName, a media type, and exactly one of url or data. A registry rejects the entry, so the resource it describes is not discoverable; where the trust manifest names an identity that does not belong to the URN's publisher, the entry is rejected as namespace squatting.
How to fix it
Give every entry an identifier of the form urn:air:<your-domain>:<name>, a displayName, a type (an IANA media type such as application/mcp-server-card+json) and exactly one of url or data. If an entry carries a trustManifest, its identity must belong to the same domain as the URN. Validate with the official tester: npx ajv-cli validate -s ard-entry.schema.json -d ard.json.
Developer: a template, theme or application change — a developer touches it
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 comet.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: The ARD manifest breaks the specification (ARD_MANIFEST_INVALID, medium severity) Page: https://comet.com/.well-known/ard.json What was measured: 1 specification error in 0 entries: [Root] Malformed JSON in manifest: Unexpected token '<', "<!doctype "... is not valid JSON Why it matters: The site's ARD manifest (/.well-known/ard.json or the source it advertises) fails the rules every entry must meet: a urn:air:<publisher>:<name> identifier, a displayName, a media type, and exactly one of url or data. A registry rejects the entry, so the resource it describes is not discoverable; where the trust manifest names an identity that does not belong to the URN's publisher, the entry is rejected as namespace squatting. How to fix it: Give every entry an identifier of the form urn:air:<your-domain>:<name>, a displayName, a type (an IANA media type such as application/mcp-server-card+json) and exactly one of url or data. If an entry carries a trustManifest, its identity must belong to the same domain as the URN. Validate with the official tester: npx ajv-cli validate -s ard-entry.schema.json -d ard.json. Detected platform: WordPress. Make the change where this platform controls it. Rule and examples: https://crawlcheck.io/rules/ARD_MANIFEST_INVALID Full report (markdown): https://crawlcheck.io/r/iqxwljzp0p.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=comet.com . The fix counts when ARD_MANIFEST_INVALID is gone from the new report.
Why this was decided
| Rule | ARD_MANIFEST_INVALID · rule pack sv34 · scope core |
|---|---|
| Evaluated | 2026-11-05 22:32:18 UTC |
| Decision | d1:e5357f3efb5db8ca760f · finding f1:0a6688c04cd0485fe16b resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build c699237f from LHR · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| crawlcheck | 200 | 213,602 | 271db53eadd6 | kept |
| crawlcheck | 200 | 214 | 7d8fbbcb055b | already_held |
| crawlcheck | 200 | 1,451 | 378c79ad2ea4 | kept |
| crawlcheck | 200 | 6,694 | 2cdfa7e69f1e | kept |
| crawlcheck | 200 | 6,694 | 2cdfa7e69f1e | kept |
| crawlcheck | 200 | 110,405 | bdd8a907342c | kept |
| crawlcheck | 200 | 6,694 | 2cdfa7e69f1e | kept |
| anon | 200 | 213,602 | e72f8a75adc3 | kept |
No recorded fetch names this path; these are the scan’s recorded fetches.
17 more in the manifest.
Artifacts: manifest:c60f0fa8e5bbb929f278625213bf199e3a54088d2482415dd8c2e135ec928500
Grade effect Caps the letter at C. Without it the letter would be B (score 79). Moves no points; the score is built from the measured rows.
Rule ARD_MANIFEST_INVALID under scoring rules v34 · fingerprint ARD_MANIFEST_INVALID|/.well-known/ard.json · new on this scan (seen in 1 of 10 readings)
Verify the fix Re-scan after the change. This finding is cleared when ARD_MANIFEST_INVALID is no longer reported at /.well-known/ard.json; if it comes back after clearing, it is marked a regression, not a new finding.
ARD_MANIFEST_INVALID · 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, $100 once.
Get this fixed — $100The main product
We fix the 3 findings on comet.com. $100, once.
1 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 eligible finding implemented on the site itself: machine files, schema, NAP, settings. Not included: new content, redesigns, plugin or theme replacement, custom integrations (the terms list them)
- 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
Sites like yours that fixed the same problem
Matched on WordPress + Fastly. A fix counts once two readings confirm it; sites are not named. Read from the technology record of 2026-10-26.
serves no /llms.txt
14 sites on a stack like yours have made this fix (Published llms.txt); 14 still hold it. 79 on any stack.
- similar site A (WordPress + Fastly; shares platform, CDN): fixed 2026-10-31, still fixed today
- similar site B (WordPress + Cloudflare + Cloudflare Bot Management; shares platform): fixed 2026-11-04, still fixed today
- similar site C (WordPress; shares platform): fixed 2026-10-30, still fixed today
serves no /entitymap.json (optional)
1 site on a stack like yours has made this fix (Published an entity map); 1 still hold it. 2 on any stack.
- similar site A (WordPress + Cloudflare; shares platform): fixed 2026-10-29, still fixed today
The signed answer lists every match.
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 213,563 decompressed bytes the homepage delivers, 5.5% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 5.5% · 11,821 B
- Markup & attributes 45.1% · 96,399 B
- Structured data (JSON-LD) 0.5% · 1,004 B
- Inline CSS 42.9% · 91,570 B
- Inline JavaScript 4.1% · 8,739 B
- Inline SVG 1.6% · 3,438 B
- HTML comments 0.3% · 592 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 32,597 B (15.3%) —
#global-styles-inline-cssopens:root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio - Inline CSS · 10,044 B (4.7%) —
#core-block-supports-inline-cssopens.wp-elements-1 a:where(:not(.wp-element-button)){color:var(--wp--prese - Inline CSS · 8,945 B (4.2%) — WordPress theme or block stylesopens
.wp-block-image>a,.wp-block-image>figure>a{display:inline-block}.wp-bl - Inline CSS · 5,920 B (2.8%) — WordPress theme or block stylesopens
.scroll-hero{--scroll-top-offset:0;--scroll-top-padding:0;position:rel - Inline CSS · 4,391 B (2.1%) — WordPress theme or block stylesopens
/*!*******************************************************************
What changed
- 2026-11-05score moved 78 → 79score-up
- 2026-11-05a new finding appeared: the ard manifest breaks the specificationappeared
- 2026-10-15the homepage began taking more than one redirect to reachappeared
- 2026-10-02score moved 76 → 77score-up
- 2026-10-02an llms.txt became readableresolved
- 2026-09-25the homepage no longer read as mostly markupresolved
- 2026-09-25the declared sitemap resolvedresolved
- 2026-09-25no llms.txt was foundappeared
- 2026-09-20a stale edge copy was servedappeared
10 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 comet.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If comet.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 “ML platforms and experiment tracking” is our label for what the product is primarily sold as; it is not scored. Back to the directory.