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

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

## Results for veremark.com

**64 out of 100** · At risk

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

- **Research** (Website readability): 96% · 33.5/35 pts · 7/8 passed
- **Evaluate** (Product access): 7% · 1/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 57% · 23/40 pts · 3/5 passed

## How a buyer's AI agent experiences Veremark

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

The agent read your site and understood what you do. It found your demo page at /speak-to-our-sales-team, but the form loads with JavaScript, so it couldn't see a way to contact you. Journey ended.

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

### 03 Page essentials

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

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

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

Evidence:

- `https://www.veremark.com/ · homepage: pass (609 words) · key pages: pass (median 856 words across 5)`
- `https://www.veremark.com/ · 609 words of page content in raw HTML (875 including nav and footer)`
- `sampled pages: product /solutions/growth (648 words), customer /whistleblowing/case-studies (998 words), blog /blog/an-employers-guide-to-whistleblowing (1444 words), about /about (856 words), product /products/verepass (315 words); median words: 856`

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

**warning** · 1.5/3 pts

3 of 6 pages we checked are missing a description.

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

Evidence:

- `https://www.veremark.com/ · title:true desc:true h1:1 canonical:true`
- `https://www.veremark.com/solutions/growth · title:true desc:false h1:1 canonical:true`
- `https://www.veremark.com/whistleblowing/case-studies · title:true desc:false h1:1 canonical:true`
- `https://www.veremark.com/blog/an-employers-guide-to-whistleblowing · title:true desc:true h1:1 canonical:true`
- `https://www.veremark.com/about · title:true desc:true h1:1 canonical:true`
- `https://www.veremark.com/products/verepass · title:true desc:false h1:1 canonical:true`

### 1.6 Company identity

**pass** · 3/3 pts

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

Evidence:

- `https://www.veremark.com/ · Organization: name=Veremark 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.veremark.com/sitemap.xml · valid:true linkedFromRobots:true urls:1148 latestLastmod:2026-10-14T08:10:24.924Z`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://veremark.com/ · median 33 ms across 5 requests`
- `https://veremark.com/ · as crawler · HTTP 200 · 311 ms to response headers`
- `https://www.veremark.com/ · as browser · HTTP 200 · 33 ms to response headers`
- `https://www.veremark.com/ · as ChatGPT-User · HTTP 200 · 35 ms to response headers`
- `https://www.veremark.com/ · as Claude-User · HTTP 200 · 31 ms to response headers`
- `https://www.veremark.com/ · as Perplexity-User · HTTP 200 · 33 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.veremark.com/llms.txt · HTTP 404 · no valid llms.txt`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Veremark'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.veremark.com/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.veremark.com/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.veremark.com/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.veremark.com/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://www.veremark.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.veremark.com/ · docs link: https://www.veremark.com/products/verelink-api`
- `no OpenAPI found (api-catalog service-desc or homepage link)`

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

### 3A Find the way in

**pass** · 8/8 pts

AI agents can find your demo page (/speak-to-our-sales-team) from the homepage.

Evidence:

- `https://www.veremark.com/speak-to-our-sales-team · 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.veremark.com/speak-to-our-sales-team · as browser · HTTP 200 · browser baseline 200`
- `https://www.veremark.com/speak-to-our-sales-team · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.veremark.com/speak-to-our-sales-team · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.veremark.com/speak-to-our-sales-team · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.veremark.com/robots.txt · robots disallow /speak-to-our-sales-team for: none`

### 3C See the form

**fail** · 0/12 pts

Your demo 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://www.veremark.com/speak-to-our-sales-team · as browser · HTTP 200 · found js.hsforms.net script, no <form> element in page code`

### 3D Understand the form

**fail** · 0/5 pts

Not scored: an agent can't understand a form it can't see.

### 3F Agent-friendly route

**bonus** · +1 bonus

You give agents a direct route: ContactPoint data.

Evidence:

- `email:none contactPoint:true 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.veremark.com/whistleblowing/case-studies · HTTP 200 · 998 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 Veremark 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 (609 words on the homepage, 856 on a typical key page).
- None of your key pages are hidden from search and AI.
- Your site identifies Veremark 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 (33 ms, median of 5 requests).
- AI agents can find your demo page (/speak-to-our-sales-team) 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

### 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%2Fveremark-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":"veremark.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":"veremark.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=veremark.com&source=b2b-ai-visibility-checker)
