Free B2B AI Visibility Checker

Would an AI agent shortlist Orkes?

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

Results for orkes.io

58out of 100

At risk

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

100%

Research

35/35 pts · 8/8 passed

7%

Evaluate

1/15 pts · 0/5 passed

42%

Reach out

18/43 pts · 1/6 passed

See what to fix first (3)

How a buyer's AI agent experiences Orkes

Research: passedEvaluate: stuckReach out: stuck

The agent read your site and understood what you do. It found your demo page at /demo, but the form loads with JavaScript, so it couldn't see a way to contact you. Journey ended.

What Orkes 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

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

Find the way in

Link your demo or contact page from the homepage navigation with a clear label like "Book a demo" or "Contact sales".

Research: can AI agents read and understand Orkes?

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

Content without JavaScript

7/7 pts

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

Evidence
https://orkes.io/ · homepage: pass (5363 words) · key pages: pass (median 190 words across 5)
https://orkes.io/ · 5363 words of page content in raw HTML (5474 including nav and footer)
sampled pages: product /platform (1010 words), customer /content/documentation/metrics/client (190 words), blog /content/learn (183 words), about /about-us (320 words), product /use-cases/product-live (72 words); median words: 190
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://orkes.io/ · title:true desc:true h1:1 canonical:true
https://orkes.io/platform · title:true desc:true h1:1 canonical:true
https://orkes.io/content/documentation/metrics/client · title:true desc:true h1:1 canonical:true
https://orkes.io/content/learn · title:true desc:true h1:1 canonical:true
https://orkes.io/about-us · title:true desc:true h1:1 canonical:true
https://orkes.io/use-cases/product-live · title:true desc:true h1:1 canonical:true
pass1.6

Company identity

3/3 pts

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

Evidence
https://orkes.io/ · Organization: name=Orkes url=yes logo=yes sameAs=yes
pass1.7

Sitemap

2/2 pts

Your sitemap is valid, linked and up to date (we checked 3 of the 3 sitemaps in your index).

Evidence
https://orkes.io/sitemap-index.xml · valid:true linkedFromRobots:true urls:1120 latestLastmod:2026-10-13T00:00:00.000Z (sitemap index with 3 sitemaps; checked 3, 3 valid)
pass1.8

Response speed

2/2 pts

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

Evidence
https://orkes.io/ · median 19 ms across 5 requests
https://orkes.io/ · as crawler · HTTP 200 · 195 ms to response headers
https://orkes.io/ · as browser · HTTP 200 · 19 ms to response headers
https://orkes.io/ · as ChatGPT-User · HTTP 200 · 16 ms to response headers
https://orkes.io/ · as Claude-User · HTTP 200 · 23 ms to response headers
https://orkes.io/ · as Perplexity-User · HTTP 200 · 17 ms to response headers
bonus1.9

AI guide files

+1 bonus

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

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

Evaluate: can AI agents try Orkes'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://orkes.io/.well-known/mcp.json · HTTP 404 · HTTP 404
https://orkes.io/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404
https://orkes.io/.well-known/ai-catalog.json · HTTP 404 · HTTP 404
https://orkes.io/.well-known/api-catalog · HTTP 404 · HTTP 404
https://orkes.io/.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://orkes.io/ · docs link: https://orkes.io/content
no OpenAPI found (api-catalog service-desc or homepage link)

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

warning3A

Find the way in

4/8 pts

Your demo page exists at /demo, but isn't linked from the homepage.

How to fix: Link your demo or contact page from the homepage navigation with a clear label like "Book a demo" or "Contact sales".

Evidence
https://orkes.io/demo · demo page found via sitemap
pass3B

Let in

10/10 pts

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

Evidence
https://orkes.io/demo · as browser · HTTP 200 · browser baseline 200
https://orkes.io/demo · as ChatGPT-User · HTTP 200 · HTTP 200
https://orkes.io/demo · as Claude-User · HTTP 200 · HTTP 200
https://orkes.io/demo · as Perplexity-User · HTTP 200 · HTTP 200
https://orkes.io/robots.txt · robots disallow /demo for: none
fail3C

See the form

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://orkes.io/demo · as browser · HTTP 200 · found js.hsforms.net script, no <form> element in page code
fail3D

Understand the form

0/5 pts

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

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
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://orkes.io/content/documentation/metrics/client · HTTP 200 · 190 words of page content in raw HTML (nav and footer excluded)
warning3H

Self-serve path

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
signals: Start for free; no sign-up link in page code

What Orkes 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 (5363 words on the homepage, 190 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 Orkes with structured data, so AI can connect the website to the brand.
  • Your sitemap is valid, linked and up to date (we checked 3 of the 3 sitemaps in your index).
  • Your homepage responds quickly (19 ms, median of 5 requests).
  • Your demo 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.