Free B2B AI Visibility Checker

Would an AI agent shortlist Socket?

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

Results for socket.dev

56out of 100

At risk

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

71%

Research

25/35 pts · 6/8 passed

7%

Evaluate

1/15 pts · 0/5 passed

57%

Reach out

23/40 pts · 3/5 passed

See what to fix first (3)

How a buyer's AI agent experiences Socket

Research: partlyEvaluate: stuckReach out: partly

The agent could read parts of your site, with gaps. It found your demo page at /demo, but found no form there. Journey ended.

What Socket should fix first to make the shortlist

01

See the form

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

02

Homepage access

Ask your web or security team to check firewall and bot-protection rules for AI agent user agents. If your firewall verifies bots by IP, real agents may be treated differently, so confirm with your provider.

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 Socket?

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://socket.dev/robots.txt · HTTP 200 · blocked from /: none; blocked on key paths: none
fail1.2

Homepage access

0/7 pts

When we requested your homepage as ChatGPT-User, we received 403 and a challenge page. A normal browser request received 200.

How to fix: Ask your web or security team to check firewall and bot-protection rules for AI agent user agents. If your firewall verifies bots by IP, real agents may be treated differently, so confirm with your provider.

Evidence
https://socket.dev/ · as browser · HTTP 200 · browser baseline 200
https://socket.dev/ · as ChatGPT-User · HTTP 403 · challenge page: cf-mitigated: challenge header
https://socket.dev/ · as Claude-User · HTTP 403 · challenge page: cf-mitigated: challenge header
https://socket.dev/ · as Perplexity-User · HTTP 403 · challenge page: cf-mitigated: challenge header
pass1.3

Content without JavaScript

7/7 pts

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

Evidence
https://socket.dev/ · homepage: pass (556 words) · key pages: pass (median 530 words across 5)
https://socket.dev/ · 556 words of page content in raw HTML (1177 including nav and footer)
sampled pages: product /features (530 words), customer /case-study/drata (914 words), blog /blog/series-c (1943 words), about /about (511 words), product /features/cli (332 words); median words: 530
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://socket.dev/ · title:true desc:true h1:1 canonical:true
https://socket.dev/features · title:true desc:true h1:1 canonical:true
https://socket.dev/case-study/drata · title:true desc:true h1:1 canonical:true
https://socket.dev/blog/series-c · title:true desc:true h1:1 canonical:true
https://socket.dev/about · title:true desc:true h1:0 canonical:true
https://socket.dev/features/cli · 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://socket.dev/ · 0 JSON-LD blocks, no Organization with a name
pass1.7

Sitemap

2/2 pts

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

Evidence
https://socket.dev/sitemap.xml · valid:true linkedFromRobots:true urls:69714 latestLastmod:2026-10-14T00:00:00.000Z (sitemap index with 10 sitemaps; checked 3, 3 valid)
pass1.8

Response speed

2/2 pts

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

Evidence
https://socket.dev/ · median 12 ms across 5 requests
https://socket.dev/ · as crawler · HTTP 200 · 84 ms to response headers
https://socket.dev/ · as browser · HTTP 200 · 109 ms to response headers
https://socket.dev/ · as ChatGPT-User · HTTP 403 · 12 ms to response headers
https://socket.dev/ · as Claude-User · HTTP 403 · 8 ms to response headers
https://socket.dev/ · as Perplexity-User · HTTP 403 · 7 ms to response headers
bonus1.9

AI guide files

+1 bonus

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

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

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

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

pass3A

Find the way in

8/8 pts

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

Evidence
https://socket.dev/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://socket.dev/demo · as browser · HTTP 200 · browser baseline 200
https://socket.dev/demo · as ChatGPT-User · HTTP 200 · HTTP 200
https://socket.dev/demo · as Claude-User · HTTP 200 · HTTP 200
https://socket.dev/demo · as Perplexity-User · HTTP 200 · HTTP 200
https://socket.dev/robots.txt · robots disallow /demo 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://socket.dev/demo · 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

+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://socket.dev/case-study/drata · HTTP 200 · 914 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 Socket gets right

  • AI search and assistant bots are allowed to read your site.
  • Your pages carry real text in the page code (556 words on the homepage, 530 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 (we checked 3 of the 10 sitemaps in your index).
  • Your homepage responds quickly (12 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 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.