Free B2B AI Visibility Checker

Would an AI agent shortlist Stuut?

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

Results for stuut.ai

85out of 100

Shortlist-ready

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

91%

Research

32/35 pts · 7/8 passed

0%

Evaluate

0/15 pts · 0/5 passed

100%

Reach out

40/40 pts · 5/5 passed

See what to fix first (3)

How a buyer's AI agent experiences Stuut

Research: passedEvaluate: stuckReach out: passed

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

What Stuut should fix first to make the shortlist

01

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.

02

Company identity

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

03

Documented

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

Research: can AI agents read and understand Stuut?

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

Content without JavaScript

7/7 pts

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

Evidence
https://www.stuut.ai/ · homepage: pass (1490 words) · key pages: pass (median 731 words across 5)
https://www.stuut.ai/ · 1490 words of page content in raw HTML (1661 including nav and footer)
sampled pages: product /product/payments (936 words), customer /case-studies/action-elevator (559 words), blog /blog/fiserv-and-stuut-partner-to-bring-agentic-ai-to-enterprise-receivables (731 words), about /about (693 words), product /product/security (840 words); median words: 731
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://www.stuut.ai/ · title:true desc:true h1:1 canonical:true
https://www.stuut.ai/product/payments · title:true desc:true h1:1 canonical:true
https://www.stuut.ai/case-studies/action-elevator · title:true desc:true h1:1 canonical:true
https://www.stuut.ai/blog/fiserv-and-stuut-partner-to-bring-agentic-ai-to-enterprise-receivables · title:true desc:true h1:1 canonical:true
https://www.stuut.ai/about · title:true desc:true h1:1 canonical:true
https://www.stuut.ai/product/security · 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.stuut.ai/ · 1 JSON-LD blocks, no Organization with a name
pass1.7

Sitemap

2/2 pts

Your sitemap is valid, linked and up to date.

Evidence
https://www.stuut.ai/sitemap.xml · valid:true linkedFromRobots:true urls:314 latestLastmod:2026-10-13T18:59:43.588Z
pass1.8

Response speed

2/2 pts

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

Evidence
https://stuut.ai/ · median 241 ms across 5 requests
https://stuut.ai/ · as crawler · HTTP 200 · 321 ms to response headers
https://www.stuut.ai/ · as browser · HTTP 200 · 10 ms to response headers
https://www.stuut.ai/ · as ChatGPT-User · HTTP 200 · 381 ms to response headers
https://www.stuut.ai/ · as Claude-User · HTTP 200 · 241 ms to response headers
https://www.stuut.ai/ · as Perplexity-User · HTTP 200 · 87 ms to response headers
bonus1.9

AI guide files

+1 bonus

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

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

Evaluate: can AI agents try Stuut'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.stuut.ai/.well-known/mcp.json · HTTP 404 · HTTP 404
https://www.stuut.ai/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404
https://www.stuut.ai/.well-known/ai-catalog.json · HTTP 404 · HTTP 404
https://www.stuut.ai/.well-known/api-catalog · HTTP 404 · HTTP 404
https://www.stuut.ai/.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.

fail2.5

Documented

0/2 pts

We couldn't find developer docs linked from your homepage or an OpenAPI spec.

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

Evidence
https://www.stuut.ai/ · no developer docs link on homepage
no OpenAPI found (api-catalog service-desc or homepage link)

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

pass3A

Find the way in

8/8 pts

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

Evidence
https://www.stuut.ai/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://www.stuut.ai/demo · as browser · HTTP 200 · browser baseline 200
https://www.stuut.ai/demo · as ChatGPT-User · HTTP 200 · HTTP 200
https://www.stuut.ai/demo · as Claude-User · HTTP 200 · HTTP 200
https://www.stuut.ai/demo · as Perplexity-User · HTTP 200 · HTTP 200
https://www.stuut.ai/robots.txt · robots disallow /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://www.stuut.ai/demo · as browser · HTTP 200 · contact form in page code with 3 fields (marketing, personalization, analytics)
pass3D

Understand the form

5/5 pts

Your form is clearly labelled with 0 required fields. An agent can fill it for its buyer.

Evidence
https://www.stuut.ai/demo · 3 fields, 0 unlabelled, 0 required, email type: false
bonus3F

Agent-friendly route

+2 bonus

You give agents a direct route: visible email, contact API.

Evidence
email:[email protected] contactPoint:false llms.txt contact:true 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://www.stuut.ai/case-studies/action-elevator · HTTP 200 · 559 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 Stuut 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 (1490 words on the homepage, 731 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 sitemap is valid, linked and up to date.
  • Your homepage responds quickly (241 ms, median of 5 requests).
  • AI agents can find your demo page (/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 form is clearly labelled with 0 required fields. An agent can fill it for its buyer.
  • Your case studies are readable text, so agents can use them as proof.

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.