Free B2B AI Visibility Checker

Would an AI agent shortlist Slash?

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

Results for slash.com

79out of 100

At risk

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

97%

Research

34/35 pts · 7/8 passed

7%

Evaluate

1/15 pts · 0/5 passed

81%

Reach out

13/16 pts · 2/3 passed

See what to fix first (3)

How a buyer's AI agent experiences Slash

Research: passedEvaluate: stuckReach out: passed

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

What Slash 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

Self-serve path

Make the sign-up page reachable and readable without JavaScript.

03

Sitemap

Fix or remove the broken sitemap files listed in your sitemap index.

Research: can AI agents read and understand Slash?

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

Content without JavaScript

7/7 pts

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

Evidence
https://www.slash.com/ · homepage: pass (971 words) · key pages: pass (median 468 words across 5)
https://www.slash.com/ · 971 words of page content in raw HTML (1615 including nav and footer)
sampled pages: product /products (244 words), customer /customers/slash-x-bland-ai (700 words), blog /blog/series-c (1091 words), about /company/about (468 words), product /platform (213 words); median words: 468
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://www.slash.com/ · title:true desc:true h1:1 canonical:true
https://www.slash.com/products · title:true desc:true h1:1 canonical:true
https://www.slash.com/customers/slash-x-bland-ai · title:true desc:true h1:1 canonical:true
https://www.slash.com/blog/series-c · title:true desc:true h1:1 canonical:true
https://www.slash.com/company/about · title:true desc:true h1:1 canonical:true
https://www.slash.com/platform · title:true desc:true h1:1 canonical:true
pass1.6

Company identity

3/3 pts

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

Evidence
https://www.slash.com/ · Organization: name=Slash url=yes logo=yes sameAs=yes
warning1.7

Sitemap

1/2 pts

1 of the 3 sitemaps we checked is broken or empty.

How to fix: Fix or remove the broken sitemap files listed in your sitemap index.

Evidence
https://www.slash.com/sitemap.xml · valid:true linkedFromRobots:true urls:114 latestLastmod:2026-10-14T00:00:00.000Z (sitemap index with 21 sitemaps; checked 3, 2 valid, broken: https://www.slash.com/sitemap/single-pages.xml)
pass1.8

Response speed

2/2 pts

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

Evidence
https://slash.com/ · median 315 ms across 5 requests
https://slash.com/ · as crawler · HTTP 200 · 424 ms to response headers
https://www.slash.com/ · as browser · HTTP 200 · 348 ms to response headers
https://www.slash.com/ · as ChatGPT-User · HTTP 200 · 304 ms to response headers
https://www.slash.com/ · as Claude-User · HTTP 200 · 315 ms to response headers
https://www.slash.com/ · as Perplexity-User · HTTP 200 · 254 ms to response headers
bonus1.9

AI guide files

+1 bonus

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

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

Evaluate: can AI agents try Slash's product?

fail2.1

Discoverable

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

Working

0/4 pts

There is no MCP server to test.

fail2.3

Understandable

0/3 pts

There is no MCP server to evaluate.

fail2.4

Connectable

0/2 pts

There is no MCP server to connect to.

warning2.5

Documented

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

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

pass3A

Find the way in

8/8 pts

AI agents can find your trial page (/register?theme=light) from the homepage.

Evidence
https://app.slash.com/register?theme=light · trial page found via homepage
inconclusive3B

Let in

not scored

We could not compare agent and browser access to your conversion page.

Evidence
https://app.slash.com/register?theme=light · as browser · HTTP 429 · browser baseline 429
https://app.slash.com/register?theme=light · as ChatGPT-User · HTTP 429 · HTTP 429
https://app.slash.com/register?theme=light · as Claude-User · HTTP 429 · HTTP 429
https://app.slash.com/register?theme=light · as Perplexity-User · HTTP 429 · HTTP 429
https://www.slash.com/robots.txt · robots disallow /register?theme=light for: none
inconclusive3C

See the form

not scored

We could not read your conversion page.

Evidence
https://app.slash.com/register?theme=light · HTTP 429
inconclusive3D

Understand the form

not scored

Not scored: we could not read the conversion page.

bonus3F

Agent-friendly route

+2 bonus

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

Evidence
email:none contactPoint:true llms.txt contact:true 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://www.slash.com/customers/slash-x-bland-ai · HTTP 200 · 700 words of page content in raw HTML (nav and footer excluded)
fail3H

Self-serve path

0/3 pts

Your sign-up page blocked our agent request.

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

Evidence
https://app.slash.com/register?theme=light · as ChatGPT-User · HTTP 429 · 0 words, form: n/a

What Slash 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 (971 words on the homepage, 468 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 Slash with structured data, so AI can connect the website to the brand.
  • Your homepage responds quickly (315 ms, median of 5 requests).
  • AI agents can find your trial page (/register?theme=light) from the homepage.
  • 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.