§13 · domain · 04 / 06

Semantic AI Search.

Semantic AI search is the practice of structuring websites so people, search engines, answer engines, and AI agents can understand entities, relationships, definitions, evidence, and source-of-record pages by meaning, not only by keywords.

Yoav Fekete works on this domain. yoavfekete.com is the applied example.

Semantic search mark A small entity graph: a central node connected to four named entities around it, with one of the connections drawn in solid line to emphasise a typed relation. entity name id links relation
FIG · entity + typed relation
KindDomain · architecture
Worked exampleyoavfekete.com itself
Canonical map/entity-map/
AdjacentAI-assisted software · Geometric Reasoning

§13.1 · definition

What "semantic AI search" means here.
Semantic AI Search /sɪˈmæn.tɪk eɪ aɪ sɜːtʃ/
noun · domain · architecture

The design of entities, relationships, definitions, evidence, and canonical pages so that humans, search engines, answer engines, and AI systems can understand what a site represents. Keywords still matter, but entities, relationships, and source-of-record pages increasingly matter too.

Vocabulary
  • Entity
  • Typed relation
  • Canonical URL
  • Structured data
  • Answer engine

§13.2 · why it matters

Three reasons entity clarity matters for public websites.

AI systems now read alongside people.

AI systems are increasingly part of how public knowledge is found and summarized. A page should be clear to a human reader while also being easy for retrieval systems to parse and cite accurately.

Entities outlive pages.

A person, project, or invention is easier to understand when it has one stable source-of-record page, a clear type, and visible links to the related entities around it.

Relations carry the meaning.

"Yoav Fekete develops Clause", "NaadLabs builds the Harmonic Sitar", and "YoYo Sitar gives it performance context" are relationship claims. They should appear in visible prose, internal links, and conservative structured data.

§13.3 · approach

Design the site as a source of record, not only as a set of pages.

Classic websites were often built as destinations: a person clicks, reads a page, and forms an impression directly. That still matters. But more discovery is becoming AI-mediated. A search summary, answer engine, assistant, or agent may encounter the site first, extract a passage, compare entities, or use the page as evidence before a human ever opens it.

That changes the design problem. A page must still be human-readable, but it also has to make its meaning explicit enough to be retrieved, summarized, cited, and distinguished from related entities.

The approach here is to treat a personal or expert website as a small public knowledge graph. Each important thing gets a stable source-of-record page: the person, the system, the invention, the lab, the concept, the note. Relationships are written in visible HTML, supported by internal links, and mirrored conservatively in structured data.

The goal is not to replace writing with schema. The goal is to make the writing legible: to humans first, and to machines without forcing them to guess.

Stance
  • One important entity, one source-of-record page.
  • Relationships visible in HTML.
  • Structured data mirrors visible content.
  • The site is the applied example.

§13.5 · working vocabulary

→ Semantic entity design Source-of-record pages Typed relationships Canonical URLs Answer-ready passages Structured-data parity

§13.6 · questions this domain opens

A site as a small knowledge graph

How can entity pages, relationship tables, canonical URLs, and visible evidence turn a small website into a source of record?

Writing for human readers and AI systems

How should definitions, headings, link text, and self-contained passages be written so they remain understandable when summarized or cited?

Don’t invent. Leave a gap.

Why is an honest missing field better than an invented credential, and how does that affect semantic credibility?

§13.7 · live example

How this site applies the idea.

yoavfekete.com is the live example of this method. The site is built around Yoav Fekete as the root person entity, then separates the connected entities instead of collapsing them: Clause, NaadLabs, Harmonic Sitar, YoYo Sitar, Afro-Raga, Representation, and the technical domains each have distinct roles and canonical pages.

The entity map makes the relationships visible. The concept page defines representation as a way of seeing. The first note, The Right Map for the Question, explains why representation changes what becomes visible, solvable, verifiable, or playable. The system pages show how the same principle appears in Clause, Harmonic Sitar, and NaadLabs.

This is not presented as a consulting page. It is a working example: a public person site structured so humans, search engines, and AI systems can understand the entities, follow the relationships, and cite the right page for the right claim.

Public pattern
  • Human-readable first.
  • Machine-legible second.
  • Relationships visible in HTML.
  • Structured data mirrors visible content.
  • Canonical URLs stay stable.
  • Unsupported claims stay out.