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

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

## Results for dwelly.group

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

AI agents can research Dwelly, 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): 88% · 35/40 pts · 4/5 passed

## How a buyer's AI agent experiences Dwelly

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

The agent read your site and understood what you do. It found your contact page at /contact?site=provider and could see how to reach your sales team.

## What Dwelly should fix first to make the shortlist

### 01 Readable proof

Publish customer proof as readable pages. Agents compare vendors on evidence.

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

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

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

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

Evidence:

- `https://www.dwelly.group/ · homepage: pass (402 words) · key pages: pass (median 426 words across 3)`
- `https://www.dwelly.group/ · 402 words of page content in raw HTML (477 including nav and footer)`
- `sampled pages: product /platform (600 words), blog /blog/london-ai-hackathon (331 words), about /about (426 words); median words: 426`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

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

Evidence:

- `checked homepage + 3 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.dwelly.group/ · title:true desc:true h1:1 canonical:true`
- `https://www.dwelly.group/platform · title:true desc:true h1:1 canonical:true`
- `https://www.dwelly.group/blog/london-ai-hackathon · title:true desc:true h1:1 canonical:true`
- `https://www.dwelly.group/about · title:true desc:true h1:1 canonical:true`

### 1.6 Company identity

**pass** · 3/3 pts

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

Evidence:

- `https://www.dwelly.group/ · Organization: name=Dwelly 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.dwelly.group/sitemap.xml · valid:true linkedFromRobots:true urls:11 latestLastmod:2026-09-11T00:00:00.000Z`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://dwelly.group/ · median 304 ms across 5 requests`
- `https://dwelly.group/ · as crawler · HTTP 200 · 652 ms to response headers`
- `https://www.dwelly.group/ · as browser · HTTP 200 · 262 ms to response headers`
- `https://www.dwelly.group/ · as ChatGPT-User · HTTP 200 · 292 ms to response headers`
- `https://www.dwelly.group/ · as Claude-User · HTTP 200 · 304 ms to response headers`
- `https://www.dwelly.group/ · as Perplexity-User · HTTP 200 · 320 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.dwelly.group/llms.txt · HTTP 404 · no valid llms.txt`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Dwelly'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.dwelly.group/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.dwelly.group/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.dwelly.group/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.dwelly.group/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://www.dwelly.group/.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.dwelly.group/ · 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 Dwelly's sales team?

### 3A Find the way in

**pass** · 8/8 pts

AI agents can find your contact page (/contact?site=provider) from the homepage.

Evidence:

- `https://www.dwelly.group/contact?site=provider · contact page found via homepage`

### 3B Let in

**pass** · 10/10 pts

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

Evidence:

- `https://www.dwelly.group/contact?site=provider · as browser · HTTP 200 · browser baseline 200`
- `https://www.dwelly.group/contact?site=provider · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.dwelly.group/contact?site=provider · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.dwelly.group/contact?site=provider · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.dwelly.group/robots.txt · robots disallow /contact?site=provider for: none`

### 3C See the form

**pass** · 12/12 pts

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

Evidence:

- `https://www.dwelly.group/contact?site=provider · as browser · HTTP 200 · contact form in page code with 5 fields (text, text, email, tel, textarea)`

### 3D Understand the form

**pass** · 5/5 pts

Your form is clearly labelled with 3 required fields. An agent can fill it for its buyer.

Evidence:

- `https://www.dwelly.group/contact?site=provider · 5 fields, 0 unlabelled, 3 required, email type: true`

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

**fail** · 0/5 pts

We couldn't find customer stories or case studies.

**How to fix:** Publish customer proof as readable pages. Agents compare vendors on evidence.

Evidence:

- `no customers / case-studies link on homepage, sitemap or key pages`

### 3H Self-serve path

**N/A** · not scored

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

## What Dwelly 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 (402 words on the homepage, 426 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 Dwelly 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 (304 ms, median of 5 requests).
- AI agents can find your contact page (/contact?site=provider) from the homepage.
- Your contact page lets in requests that identify as ChatGPT, Claude and Perplexity.
- Your contact form is in the page code, so AI agents can see it.
- Your form is clearly labelled with 3 required fields. An agent can fill it for its buyer.

## 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%2Fdwelly-group)

### 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":"dwelly.group"}`.

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":"dwelly.group"}`.

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