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

56out of 100

At risk

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

80%

Research

26.5/33 pts · 5/7 passed

7%

Evaluate

1/15 pts · 0/5 passed

51%

Reach out

20.5/40 pts · 2/5 passed

See what to fix first (3)

How a buyer's AI agent experiences Moss

Research: passedEvaluate: stuckReach 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 [email protected].

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?

pass1.1

AI search crawler access

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
pass1.2

Homepage access

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
warning1.3

Content without JavaScript

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
pass1.4

Accidentally hidden pages

4/4 pts

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

Evidence
checked homepage + 2 key pages
pass1.5

Page essentials

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
fail1.6

Company identity

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

Sitemap

not scored

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

Evidence
https://www.getmoss.com/sitemap.xml · timeout
pass1.8

Response speed

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
bonus1.9

AI guide files

+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?

fail2.1

Discoverable

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
fail2.2

Working

0/4 pts

There is no MCP server to test.

fail2.3

Understandable

0/3 pts

There is no MCP server to evaluate.

fail2.4

Connectable

0/2 pts

There is no MCP server to connect to.

warning2.5

Documented

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?

pass3A

Find the way in

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
pass3B

Let in

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
fail3C

See the form

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
fail3D

Understand the form

0/5 pts

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

bonus3F

Agent-friendly route

+1 bonus

You give agents a direct route: visible email.

Evidence
email:[email protected] contactPoint:false llms.txt contact:false MCP contact tool:false
warning3G

Readable proof

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)
N/A3H

Self-serve path

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

Compare with a competitor

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

Fixed something?

How we checkedIs this your company? Request an update or removal

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.