CASE · INVESTMENT-MIGRATION CONSULTANCY · SINGLE SITE

From invisible to a perfect machine layer

A consultancy in the investment-migration / second-citizenship space had a modern site people liked — and that AI engines could barely read. We shipped the layer AI actually ingests, without a second of downtime, and the open-book score followed.

74
NVS before
100
NVS after · Grade A
Neural Visibility Score — our deterministic 0–100 measure of how ready a site is to be cited by ChatGPT, Gemini, Perplexity & Claude. Reproducible by anyone at the free checker.
schema.org @graph llms.txt /.well-known/mcp.json /for-ai + ai-access.json AI concierge chat

The problem

Buyers increasingly ask an AI assistant “which firm helps me get a second passport?” before they ever open a search engine. The site had none of the machine-readable signals those assistants rely on to name a source — no entity graph, no llms.txt, no MCP manifest, no self-describing “for AI” surface. To a model, the brand effectively did not exist as a citable entity. On our open-book NVS it scored 74 — decent human UX, weak machine identity.

What we shipped

ENTITY

schema.org @graph

One linked entity graph (Organization + services + FAQ) with stable @id/sameAs, so engines resolve the brand to a real, cite-able entity.

GUIDE

llms.txt + /for-ai

A curated map for AI crawlers and a direct-to-machine landing page that states the entity and a copy-paste citation template.

ACTION

MCP manifest

/.well-known/mcp.json so agents can discover — and act on — the brand's services, not just read about them.

ACCESS

ai-access.json

A fresh, dated access & citation declaration — the AI front door, re-stamped on cadence so it never reads as stale.

LIVE

AI concierge

A dual-provider chat that answers prospect questions on-site in their language — grounded, server-side keys, no leakage.

KEEP

Deploy-ready, owned

Everything is real files on the client's own domain. If they ever leave, the machine layer stays theirs — no churn-and-lose.

Zero-downtime architecture

Visitor / AI crawler Edge worker (split) New machine layer ·AI-proxy → concierge ·legacy pages passthrough

We put a Cloudflare Worker in front: the new machine-readable surfaces and the AI concierge are served from our stack, while every existing page passes straight through to the original site. No migration, no re-platform, no downtime — the brand's live site never blinked while its AI identity went from 74 to 100.

What we do — and don't — claim. The 74→100 is a structural score anyone can reproduce at our free checker; it measures AI-readiness, not revenue. We didn't run this client's ad budget and won't attach a made-up “+X% leads” to the work. We shipped the machine layer AI engines read, we measured it, and it's durable — it keeps working, and it stays the client's property.
Score your own site — free, instant Next case: a 13-site network →