The entity-attribute-value (EAV) model is a way of describing any topic as things (entities), the properties people ask about (attributes) and the facts that fill them (values). In SEO, it turns a vague subject into a concrete list of what a complete page or site must cover, which is why it sits at the centre of semantic SEO and Koray Tuğberk GÜBÜR’s topical authority framework.
Entity, attribute, value: the three parts
Take a single product, the Breville Bambino espresso machine:
| Entity | Attribute | Value (example) |
|---|---|---|
| Breville Bambino | Heating system | Thermojet |
| Breville Bambino | Heat-up time | About 3 seconds |
| Breville Bambino | Portafilter size | 54 mm |
| Breville Bambino | Milk frothing | Manual steam wand |
- Entity: a uniquely identifiable thing. A product, person, place, organisation or concept.
- Attribute: a property of that entity that someone might want to know about.
- Value: the specific fact for that attribute. Values are what AI answers and featured snippets quote.
Search engines store knowledge in roughly this shape. Google’s Knowledge Graph is a large network of entities, their attributes and the relationships between them. Writing in the same shape makes your content easier to understand and easier to extract.
Why EAV matters for SEO
- It defines completeness. A page about an entity is complete when it covers the attributes people actually ask about. EAV turns “write a good page” into a checklist.
- It prevents thin and duplicate pages. Once attributes are listed, you can decide which deserve their own URL and which are sections. That decision is the core of a topical map.
- It matches how AI search retrieves. AI Mode splits a prompt into sub-questions, a process called query fan-out. Most sub-questions are attribute questions: price, size, comparison, compatibility. Covering attributes means covering the fan-out.
- It gives you quotable facts. Values stated plainly (“heats up in about 3 seconds”) are what generative answers lift. Vague prose gives them nothing.
Root, rare and unique attributes
Not all attributes carry the same weight. Koray’s framework sorts them into three groups, and the split is useful for prioritising:
- Root attributes apply to every entity of that type. Every espresso machine has a price, a boiler type and a pressure rating. Missing these makes a page incomplete.
- Rare attributes apply to some entities in the type. A built-in grinder or a PID controller. Covering them where relevant shows depth beyond the obvious.
- Unique attributes belong to one entity alone, such as a patented heating system. These are what differentiate your page from every competitor that covered only the root attributes.
Most competing pages cover root attributes and stop. Rare and unique attributes are where you win.
How to find an entity’s attributes
- Knowledge sources: Wikipedia infoboxes and Wikidata properties list the attributes the wider web already associates with an entity type.
- Questions people ask: People Also Ask, Search Console queries, forums and AI prompts reveal attributes in question form (“how loud is”, “does it work with”).
- Specifications and documentation: manufacturer specs, standards and regulations cover attributes enthusiasts care about.
- Competitor headings: scan the headings of top-ranking pages. Attributes they all share are root; attributes only one covers may be rare.
- Your own expertise: sales calls, support tickets and client work surface unique attributes no tool will show you.
An extraction tool helps you check which entities a page already mentions; Google’s Natural Language API and dedicated tools both do this.
From EAV to pages: a worked example
Say your central entity is home espresso machines. The EAV pass produces something like this:
| Attribute | Type | Becomes |
|---|---|---|
| Boiler type (single, dual, heat exchanger, thermoblock) | Root | Its own comparison page |
| Price range | Root | Section in every buying guide, plus a “best under $X” page |
| Pressure (bar) | Root | Section on the “what is espresso” page |
| PID temperature control | Rare | Explainer page linked from relevant reviews |
| Built-in grinder | Rare | “All-in-one vs separate grinder” page |
The rule of thumb: an attribute gets its own URL when it has its own search intent and enough to say. Otherwise it becomes a section on its parent page. The full process is in how to build a topical map.
EAV on the page
- Name the entity in the title, H1 and first sentence.
- Use attribute names as headings where they match how people ask.
- State values plainly and early in each section, with units.
- Put comparable values in tables so both readers and machines can scan them.
- Where structured data exists for the type (Product, LocalBusiness, SoftwareApplication), mark the same values up. Schema confirms what the page says; see schema markup for semantic SEO.
Common EAV mistakes
- Listing attributes but not values. “Heat-up time is important” helps nobody. “About 3 seconds” does.
- Treating synonyms as attributes. “Cheap”, “budget” and “affordable” are one attribute (price), not three pages.
- Stopping at root attributes. That produces the same page everyone else wrote.
- Inconsistent values across pages. If two of your pages give different figures for the same attribute, you undermine trust in both.
EAV is the foundation layer of semantic SEO. For the wider picture, see what is semantic SEO, entity SEO explained and how to get topical authority.
Frequently asked questions
What does EAV stand for in SEO?
EAV stands for entity-attribute-value: a way of modelling a topic as entities, the attributes people ask about, and the specific values for each attribute.
What are root, rare and unique attributes?
Root attributes apply to every entity of a type, rare attributes to some of them, and unique attributes to one entity alone. Covering rare and unique attributes is what differentiates a page.
How is EAV related to topical maps?
EAV is the step that lists what a subject contains. The topical map then decides which attributes become their own pages and which become sections, and how those pages link.
Do I need schema markup to use EAV?
No. EAV is about what your content covers. Schema markup can confirm the same values in a machine-readable form, but it cannot replace them on the page.