Audit 20: Entity Attribute Audit

Map an entity's root, rare, and unique attributes — then verify coverage in content, schema, and the Knowledge Graph using Koray Tugberk's E-A-V methodology.

Title & Description

What it is: A systematic audit that evaluates how completely an entity's attributes are covered across content and structured data, using the Entity-Attribute-Value (E-A-V) model to identify gaps and prioritize coverage.

When to run it: When building topical authority around a central entity, when launching a new content strategy, when Knowledge Panel attributes are incomplete, or when content is not ranking despite adequate links.

Source: Koray Tugberk's Entity SEO methodology (Topical Authority and Semantic SEO Course — Lessons 9, 38, 46, 68, 78, 84)

Patent & Research Foundation

Entity-Attribute-Value (E-A-V) Patent Basis

US20150127617A1 - Entity Salience (2015) 4 factors determine entity importance to a document:

Position (earlier = higher salience)
Frequency (more mentions = higher salience)
Centrality (more connections to other entities = higher)
Co-occurrence (appears near related entities = stronger signal)

US8594996B2 - Entity Recognition & Disambiguation (2012-2014)

Named Entity Recognition extracts entities from content
Entity type classification (Person, Organization, Place, etc.)
Context used to resolve ambiguous entities
Knowledge base integration for entity confirmation

US20120158633A1 - Knowledge Graph (2012)

Entity-attribute-relationship database
Standard attributes for each entity type
Cross-entity relationship mapping

The E-A-V Model

Every piece of content follows: Entity → Attribute → Value

Entity:    Water
Attribute: Benefits
Value:     Hydration, cognitive function, temperature regulation

Entity:    Germany
Attribute: Population
Value:     83 million people

Entity:    QR Code
Attribute: Types
Value:     Static QR codes, Dynamic QR codes

The Three Attribute Types

1. Root Attributes Attributes that appear in ALL instances of the entity class.

City: population, area, mayor, demographics, parks
Product: price, dimensions, materials, manufacturer
Person: name, date of birth, nationality, occupation

Purpose: Provide accuracy and comprehensiveness.

2. Rare Attributes Attributes that appear in SOME but not all instances.

City: nuclear plant, beaches, historic sites (only cities that have them)
Product: organic certification (only certified products)

Purpose: Qualify and differentiate the specific entity.

3. Unique Attributes Attributes that exist ONLY for a specific instance.

Paris: Eiffel Tower
Coca-Cola: secret formula mythology
Amazon: two-day delivery standard

Purpose: Highest relevance signal. A unique attribute functions as a SYNONYM for the entity itself.

Attribute Prioritization

Order of content priority:

1. UNIQUE attributes FIRST
   → Highest relevance
   → Functions as synonym for entity
   → Establishes definitional identity

2. ROOT attributes SECOND
   → Accuracy and comprehensiveness
   → Shows complete entity coverage
   → Required for Knowledge Graph completeness

3. RARE attributes THIRD
   → Qualification and differentiation
   → Separates entity from generic competitors
   → Builds topical depth

Audit Methodology

Phase 1: Central Entity Identification

Define the central entity for the site:

What entity appears in EVERY article across the site?
What is the site's monetization model linked to?
What entity has the most query networks in this niche?

Example entities:

Roofing contractor → Entity: "Roofing" / "Roofing Contractor"
Health supplement → Entity: "Magnesium" (if that's the product)
Law firm → Entity: "Family Law" + geographic entity

Phase 2: Root Attribute Mapping

List all root attributes for the entity type. These are MANDATORY coverage areas.

Attribute Audit Table:

Root Attribute	Content Exists?	Schema Markup?	KG Confirmed?	Gap Level
[Attribute 1]	Yes/No	Yes/No	Yes/No	None/Low/High
[Attribute 2]	Yes/No	Yes/No	Yes/No	None/Low/High
[Attribute 3]	Yes/No	Yes/No	Yes/No	None/Low/High

Phase 3: Rare Attribute Identification

For the specific entity, which rare attributes apply?

Method: Search "[entity] [potential rare attribute]"
       Check if competitors cover this attribute
       Check if the entity actually has this attribute
       Verify with primary sources

Examples for a roofing contractor entity:
- Emergency services (24/7 availability) — if offered
- Specific certifications (GAF certified, etc.)
- Specialty materials (metal roofing, TPO, etc.)
- Geographic specialization

Phase 4: Unique Attribute Discovery

What is UNIQUE to this specific entity instance?

For a roofing company:
- Specific warranty terms no competitor offers
- Unique financing program
- Proprietary inspection process
- Specific awards or recognition
- Years in business + specific founding story
- Specific neighborhoods or zip codes served

These unique attributes should be:
1. Featured prominently in schema (description)
2. Mentioned in the first paragraph of relevant pages
3. Consistently referenced across all content
4. Used as differentiators in service area pages

Phase 5: Content-Schema Alignment Check

For each identified attribute:

[ ] Attribute mentioned in content (yes/no)
[ ] Attribute present in schema markup (yes/no)
[ ] Schema accurately reflects content claims (yes/no)
[ ] Value is specific (numbers, measurements, facts) vs. vague
[ ] Consistent value across all pages mentioning this attribute

Critical rule from Koray: If you say "3.8 liters" on one page and something different on another, you're writing random articles — the search engine detects this inconsistency and reduces entity confidence.

Phase 6: Attribute Chain Mapping

For key attributes, map the chain:

Attribute: [roofing materials]
Chain:
  Define the attribute → What is roofing material?
  Measure it → Durability ratings, cost per square
  Calculate it → Material needed for given roof size
  Change it → How to select the right material
  Effect → How material choice affects home value, energy efficiency

Each step in the chain = a content opportunity

Scoring

Score	Interpretation
90-100	Entity fully mapped — all root, rare, and unique attributes covered
75-89	Minor gaps — primarily rare or unique attributes missing
60-74	Significant gaps — root attributes missing or inconsistent
Below 60	Major work needed — entity not properly established

Anti-Patterns (Common Mistakes)

WRONG: Treating entities as keywords instead of things with attributes
RIGHT: Define the entity, map its attributes, cover each attribute

WRONG: Inconsistent values across pages (contradicting yourself)
RIGHT: Verify every value once, use that value consistently site-wide

WRONG: Creating quality nodes for easy, low-competition topics
RIGHT: Quality nodes target hard, authority-level queries first

WRONG: Not connecting attributes back to the central entity
RIGHT: Every attribute section connects to the site's central entity

WRONG: Using different structures for entities of the same class
RIGHT: Template one methodology and apply consistently to all instances

Entity Extraction Audit — Entity signals in existing content
Knowledge Graph Gap Filler — KG completeness
Phrase-Based Optimizer — Topical phrase coverage

Audit 20: Entity Attribute Audit ​

Title & Description ​

Patent & Research Foundation ​

Entity-Attribute-Value (E-A-V) Patent Basis ​

The E-A-V Model ​

Every piece of content follows: Entity → Attribute → Value ​

The Three Attribute Types ​

Attribute Prioritization ​

Audit Methodology ​

Phase 1: Central Entity Identification ​

Phase 2: Root Attribute Mapping ​

Phase 3: Rare Attribute Identification ​

Phase 4: Unique Attribute Discovery ​

Phase 5: Content-Schema Alignment Check ​

Phase 6: Attribute Chain Mapping ​

Scoring ​

Anti-Patterns (Common Mistakes) ​

Related Audits ​