--- title: "Content architecture for answer engines | Len P. van der Hof" description: "Answer engines lift a clean capsule: one claim per URL, named entities, visible sources. Structured data can clarify that. It does not guarantee a citation…" image: "https://lenvanderhof.com/media/generated/blog-hero-architecture-en-v2.80a8f0603698.wide.webp" --- [SEO, GEO and AEO](https://lenvanderhof.com/en/blog/category/seo-geo-aeo/) Research guide # Content architecture that answer engines can lift One claim per URL, named entities, and structured data a machine can quote without inventing you. Len P. van der HofPublished 22 August 20264 min read One claim. One URL. The rest of the stack can wait. Direct answer Content architecture for answer engines is not a schema trick. An engine can lift a page only when the claim is stated once, on one URL, attached to a named person or organization it can verify, and backed by evidence it can see. GEO is the system. AEO is the page. CITATION is the standard: discoverable, attributed, answer-shaped, evidenced, and actually used. Structured data can name the entity. It does not guarantee a citation. FAQPage is not a current rich-result tactic. If the same idea lives in six half-pages, the engine will quote someone who wrote it once. ## Key takeaways - One claim, one URL. If you cannot point at the sentence, the engine cannot either. - Name the entity. sameAs and DefinedTerm help a machine not invent you. - Schema clarifies. It does not guarantee a lift. Do not ship FAQPage for rich results. - How engines choose sources is a different article. This page is the architecture of the page they would lift. A page can rank and still never appear in an answer. The usual diagnosis is “we need more GEO.” Often the claim is smeared: a half-definition on the homepage, a metaphor in a newsletter, a third version on a book page, none of them a sentence a machine can lift without inventing you. [How answer engines select sources](https://lenvanderhof.com/en/blog/how-answer-engines-select-sources/) is the selection article: crawl, understand, extract, trust. This page is the architecture of the thing they would extract. ## One claim, one URL [AEO](https://lenvanderhof.com/glossary/aeo/) is the craft of one URL. A direct answer near the top. Named entities. Visible sources. No invented FAQ schema. If you cannot point at the sentence that owns the claim, you do not have a page. You have a theme. Write the claim in one line. Put it on one address. Link the rest of the site *to* that address. Do not rewrite it six times in six tones and hope the engine picks the least wrong one. That is also the first move in [CITATION](https://lenvanderhof.com/glossary/citation/): a page worth quoting is discoverable, attributed, answer-shaped, evidenced, and actually used. Search eligibility is not enough. The engine lifts the first clean capsule it can verify. ## A smeared claim, then one owner Suppose the claim is: an AI agent holds a goal, uses tools, and continues across steps under a charter. Smeared, it lives as a slogan on the homepage, a looser paragraph in a newsletter, and a third wording on a book page. None of them is the sentence. An engine that quotes you has to invent the short form. Owned, it lives on [What is an AI agent?](https://lenvanderhof.com/en/blog/what-is-an-ai-agent/). The homepage links there. The newsletter links there. The book page links there. The glossary capsule agrees. One URL. One first screen. The rest of the site is a path, not a remix. That is architecture. Selection is a different job, already written. ## Name the entity, do not make the machine guess Attribution fails when the machine cannot tell who you are. Give the person and the organization stable names. Repeat them. Point `sameAs` at the profiles you actually control. If you define a term, give it a [DefinedTerm](https://lenvanderhof.com/glossary/) page with one definition, not a slogan. Structured data can carry that identity. Google is explicit that markup does not guarantee a rich result and is not required for generative search. Use it to stop the engine inventing a second you. Do not use it as a citation spell. Do not ship `FAQPage` for rich results. Ordinary FAQ rich results ended on 7 May 2026. A visible question-and-answer block can still help a reader. It is not a current rich-result tactic. The selection article already sources that. `llms.txt` is a convenience file. It does not replace crawlable HTML. Do not treat it as a ranking lever. ## The first screen is the capsule A tired reader, and a machine, should be able to use the page without a scroll of throat-clearing. - One sentence that states the claim, with its conditions. - The named person or organization. - The source a stranger could check. - Then depth. Length is allowed. Hiding the claim in paragraph nine is not. If the first screen is a brand manifesto, you asked the engine to write your definition for you. ## Gates before lift A capsule that cannot survive a fact-check is not architecture. It is a faster way to be wrong in someone else’s answer. [BooksOS](https://lenvanderhof.com/frameworks/booksos/) is the live production system in [The Agentic Author](https://lenvanderhof.com/books/the-agentic-author/): evidence, quotation, voice, figures, bilingual parity, typesetting, and a refusal to ship below threshold. Agents draft. Gates decide. If a claim would fail those gates, do not put it in the first screen and call it AEO. [The Findability Engine](https://lenvanderhof.com/books/the-findability-engine/) is the book that treats this as an operating system: identity, evidence, retrieval-ready content, proof assets. It is in production, English first. It is not for sale. The standard is already how this site is built: one glossary row, one framework URL, one person `sameAs` list, no manuscript books in the sitemap. [GEO](https://lenvanderhof.com/glossary/geo/) is the system around the page. This article is the page. ## A fifteen-minute audit Pick the claim you most want cited. StepPass looks likeFail looks like1. One sentenceYou can read it aloudA theme, a vibe, three versions2. One URLYou paste a single addressYou need two tabs3. Named entitysameAs resolves404, or a nickname the rest of the web does not use4. Checkable sourceA stranger can open it“Leading study,” no link5. Schema honestyIdentity markup, no FAQPage for a dead rich resultFAQ schema as a citation spell If step 2 or 4 is blank, stop buying “GEO retainers.” Fix the page. The engine cannot lift what you refused to state once. Cite this:Content architecture that answer engines can lift.Len P. van der Hof. [https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/](https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/) · Published 22 August 2026. ## Terminology - [CITATION](https://lenvanderhof.com/glossary/citation/) - [GEO](https://lenvanderhof.com/glossary/geo/) - [AEO](https://lenvanderhof.com/glossary/aeo/) ## Sources 1. [CITATION (glossary)](https://lenvanderhof.com/glossary/citation/) 2. [GEO (glossary)](https://lenvanderhof.com/glossary/geo/) 3. [AEO (glossary)](https://lenvanderhof.com/glossary/aeo/) 4. [How answer engines select sources](https://lenvanderhof.com/en/blog/how-answer-engines-select-sources/) 5. [The Findability Engine](https://lenvanderhof.com/books/the-findability-engine/) 6. [The Agentic Author](https://lenvanderhof.com/books/the-agentic-author/) 7. [BooksOS](https://lenvanderhof.com/frameworks/booksos/) 8. [Introduction to structured data markup in Google Search](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) · Google Search Central 9. [FAQ structured data deprecation](https://developers.google.com/search/docs/appearance/structured-data/faqpage) · Google Search Central ## Related essays - [How answer engines select sources](https://lenvanderhof.com/en/blog/how-answer-engines-select-sources/) - [How to get cited by ChatGPT](https://lenvanderhof.com/en/blog/how-to-get-cited-2026/) - [The Agentic Author: introduction](https://lenvanderhof.com/en/blog/the-agentic-author-introduction/) - [GEO meaning: generative engine optimization, not geography](https://lenvanderhof.com/en/blog/what-geo-means/) - [What AEO means: answer engine optimization, not customs](https://lenvanderhof.com/en/blog/what-is-aeo/) - [What is BooksOS? Seven gates, not a writing CMS](https://lenvanderhof.com/en/blog/what-is-booksos/) - [What is an evidence ledger?](https://lenvanderhof.com/en/blog/what-is-an-evidence-ledger/) - [Literary agent or AI agent: two different jobs](https://lenvanderhof.com/en/blog/literary-agent-or-ai-agent/) ## Further reading - [How answer engines select sources](https://lenvanderhof.com/en/blog/how-answer-engines-select-sources/) - [CITATION](https://lenvanderhof.com/glossary/citation/) - [GEO](https://lenvanderhof.com/glossary/geo/) - [AEO](https://lenvanderhof.com/glossary/aeo/) - [BooksOS](https://lenvanderhof.com/frameworks/booksos/) - [The Agentic Author](https://lenvanderhof.com/books/the-agentic-author/) - [The Findability Engine](https://lenvanderhof.com/books/the-findability-engine/) About the author ## [Len P. van der Hof](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) Entrepreneur, AI Innovator and Venture Builder Len P. van der Hof builds practical AI systems, digital ventures and evidence-informed tools for founders. ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Person", "@id": "https://lenvanderhof.com/#person", "name": "Len P. van der Hof", "alternateName": [ "Len van der Hof", "L.P. van der Hof", "Leendert Pieter van der Hof" ], "honorificSuffix": "MSc", "url": "https://lenvanderhof.com/", "image": [ "https://lenvanderhof.com/photos/len-portrait-1.jpg", "https://lenvanderhof.com/photos/len-portrait-2.jpg", "https://lenvanderhof.com/photos/len-portrait-3.jpg", "https://lenvanderhof.com/photos/len-portrait-4.jpg", "https://lenvanderhof.com/photos/len-speaking.jpg", "https://lenvanderhof.com/photos/len-hero.jpg" ], "jobTitle": "Entrepreneur, AI Innovator and Venture Builder", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "address": { "@type": "PostalAddress", "addressLocality": "Zwijndrecht", "addressCountry": "NL" }, "alumniOf": { "@type": "CollegeOrUniversity", "name": "Rotterdam School of Management, Erasmus University" }, "knowsAbout": [ "Artificial intelligence", "AI agents", "Agentic AI systems", "LLM routing", "SEO", "Generative engine optimization", "Answer engine optimization", "Venture building", "Founder performance", "Founder psychology", "Evidence-based decision-making" ], "sameAs": [ "https://www.linkedin.com/in/lenvanderhof/", "https://x.com/LenvanderHof", "https://www.youtube.com/channel/UCTG20buKqYYbitqqf7l3zJA", "https://www.instagram.com/Lenvanderhof/", "https://www.threads.com/@lenvanderhof", "https://github.com/Lenvanderhof", "https://huggingface.co/LPH98", "https://www.npmjs.com/~lenvanderhof", "https://www.goodreads.com/author/show/70983905.Len_P_van_der_Hof", "https://www.amazon.com/author/lenvanderhof", "https://www.bol.com/nl/nl/b/len-p-van-der-hof-msc/609879394/", "https://bsky.app/profile/lenvanderhof.com", "https://mastodon.social/@Lenvanderhof", "https://crates.io/users/Lenvanderhof", "https://cursor.com/@Lenvanderhof", "https://medium.com/@Lenvanderhof", "https://gitlab.com/Lenvanderhof", "https://hub.docker.com/u/lenvanderhof/", "https://dev.to/lenvanderhof", "https://www.facebook.com/Lenvanderhof", "https://soundcloud.com/Lenvanderhof" ], "affiliation": [ { "@id": "https://lenvanderhof.com/#publisher" }, { "@id": "https://lenvanderhof.com/#mindsesh" }, { "@id": "https://lenvanderhof.com/#lifestyle" } ] }, { "@type": "WebSite", "@id": "https://lenvanderhof.com/#website", "url": "https://lenvanderhof.com/", "name": "Len P. van der Hof", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "inLanguage": [ "en", "nl" ], "publisher": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#publisher", "name": "LPH98.ventures", "url": "https://lph98.ventures", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#mindsesh", "name": "MindSesh", "url": "https://mindsesh.net", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#reasonkit", "name": "ReasonKit", "url": "https://reasonkit.sh", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#undominated", "name": "Undominated.ai", "url": "https://undominated.ai", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#lifestyle", "name": "LPH98.lifestyle", "url": "https://lph98.lifestyle", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "ImageObject", "@id": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/#primaryimage", "url": "https://lenvanderhof.com/media/generated/blog-hero-architecture-en-v2.80a8f0603698.wide.webp", "contentUrl": "https://lenvanderhof.com/media/generated/blog-hero-architecture-en-v2.80a8f0603698.wide.webp", "representativeOfPage": true }, { "@type": "BreadcrumbList", "@id": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://lenvanderhof.com/" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://lenvanderhof.com/en/blog/" }, { "@type": "ListItem", "position": 3, "name": "SEO, GEO and AEO", "item": "https://lenvanderhof.com/en/blog/category/seo-geo-aeo/" }, { "@type": "ListItem", "position": 4, "name": "Content architecture that answer engines can lift", "item": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/" } ] }, { "@type": "WebPage", "@id": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/#webpage", "url": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/", "name": "Content architecture that answer engines can lift", "description": "Answer engines lift a clean capsule: one claim per URL, named entities, visible sources. Structured data can clarify that. It does not guarantee a citation. FAQPage will not save a smeared claim.", "isPartOf": { "@id": "https://lenvanderhof.com/#website" }, "primaryImageOfPage": { "@id": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/#primaryimage" }, "breadcrumb": { "@id": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/#breadcrumb" }, "inLanguage": "en-GB" }, { "@type": "BlogPosting", "@id": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/#article", "mainEntityOfPage": { "@id": "https://lenvanderhof.com/en/blog/content-architecture-for-answer-engines/#webpage" }, "headline": "Content architecture that answer engines can lift", "description": "Answer engines lift a clean capsule: one claim per URL, named entities, visible sources. Structured data can clarify that. It does not guarantee a citation. FAQPage will not save a smeared claim.", "datePublished": "2026-08-22T09:00:00.000Z", "author": { "@id": "https://lenvanderhof.com/#person" }, "publisher": { "@id": "https://lenvanderhof.com/#person" }, "image": [ "https://lenvanderhof.com/media/generated/blog-hero-architecture-en-v2.80a8f0603698.square.webp", "https://lenvanderhof.com/media/generated/blog-hero-architecture-en-v2.80a8f0603698.landscape.webp", "https://lenvanderhof.com/media/generated/blog-hero-architecture-en-v2.80a8f0603698.wide.webp" ], "articleSection": "SEO, GEO and AEO", "inLanguage": "en-GB" } ] } ```