Free B2B AI Visibility Checker

Would an AI agent shortlist Neo4j?

Last checked 2026-11-06 · 21 checks · Read-only, no browser

Results for neo4j.com

73out of 100

At risk

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

100%

Research

35/35 pts · 8/8 passed

47%

Evaluate

7/15 pts · 2/5 passed

60%

Reach out

26/43 pts · 4/6 passed

See what to fix first (3)

How a buyer's AI agent experiences Neo4j

Research: passedEvaluate: stuckReach out: partly

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

What Neo4j should fix first to make the shortlist

01

See the form

Render the form in the page HTML. Marketo: use a server-rendered form posting to the Marketo Forms API, or add a plain HTML fallback form that posts to your CRM.

02

Working

Check the endpoint's availability and that it speaks MCP over HTTP.

03

Understandable

Describe what each tool does, when to use it and what it returns, in plain language.

Research: can AI agents read and understand Neo4j?

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://neo4j.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://neo4j.com/ · as browser · HTTP 200 · browser baseline 200
https://neo4j.com/ · as ChatGPT-User · HTTP 200 · HTTP 200
https://neo4j.com/ · as Claude-User · HTTP 200 · HTTP 200
https://neo4j.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 (1403 words on the homepage, 1320 on a typical key page).

Evidence
https://neo4j.com/ · homepage: pass (1403 words) · key pages: pass (median 1320 words across 5)
https://neo4j.com/ · 1403 words of page content in raw HTML (1876 including nav and footer)
sampled pages: product /product/ (1088 words), customer /blog/customer-360/connected-ai-ready-cx/ (2434 words), blog /blog/graph-database/neo4j-graph-visualization-library/ (1320 words), about /company/ (1124 words), product /product/auradb/ (2584 words); median words: 1320
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://neo4j.com/ · title:true desc:true h1:1 canonical:true
https://neo4j.com/product/ · title:true desc:true h1:1 canonical:true
https://neo4j.com/blog/customer-360/connected-ai-ready-cx/ · title:true desc:true h1:1 canonical:true
https://neo4j.com/blog/graph-database/neo4j-graph-visualization-library/ · title:true desc:true h1:1 canonical:true
https://neo4j.com/company/ · title:true desc:true h1:1 canonical:true
https://neo4j.com/product/auradb/ · title:true desc:true h1:1 canonical:true
pass1.6

Company identity

3/3 pts

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

Evidence
https://neo4j.com/ · Organization: name=Neo4j 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 23 sitemaps in your index).

Evidence
https://neo4j.com/sitemap_index.xml · valid:true linkedFromRobots:true urls:2740 latestLastmod:2026-11-06T14:41:09.000Z (sitemap index with 23 sitemaps; checked 3, 3 valid)
pass1.8

Response speed

2/2 pts

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

Evidence
https://neo4j.com/ · median 49 ms across 5 requests
https://neo4j.com/ · as crawler · HTTP 200 · 91 ms to response headers
https://neo4j.com/ · as browser · HTTP 200 · 38 ms to response headers
https://neo4j.com/ · as ChatGPT-User · HTTP 200 · 48 ms to response headers
https://neo4j.com/ · as Claude-User · HTTP 200 · 49 ms to response headers
https://neo4j.com/ · as Perplexity-User · HTTP 200 · 60 ms to response headers
bonus1.9

AI guide files

+1 bonus

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

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

Evaluate: can AI agents try Neo4j's product?

pass2.1

Discoverable

4/4 pts

AI agents can discover your MCP server from your website, at https://neo4j.com/developer/genai-ecosystem/model-context-protocol-mcp/.

Evidence
https://neo4j.com/.well-known/mcp.json · HTTP 403 · HTTP 403
https://neo4j.com/.well-known/mcp/server-card.json · HTTP 200 · valid JSON
https://neo4j.com/.well-known/ai-catalog.json · HTTP 403 · HTTP 403
https://neo4j.com/.well-known/api-catalog · HTTP 200 · valid JSON
https://neo4j.com/.well-known/oauth-protected-resource · HTTP 403 · HTTP 403
https://neo4j.com/ · homepage mentions MCP: https://neo4j.com/developer/genai-ecosystem/model-context-protocol-mcp/, https://neo4j.com/developer/genai-ecosystem/model-context-protocol-mcp/, https://neo4j.com/developer/genai-ecosystem/model-context-protocol-mcp/
fail2.2

Working

0/4 pts

Your MCP server returned an error (HTTP 403) instead of a valid MCP response.

How to fix: Check the endpoint's availability and that it speaks MCP over HTTP.

Evidence
https://neo4j.com/developer/genai-ecosystem/model-context-protocol-mcp/ · HTTP 403 · initialize: HTTP 403 in 14 ms
fail2.3

Understandable

0/3 pts

Your MCP server did not return a tool list.

How to fix: Describe what each tool does, when to use it and what it returns, in plain language.

pass2.4

Connectable

2/2 pts

An agent can work out how to connect to your MCP server.

Evidence
https://neo4j.com/developer/genai-ecosystem/model-context-protocol-mcp/ · HTTP 403 · WWW-Authenticate: none
https://neo4j.com/.well-known/oauth-protected-resource · HTTP 403 · none
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://neo4j.com/ · docs link: https://neo4j.com/docs/
no OpenAPI found (api-catalog service-desc or homepage link)

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

pass3A

Find the way in

8/8 pts

AI agents can find your contact page (/contact-us/?ref=nav) from the homepage.

Evidence
https://neo4j.com/contact-us/?ref=nav · 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://neo4j.com/contact-us/?ref=nav · as browser · HTTP 200 · browser baseline 200
https://neo4j.com/contact-us/?ref=nav · as ChatGPT-User · HTTP 200 · HTTP 200
https://neo4j.com/contact-us/?ref=nav · as Claude-User · HTTP 200 · HTTP 200
https://neo4j.com/contact-us/?ref=nav · as Perplexity-User · HTTP 200 · HTTP 200
https://neo4j.com/robots.txt · robots disallow /contact-us/?ref=nav for: none
fail3C

See the form

0/12 pts

Your contact form is loaded with JavaScript (Marketo). 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. Marketo: use a server-rendered form posting to the Marketo Forms API, or add a plain HTML fallback form that posts to your CRM.

Evidence
https://neo4j.com/contact-us/?ref=nav · as browser · HTTP 200 · found MktoForms2 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
pass3G

Readable proof

5/5 pts

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

Evidence
https://neo4j.com/blog/customer-360/connected-ai-ready-cx/ · HTTP 200 · 2434 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://neo4j.com/nodes/?utm_source=website&utm_medium=strip-banner&utm_campaign=dev · as ChatGPT-User · HTTP 200 · 2453 words, form: none

What Neo4j 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 (1403 words on the homepage, 1320 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 Neo4j 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 23 sitemaps in your index).
  • Your homepage responds quickly (49 ms, median of 5 requests).
  • AI agents can discover your MCP server from your website, at https://neo4j.com/developer/genai-ecosystem/model-context-protocol-mcp/.
  • An agent can work out how to connect to your MCP server.
  • AI agents can find your contact page (/contact-us/?ref=nav) from the homepage.
  • Your contact page lets in requests that identify as ChatGPT, Claude and Perplexity.
  • 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.