Be found by search and by AI.

People ask search engines and AI assistants before they visit your site. Birkly lets you decide what all of them see, from page titles to verified claims about your business.

{from 'birkly' get 'discovery'}

One place for how your site is found.

The Discovery area in the admin has three independent packs. Each one has its own switch; turning one off stops its public output and keeps your settings.

Pack 1 · for search engines

SEO

Titles, descriptions and social previews for every page and every collection detail URL, in one site URL map.

Google, Bing, social networks

Pack 2 · for chat AIs

Agent Guide

A structured, versioned account of who you are, what you offer and what you claim, with sources to check.

ChatGPT, Claude, Perplexity and more

Pack 3 · for browser assistants

Website tools

Safe, declared actions an AI in a visitor’s browser can use on your site, built on WebMCP.

Off by default

{from 'discovery' get 'seo'}

Every URL, configured in one map.

The site URL map is the only place where you decide how pages appear in Google, Bing and social networks. Server-rendered and browser-rendered pages read the same map, so nothing is configured twice.

Three layers, most specific winsFrom a site-wide default to one blog post.

  • Site defaultsfallback title, description, imageevery page
  • Static pagesper HTML file in your project/about.html
  • Collection itemsper entry on its detail URL/blog?slug=hello-world

{from 'birkly' get 'agent guide'}

Agents are reading about you right now. Decide what they find.

Everything so far has been about agents you invited in. This is the other kind: the assistant answering a stranger’s question about your product, with no connector and no account.

Agent Guide is a page in your Birkly site that answers instead: a structured account of who you are, what you sell, what you claim, and where each claim can be verified.

get_agent_guide_contextget_agent_guide_claimget_agent_guide_productlist_agent_guide_products

GET /.well-known/agent-guide.json

identity
Official name, description, categories, what you actually do.
usage_hints
Which fields are authoritative, and when to follow a link instead.
communication_guidance
Preferred terms, avoided terms, required qualifications, tone, voice.
claims
Statements with a review status, evidence links and an expiry date.
positioning
Differentiators, who it suits, and who it does not.
products_services
Each with canonical detail links, best-for, and linked claims.
sources_of_truth
Ranked, typed references back to the collections that hold the real data.

Three delivery methods, one published version: the well-known URL, schema.org JSON-LD in the page, and MCP tools.

{for each step in 'agent guide'}

From sources to a published guide in about 15 minutes.

A guided setup walks you through the first version. AI Assist can suggest text, but nothing lands in your draft until you accept it.

01

Sources

Declare what is true first: your About page, product collections, key documents.

02

Context and products

Short summaries of who you are and what you offer, built on those sources.

03

Claims

Statements like ratings or certifications, each with evidence, a review status and an expiry date.

04

Publish

A versioned guide goes live on your domain. Drafts are never served.

{from 'discovery' get 'website tools'}

Let browser assistants act, safely.

AI helpers inside a visitor’s browser usually guess from your HTML. Website tools give them clear actions instead, built on the emerging WebMCP standard. They are off until you switch them on.

A visitor asks their browser assistant“Book me a seat at Thursday’s workshop.”

  • Submit a contact formpublic formsdeclared action
  • Add a product to the cartCommerce plugindeclared action
  • RSVP to an eventEvents plugindeclared action
NextConnect any website