Skip to main content

Case study · AI search (GEO) · Agent integrations · SEO

Made Verdacert findable in AI answers on a Domain Rating of 4 - AI assistants out-sent organic search 2.8× in October

GEO / AI searchAgent integrations (MCP + API)SEOMultilingual contentAnalytics & attributionWeb development
ClientVerdacert
IndustryLegal & immigration services (certified translation)
EngagementMay 2026 – Nov 2026 · 6 months, ongoing
AI vs. organic search, October
2.8×

1,811 vs. 638 sessions (GA4) · Ahrefs Domain Rating: 4

Visits from AI assistants
3,236

GA4, launch - Nov 6, 2026 · headless-scraper traffic excluded

Checkout rate per visit, AI vs. search
~8×

30 checkout events from 194 AI visits vs. 8 from 436 search visits · Oct 4 - Nov 6, 2026

Verdacert - verdacert.com
Certified translation from 103 languages, built for assistants and agents: llms.txt, machine-readable pricing, and an MCP server on the official registry
Verdacert - verdacert.com
FIG 01

Verdacert certifies document translations for USCIS, US courts and universities - 103 source languages, native-speaker review on every document, and a signed certificate anyone can verify. It launched in May 2026 on a domain with almost no authority (Ahrefs Domain Rating: 4), so ranking in Google was always going to be slow. Higglo built it to be legible to AI assistants and AI agents from its first weeks. By October, AI assistants were sending 2.8× as many visits as organic search, and AI-referred buyers were reaching checkout at about 8× the per-visit rate.

The brief

Verdacert's buyers are immigrants, paralegals and law firms with a USCIS, court or university deadline - and a growing share of them start by asking an AI assistant where to get a certified translation. Each order ships a signed certification statement and a public verification URL backed by a cryptographically signed receipt, so the product is built to be checked by machines as well as people.

It launched in May 2026 on a domain with almost no authority. As of November 2026, Ahrefs rates it a Domain Rating of 4. The brief was to make Verdacert legible to AI assistants and AI agents from launch week, so it could be found in the answers people actually read, and to measure that on checkouts.

The results

  • AI assistants sent 2.8× organic search's visits in October 2026 (1,811 vs. 638), and have out-sent search every week since September 7.
  • 3,236 visits from AI assistants since launch, through November 6, 2026, with headless-scraper traffic excluded.
  • AI-referred buyers convert far better. Since checkout tracking began on October 4, AI visitors to customer pages triggered 30 checkout events from 194 visits; organic search, 8 from 436 - about 8× the per-visit rate.
  • AI became the recruiting channel. 2,515 visits to translator job pages came from AI assistants - 8.6× organic search - for reviewer roles in languages like Rohingya, Somali, Oromo and Dari.

Who the AI visitors are

Not every AI visit is a buyer, and the case study is more useful if we say so. Most of Verdacert's AI traffic lands on reviewer job pages: people looking for certified-translation work. That is real value for a service that needs native speakers of rare languages, but it isn't revenue. On customer pages, organic search still sends more visits than AI assistants. What AI sends instead is intent: people who asked a specific question - questions like how to get a birth certificate translated for USCIS, or what a certified Farsi translation costs - and arrive ready to order.

What we built for assistants and agents

  • An llms.txt that answers the buying questions. Following the llmstxt.org spec, Verdacert's llms.txt carries every price tier, turnaround time, guarantee and source language, with Markdown twins of key pages, so an assistant quotes Verdacert accurately instead of guessing.
  • Explicit AI-crawler access. robots.txt names and admits GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended and Applebot-Extended.
  • Machine-readable pricing. Organization, ProfessionalService, Service and Offer schema with unit-price specifications, and every advertised price rendered from the live pricing engine - one source of truth for pages, snippets and assistants.
  • Agent-ready from day ten. An MCP server with 8 tools (quote, submit, track, retrieve, refund, case packets and certificate verification), listed on the official MCP Registry, with a /.well-known/mcp.json manifest, a REST API and OpenAPI spec, and free sandbox keys - so an AI agent can order and verify a certified translation without a human in the browser.
  • Multilingual programmatic pages. 30,666 indexable URLs across seven site languages - English, Arabic, Farsi, Urdu, Turkish, Spanish and Haitian Creole - covering document types, language-by-document pages and guides.
  • A page for every role. Each reviewer opening has its own indexable job page with JobPosting schema, which is what turned AI assistants into Verdacert's recruiting channel.

What we learned

  • Low authority didn't block AI visibility. On a Domain Rating of 4, AI assistants were sending 2.8× organic search's traffic within five months of launch.
  • Clean data beats big data. A headless scraper was 92% of GA4 users in September-October 2026 until it was filtered out. Without that filter, every channel comparison here would have been wrong.
  • Measure AI on the outcome you sell. Visit counts would have overstated buyer demand from AI; checkout events show where AI is actually worth the most.

The same playbook drives LandEarly, where AI assistants send 2.4× organic search's visits and convert 2.4× better, and Raven Health, cited by all six major assistants.

Methodology

Traffic and conversion figures are from Verdacert's Google Analytics 4 property, pulled November 7, 2026, using GA4's default "AI Assistant" and "Organic Search" channel groups, with sessions at a 1366×1366 screen resolution (a headless scraper) excluded. Customer pages exclude careers, reviewer sign-up, sign-in and account pages in every site language. Checkout comparisons start October 4, 2026, the first day key events were recorded; "checkout events" are begin_checkout and purchase key events. Some purchases are recorded server-side without a channel, so AI-attributed purchases are a floor. Domain Rating is from Ahrefs; page counts are from verdacert.com's live sitemaps; the MCP listing is on registry.modelcontextprotocol.io.

Six workstreams, one delivery cadence.

WS.01

AI-crawler access & llms.txt

An llms.txt that follows the llmstxt.org spec and carries what an assistant needs to answer accurately - every price tier, turnaround, guarantee and source language - with Markdown twins of key pages. robots.txt explicitly admits GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended and Applebot-Extended.

3,236AI visits
WS.02

Machine-readable pricing

Organization, ProfessionalService, Service and Offer schema with UnitPriceSpecification, every advertised price rendered from the live pricing engine, and one consolidated entity across the site - so assistants quote the current price, not a stale one.

WS.03

Agent-ready

An MCP server with 8 tools (capabilities, quote, submit, status, result, refund, case packet, certificate verification) listed on the official MCP Registry, a /.well-known/mcp.json manifest, a public REST API with an OpenAPI spec, free sandbox keys and developer docs.

8MCP tools
WS.04

Multilingual content

30,666 indexable URLs across 7 site languages (English, Arabic, Farsi, Urdu, Turkish, Spanish, Haitian Creole): document-type pages, language-by-document pages, and guides such as translating an Iranian shenasnameh.

30,666indexable URLs
WS.05

AI-sourced recruiting

Every reviewer opening got its own indexable job page with JobPosting schema in September 2026. AI assistants now send 8.6× organic search's traffic to those pages - the supply side of a service that needs native speakers of rare languages.

2,515recruiting visits
WS.06

Measurement

AI assistants classified as their own channel in GA4 and in first-party analytics that join each visit to its order, with headless-browser traffic filtered out (a square-screen scraper had been 92% of GA4 users in Sept-Oct 2026).

~8×checkout rate vs. search

What we built, feature by feature.

Feature
Before
After
AI-assistant visits / month
10 (June 2026)
1,811 (October 2026)
AI vs. organic search
June: 10 vs. 40
October: 1,811 vs. 638
Checkout events per visit
Not tracked
AI ~8× organic search
llms.txt
None (May 12 launch)
Full pricing, turnaround, guarantees, 103 languages
Agent access
None
MCP server on the official registry + REST API
Site languages
English, Arabic, Farsi
7, with 30,666 indexable URLs
Translator recruiting
No per-role pages
Indexable page per role; 2,515 AI visits

Engagement timeline

How the work unfolded, week by week.

May 12, 2026

Launch

MVP live with per-page SEO metadata, an expanded sitemap, and Arabic and Farsi right-to-left home pages.

Deliverable · Site + RTL locales
May 21 - 22

GEO & agent foundation

Business vertical pages, llms.txt, a JSON-LD sweep across marketing pages, the MCP manifest and developer docs.

Deliverable · llms.txt + MCP
May 24 - 29

Pricing for retrieval

Per-tier pricing surfaced for AI retrieval and search snippets; MCP and API surfaced to AI crawlers.

Deliverable · Machine-readable pricing
Jun 3 - 4

Index hygiene

IndexNow and Bing verification, one canonical host, and a single Organization entity across the site.

Deliverable · Canonical + IndexNow
Aug 19

One source of truth for prices

Every advertised price rendered from the pricing engine; llms.txt and Markdown twins made discoverable to AI crawlers.

Deliverable · Price parity everywhere
Sep 14

Recruiting pages

Every reviewer opening gets its own indexable job page with JobPosting schema.

Deliverable · Per-role job pages
Oct 2026

AI out-sends search

1,811 AI-assistant visits in October - 2.8× organic search - with checkout tracking live from October 4.

Deliverable · 2.8× organic search

Results

AI assistants have out-sent organic search every week since September 7

Weekly GA4 sessions from AI assistants, weeks of Aug 10 - Oct 26, 2026, with headless-scraper traffic excluded. Organic search sent 14-174 sessions a week over the same span. AI traffic includes translator-recruiting pages; on customer pages alone, organic search still sends more visits, but AI-referred visitors reach checkout at about 8× the per-visit rate.

7505002500Aug 10Aug 17Aug 24Aug 31Sep 7Sep 14Sep 21Sep 28Oct 5Oct 12Oct 19Oct 264.1× search

Weekly sessions from AI assistants (GA4, headless-scraper traffic excluded)

Weekly GA4 sessions from AI assistants, weeks of Aug 10 - Oct 26, 2026, with headless-scraper traffic excluded. Organic search sent 14-174 sessions a week over the same span. AI traffic includes translator-recruiting pages; on customer pages alone, organic search still sends more visits, but AI-referred visitors reach checkout at about 8× the per-visit rate.

AI-assistant sessionsOrganic search sessions

Next step

Want a strategy built around your market?

Higglo can map the technical blockers, entity gaps, and conversion friction holding back your organic growth - and ship the system that removes them.

What a kickoff looks like
Week 01Audit & shadow
Week 02Architecture plan
Week 03+Weekly shipping cadence

Get a free growth plan for your centers

Step 1 of 4

What best describes you?

Rather talk first?Book a 30-minute call