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

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

## Results for getmoss.com

**56 out of 100** · At risk

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

- **Research** (Website readability): 80% · 26.5/33 pts · 5/7 passed
- **Evaluate** (Product access): 7% · 1/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 51% · 20.5/40 pts · 2/5 passed

## How a buyer's AI agent experiences Moss

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

The agent read your site and understood what you do. It found your contact page at /contact, but found no form there. It could still use join@getmoss.com.

## What Moss 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 Content without JavaScript

Make sure headlines, descriptions and key copy are in the HTML the server sends, not only added by JavaScript. Server-side rendering or static generation fixes this.

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

### 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.getmoss.com/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.getmoss.com/ · as browser · HTTP 200 · browser baseline 200`
- `https://www.getmoss.com/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.getmoss.com/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.getmoss.com/ · as Perplexity-User · HTTP 200 · HTTP 200`

### 1.3 Content without JavaScript

**warning** · 3.5/7 pts

Your homepage carries real text (691 words), but your key pages carry little text without JavaScript (74 words on a typical one).

**How to fix:** Make sure headlines, descriptions and key copy are in the HTML the server sends, not only added by JavaScript. Server-side rendering or static generation fixes this.

Evidence:

- `https://www.getmoss.com/ · homepage: pass (691 words) · key pages: below 150 (median 74 words across 2)`
- `https://www.getmoss.com/ · 691 words of page content in raw HTML (869 including nav and footer)`
- `sampled pages: customer /customer-stories/hive (74 words), about /about-us (466 words); median words: 74`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

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

Evidence:

- `checked homepage + 2 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.getmoss.com/ · title:true desc:true h1:2 canonical:true`
- `https://www.getmoss.com/customer-stories/hive · title:true desc:true h1:1 canonical:true`
- `https://www.getmoss.com/about-us · 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.getmoss.com/ · 0 JSON-LD blocks, no Organization with a name`

### 1.7 Sitemap

**inconclusive** · not scored

We could not fetch your sitemap because of a network error on our side.

Evidence:

- `https://www.getmoss.com/sitemap.xml · timeout`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://getmoss.com/ · median 191 ms across 5 requests`
- `https://getmoss.com/ · as crawler · HTTP 200 · 924 ms to response headers`
- `https://www.getmoss.com/ · as browser · HTTP 200 · 188 ms to response headers`
- `https://www.getmoss.com/ · as ChatGPT-User · HTTP 200 · 191 ms to response headers`
- `https://www.getmoss.com/ · as Claude-User · HTTP 200 · 254 ms to response headers`
- `https://www.getmoss.com/ · as Perplexity-User · HTTP 200 · 182 ms to response headers`

### 1.9 AI guide files

**bonus** · +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://www.getmoss.com/llms.txt · HTTP 404 · no valid llms.txt`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Moss'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.getmoss.com/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.getmoss.com/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.getmoss.com/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.getmoss.com/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://www.getmoss.com/.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://www.getmoss.com/ · docs link: https://developers.getmoss.com/?origin-page=en-us`
- `no OpenAPI found (api-catalog service-desc or homepage link)`

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

### 3A Find the way in

**pass** · 8/8 pts

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

Evidence:

- `https://www.getmoss.com/contact · contact page found via homepage`

### 3B Let in

**pass** · 10/10 pts

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

Evidence:

- `https://www.getmoss.com/contact · as browser · HTTP 200 · browser baseline 200`
- `https://www.getmoss.com/contact · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.getmoss.com/contact · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.getmoss.com/contact · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.getmoss.com/robots.txt · robots disallow /contact 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.getmoss.com/contact · 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** · +1 bonus

You give agents a direct route: visible email.

Evidence:

- `email:join@getmoss.com contactPoint:false llms.txt contact:false MCP contact tool:false`

### 3G Readable proof

**warning** · 2.5/5 pts

Your case studies are thin. Agents can't use proof they can't read.

**How to fix:** Publish at least the headline results of each case study as page text.

Evidence:

- `https://www.getmoss.com/customer-stories/hive · HTTP 200 · 74 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 Moss 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.
- 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 (191 ms, median of 5 requests).
- AI agents can find your contact page (/contact) from the homepage.
- Your contact page lets in requests that identify as ChatGPT, Claude and Perplexity.

## 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%2Fgetmoss-com)

### 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":"getmoss.com"}`.

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":"getmoss.com"}`.

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