Sites/yapglobal.com

yapglobal.com

YAP Global is a financial and technology PR consultancy that advises companies in the digital assets, fintech, and AI sectors.

marketingpublic-relationscrisis-communicationevent-managementmedia-training
37
AI-Readiness / 100
Level 2 · Basic Presence
248/248
Pages analyzed
2/15
Questions answered
Live
For AI agents

Content

AI-judged Q&A · 70% of score

34

2 of 15 buyer questions answered cleanly

Your site doesn't cover:

eventscontentservices
See all 13 gaps

Protocol

Technical hygiene · 30% of score

45

5 of 11 items installed

Missing:

llms.txt +3MCP card +3WebMCP +3
Install with Lattis · +9 pts

Protocol fix list

6 to ship · 5 passing

Start here

install llms.txt

Machine-readable index that routes AI agents to the pages you want them to read. We generate one for you — install at your root.

+3 pts

One-click installs

We host the heavy lifting — you ship one file or one line.

MCP server card

One JSON file at /.well-known/mcp/server-card.json tells agents you have an MCP server. Ours points at mcp.lattis.dev so Lattis handles queries for you.

+3 pts
Download server-card.json

Host at yapglobal.com/.well-known/mcp/server-card.json — points agents at Lattis as your MCP server.

WebMCP

Paste the widget script — that is the W3C WebMCP draft (navigator.modelContext) and the actual integration. Then also host the discovery manifest so crawlers can find your tool surface without rendering JS. Do both; the script is the spec, the manifest is just discoverability.

+3 pts

1. Runtime — paste in <head>

<script async src="https://lattis.dev/widget.js"></script>

Calls navigator.modelContext.provideContext() — the W3C WebMCP draft. Agents on the page see your tools live, scoped to yapglobal.com.

2. Discovery — host the manifest

Download webmcp.json

Host at yapglobal.com/.well-known/webmcp.json. The WebMCP spec defines no discovery mechanism, so crawlers can't see runtime registrations — this manifest closes that gap.

Paste into robots.txt

Static snippets that tell agents your policy.

Content-Signal policy

Cloudflare-launched (Sep 2025) signal in robots.txt. Declare your stance on search, ai-input, and ai-train.

+3 pts
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /

Add to yapglobal.com/robots.txt. Adjust values: search, ai-input, ai-train each accept yes or no.

Platform-level

Requires config or code on your side. Docs linked where useful.

Markdown content negotiation

Respond to Accept: text/markdown with plain markdown — agents pay ~80% fewer tokens. If you're on Cloudflare, it's a zone toggle.

+3 pts

Zone-level toggle if you're on Cloudflare. Non-CF: implement server-side content negotiation on Accept: text/markdown.

Cloudflare: Markdown for Agents

OpenAPI spec

No OpenAPI discoverable at standard paths (/openapi.json, /api-docs, etc.). If you have an API, publish the spec.

+3 pts

Publish at a standard path (/openapi.json) and link from your docs. Agents will discover it automatically.

OpenAPI Initiative

Already passing

robots.txtsitemap.xmlAllow major AI crawlersClean crawl rateServer-rendered content

Content gaps

13 gaps

Also covered by yapglobal.com

strategyoperations

MCP Server

AI agents can query this site directly via MCP. Add this endpoint to Claude Code, Cursor, or any MCP client.

Endpoint

https://mcp.lattis.dev/s/yapglobal-com/mcp

Claude Code

claude mcp add yapglobal --transport http https://mcp.lattis.dev/s/yapglobal-com/mcp

Cursor

{
  "mcpServers": {
    "yapglobal": {
      "url": "https://mcp.lattis.dev/s/yapglobal-com/mcp"
    }
  }
}

WebMCP — runtime + discovery

1. Widget script — drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script — that's the W3C draft and the actual integration agents care about.

<script async src="https://lattis.dev/widget.js"></script>

Renders a small "AI-indexed by Lattis" badge bottom-right. Hide with [data-lattis] { display: none !important; }.

2. Discovery manifest — host alongside the script. The WebMCP spec defines no discovery mechanism, so crawlers can't see the runtime registration. This static JSON closes the gap.

Download webmcp.json

Host at yapglobal.com/.well-known/webmcp.json.