---
title: "Would AI Agents Shortlist Juicebox? 66/100 AI Agent Readiness | VertoDigital"
description: "Juicebox scored 66/100 (At risk) on AI agent readiness. See whether buyers' AI agents would shortlist Juicebox: can they research it, evaluate the product and reach sales? Evidence and fixes included."
url: "https://vertodigital.com/b2b-ai-visibility-checker/tool/juicebox-ai"
image: "https://vertodigital.com/b2b-ai-visibility-checker/tool/juicebox-ai/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 Juicebox?

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

## Results for juicebox.ai

**66 out of 100** · At risk

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

- **Research** (Website readability): 97% · 34/35 pts · 7/8 passed
- **Evaluate** (Product access): 7% · 1/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 57% · 24.5/43 pts · 3/6 passed

## How a buyer's AI agent experiences Juicebox

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

The agent read your site and understood what you do. It found your trial page at /, but found no form there. It could still use sales@juicebox.work.

## What Juicebox should fix first to make the shortlist

### 01 See the form

Add a simple form, or at least a visible sales email address.

### 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 Self-serve path

Make the sign-up page reachable and readable without JavaScript.

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

### 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://juicebox.ai/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://juicebox.ai/ · as browser · HTTP 200 · browser baseline 200`
- `https://juicebox.ai/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://juicebox.ai/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://juicebox.ai/ · 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 (2416 words on the homepage, 1677 on a typical key page).

Evidence:

- `https://juicebox.ai/ · homepage: pass (2416 words) · key pages: pass (median 1677 words across 4)`
- `https://juicebox.ai/ · 2416 words of page content in raw HTML (2416 including nav and footer)`
- `sampled pages: product /services-agreement (4026 words), customer /customers/omnea (1461 words), blog /blog (1677 words), product /careers/product-manager (1871 words); median words: 1677`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

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

Evidence:

- `checked homepage + 4 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://juicebox.ai/ · title:true desc:true h1:1 canonical:true`
- `https://juicebox.ai/services-agreement · title:true desc:true h1:2 canonical:true`
- `https://juicebox.ai/customers/omnea · title:true desc:true h1:1 canonical:true`
- `https://juicebox.ai/blog · title:true desc:true h1:1 canonical:true`
- `https://juicebox.ai/careers/product-manager · title:true desc:true h1:3 canonical:true`

### 1.6 Company identity

**pass** · 3/3 pts

Your site identifies Juicebox with structured data, so AI can connect the website to the brand.

Evidence:

- `https://juicebox.ai/ · Organization: name=Juicebox url=yes logo=yes sameAs=yes`

### 1.7 Sitemap

**warning** · 1/2 pts

2 of the 3 sitemaps we checked are broken or empty.

**How to fix:** Fix or remove the broken sitemap files listed in your sitemap index.

Evidence:

- `https://juicebox.ai/sitemap_index.xml · valid:true linkedFromRobots:true urls:125 latestLastmod:2026-10-15T00:00:00.000Z (sitemap index with 4 sitemaps; checked 3, 1 valid, broken: https://juicebox.ai/blog/sitemap.xml, https://juicebox.ai/hire/sitemap.xml)`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://juicebox.ai/ · median 77 ms across 5 requests`
- `https://juicebox.ai/ · as crawler · HTTP 200 · 207 ms to response headers`
- `https://juicebox.ai/ · as browser · HTTP 200 · 183 ms to response headers`
- `https://juicebox.ai/ · as ChatGPT-User · HTTP 200 · 60 ms to response headers`
- `https://juicebox.ai/ · as Claude-User · HTTP 200 · 62 ms to response headers`
- `https://juicebox.ai/ · as Perplexity-User · HTTP 200 · 77 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://juicebox.ai/llms.txt · HTTP 200 · valid llms.txt (markdown, starts with # heading)`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Juicebox'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://juicebox.ai/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://juicebox.ai/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://juicebox.ai/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://juicebox.ai/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://juicebox.ai/.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

**warning** · 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://juicebox.ai/ · docs link: http://docs.juicebox.ai/`
- `no OpenAPI found (api-catalog service-desc or homepage link)`

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

### 3A Find the way in

**pass** · 8/8 pts

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

Evidence:

- `https://app.juicebox.ai/ · trial page found via homepage`

### 3B Let in

**pass** · 10/10 pts

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

Evidence:

- `https://app.juicebox.ai/ · as browser · HTTP 200 · browser baseline 200`
- `https://app.juicebox.ai/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://app.juicebox.ai/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://app.juicebox.ai/ · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://juicebox.ai/robots.txt · robots disallow / for: none`

### 3C See the form

**fail** · 0/12 pts

We couldn't find a form on your conversion page.

**How to fix:** Add a simple form, or at least a visible sales email address.

Evidence:

- `https://app.juicebox.ai/ · as browser · HTTP 200 · no <form> element and no known form embed`

### 3D Understand the form

**fail** · 0/5 pts

Not scored: an agent can't understand a form it can't see.

### 3F Agent-friendly route

**bonus** · +2 bonus

You give agents a direct route: visible email, contact API.

Evidence:

- `email:sales@juicebox.work contactPoint:false llms.txt contact:true 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://juicebox.ai/customers/omnea · HTTP 200 · 1461 words of page content in raw HTML (nav and footer excluded)`

### 3H Self-serve path

**warning** · 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:

- `https://app.juicebox.ai/ · as ChatGPT-User · HTTP 200 · 0 words, form: none`

## What Juicebox 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 (2416 words on the homepage, 1677 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 site identifies Juicebox with structured data, so AI can connect the website to the brand.
- Your homepage responds quickly (77 ms, median of 5 requests).
- AI agents can find your trial page (/) from the homepage.
- Your trial page lets in requests that identify as ChatGPT, Claude and Perplexity.
- 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%2Fjuicebox-ai)

### 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":"juicebox.ai"}`.

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":"juicebox.ai"}`.

[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=juicebox.ai&source=b2b-ai-visibility-checker)
