mysterytrip.co

Last audited Jun 12, 2026 · Good · Visit site ↗

As of Jun 12, 2026, AI agents read mysterytrip.co at Good readiness (66/100). The AI-visibility lens (ChatGPT/Claude/Gemini mentions) hasn't been seeded yet for this domain.

66
/ 100
Agent Readiness
In progress
queued
AI Visibility

Agent Readiness

Discoverability

80/100

Can AI crawlers find your content and understand your policies?

  • robots.txt present
    HTTP 200
  • sitemap.xml present
    HTTP 200
  • Sitemap declared in robots.txt
  • !
    AI bot rules in robots.txt
    No explicit rules for GPTBot / ClaudeBot / Google-Extended
    How to fix

    Add `User-agent: GPTBot`, `User-agent: ClaudeBot`, `User-agent: Google-Extended` blocks with explicit Allow/Disallow so AI crawlers know your stance.

  • !
    Content Signals declared
    No Cloudflare Content-Signal directive
    How to fix

    Add `Content-Signal: search=yes, ai-train=no, ai-input=yes` (tune the values to your policy) inside a User-agent group in robots.txt.

Agent Endpoints

0/100

Standard well-known endpoints agents probe to interact with your site.

  • MCP server card (/.well-known/mcp/server-card.json)
    Publish an MCP server card to expose agent tools
    How to fix

    Publish an MCP server-card JSON at /.well-known/mcp/server-card.json describing your tools, transport, and capabilities. Spec: SEP-1649/SEP-2127.

  • API catalog (/.well-known/api-catalog)
    RFC 9727 API catalog helps agents discover your APIs
    How to fix

    Serve a `application/linkset+json` document at /.well-known/api-catalog listing your OpenAPI / service descriptions. RFC 9727.

  • OAuth protected resource (/.well-known/oauth-protected-resource)
    RFC 9728 lets agents discover auth requirements
    How to fix

    Publish a JSON document at /.well-known/oauth-protected-resource with `resource` and `authorization_servers` fields. RFC 9728.

  • OpenID configuration (/.well-known/openid-configuration)
    Helpful if your site offers identity / sign-in for agents
    How to fix

    If your product supports sign-in, expose OpenID Connect discovery at /.well-known/openid-configuration so agents can authenticate users on their behalf.

Content Negotiation

83/100

How well your site speaks formats AI agents prefer.

  • llms.txt present
    HTTP 200
  • !
    Markdown content negotiation
    Returned text/html; charset=utf-8 despite Accept: text/markdown
    How to fix

    When `Accept: text/markdown` is sent, return the same content as Markdown (Content-Type: text/markdown). Agents prefer it because it's cheaper to parse than HTML.

  • Link header on /
    <https://mysterytrip.co/wp-json/>; rel="https://api.w.org/", <https://mysterytrip.co/wp-json/wp/v2/pages/84>; rel="alter

Search Optimization

100/100

HTML signals that Google AI Search + LLM crawlers use to rank you.

  • Homepage reachable
    HTTP 200
  • HTTPS
  • Title tag
    Mystery Trip | Corporate Team Bonding Events
  • Meta description
    4.8★ rated custom team bonding events since 2009. Trusted by Google, Meta, Netflix. Transf…
  • Canonical URL
  • Open Graph tags
    title, description, image
  • Schema.org structured data
    WebPage, FAQPage
  • Mobile viewport
  • html lang attribute
  • Image alt text
    297/297 images have alt

Auth Standards optional

0/100

Optional: cryptographic verification for trusted bots.

  • Web Bot Auth directory
    Publish /.well-known/http-message-signatures-directory to verify trusted bots
    How to fix

    If you operate a bot, publish your signing keys at /.well-known/http-message-signatures-directory per draft-meunier-web-bot-auth-architecture. Most non-bot sites can leave this missing.

AI Visibility

In progress

Querying ChatGPT, Claude & Gemini for mysterytrip.co

This part of the audit runs offline because it calls each model. We'll ping you the moment results land — drop your email below.

Recently audited

Get notified when we re-audit mysterytrip.co

We'll ping you with fresh AI visibility + readiness data.