Free B2B AI Visibility Checker

Would an AI agent shortlist Eye Security?

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

Results for eye.security

76out of 100

At risk

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

97%

Research

34/35 pts · 7/8 passed

N/A

Evaluate

not scored

57%

Reach out

23/40 pts · 3/5 passed

See what to fix first (2)

How a buyer's AI agent experiences Eye Security

Research: passedEvaluate: not scoredReach out: partly

The agent read your site and understood what you do. It found your contact page at /contact/, but the form loads with JavaScript, so it couldn't see a way to contact you. It could still use [email protected].

What Eye Security 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

Response speed

Review hosting, caching and CDN settings for the homepage.

Research: can AI agents read and understand Eye Security?

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

Content without JavaScript

7/7 pts

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

Evidence
https://eye.security/ · homepage: pass (1300 words) · key pages: pass (median 1295 words across 5)
https://eye.security/ · 1300 words of page content in raw HTML (1517 including nav and footer)
sampled pages: product /solution/ (1295 words), customer /case-study/keytec/ (1249 words), blog /de/blog/ (4369 words), about /about-us/ (1270 words), product /solution/ (1295 words); median words: 1295
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://eye.security/ · title:true desc:true h1:1 canonical:true
https://eye.security/solution/ · title:true desc:true h1:1 canonical:true
https://eye.security/case-study/keytec/ · title:true desc:true h1:1 canonical:true
https://eye.security/de/blog/ · title:true desc:true h1:1 canonical:true
https://eye.security/about-us/ · title:true desc:true h1:1 canonical:true
https://eye.security/solution/ · title:true desc:true h1:1 canonical:true
pass1.6

Company identity

3/3 pts

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

Evidence
https://eye.security/ · Organization: name=Eye Security 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 21 sitemaps in your index).

Evidence
https://eye.security/sitemap_index.xml · valid:true linkedFromRobots:true urls:339 latestLastmod:2026-10-13T12:10:40.000Z (sitemap index with 21 sitemaps; checked 3, 3 valid)
warning1.8

Response speed

1/2 pts

Your homepage took 1830 ms to start responding (median of 5 requests). Agents on a time budget may give up.

How to fix: Review hosting, caching and CDN settings for the homepage.

Evidence
https://eye.security/ · median 1830 ms across 5 requests
https://eye.security/ · as crawler · HTTP 200 · 3190 ms to response headers
https://eye.security/ · as browser · HTTP 200 · 1870 ms to response headers
https://eye.security/ · as ChatGPT-User · HTTP 200 · 1830 ms to response headers
https://eye.security/ · as Claude-User · HTTP 200 · 1673 ms to response headers
https://eye.security/ · as Perplexity-User · HTTP 200 · 1640 ms to response headers
bonus1.9

AI guide files

+1 bonus

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

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

Evaluate: can AI agents try Eye Security's product?

We didn't find product signals (developer docs, API, app login) on eye.security, so we didn't score product access. If you sell software, an MCP server lets AI agents evaluate your product directly. That's quickly becoming a shortlist factor.

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

pass3A

Find the way in

8/8 pts

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

Evidence
https://eye.security/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://eye.security/contact/ · as browser · HTTP 200 · browser baseline 200
https://eye.security/contact/ · as ChatGPT-User · HTTP 200 · HTTP 200
https://eye.security/contact/ · as Claude-User · HTTP 200 · HTTP 200
https://eye.security/contact/ · as Perplexity-User · HTTP 200 · HTTP 200
https://eye.security/robots.txt · robots disallow /contact/ for: none
fail3C

See the form

0/12 pts

Your contact 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://eye.security/contact/ · as browser · HTTP 200 · found js-eu1.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

+1 bonus

You give agents a direct route: visible email.

Evidence
email:[email protected] 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://eye.security/case-study/keytec/ · HTTP 200 · 1249 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 Eye Security 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 (1300 words on the homepage, 1295 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 Eye Security 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 21 sitemaps in your index).
  • AI agents can find your contact page (/contact/) 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.

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.