Free B2B AI Visibility Checker

Would an AI agent shortlist Omni?

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

Results for omni.co

83out of 100

Shortlist-ready

AI agents can research Omni, evaluate the product and get buyers to the sales team.

100%

Research

35/35 pts · 8/8 passed

20%

Evaluate

3/15 pts · 0/5 passed

88%

Reach out

38/43 pts · 5/6 passed

See what to fix first (3)

How a buyer's AI agent experiences Omni

Research: passedEvaluate: stuckReach out: passed

The agent read your site and understood what you do. It found your demo page at /request-demo and could see how to reach your sales team.

What Omni should fix first to make the shortlist

01

Understand the form

Label every field, use the right field types (email, phone) and cut required fields to what sales really needs.

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.

03

Documented

Link developer docs from the homepage and publish your OpenAPI spec at a discoverable URL.

Research: can AI agents read and understand Omni?

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://omni.co/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://omni.co/ · as browser · HTTP 200 · browser baseline 200
https://omni.co/ · as ChatGPT-User · HTTP 200 · HTTP 200
https://omni.co/ · as Claude-User · HTTP 200 · HTTP 200
https://omni.co/ · as Perplexity-User · HTTP 200 · HTTP 200
pass1.3

Content without JavaScript

7/7 pts

Your pages carry real text in the page code (937 words on the homepage, 718 on a typical key page).

Evidence
https://omni.co/ · homepage: pass (937 words) · key pages: pass (median 718 words across 5)
https://omni.co/ · 937 words of page content in raw HTML (1175 including nav and footer)
sampled pages: product /platform (993 words), customer /blog/case-study-meandu (1708 words), blog /blog/older/2 (140 words), about /about (506 words), product /blog/product-updates-july-2023 (718 words); median words: 718
pass1.4

Accidentally hidden pages

4/4 pts

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

Evidence
checked homepage + 5 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://omni.co/ · title:true desc:true h1:1 canonical:true
https://omni.co/platform · title:true desc:true h1:1 canonical:true
https://omni.co/blog/case-study-meandu · title:true desc:true h1:1 canonical:true
https://omni.co/blog/older/2 · title:true desc:false h1:0 canonical:true
https://omni.co/about · title:true desc:true h1:1 canonical:true
https://omni.co/blog/product-updates-july-2023 · title:true desc:true h1:1 canonical:true
pass1.6

Company identity

3/3 pts

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

Evidence
https://omni.co/ · Organization: name=Omni Analytics url=yes logo=yes sameAs=yes
pass1.7

Sitemap

2/2 pts

Your sitemap is valid, linked and up to date.

Evidence
https://omni.co/sitemap.xml · valid:true linkedFromRobots:true urls:262 latestLastmod:2026-10-14T00:00:00.000Z
pass1.8

Response speed

2/2 pts

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

Evidence
https://omni.co/ · median 45 ms across 5 requests
https://omni.co/ · as crawler · HTTP 200 · 251 ms to response headers
https://omni.co/ · as browser · HTTP 200 · 52 ms to response headers
https://omni.co/ · as ChatGPT-User · HTTP 200 · 42 ms to response headers
https://omni.co/ · as Claude-User · HTTP 200 · 45 ms to response headers
https://omni.co/ · as Perplexity-User · HTTP 200 · 40 ms to response headers
bonus1.9

AI guide files

+1 bonus

You publish an llms.txt file. Early, and a good signal.

Evidence
https://omni.co/llms.txt · HTTP 200 · valid llms.txt (markdown, starts with # heading)
no <link rel="alternate" type="text/markdown">

Evaluate: can AI agents try Omni's product?

warning2.1

Discoverable

2/4 pts

Your website mentions an MCP server, but doesn't tell AI agents where it is in a way they can find on their own.

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.

Evidence
https://omni.co/.well-known/mcp.json · HTTP 404 · HTTP 404
https://omni.co/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404
https://omni.co/.well-known/ai-catalog.json · HTTP 404 · HTTP 404
https://omni.co/.well-known/api-catalog · HTTP 404 · HTTP 404
https://omni.co/.well-known/oauth-protected-resource · HTTP 404 · HTTP 404
https://omni.co/ · homepage mentions MCP: https://docs.omni.co/ai/mcp/cursor, https://docs.omni.co/ai/mcp/index, https://docs.omni.co/docs/ai/mcp
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://omni.co/ · docs link: https://docs.omni.co/demos
no OpenAPI found (api-catalog service-desc or homepage link)

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

pass3A

Find the way in

8/8 pts

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

Evidence
https://omni.co/request-demo · demo page found via homepage
pass3B

Let in

10/10 pts

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

Evidence
https://omni.co/request-demo · as browser · HTTP 200 · browser baseline 200
https://omni.co/request-demo · as ChatGPT-User · HTTP 200 · HTTP 200
https://omni.co/request-demo · as Claude-User · HTTP 200 · HTTP 200
https://omni.co/request-demo · as Perplexity-User · HTTP 200 · HTTP 200
https://omni.co/robots.txt · robots disallow /request-demo for: none
pass3C

See the form

12/12 pts

Your demo form is in the page code, so AI agents can see it.

Evidence
https://omni.co/request-demo · as browser · HTTP 200 · contact form in page code with 8 fields (firstname, lastname, email, phone, company, hq_country, business_website, how_did_you_hear_about_us__c)
fail3D

Understand the form

0/5 pts

5 fields have no label.

How to fix: Label every field, use the right field types (email, phone) and cut required fields to what sales really needs.

Evidence
https://omni.co/request-demo · 8 fields, 5 unlabelled, 6 required, email type: true
bonus3F

Agent-friendly route

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

Readable proof

5/5 pts

Your case studies are readable text, so agents can use them as proof.

Evidence
https://omni.co/blog/case-study-meandu · HTTP 200 · 1708 words of page content in raw HTML (nav and footer excluded)
pass3H

Self-serve path

3/3 pts

Agents can find and reach your free trial / sign-up.

Evidence
https://omni.co/demo · as ChatGPT-User · HTTP 200 · 437 words, form: inline

What Omni 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 (937 words on the homepage, 718 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 Omni Analytics with structured data, so AI can connect the website to the brand.
  • Your sitemap is valid, linked and up to date.
  • Your homepage responds quickly (45 ms, median of 5 requests).
  • AI agents can find your demo page (/request-demo) from the homepage.
  • Your demo page lets in requests that identify as ChatGPT, Claude and Perplexity.
  • Your demo form is in the page code, so AI agents can see it.
  • Your case studies are readable text, so agents can use them as proof.
  • Agents can find and reach your free trial / sign-up.

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.