---
title: "Would AI Agents Shortlist GitGuardian? 75/100 AI Agent Readiness | VertoDigital"
description: "GitGuardian scored 75/100 (At risk) on AI agent readiness. See whether buyers' AI agents would shortlist GitGuardian: can they research it, evaluate the product and reach sales? Evidence and fixes included."
url: "https://vertodigital.com/b2b-ai-visibility-checker/tool/gitguardian-com"
image: "https://vertodigital.com/b2b-ai-visibility-checker/tool/gitguardian-com/og.png"
---

> For AI agents: an index of every page on this site is at https://vertodigital.com/llms.txt

Free B2B AI Visibility Checker

# Would an AI agent shortlist GitGuardian?

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

## Results for gitguardian.com

**75 out of 100** · At risk

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

- **Research** (Website readability): 83% · 29/35 pts · 6/8 passed
- **Evaluate** (Product access): 7% · 1/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 91% · 39/43 pts · 4/6 passed

## How a buyer's AI agent experiences GitGuardian

- Research: passed
- Evaluate: stuck
- Reach out: passed

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

## What GitGuardian 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 Page essentials

Give every key page a unique title, a one-sentence description, one main heading and a canonical URL.

### 03 Company identity

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

## Research: can AI agents read and understand GitGuardian?

### 1.1 AI search crawler access

**pass** · 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.gitguardian.com/robots.txt · HTTP 200 · blocked from /: none; blocked on key paths: none`

### 1.2 Homepage access

**pass** · 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.gitguardian.com/ · as browser · HTTP 200 · browser baseline 200`
- `https://www.gitguardian.com/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.gitguardian.com/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.gitguardian.com/ · as Perplexity-User · HTTP 200 · HTTP 200`

### 1.3 Content without JavaScript

**pass** · 7/7 pts

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

Evidence:

- `https://www.gitguardian.com/ · homepage: pass (762 words) · key pages: pass (median 1017 words across 5)`
- `https://www.gitguardian.com/ · 762 words of page content in raw HTML (924 including nav and footer)`
- `sampled pages: product /platform (1017 words), customer /legal/client-partner-prospect-privacy-notice (2742 words), blog /resources/what-to-do-if-you-expose-a-secret (116 words), about /about-us (376 words), product /solutions/git-secret (1713 words); median words: 1017`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

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

Evidence:

- `checked homepage + 5 key pages`

### 1.5 Page essentials

**fail** · 0/3 pts

6 of 6 pages we checked are missing a description / main heading / canonical.

**How to fix:** Give every key page a unique title, a one-sentence description, one main heading and a canonical URL.

Evidence:

- `https://www.gitguardian.com/ · title:true desc:true h1:1 canonical:false`
- `https://www.gitguardian.com/platform · title:true desc:true h1:1 canonical:false`
- `https://www.gitguardian.com/legal/client-partner-prospect-privacy-notice · title:true desc:false h1:2 canonical:false`
- `https://www.gitguardian.com/resources/what-to-do-if-you-expose-a-secret · title:true desc:false h1:2 canonical:false`
- `https://www.gitguardian.com/about-us · title:true desc:true h1:2 canonical:false`
- `https://www.gitguardian.com/solutions/git-secret · title:true desc:true h1:4 canonical:false`

### 1.6 Company identity

**fail** · 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.gitguardian.com/ · 0 JSON-LD blocks, no Organization with a name`

### 1.7 Sitemap

**pass** · 2/2 pts

Your sitemap is valid, linked and up to date.

Evidence:

- `https://www.gitguardian.com/sitemap.xml · valid:true linkedFromRobots:true urls:1116 latestLastmod:2026-10-15T05:08:35.679Z`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://gitguardian.com/ · median 43 ms across 5 requests`
- `https://gitguardian.com/ · as crawler · HTTP 200 · 343 ms to response headers`
- `https://www.gitguardian.com/ · as browser · HTTP 200 · 34 ms to response headers`
- `https://www.gitguardian.com/ · as ChatGPT-User · HTTP 200 · 40 ms to response headers`
- `https://www.gitguardian.com/ · as Claude-User · HTTP 200 · 43 ms to response headers`
- `https://www.gitguardian.com/ · as Perplexity-User · HTTP 200 · 49 ms to response headers`

### 1.9 AI guide files

**bonus** · +0 bonus

Opportunity: an llms.txt file and markdown page versions give AI agents a clean map of your site. Not yet confirmed as used by the major AI engines, but cheap to add.

Evidence:

- `https://www.gitguardian.com/llms.txt · HTTP 404 · no valid llms.txt`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try GitGuardian's product?

### 2.1 Discoverable

**fail** · 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.gitguardian.com/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.gitguardian.com/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.gitguardian.com/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.gitguardian.com/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://www.gitguardian.com/.well-known/oauth-protected-resource · HTTP 404 · HTTP 404`

### 2.2 Working

**fail** · 0/4 pts

There is no MCP server to test.

### 2.3 Understandable

**fail** · 0/3 pts

There is no MCP server to evaluate.

### 2.4 Connectable

**fail** · 0/2 pts

There is no MCP server to connect to.

### 2.5 Documented

**warning** · 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://www.gitguardian.com/ · docs link: https://docs.gitguardian.com/`
- `no OpenAPI found (api-catalog service-desc or homepage link)`

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

### 3A Find the way in

**pass** · 8/8 pts

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

Evidence:

- `https://www.gitguardian.com/book-a-demo · demo page found via homepage`

### 3B Let in

**pass** · 10/10 pts

Your demo page lets in requests that identify as ChatGPT, Claude and Perplexity.

Evidence:

- `https://www.gitguardian.com/book-a-demo · as browser · HTTP 200 · browser baseline 200`
- `https://www.gitguardian.com/book-a-demo · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.gitguardian.com/book-a-demo · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.gitguardian.com/book-a-demo · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.gitguardian.com/robots.txt · robots disallow /book-a-demo for: none`

### 3C See the form

**pass** · 12/12 pts

Your demo form is in the page code, so AI agents can see it.

Evidence:

- `https://www.gitguardian.com/book-a-demo · as browser · HTTP 200 · contact form in page code with 21 fields (First-Name, Last-name, Job-title, Company, developers-team, developers-team, developers-team, developers-team); ignored 1 header/footer/newsletter form(s)`

### 3D Understand the form

**warning** · 2.5/5 pts

3 fields have no label.

**How to fix:** Label every field, use the right field types (email, phone) and cut required fields to what sales really needs.

Evidence:

- `https://www.gitguardian.com/book-a-demo · 21 fields, 3 unlabelled, 7 required, email type: true`

### 3F Agent-friendly route

**bonus** · +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`

### 3G Readable proof

**pass** · 5/5 pts

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

Evidence:

- `https://www.gitguardian.com/legal/client-partner-prospect-privacy-notice · HTTP 200 · 2742 words of page content in raw HTML (nav and footer excluded)`

### 3H Self-serve path

**warning** · 1.5/3 pts

Your sign-up page loads only with JavaScript.

**How to fix:** Make the sign-up page reachable and readable without JavaScript.

Evidence:

- `https://dashboard.gitguardian.com/auth/signup · as ChatGPT-User · HTTP 200 · 0 words, form: none`

## What GitGuardian 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 (762 words on the homepage, 1017 on a typical key page).
- None of your key pages are hidden from search and AI.
- Your sitemap is valid, linked and up to date.
- Your homepage responds quickly (43 ms, median of 5 requests).
- AI agents can find your demo page (/book-a-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 case studies are readable text, so agents can use them as proof.

## Next steps

### Share with your team

Send the report to your web team, or post your score on LinkedIn.

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fvertodigital.com%2Fb2b-ai-visibility-checker%2Ftool%2Fgitguardian-com)

### Compare with a competitor

Agents can start one through the API: `POST https://vertodigital.com/agent/readiness/checks` with `{"domain":"competitor.com","mode":"compare","compare_with":"gitguardian.com"}`.

Comparisons are private. Only people with the link can see them.

### Fixed something?

Agents can rescan through the API: `POST https://vertodigital.com/agent/readiness/checks` with `{"domain":"gitguardian.com"}`.

[How we checked](https://vertodigital.com/b2b-ai-visibility-checker/tool/how-it-works)

[Is this your company? Request an update or removal](https://vertodigital.com/b2b-ai-visibility-checker/tool/request-update)

## 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.

[Book your Pipeline Readiness Assessment](https://vertodigital.com/assessment?domain=gitguardian.com&source=b2b-ai-visibility-checker)
