---
title: "Would AI Agents Shortlist Corgi? 86/100 AI Agent Readiness | VertoDigital"
description: "Corgi scored 86/100 (Shortlist-ready) on AI agent readiness. See whether buyers' AI agents would shortlist Corgi: can they research it, evaluate the product and reach sales? Evidence and fixes included."
url: "https://vertodigital.com/b2b-ai-visibility-checker/tool/corgi-insure"
image: "https://vertodigital.com/b2b-ai-visibility-checker/tool/corgi-insure/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 Corgi?

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

## Results for corgi.insure

**86 out of 100** · Shortlist-ready

AI agents can research Corgi, evaluate the product and get buyers to the sales team.

- **Research** (Website readability): 100% · 35/35 pts · 8/8 passed
- **Evaluate** (Product access): 0% · 0/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 94% · 37.5/40 pts · 4/5 passed

## How a buyer's AI agent experiences Corgi

- 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 Corgi 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 Understand the form

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

### 03 Documented

Link developer docs from the homepage and publish your OpenAPI spec at a discoverable URL.

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

### 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.corgi.insure/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.corgi.insure/ · as browser · HTTP 200 · browser baseline 200`
- `https://www.corgi.insure/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.corgi.insure/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.corgi.insure/ · 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 (2596 words on the homepage, 487 on a typical key page).

Evidence:

- `https://www.corgi.insure/ · homepage: pass (2596 words) · key pages: pass (median 487 words across 4)`
- `https://www.corgi.insure/ · 2596 words of page content in raw HTML (3309 including nav and footer)`
- `sampled pages: product /blog/platform-provides-same-day-tech-e-and-o-and-ai-liability-coverage-for-llm-powered-products (1536 words), customer /customers/intryc (487 words), blog /blog/the-fastest-underwriting-path-for-startup-insurance (1722 words), about /about (443 words); median words: 487`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

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

Evidence:

- `checked homepage + 4 key pages`

### 1.5 Page essentials

**pass** · 3/3 pts

Your pages clearly state what they are: titles, descriptions and headings are in place.

Evidence:

- `https://www.corgi.insure/ · title:true desc:true h1:1 canonical:true`
- `https://www.corgi.insure/blog/platform-provides-same-day-tech-e-and-o-and-ai-liability-coverage-for-llm-powered-products · title:true desc:true h1:1 canonical:true`
- `https://www.corgi.insure/customers/intryc · title:true desc:true h1:1 canonical:true`
- `https://www.corgi.insure/blog/the-fastest-underwriting-path-for-startup-insurance · title:true desc:true h1:1 canonical:true`
- `https://www.corgi.insure/about · title:true desc:true h1:1 canonical:true`

### 1.6 Company identity

**pass** · 3/3 pts

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

Evidence:

- `https://www.corgi.insure/ · Organization: name=Corgi Insurance url=yes logo=yes sameAs=yes`

### 1.7 Sitemap

**pass** · 2/2 pts

Your sitemap is valid, linked and up to date.

Evidence:

- `https://www.corgi.insure/sitemap.xml · valid:true linkedFromRobots:true urls:104 latestLastmod:2026-10-01T00:00:00.000Z`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://corgi.insure/ · median 74 ms across 5 requests`
- `https://corgi.insure/ · as crawler · HTTP 200 · 449 ms to response headers`
- `https://www.corgi.insure/ · as browser · HTTP 200 · 56 ms to response headers`
- `https://www.corgi.insure/ · as ChatGPT-User · HTTP 200 · 89 ms to response headers`
- `https://www.corgi.insure/ · as Claude-User · HTTP 200 · 56 ms to response headers`
- `https://www.corgi.insure/ · as Perplexity-User · HTTP 200 · 74 ms to response headers`

### 1.9 AI guide files

**bonus** · +1 bonus

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

Evidence:

- `https://www.corgi.insure/llms.txt · HTTP 200 · valid llms.txt (markdown, starts with # heading)`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Corgi'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.corgi.insure/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.corgi.insure/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.corgi.insure/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.corgi.insure/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://www.corgi.insure/.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

**fail** · 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://www.corgi.insure/ · 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 Corgi'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.corgi.insure/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.corgi.insure/book-a-demo · as browser · HTTP 200 · browser baseline 200`
- `https://www.corgi.insure/book-a-demo · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.corgi.insure/book-a-demo · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.corgi.insure/book-a-demo · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.corgi.insure/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.corgi.insure/book-a-demo · as browser · HTTP 200 · contact form in page code with 5 fields (fullName, workEmail, companyName, preparationNotes, website)`

### 3D Understand the form

**warning** · 2.5/5 pts

1 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.corgi.insure/book-a-demo · 5 fields, 1 unlabelled, 3 required, email type: true`

### 3F Agent-friendly route

**bonus** · +3 bonus

You give agents a direct route: visible email, ContactPoint data, contact API.

Evidence:

- `email:hello@corgi.insure contactPoint:true llms.txt contact:true 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.corgi.insure/customers/intryc · HTTP 200 · 487 words of page content in raw HTML (nav and footer excluded)`

### 3H Self-serve path

**N/A** · not scored

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

## What Corgi 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 (2596 words on the homepage, 487 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 Corgi Insurance with structured data, so AI can connect the website to the brand.
- Your sitemap is valid, linked and up to date.
- Your homepage responds quickly (74 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%2Fcorgi-insure)

### 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":"corgi.insure"}`.

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":"corgi.insure"}`.

[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=corgi.insure&source=b2b-ai-visibility-checker)
