Free B2B AI Visibility Checker

Would an AI agent shortlist Nous Research?

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

Results for nousresearch.com

59out of 100

At risk

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

97%

Research

34/35 pts · 7/8 passed

0%

Evaluate

0/15 pts · 0/5 passed

45%

Reach out

18/40 pts · 2/5 passed

See what to fix first (3)

How a buyer's AI agent experiences Nous Research

Research: passedEvaluate: stuckReach out: stuck

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 Nous Research should fix first to make the shortlist

01

See the form

Add a simple form, or at least a visible sales email address.

02

Readable proof

Publish customer proof as readable pages. Agents compare vendors on evidence.

03

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.

Research: can AI agents read and understand Nous Research?

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

Content without JavaScript

7/7 pts

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

Evidence
https://nousresearch.com/ · homepage: pass (455 words) · key pages: pass (median 493 words across 3)
https://nousresearch.com/ · 455 words of page content in raw HTML (540 including nav and footer)
sampled pages: product /careers/product-analytics-engineer (435 words), blog /blog (997 words), product /careers/product-manager-hermes-agent (493 words); median words: 493
pass1.4

Accidentally hidden pages

4/4 pts

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

Evidence
checked homepage + 3 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://nousresearch.com/ · title:true desc:true h1:1 canonical:true
https://nousresearch.com/careers/product-analytics-engineer · title:true desc:true h1:1 canonical:true
https://nousresearch.com/blog · title:true desc:true h1:1 canonical:true
https://nousresearch.com/careers/product-manager-hermes-agent · title:true desc:true h1:1 canonical:true
pass1.6

Company identity

3/3 pts

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

Evidence
https://nousresearch.com/ · Organization: name=Nous Research url=yes logo=no sameAs=yes
warning1.7

Sitemap

1/2 pts

Your sitemap has no last-updated dates, so agents can't tell what changed.

How to fix: Link your sitemap from robots.txt and keep lastmod dates current.

Evidence
https://nousresearch.com/sitemap.xml · valid:true linkedFromRobots:true urls:38 latestLastmod:none
pass1.8

Response speed

2/2 pts

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

Evidence
https://nousresearch.com/ · median 65 ms across 5 requests
https://nousresearch.com/ · as crawler · HTTP 200 · 136 ms to response headers
https://nousresearch.com/ · as browser · HTTP 200 · 76 ms to response headers
https://nousresearch.com/ · as ChatGPT-User · HTTP 200 · 65 ms to response headers
https://nousresearch.com/ · as Claude-User · HTTP 200 · 49 ms to response headers
https://nousresearch.com/ · as Perplexity-User · HTTP 200 · 63 ms to response headers
bonus1.9

AI guide files

+1 bonus

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

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

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

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://nousresearch.com/ · 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 Nous Research's sales team?

pass3A

Find the way in

8/8 pts

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

Evidence
https://nousresearch.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://nousresearch.com/contact · as browser · HTTP 200 · browser baseline 200
https://nousresearch.com/contact · as ChatGPT-User · HTTP 200 · HTTP 200
https://nousresearch.com/contact · as Claude-User · HTTP 200 · HTTP 200
https://nousresearch.com/contact · as Perplexity-User · HTTP 200 · HTTP 200
https://nousresearch.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://nousresearch.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
fail3G

Readable proof

0/5 pts

We couldn't find customer stories or case studies.

How to fix: Publish customer proof as readable pages. Agents compare vendors on evidence.

Evidence
no customers / case-studies link on homepage, sitemap or key pages
N/A3H

Self-serve path

not scored

No product-led signals (free trial, sign up) found, so self-serve was not scored.

What Nous Research 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 (455 words on the homepage, 493 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 Nous Research with structured data, so AI can connect the website to the brand.
  • Your homepage responds quickly (65 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.