CrawlCheck

Directory · Model and API providers

Adept — what a crawler receives from adept.ai

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

65
Dgrade

AI assistants are being shown something other than your site.

AI visibility 65/100, measured 2026-11-02 10:07 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can technically reach this site and would struggle to get anything quotable out of it.

Held at D A high-severity finding sets the letter.

Open the full report adept.ai ↗

6

findings

✗

llms.txt on its host

✗

entity map on its host

10

scans on record since 2026-09-17

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.

79

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.

79

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.

33

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, the lowest of the three.

What to fix

6 findings on this site, 3 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 High 2 Medium 3 Note

1No XML sitemap foundNo sitemap at any conventional path and none declared.HighDeveloper

What we saw

No sitemap at any conventional path and none declared.

Why it matters

Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.

How to fix it

Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.

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 adept.ai. 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: No XML sitemap found (NO_SITEMAP_FOUND, high severity)
Page: https://adept.ai/
What was measured: No sitemap at any conventional path and none declared.
Why it matters: Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.
How to fix it: Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.

Rule and examples: https://crawlcheck.io/rules/NO_SITEMAP_FOUND
Full report (markdown): https://crawlcheck.io/r/rgtu9dmvhh.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=adept.ai . The fix counts when NO_SITEMAP_FOUND is gone from the new report.
Why this was decided
RuleNO_SITEMAP_FOUND · rule pack sv34 · scope core
Evaluated2026-11-02 10:07:08 UTC
Decisiond1:018de3c6f37f750d47e4 · finding f1:c0fc074ee3faf97e1687 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 5472fbf1 from SIN · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /sitemap.xml40413,968bba6151a89ccalready_held
read: /sitemap_index.xml40413,968bba6151a89ccalready_held
read: /wp-sitemap.xml40413,968bba6151a89ccalready_held

20 more in the manifest.

Artifacts: manifest:212a8e9431574a76b00424082f8523c32f32c427da6b68dac4802af42eed9e48

Grade effect Caps the letter at D. Without it the letter would be C (score 65). Moves no points; the score is built from the measured rows.

Rule NO_SITEMAP_FOUND under scoring rules v34 · fingerprint NO_SITEMAP_FOUND|/ · persisting (2 scans)

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

NO_SITEMAP_FOUND · full transcript

2www and the apex both serve the site instead of one redirecting🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
3robots.txt declares no sitemap/robots.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
4The 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
5No llms.txt/llms.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
6HTTPS 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

Open the other 5

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

Sites like yours that fixed the same problem

Matched on Cloudflare. 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

28 sites on a stack like yours have made this fix (Published llms.txt); 28 still hold it. 75 on any stack.

  • similar site A (Cloudflare; shares CDN): fixed 2026-10-31, still fixed today
  • similar site B (Wix + Cloudflare + Cloudflare Bot Management; shares CDN): fixed 2026-10-31, still fixed today
  • similar site C (Cloudflare; shares CDN): fixed 2026-10-31, still fixed today

serves no /agents.md (optional)

8 sites on a stack like yours have made this fix (Published agents.md); 8 still hold it. 15 on any stack.

  • similar site A (Cloudflare; shares CDN): fixed 2026-11-01, still fixed today
  • similar site B (WordPress + Cloudflare + Cloudflare Bot Management; shares CDN): fixed 2026-10-31, still fixed today
  • similar site C (Cloudflare; shares CDN): fixed 2026-10-24, still fixed today

serves no /entitymap.json (optional)

2 sites on a stack like yours have made this fix (Published an entity map); 2 still hold it.

  • similar site A (WordPress + Cloudflare; shares CDN): fixed 2026-10-29, still fixed today
  • similar site B (Cloudflare; shares CDN): fixed 2026-10-15, still fixed today

The signed answer lists every match.

The chain a crawler follows

The chain breaks at sitemap. 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 41,530 decompressed bytes the homepage delivers, 7.7% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 7.7% · 3,187 B
  • Markup & attributes 72.3% · 30,033 B
  • Inline CSS 1.3% · 522 B
  • Inline JavaScript 5.3% · 2,218 B
  • Inline SVG 13.3% · 5,538 B
  • HTML comments 0.1% · 32 B

The individual blocks that weigh the most, so the fix is a search rather than a hunt:

  • Inline SVG · 2,769 B (6.7%) — unnamedopens <path class="letter-A" d="M0 163.455H37.0961L51.7027 124.388H119.287L1
  • Inline SVG · 2,769 B (6.7%) — unnamedopens <path class="letter-A" d="M0 163.455H37.0961L51.7027 124.388H119.287L1
Section average over 2 scans on this score version · held at 65 since 2026-11-02
0501002026-10-26 07:35 · 65/100 · 6 findings2026-11-02 10:07 · 65/100 · 6 findings2026-10-262026-11-02

What changed

  1. 2026-11-02score moved 66 → 67score-up
  2. 2026-10-26resolved: whether a sitemap exists could not be determined — every path was refusedresolved
  3. 2026-10-26resolved: the sitemap is refusedresolved
  4. 2026-10-26resolved: the site refuses plain automated requests; it was measured through a real browserresolved
  5. 2026-10-26the homepage began taking more than one redirect to reachappeared
  6. 2026-10-26no sitemap could be foundappeared
  7. 2026-10-26a new finding appeared: www and the apex both serve the site instead of one redirectingappeared
  8. 2026-10-18resolved: this origin refused crawlcheck, so the site was never measuredresolved
  9. 2026-10-18a new finding appeared: whether a sitemap exists could not be determined — every path was refusedappeared
  10. 2026-10-18a new finding appeared: the sitemap is refusedappeared
  11. 2026-10-18a new finding appeared: the site refuses plain automated requests; it was measured through a real browserappeared
  12. 2026-10-18robots.txt no longer named a sitemapappeared

10 scans on record, first 2026-09-17. 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 adept.ai

Is this your company?

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