---
title: "Would AI Agents Shortlist Convex? 76/100 AI Agent Readiness | VertoDigital"
description: "Convex scored 76/100 (At risk) on AI agent readiness. See whether buyers' AI agents would shortlist Convex: can they research it, evaluate the product and reach sales? Evidence and fixes included."
url: "https://vertodigital.com/b2b-ai-visibility-checker/tool/convex-dev"
image: "https://vertodigital.com/b2b-ai-visibility-checker/tool/convex-dev/og.png"
---

> For AI agents: an index of every page on this site is at https://vertodigital.com/llms.txt

Free B2B AI Visibility Checker

# Would an AI agent shortlist Convex?

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

## Results for convex.dev

**76 out of 100** · At risk

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

- **Research** (Website readability): 89% · 31/35 pts · 6/8 passed
- **Evaluate** (Product access): 13% · 2/15 pts · 1/5 passed
- **Reach out** (Agent conversion): 84% · 33.5/40 pts · 3/5 passed

## How a buyer's AI agent experiences Convex

- Research: passed
- Evaluate: stuck
- Reach out: passed

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

## What Convex should fix first to make the shortlist

### 01 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.

### 02 Find the way in

Link your demo or contact page from the homepage navigation with a clear label like "Book a demo" or "Contact sales".

### 03 Company identity

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

## Research: can AI agents read and understand Convex?

### 1.1 AI search crawler access

**pass** · 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://www.convex.dev/robots.txt · HTTP 200 · blocked from /: none; blocked on key paths: none`

### 1.2 Homepage access

**pass** · 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://www.convex.dev/ · as browser · HTTP 200 · browser baseline 200`
- `https://www.convex.dev/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.convex.dev/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.convex.dev/ · as Perplexity-User · HTTP 200 · HTTP 200`

### 1.3 Content without JavaScript

**pass** · 7/7 pts

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

Evidence:

- `https://www.convex.dev/ · homepage: pass (859 words) · key pages: pass (median 407 words across 5)`
- `https://www.convex.dev/ · 859 words of page content in raw HTML (1110 including nav and footer)`
- `sampled pages: product /can-do/feature-flags (107 words), customer /case-studies/conduit (407 words), blog /hackathons/resources (497 words), about /about-us (1847 words), product /templates/product-hunt-digg-hacknews-clone (120 words); median words: 407`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

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

Evidence:

- `checked homepage + 5 key pages`

### 1.5 Page essentials

**pass** · 3/3 pts

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

Evidence:

- `https://www.convex.dev/ · title:true desc:true h1:1 canonical:true`
- `https://www.convex.dev/can-do/feature-flags · title:true desc:true h1:1 canonical:true`
- `https://www.convex.dev/case-studies/conduit · title:true desc:true h1:1 canonical:true`
- `https://www.convex.dev/hackathons/resources · title:true desc:true h1:1 canonical:true`
- `https://www.convex.dev/about-us · title:true desc:true h1:1 canonical:true`
- `https://www.convex.dev/templates/product-hunt-digg-hacknews-clone · title:true desc:true h1:1 canonical:true`

### 1.6 Company identity

**fail** · 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://www.convex.dev/ · 0 JSON-LD blocks, no Organization with a name`

### 1.7 Sitemap

**warning** · 1/2 pts

Your sitemap has no last-updated dates, so agents can't tell what changed.

**How to fix:** Link your sitemap from robots.txt and keep lastmod dates current.

Evidence:

- `https://www.convex.dev/sitemap.xml · valid:true linkedFromRobots:true urls:205 latestLastmod:none`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://convex.dev/ · median 52 ms across 5 requests`
- `https://convex.dev/ · as crawler · HTTP 200 · 261 ms to response headers`
- `https://www.convex.dev/ · as browser · HTTP 200 · 38 ms to response headers`
- `https://www.convex.dev/ · as ChatGPT-User · HTTP 200 · 54 ms to response headers`
- `https://www.convex.dev/ · as Claude-User · HTTP 200 · 52 ms to response headers`
- `https://www.convex.dev/ · as Perplexity-User · HTTP 200 · 36 ms to response headers`

### 1.9 AI guide files

**bonus** · +1 bonus

You publish an llms.txt file. Early, and a good signal.

Evidence:

- `https://www.convex.dev/llms.txt · HTTP 200 · valid llms.txt (markdown, starts with # heading)`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Convex's product?

### 2.1 Discoverable

**fail** · 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://www.convex.dev/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.convex.dev/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.convex.dev/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.convex.dev/.well-known/api-catalog · HTTP 200 · valid JSON`
- `https://www.convex.dev/.well-known/oauth-protected-resource · HTTP 404 · HTTP 404`

### 2.2 Working

**fail** · 0/4 pts

There is no MCP server to test.

### 2.3 Understandable

**fail** · 0/3 pts

There is no MCP server to evaluate.

### 2.4 Connectable

**fail** · 0/2 pts

There is no MCP server to connect to.

### 2.5 Documented

**pass** · 2/2 pts

Your developer docs and API spec are easy for agents to find.

Evidence:

- `https://www.convex.dev/ · docs link: https://docs.convex.dev/`
- `https://api.convex.dev/v1/openapi.json · HTTP 200 · OpenAPI spec fetched and valid`

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

### 3A Find the way in

**warning** · 4/8 pts

Your contact page exists at /enterprise/contact, but isn't linked from the homepage.

**How to fix:** Link your demo or contact page from the homepage navigation with a clear label like "Book a demo" or "Contact sales".

Evidence:

- `https://www.convex.dev/enterprise/contact · contact page found via sitemap`

### 3B Let in

**pass** · 10/10 pts

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

Evidence:

- `https://www.convex.dev/enterprise/contact · as browser · HTTP 200 · browser baseline 200`
- `https://www.convex.dev/enterprise/contact · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.convex.dev/enterprise/contact · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.convex.dev/enterprise/contact · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.convex.dev/robots.txt · robots disallow /enterprise/contact for: none`

### 3C See the form

**pass** · 12/12 pts

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

Evidence:

- `https://www.convex.dev/enterprise/contact · as browser · HTTP 200 · contact form in page code with 5 fields (website_confirm, name, email, company, whereHeard)`

### 3D Understand the form

**warning** · 2.5/5 pts

1 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://www.convex.dev/enterprise/contact · 5 fields, 1 unlabelled, 4 required, email type: false`

### 3F Agent-friendly route

**bonus** · +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`

### 3G Readable proof

**pass** · 5/5 pts

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

Evidence:

- `https://www.convex.dev/case-studies/conduit · HTTP 200 · 407 words of page content in raw HTML (nav and footer excluded)`

### 3H Self-serve path

**N/A** · not scored

No product-led signals (free trial, sign up) found, so self-serve was not scored.

## What Convex 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 (859 words on the homepage, 407 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 (52 ms, median of 5 requests).
- Your developer docs and API spec are easy for agents to find.
- 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

### Share with your team

Send the report to your web team, or post your score on LinkedIn.

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fvertodigital.com%2Fb2b-ai-visibility-checker%2Ftool%2Fconvex-dev)

### Compare with a competitor

Agents can start one through the API: `POST https://vertodigital.com/agent/readiness/checks` with `{"domain":"competitor.com","mode":"compare","compare_with":"convex.dev"}`.

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

### Fixed something?

Agents can rescan through the API: `POST https://vertodigital.com/agent/readiness/checks` with `{"domain":"convex.dev"}`.

[How we checked](https://vertodigital.com/b2b-ai-visibility-checker/tool/how-it-works)

[Is this your company? Request an update or removal](https://vertodigital.com/b2b-ai-visibility-checker/tool/request-update)

## 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.

[Book your Pipeline Readiness Assessment](https://vertodigital.com/assessment?domain=convex.dev&source=b2b-ai-visibility-checker)
