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

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

## Results for reco.ai

**74 out of 100** · At risk

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

- **Research** (Website readability): 91% · 32/35 pts · 7/8 passed
- **Evaluate** (Product access): N/A · not scored
- **Reach out** (Agent conversion): 57% · 23/40 pts · 3/5 passed

## How a buyer's AI agent experiences Reco

- Research: passed
- Evaluate: not scored
- Reach out: partly

The agent read your site and understood what you do. It found your demo page at /demo-request, but the form loads with JavaScript, so it couldn't see a way to contact you. It could still use info@reco.ai.

## What Reco should fix first to make the shortlist

### 01 See the form

Render the form in the page HTML. HubSpot: use HubSpot's raw HTML form option or the Forms API, or add a plain HTML fallback form that posts to your CRM.

### 02 Company identity

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

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

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

Evidence:

- `https://www.reco.ai/ · homepage: pass (685 words) · key pages: pass (median 407 words across 5)`
- `https://www.reco.ai/ · 685 words of page content in raw HTML (1206 including nav and footer)`
- `sampled pages: product /platform (787 words), customer /customer-stories/tampa-general-hospital (1250 words), blog /blog/rag-poisoning (300 words), about /about-us (407 words), product /platform/agent-runtime (378 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.reco.ai/ · title:true desc:true h1:1 canonical:true`
- `https://www.reco.ai/platform · title:true desc:true h1:1 canonical:true`
- `https://www.reco.ai/customer-stories/tampa-general-hospital · title:true desc:true h1:1 canonical:true`
- `https://www.reco.ai/blog/rag-poisoning · title:true desc:true h1:1 canonical:true`
- `https://www.reco.ai/about-us · title:true desc:true h1:1 canonical:true`
- `https://www.reco.ai/platform/agent-runtime · 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.reco.ai/ · 0 JSON-LD blocks, no Organization with a name`

### 1.7 Sitemap

**pass** · 2/2 pts

Your sitemap is valid, linked and up to date.

Evidence:

- `https://www.reco.ai/sitemap.xml · valid:true linkedFromRobots:true urls:916 latestLastmod:2026-10-13T18:34:42.386Z`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://reco.ai/ · median 44 ms across 5 requests`
- `https://reco.ai/ · as crawler · HTTP 200 · 467 ms to response headers`
- `https://www.reco.ai/ · as browser · HTTP 200 · 54 ms to response headers`
- `https://www.reco.ai/ · as ChatGPT-User · HTTP 200 · 40 ms to response headers`
- `https://www.reco.ai/ · as Claude-User · HTTP 200 · 37 ms to response headers`
- `https://www.reco.ai/ · as Perplexity-User · HTTP 200 · 44 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.reco.ai/llms.txt · HTTP 200 · valid llms.txt (markdown, starts with # heading)`
- `no <link rel="alternate" type="text/markdown">`

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

We didn't find product signals (developer docs, API, app login) on reco.ai, so we didn't score product access. If you sell software, an MCP server lets AI agents evaluate your product directly. That's quickly becoming a shortlist factor.

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

### 3A Find the way in

**pass** · 8/8 pts

AI agents can find your demo page (/demo-request) from the homepage.

Evidence:

- `https://www.reco.ai/demo-request · demo page found via homepage`

### 3B Let in

**pass** · 10/10 pts

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

Evidence:

- `https://www.reco.ai/demo-request · as browser · HTTP 200 · browser baseline 200`
- `https://www.reco.ai/demo-request · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.reco.ai/demo-request · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.reco.ai/demo-request · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.reco.ai/robots.txt · robots disallow /demo-request for: none`

### 3C See the form

**fail** · 0/12 pts

Your demo form is loaded with JavaScript (HubSpot). People see it. AI agents that read the page code see a page with no way to contact you.

**How to fix:** Render the form in the page HTML. HubSpot: use HubSpot's raw HTML form option or the Forms API, or add a plain HTML fallback form that posts to your CRM.

Evidence:

- `https://www.reco.ai/demo-request · as browser · HTTP 200 · found js.hsforms.net script, no <form> element in page code`

### 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:info@reco.ai 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://www.reco.ai/customer-stories/tampa-general-hospital · HTTP 200 · 1250 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 Reco 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 (685 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 sitemap is valid, linked and up to date.
- Your homepage responds quickly (44 ms, median of 5 requests).
- AI agents can find your demo page (/demo-request) from the homepage.
- Your demo 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%2Freco-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":"reco.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":"reco.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=reco.ai&source=b2b-ai-visibility-checker)
