Agent-Ready. The new SEO.

GEO instead of SEO: the strategy behind Agent-Ready

Behind Agent-Ready sits a larger shift in online marketing. Since 2025 the industry has a name for it: GEO, Generative Engine Optimization. SEO optimizes for appearing high in Google's results list. GEO optimizes for being named and cited directly in the finished answers of ChatGPT, Perplexity, Gemini, and Claude.

The difference sounds small but is strategically large. A user who receives a finished AI answer often does not click on the classic result at all. If you appear in the answer itself, you are visible. If not, you disappear, even while your Google rankings still hold.

Where do SEO and GEO differ?

SEO and GEO differ in eight points: the goal, the form of the search output, the platforms, the ranking signals, the type of query, the shape of the user journey, the stability of the results, and the success metric. The table below places the differences side by side.

Why is Agent-Ready the technical foundation for GEO?

GEO is the strategy. Agent-Ready is the prerequisite. For an AI to cite a page at all, it has to read the page's structure cleanly. That works only if three building blocks are in place: an llms.txt as a table of contents for language models, schema.org structured data as a machine-readable label per page, and semantic HTML instead of div soup.

Anyone serious about GEO without implementing Agent-Ready is optimizing text for a machine that does not reliably understand the page. The two belong together: GEO decides what is on the page. Agent-Ready ensures the AI finds it.

SEO remains the entrance. Without indexing, no AI agent reaches the page either. GEO and Agent-Ready build on top of it. Whoever serves all three layers cleanly is visible in the AI era.

What about Google AI Overviews?

Google published its own AI Optimization Guide on 15 May 2026. Its core message: classic SEO and "people-first content" are enough; an llms.txt is not necessary; special AI markup is a myth. The message sounds tidy. To read it correctly, you have to know where it comes from.

Google is not neutral on this question. With AI Overviews, Google itself is a provider of an AI answer product and therefore a direct competitor to ChatGPT, Claude, and Perplexity. Google's strength is the web index it has built for 25 years. Google does not need an llms.txt to understand a page. The other AI platforms do not have that index. They depend on website operators delivering content in a clean structure. That is exactly what llms.txt does. If it becomes the norm, Google's role as middleman between website and AI shrinks. That explains why Google's official line calls it a "myth".

The other AI providers see it differently. Anthropic Claude, OpenAI ChatGPT, and Mistral actively read and use llms.txt. Anthropic operates four official bots (Claude-User, Claude-SearchBot, ClaudeBot, claude-code) that preferentially crawl sites which provide one. For Perplexity, llms.txt is a weaker signal. The engine there weighs freshness, clear structure, and external authority more heavily. See the dedicated Perplexity section below.

In practice: of the three Agent-Ready building blocks, Google explicitly recommends two itself. schema.org structured data and semantic HTML appear verbatim in Google's own AIO guide. Only llms.txt is contested, and the dispute is explainable as business strategy, not as a technical fact. An llms.txt costs one text file and ten minutes of work. It does not hurt with Google and qualifies your page for the AI answers of platforms that are not Google. That is exactly the bet Agent-Ready is making.

What about Perplexity?

Perplexity is the most-cited "answer engine" in the industry: instead of a list of hits, it delivers a summarized answer and cites five to ten sources per answer with direct links. That makes Perplexity the most direct path to measurable traffic from AI answers. Whoever appears in Perplexity citations earns a click.

The mechanics behind it work differently from Google and from Claude or ChatGPT. Perplexity scores sources through a three-stage reranking: relevance, then authority, then freshness and structure. llms.txt plays a minor role here. The real levers are:

• Freshness. Perplexity favors content updated within the last 60 to 90 days. A visible "Last updated: May 2026" plus a maintained dateModified in the JSON-LD is measurable.
• Clear structure. Each heading framed as a concrete question, followed by a 40-to-80-word answer, then the explanation. Tables and lists for comparisons. Perplexity extracts such passages cleanly.
• External authority. Mentions in Reddit discussions, in "best of" lists from reputable industry publications, and in Wikipedia. Perplexity actively reads these signals.
• Original data and studies. Primary sources that others must cite show up disproportionately often in Perplexity's top-three citation positions.
• PerplexityBot allowed in robots.txt. Without that permission the page is not crawled. On Fiperly this is in place.

In practice: anyone aiming for Perplexity visibility does not write primarily for an AI but establishes an update discipline, builds comparison and review content with a clear question-answer structure, and ensures the brand is mentioned outside its own domain. Agent-Ready remains the technical foundation (semantic HTML, schema, readable structure), but the bulk of the work for Perplexity visibility lies in editorial discipline and external presence.

Which AI platform responds to which measure?

To complete the picture: here is an honest map of the major AI answer engines and their respective levers. What works at Anthropic Claude only helps at the margin with Perplexity, and Google ignores still other things. The good news: whoever cleanly serves all three Agent-Ready building blocks and maintains content with structure, freshness, and sources covers every platform at once.

The single most important measure from this overview: explicitly allow all relevant AI crawlers in your robots.txt. Many sites accidentally block them through default configurations (especially with Cloudflare) and thus disappear completely from AI answers — including from platforms that would otherwise cite them well. Fiperly has all the bots listed above enabled in its robots.txt.

In simple terms

Imagine a friend asking you about a topic in conversation. In the past, they would have searched on Google, scanned five articles, and formed their own opinion. Today they ask ChatGPT, Claude, or Perplexity instead — and receive a single summarized answer drawn from several websites. Which sites get a voice in that answer is decided by the AI in fractions of a second.

This is exactly where it is decided whether your site is visible in the new web. A website built so that AI agents can understand it gets cited. A website built only for human eyes gets overlooked. Not because it is worse — but because the AI cannot reliably decipher its content.

Agent-Ready is the simple answer to this new reality. Three small building blocks — a text file, a touch of machine-readable labeling, and clean HTML — turn any website into a source that AI systems understand and recommend. The logo on your site shows visitors and machines at the same time: this site has arrived in the AI era.

For developers, this is done in an hour. For non-developers there are guides, tools, and agencies — the effort is manageable, the effect long-lasting. Anyone who acts now is among the first thousand websites worldwide to officially position themselves as Agent-Ready.

The three great web seals — and why Agent-Ready will be the third

In thirty years, the internet has produced two universal quality seals. Both began as an insider topic and became the standard within a few years. Agent-Ready stands on the threshold of becoming the third:

1. HTTPS (since around 2014) — the padlock in the address bar. Indicates: the connection is encrypted. Today: a baseline requirement; without HTTPS, browsers flag a site as insecure.
2. Mobile-Friendly (since 2015) — Google rewards mobile-optimized pages in search. Today: a baseline requirement; non-mobile sites have effectively disappeared.
3. Agent-Ready (from 2026) — the seal indicating that a page is structurally readable for AI agents. Within a few years, the standard against which credibility and visibility on the web will be measured.

Whoever adopts Agent-Ready today gains the same head start that early adopters of HTTPS and Mobile-Friendly enjoyed — with the difference that AI-powered search is growing faster than mobile browsing ever did.

What does "Agent-Ready" mean?

Agent-Ready describes a state in which a website is fully accessible not only to human readers but also to machine readers — in particular Large Language Models and the agents they drive. A website earns the badge if it meets three core requirements:

• /llms.txt sits at the root and describes the site in clear Markdown — purpose, key subpages, contact details, citation rules. Following the proposal by llmstxt.org (Jeremy Howard, fast.ai, September 2024).
• Structured data in JSON-LD according to schema.org — at minimum Organization and WebSite, and depending on content also Article, TechArticle, FAQPage, Product, Event, or Person.
• Semantic HTML with a clean heading hierarchy, real <nav>/<main>/<article>/<section> tags, descriptive alt text, and meaningful link anchors instead of "click here".

No new framework, no dependency, no fees. Pure craft — back to the way HTML was originally meant to be, before JavaScript frameworks and cookie banners made pages inaccessible to machines.

Why classic SEO is no longer enough

Search is shifting. Anyone in 2026 looking up a fact, a product recommendation, or a medical interpretation no longer automatically types into the Google search box, but puts the question directly to a language model. ChatGPT, Claude, Perplexity, Gemini, and the AI assistants built into browsers, IDEs, and operating systems pull answers from the web — but they deliver them not as a list of links, but as a summarized answer with attribution.

This fundamentally changes the rules of the game. For ten years, SEO meant keyword density, backlinks, page speed, meta descriptions. That is no longer enough. A language model needs clear prose, machine-readable structure, and concrete facts with sources. It ignores text that is merely keyword-optimized and rewards text that explains something to an intelligent reader.

This new optimization approach already has a name: Generative Engine Optimization, or GEO for short. Agent-Ready is the visible certification of that approach. Anyone who carries the badge signals: this site is built not for SEO tricks, but for substantial answers — and that is exactly what models pull into their responses.

How LLM agents read a website

An AI agent has only a few seconds to determine whether and how a page is relevant to a specific user question. The process typically follows the steps summarized under the term Retrieval-Augmented Generation (RAG):

1. Discovery — The agent finds the page via a search engine, a link in another answer, an entry in an llms.txt file, or a direct user link.
2. Fetch — It retrieves the page, ideally as static HTML. Pages that load their content only through JavaScript are invisible to many agents.
3. Parse — The agent extracts headings, paragraphs, lists, tables, and structured data. The cleaner the HTML, the more reliable the result.
4. Chunk & Embed — The text is broken into meaningful sections and embedded in a vector space so the model can measure their relevance to the user question.
5. Cite — The matching sections flow into the generated answer, usually with attribution and a link back to the originating page.

Agent-Ready targets steps 2 through 5. A cleanly structured page is found more reliably, parsed more accurately, chunked more precisely, and cited more often. Sites without semantic HTML, without JSON-LD, and without llms.txt appear in AI answers far less frequently — and when they do appear, often with factual errors, because the model has to guess what the page is actually saying.

Checklist — Is my site Agent-Ready?

The following twelve points are mandatory. Tick all of them and you meet the standard and may display the badge:

• /llms.txt sits at the root, is under 500 lines, and describes purpose, key pages, contact, and citation rules in Markdown.
• /robots.txt explicitly allows the major AI bots: ClaudeBot, Claude-User, Claude-SearchBot, claude-code (Anthropic 4-bot system, as of May 2026), GPTBot, ChatGPT-User, OAI-SearchBot (OpenAI), PerplexityBot, Perplexity-User, Google-Extended, Google-Agent, Applebot, Applebot-Extended, MistralAI-User, DuckAssistBot, Meta-ExternalAgent, Meta-WebIndexer, Amazonbot, CCBot, Bytespider.
• /sitemap.xml exists and lists all public URLs with a lastmod date.
• JSON-LD with Organization and WebSite in the <head> of every page.
• Articles and guides additionally carry Article or TechArticle with author, datePublished, and dateModified.
• FAQ sections are marked up as FAQPage schema.
• Clean H1-to-H3 hierarchy — exactly one H1 per page, no skipped levels.
• Real semantic tags <nav>, <main>, <article>, <section>, <aside>, <footer> instead of a wall of <div>s.
• All images have descriptive alt attributes — no empty ones, no file names, no keyword-spam strings.
• Links use meaningful anchor text ("see the price overview" instead of "click here").
• Content is deliverable as static HTML — JavaScript rendering is not a requirement.
• Canonical URL, meta description, and Open Graph data are set individually on each page.

Tip: test your own page with Google's Rich Results Test, with view-source: in the browser, and by asking a question about your page in ChatGPT or Perplexity. If the content is summarized and cited correctly, that is a strong sign that Agent-Ready is working.

Recommended since May 2026 — beyond the mandatory checklist

Four additions have established themselves in 2026 as extra leverage. They are not required for the badge, but sites that take 2026 seriously have them in place:

/llms-full.txt — the full-text variant

More than 844,000 sites already publish llms.txt. The next differentiator is llms-full.txt: same Markdown structure, but instead of navigational links it contains the consolidated full text of your most important pages in a single file. LLMs get the entire brand context in one fetch, without having to parse dozens of HTML pages. Especially useful for sites of manageable size — marketing hubs, documentation, brand landing pages.

Anthropic 4-bot system instead of 3-bot

Since May 2026, Anthropic runs four separate bots, each with its own purpose and user agent — ClaudeBot (training), Claude-User (user fetches), Claude-SearchBot (search), and claude-code (Claude Code CLI). All four should appear individually in your robots.txt, because each has its own user-agent string and can be controlled independently.

Strategic decision: search bots vs. training bots

One of the most important business decisions in 2026: should training bots like ClaudeBot, GPTBot, CCBot, and Google-Extended be allowed to ingest your content for model training? Sites that need to protect paid content (premium articles, exclusive data, subscriber-only knowledge) block them and only allow the retrieval bots (Claude-SearchBot, OAI-SearchBot, PerplexityBot, ChatGPT-User, Claude-User) — so content appears in AI answers but doesn't flow into training. Sites that prioritize reach and have no paid content allow both groups. Both strategies are legitimate in 2026 — they just need to be a deliberate choice, documented as a comment in robots.txt.

MCP card — a name tag for your site that AI agents can read

Think of the MCP card as a doorbell label that only AI agents read. It is a tiny text file at a fixed spot — at /.well-known/mcp-server-metadata.json. In short keywords it states: what this site is called, what it offers, who is behind it, and where an agent can connect. "MCP" stands for Model Context Protocol and has been a fixed, open standard since November 2025 — a shared language that lets AI services introduce themselves to one another.

The honest part: a card on its own does nothing magic yet. It only becomes truly useful once a real service runs behind the address you list, one an agent can actually use. Until you are there, you simply write "status": "planned" into it. Even that alone gets your site listed early in the directories that AI agents scan for such cards. Being early means being found first.

Two simple rules: only place the card once your site is publicly visible — not while it is still under construction and closed to search engines. And keep the content short and honest: better "planned" than a promise the site cannot keep yet.

Quick start — llms.txt in 30 seconds

Here's what a minimal llms.txt looks like. Place the file in the root directory of your website (i.e. at https://your-domain.com/llms.txt) and adapt the contents:

# Company Name

> Short description: What the site is and who it is made for.

## Key pages

- [Home](https://your-domain.com/)
- [About us](https://your-domain.com/about)
- [Products](https://your-domain.com/products)
- [Contact](https://your-domain.com/contact)

## Contact

- Email: info@your-domain.com
- Responsible: First Last

## Citation rules

Please cite this site with full name and URL.

That's it. No build step, no framework — a simple text file in Markdown.

Quick start — JSON-LD minimal example

Add this code block to the <head> of every page. It tells search engines and AI agents the basic information about your company and website:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Company Name",
  "url": "https://your-domain.com",
  "logo": "https://your-domain.com/logo.png",
  "description": "What your company does.",
  "email": "info@your-domain.com"
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Company Name",
  "url": "https://your-domain.com",
  "inLanguage": "en-US"
}
</script>

Test the result with the Google Rich Results Test — you'll see immediately whether Google detects the data correctly.

Already live on

Agent-Ready is not a concept on paper — it is already running in production on these websites:

• fiperly.de — Parent brand and initiator of the Agent-Ready standard. llms.txt, JSON-LD (Organization, WebSite, TechArticle, HowTo, FAQPage), semantic HTML, hreflang DE/EN.
• kipode.de — Fact-based information about Germany's situation in 2026. llms.txt, JSON-LD (Organization, WebSite, FAQPage), pillar articles with TechArticle schema.
• healthmetricslab.com — Longevity platform with biomarker data. llms.txt, JSON-LD (Organization, WebSite, Product), healthspan calculator with structured data.

Your site is missing from the list? Drop us a line — we're happy to include every Agent-Ready website.

Glossary — the key terms around Agent-Ready

llms.txt

A Markdown file at the root of a website, proposed in September 2024 by Jeremy Howard (co-founder of fast.ai). It explains in plain text to a language model what the site is about, which subpages are most important, and which sources the agent should cite. The format is deliberately simple: an H1 with the project name, a paragraph of introduction, then H2 headings with lists of relevant URLs.

schema.org

A shared vocabulary from Google, Microsoft, Yahoo, and Yandex for structured data on the web, launched in 2011. Through types such as Organization, Person, Article, or Product, content is annotated in a machine-readable way. The best way to embed schema.org is as JSON-LD in the <head>.

JSON-LD

JavaScript Object Notation for Linked Data — Google's recommended way to embed schema.org. A JSON block inside <script type="application/ld+json"> doesn't disturb the HTML but is immediately processable for crawlers and LLM agents.

Generative Engine Optimization (GEO)

The evolution of SEO. While SEO aims to appear at the top of result lists, GEO aims to be cited in the generated answers of AI systems. The key levers are clear facts, verifiable sources, structured text, and machine-readable markup.

Retrieval-Augmented Generation (RAG)

A method in which a language model does not answer purely from its training knowledge but retrieves matching sources at runtime and incorporates them into the answer. RAG is the standard for modern AI assistants and the reason why websites are becoming increasingly important as a supply source for agents.

Semantic HTML

HTML that conveys its meaning through tag names. Navigation belongs in <nav>, the main content in <main>, a self-contained article in <article>. For machines, the difference between a <div class="nav"> and a real <nav> is significant — only the latter is intelligible without guessing class names.

LLM bot / AI crawler

An automated retrieval agent operated by an AI provider. Examples: ClaudeBot, Claude-User, Claude-SearchBot (Anthropic), GPTBot and OAI-SearchBot (OpenAI), PerplexityBot (Perplexity), Google-Extended and Google-Agent (Google/Gemini), DuckAssistBot (DuckDuckGo), MistralAI-User (Mistral), Meta-ExternalAgent and Meta-WebIndexer (Meta), Amazonbot (Amazon), CCBot (Common Crawl). Access is controlled through robots.txt.

The vision behind Agent-Ready

In its first thirty years, the internet produced two great quality seals: the HTTPS lock next to the address bar, indicating that a connection is encrypted, and the Mobile-Friendly notice from 2015, with which Google distinguished mobile-ready pages from non-mobile ones. Both seals became the standard within a few years and made the web measurably better.

With the breakthrough of language models, a third seal is missing: one for sites that AI agents can cleanly understand. There are good individual building blocks — llms.txt, schema.org, semantic HTML — but no shared, visible marker that brings them under one roof. This is precisely the gap that Agent-Ready closes.

The idea is explicitly open: the badge belongs to no one. Fiperly provided the impulse, formulated the criteria, and supplied the logo file, but the standard only lives if many adopt it. Every agency, every startup, every blog, and every public institution is invited to embed the badge — without registration, without fees, without strings attached.

The specification, example files, and badge are also published openly on GitHub at github.com/michaelbertelsenmedia-commits/agent-ready. The repository is licensed under CC0 1.0 Universal (public domain) and accepts pull requests, translations, and implementation reports.

We believe that within a few years Agent-Ready will be as self-evident a part of web craftsmanship as HTTPS or Mobile-Friendly. The web has proven in every new era that it can renew itself technically without losing its open character. The AI era is no exception — it just needs someone to take the first step.

Download the badge

The Agent-Ready logo is available for free download as a PNG with a transparent background in three sizes. PNG is the right format because the logo features photo-realistic depth, golden shine, and shading — these effects would be lost as SVG. The transparent edges allow the badge to be placed on light or dark backgrounds without showing a rectangular box.

320 × 320 px

PNG · approx. 138 KB

Footer badge, small web embedding, standard size

Download

512 × 512 px

PNG · approx. 447 KB

Hero section, Retina displays, larger placement

Download

1024 × 1024 px

PNG · approx. 1.3 MB

Print, social media posts, press materials

Download

How to embed the badge on your website

Recommended placement: in the footer, next to imprint and privacy. Link it to your own /llms.txt or directly to this explainer page so that visitors and crawlers can see what the seal means.

<a href="/llms.txt" title="Agent-Ready — this site is optimized for LLM agents">
  <img src="https://www.fiperly.de/assets/img/agent-ready-logo.png" alt="Agent-Ready Badge — KI and Robots Welcome" width="80" height="80">
</a>

Why Fiperly?

Fiperly is an independent AI development company from Germany. We build brands that put artificial intelligence to work where it measurably helps people — in public information, health, fashion, and everyday life. That a website in the AI era should also be readable for agents is, for us, a duty rather than a nice-to-have. We make the badge freely available because it is a shortcoming that no one has built it before.

The badge belongs to no one — it is in the public domain. Use it, copy it, modify it. If you'd like, drop us a line letting us know where you've put it — we're collecting examples.