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

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

## Results for ema.ai

**68 out of 100** · At risk

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

- **Research** (Website readability): 81% · 28.5/35 pts · 5/8 passed
- **Evaluate** (Product access): N/A · not scored
- **Reach out** (Agent conversion): 57% · 24.5/43 pts · 3/6 passed

## How a buyer's AI agent experiences Ema

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

The agent read your site and understood what you do. It found your demo page at /hire-ema, but found no form there. Journey ended.

## What Ema should fix first to make the shortlist

### 01 See the form

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

### 02 Company identity

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

### 03 Accidentally hidden pages

Remove the noindex tag or header unless hiding this page is intentional.

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

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

Evidence:

- `https://www.ema.ai/ · homepage: pass (601 words) · key pages: pass (median 436 words across 5)`
- `https://www.ema.ai/ · 601 words of page content in raw HTML (657 including nav and footer)`
- `sampled pages: product /blog/tags/platform (37 words), customer /hire-ema/customer-experiences (11166 words), blog /agent-qa/insights (436 words), about /about-us (929 words), product /blog/product-launch (172 words); median words: 436`

### 1.4 Accidentally hidden pages

**warning** · 2/4 pts

/blog/tags/platform tells search engines and AI not to index it (noindex).

**How to fix:** Remove the noindex tag or header unless hiding this page is intentional.

Evidence:

- `https://www.ema.ai/blog/tags/platform · noindex`

### 1.5 Page essentials

**warning** · 1.5/3 pts

2 of 6 pages we checked are missing a title / description.

**How to fix:** Give every key page a unique title, a one-sentence description, one main heading and a canonical URL.

Evidence:

- `https://www.ema.ai/ · title:true desc:true h1:1 canonical:true`
- `https://www.ema.ai/blog/tags/platform · title:false desc:false h1:1 canonical:true`
- `https://www.ema.ai/hire-ema/customer-experiences · title:true desc:false h1:1 canonical:true`
- `https://builder-docs.ema.ai/agent-qa/insights · title:true desc:true h1:1 canonical:true`
- `https://www.ema.ai/about-us · title:true desc:true h1:1 canonical:true`
- `https://www.ema.ai/blog/product-launch · 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.ema.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 (we checked 1 of the 1 sitemaps in your index).

Evidence:

- `https://www.ema.ai/sitemap.xml · valid:true linkedFromRobots:true urls:2297 latestLastmod:2026-10-14T20:55:04.708Z (sitemap index with 1 sitemaps; checked 1, 1 valid)`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://ema.ai/ · median 59 ms across 5 requests`
- `https://ema.ai/ · as crawler · HTTP 200 · 132 ms to response headers`
- `https://www.ema.ai/ · as browser · HTTP 200 · 59 ms to response headers`
- `https://www.ema.ai/ · as ChatGPT-User · HTTP 200 · 59 ms to response headers`
- `https://www.ema.ai/ · as Claude-User · HTTP 200 · 57 ms to response headers`
- `https://www.ema.ai/ · as Perplexity-User · HTTP 200 · 59 ms to response headers`

### 1.9 AI guide files

**bonus** · +1 bonus

You publish markdown versions of your pages. Early, and a good signal.

Evidence:

- `https://www.ema.ai/llms.txt · no valid llms.txt`
- `markdown alternate: https://www.ema.ai/index.md`

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

We didn't find product signals (developer docs, API, app login) on ema.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 Ema's sales team?

### 3A Find the way in

**pass** · 8/8 pts

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

Evidence:

- `https://www.ema.ai/hire-ema · 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.ema.ai/hire-ema · as browser · HTTP 200 · browser baseline 200`
- `https://www.ema.ai/hire-ema · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.ema.ai/hire-ema · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.ema.ai/hire-ema · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.ema.ai/robots.txt · robots disallow /hire-ema 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://www.ema.ai/hire-ema · 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** · +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.ema.ai/hire-ema/customer-experiences · HTTP 200 · 11166 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://try.ema.ai/ · as ChatGPT-User · HTTP 200 · 0 words, form: none`

## What Ema 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 (601 words on the homepage, 436 on a typical key page).
- Your sitemap is valid, linked and up to date (we checked 1 of the 1 sitemaps in your index).
- Your homepage responds quickly (59 ms, median of 5 requests).
- AI agents can find your demo page (/hire-ema) 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%2Fema-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":"ema.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":"ema.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=ema.ai&source=b2b-ai-visibility-checker)
