Free B2B AI Visibility Checker

Would an AI agent shortlist Dust?

Last checked 2026-10-15 · 21 checks · Read-only, no browser

Results for dust.tt

73out of 100

At risk

AI agents consider Dust, but lose the way before buyers reach the sales team.

86%

Research

30/35 pts · 6/8 passed

7%

Evaluate

1/15 pts · 0/5 passed

85%

Reach out

36.5/43 pts · 4/6 passed

See what to fix first (3)

How a buyer's AI agent experiences Dust

Research: passedEvaluate: stuckReach out: passed

The agent read your site and understood what you do. It found your contact page at /home/contact and could see how to reach your sales team.

What Dust should fix first to make the shortlist

01

Understand the form

Label every field, use the right field types (email, phone) and cut required fields to what sales really needs.

02

Discoverable

Tell agents where your MCP server is: publish /.well-known/mcp/server-card.json (or /.well-known/mcp.json) with its URL, and mention it in your developer docs and llms.txt. No MCP server yet? If your product has an API, it is the fastest way to let agents evaluate it.

03

Company identity

Add Organization structured data (name, URL, logo, official profiles) to your homepage.

Research: can AI agents read and understand Dust?

pass1.1

AI search crawler access

7/7 pts

AI search and assistant bots are allowed to read your site.

Training bots: GPTBot: allowed, ClaudeBot: allowed, Google-Extended: allowed, CCBot: allowed. Blocking these is a valid choice and doesn't affect this score.

Evidence
https://dust.tt/robots.txt · HTTP 404 · no robots.txt (everything allowed)
pass1.2

Homepage access

7/7 pts

Your homepage lets in requests that identify as ChatGPT, Claude and Perplexity, and serves them the same page as a browser.

Evidence
https://dust.tt/ · as browser · HTTP 200 · browser baseline 200
https://dust.tt/ · as ChatGPT-User · HTTP 200 · HTTP 200
https://dust.tt/ · as Claude-User · HTTP 200 · HTTP 200
https://dust.tt/ · as Perplexity-User · HTTP 200 · HTTP 200
pass1.3

Content without JavaScript

7/7 pts

Your pages carry real text in the page code (1066 words on the homepage, 546 on a typical key page).

Evidence
https://dust.tt/ · homepage: pass (1066 words) · key pages: pass (median 546 words across 5)
https://dust.tt/ · 1066 words of page content in raw HTML (1131 including nav and footer)
sampled pages: product /home/product (430 words), customer /home/solutions/customer-support (523 words), blog /blog (701 words), about /home/about (784 words), product /home/solutions/it (546 words); median words: 546
pass1.4

Accidentally hidden pages

4/4 pts

None of your key pages are hidden from search and AI.

Evidence
checked homepage + 5 key pages
pass1.5

Page essentials

3/3 pts

Your pages clearly state what they are: titles, descriptions and headings are in place.

Evidence
https://dust.tt/ · title:true desc:true h1:2 canonical:true
https://dust.tt/home/product · title:true desc:true h1:1 canonical:true
https://dust.tt/home/solutions/customer-support · title:true desc:true h1:1 canonical:true
https://dust.tt/blog · title:true desc:true h1:1 canonical:true
https://dust.tt/home/about · title:true desc:true h1:1 canonical:true
https://dust.tt/home/solutions/it · title:true desc:true h1:1 canonical:true
fail1.6

Company identity

0/3 pts

Your site doesn't identify the company in structured data.

How to fix: Add Organization structured data (name, URL, logo, official profiles) to your homepage.

Evidence
https://dust.tt/ · 0 JSON-LD blocks, no Organization with a name
fail1.7

Sitemap

0/2 pts

We couldn't find a valid sitemap.

How to fix: Publish a sitemap.xml and link it from robots.txt.

Evidence
https://dust.tt/sitemap.xml · valid:false linkedFromRobots:false urls:0 latestLastmod:none (HTTP 404)
pass1.8

Response speed

2/2 pts

Your homepage responds quickly (148 ms, median of 5 requests).

Evidence
https://dust.tt/ · median 148 ms across 5 requests
https://dust.tt/ · as crawler · HTTP 200 · 148 ms to response headers
https://dust.tt/ · as browser · HTTP 200 · 148 ms to response headers
https://dust.tt/ · as ChatGPT-User · HTTP 200 · 149 ms to response headers
https://dust.tt/ · as Claude-User · HTTP 200 · 143 ms to response headers
https://dust.tt/ · as Perplexity-User · HTTP 200 · 160 ms to response headers
bonus1.9

AI guide files

+0 bonus

Opportunity: an llms.txt file and markdown page versions give AI agents a clean map of your site. Not yet confirmed as used by the major AI engines, but cheap to add.

Evidence
https://dust.tt/llms.txt · HTTP 404 · no valid llms.txt
no <link rel="alternate" type="text/markdown">

Evaluate: can AI agents try Dust's product?

fail2.1

Discoverable

0/4 pts

We couldn't find an MCP server from your website. If you have one, AI agents arriving at your site can't find it either.

How to fix: Tell agents where your MCP server is: publish /.well-known/mcp/server-card.json (or /.well-known/mcp.json) with its URL, and mention it in your developer docs and llms.txt. No MCP server yet? If your product has an API, it is the fastest way to let agents evaluate it.

Evidence
https://dust.tt/.well-known/mcp.json · HTTP 404 · HTTP 404
https://dust.tt/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404
https://dust.tt/.well-known/ai-catalog.json · HTTP 404 · HTTP 404
https://dust.tt/.well-known/api-catalog · HTTP 404 · HTTP 404
https://dust.tt/.well-known/oauth-protected-resource · HTTP 200 · valid JSON
fail2.2

Working

0/4 pts

There is no MCP server to test.

fail2.3

Understandable

0/3 pts

There is no MCP server to evaluate.

fail2.4

Connectable

0/2 pts

There is no MCP server to connect to.

warning2.5

Documented

1/2 pts

We couldn't find an OpenAPI spec.

How to fix: Link developer docs from the homepage and publish your OpenAPI spec at a discoverable URL.

Evidence
https://dust.tt/ · docs link: https://docs.dust.tt/docs/intro
no OpenAPI found (api-catalog service-desc or homepage link)

Reach out: can an AI agent get a buyer to Dust's sales team?

pass3A

Find the way in

8/8 pts

AI agents can find your contact page (/home/contact) from the homepage.

Evidence
https://dust.tt/home/contact · contact page found via homepage
pass3B

Let in

10/10 pts

Your contact page lets in requests that identify as ChatGPT, Claude and Perplexity.

Evidence
https://dust.tt/home/contact · as browser · HTTP 200 · browser baseline 200
https://dust.tt/home/contact · as ChatGPT-User · HTTP 200 · HTTP 200
https://dust.tt/home/contact · as Claude-User · HTTP 200 · HTTP 200
https://dust.tt/home/contact · as Perplexity-User · HTTP 200 · HTTP 200
https://dust.tt/robots.txt · robots disallow /home/contact for: none
pass3C

See the form

12/12 pts

Your contact form is in the page code, so AI agents can see it.

Evidence
https://dust.tt/home/contact · as browser · HTTP 200 · contact form in page code with 6 fields (firstname, lastname, email, mobilephone, landing_use_cases, checkbox)
fail3D

Understand the form

0/5 pts

5 fields have no label.

How to fix: Label every field, use the right field types (email, phone) and cut required fields to what sales really needs.

Evidence
https://dust.tt/home/contact · 6 fields, 5 unlabelled, 0 required, email type: true
bonus3F

Agent-friendly route

+0 bonus

Opportunity: a visible sales email, contact details in structured data, or a contact API gives agents a way in even when forms fail. Very few B2B sites do this yet.

Evidence
email:none contactPoint:false llms.txt contact:false MCP contact tool:false
pass3G

Readable proof

5/5 pts

Your case studies are readable text, so agents can use them as proof.

Evidence
https://dust.tt/home/solutions/customer-support · HTTP 200 · 523 words of page content in raw HTML (nav and footer excluded)
warning3H

Self-serve path

1.5/3 pts

Your sign-up page loads only with JavaScript.

How to fix: Make the sign-up page reachable and readable without JavaScript.

Evidence
signals: Try for free; no sign-up link in page code

What Dust gets right

  • AI search and assistant bots are allowed to read your site.
  • Your homepage lets in requests that identify as ChatGPT, Claude and Perplexity, and serves them the same page as a browser.
  • Your pages carry real text in the page code (1066 words on the homepage, 546 on a typical key page).
  • None of your key pages are hidden from search and AI.
  • Your pages clearly state what they are: titles, descriptions and headings are in place.
  • Your homepage responds quickly (148 ms, median of 5 requests).
  • AI agents can find your contact page (/home/contact) from the homepage.
  • Your contact page lets in requests that identify as ChatGPT, Claude and Perplexity.
  • Your contact form is in the page code, so AI agents can see it.
  • Your case studies are readable text, so agents can use them as proof.

Next steps

Compare with a competitor

Comparisons are private. Only people with the link can see them.

Fixed something?

How we checkedIs this your company? Request an update or removal

The check shows where agents drop off. The Assessment shows what it's costing you.

Our Pipeline Readiness Assessment is a complimentary 5-day diagnostic across paid efficiency, organic and AI search visibility, and pipeline data, with a 30-minute debrief from a specialist.