Free B2B AI Visibility Checker

Would an AI agent shortlist RemotePass?

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

Results for remotepass.com

83out of 100

Shortlist-ready

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

100%

Research

35/35 pts · 8/8 passed

0%

Evaluate

0/15 pts · 0/5 passed

97%

Reach out

41.5/43 pts · 5/6 passed

See what to fix first (3)

How a buyer's AI agent experiences RemotePass

Research: passedEvaluate: stuckReach out: passed

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

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

Documented

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

03

Self-serve path

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

Research: can AI agents read and understand RemotePass?

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

Evidence
https://www.remotepass.com/ · homepage: pass (1519 words) · key pages: pass (median 814 words across 3)
https://www.remotepass.com/ · 1519 words of page content in raw HTML (1972 including nav and footer)
sampled pages: customer /ar/case-studies (351 words), blog /ar/blog/uae-wps-rules-2026-mr-340 (3187 words), about /about-us (814 words); median words: 814
pass1.4

Accidentally hidden pages

4/4 pts

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

Evidence
checked homepage + 3 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.remotepass.com/ · title:true desc:true h1:1 canonical:true
https://www.remotepass.com/ar/case-studies · title:true desc:true h1:1 canonical:true
https://www.remotepass.com/ar/blog/uae-wps-rules-2026-mr-340 · title:true desc:true h1:1 canonical:true
https://www.remotepass.com/about-us · title:true desc:true h1:1 canonical:true
pass1.6

Company identity

3/3 pts

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

Evidence
https://www.remotepass.com/ · Organization: name=RemotePass url=yes logo=yes sameAs=yes
pass1.7

Sitemap

2/2 pts

Your sitemap is valid, linked and up to date (we checked 3 of the 6 sitemaps in your index).

Evidence
https://www.remotepass.com/sitemap_index.xml · valid:true linkedFromRobots:true urls:1397 latestLastmod:2026-10-14T12:41:11.000Z (sitemap index with 6 sitemaps; checked 3, 3 valid)
pass1.8

Response speed

2/2 pts

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

Evidence
https://remotepass.com/ · median 59 ms across 5 requests
https://remotepass.com/ · as crawler · HTTP 200 · 592 ms to response headers
https://www.remotepass.com/ · as browser · HTTP 200 · 41 ms to response headers
https://www.remotepass.com/ · as ChatGPT-User · HTTP 200 · 80 ms to response headers
https://www.remotepass.com/ · as Claude-User · HTTP 200 · 31 ms to response headers
https://www.remotepass.com/ · as Perplexity-User · HTTP 200 · 59 ms to response headers
bonus1.9

AI guide files

+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.remotepass.com/llms.txt · HTTP 404 · no valid llms.txt
no <link rel="alternate" type="text/markdown">

Evaluate: can AI agents try RemotePass'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.remotepass.com/.well-known/mcp.json · HTTP 404 · HTTP 404
https://www.remotepass.com/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404
https://www.remotepass.com/.well-known/ai-catalog.json · HTTP 404 · HTTP 404
https://www.remotepass.com/.well-known/api-catalog · HTTP 404 · HTTP 404
https://www.remotepass.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.

fail2.5

Documented

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.remotepass.com/ · 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 RemotePass's sales team?

pass3A

Find the way in

8/8 pts

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

Evidence
https://www.remotepass.com/demo-request · demo page found via homepage
pass3B

Let in

10/10 pts

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

Evidence
https://www.remotepass.com/demo-request · as browser · HTTP 200 · browser baseline 200
https://www.remotepass.com/demo-request · as ChatGPT-User · HTTP 200 · HTTP 200
https://www.remotepass.com/demo-request · as Claude-User · HTTP 200 · HTTP 200
https://www.remotepass.com/demo-request · as Perplexity-User · HTTP 200 · HTTP 200
https://www.remotepass.com/robots.txt · robots disallow /demo-request for: none
pass3C

See the form

12/12 pts

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

Evidence
https://www.remotepass.com/demo-request · as browser · HTTP 200 · contact form in page code with 3 fields (marketing-2, personalization-2, analytics-2)
pass3D

Understand the form

5/5 pts

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

Evidence
https://www.remotepass.com/demo-request · 3 fields, 0 unlabelled, 0 required, email type: false
bonus3F

Agent-friendly route

+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
pass3G

Readable proof

5/5 pts

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

Evidence
https://www.remotepass.com/ar/case-studies · HTTP 200 · 351 words of page content in raw HTML (nav and footer excluded)
warning3H

Self-serve path

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://app.remotepass.com/signup · as ChatGPT-User · HTTP 200 · 0 words, form: none

What RemotePass 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 (1519 words on the homepage, 814 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 RemotePass with structured data, so AI can connect the website to the brand.
  • Your sitemap is valid, linked and up to date (we checked 3 of the 6 sitemaps in your index).
  • Your homepage responds quickly (59 ms, median of 5 requests).
  • AI agents can find your demo page (/demo-request) 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 form is clearly labelled with 0 required fields. An agent can fill it for its buyer.
  • 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.