What is an entity in SEO? The thing behind the phrase.
An entity in SEO is a distinct person, organization, product, place, event, concept, technology, topic, or other identifiable thing that a page refers to in a clear context.
A keyword is the word or phrase. The entity is the thing that word or phrase refers to. Entity work adds identity, type, attributes, relationships, and context so a page does not leave the intended meaning loose.
- Identity before repetition
- Attributes make the thing specific
- Relationships connect the wider topic
- Human review remains required
Entity Clarity Builder
Turn a name or phrase into a page-ready identity packet and MIRENA prompt.
This local builder reads only the fields shown here. It does not crawl the target, query Google, verify an identity, or send and store the values.
MIRENA entity clarity packet
Attributes
Relationships
Priority actions
Full MIRENA prompt
An entity is the identifiable thing a page refers to.
The name alone may not be enough. Clear entity work combines the name with a type, intended meaning, attributes, relationships, and a stable page role.
The practical distinction
A query can contain a keyword. A page can repeat that keyword. Neither step settles which thing the page means.
Entity clarity begins when the page names the thing, says what kind of thing it is, explains the intended context, and supports that identity with facts or relationships.
The definition page should stop there. Detailed work on attributes, disambiguation, hierarchy, salience, entity maps, and audits belongs on the sibling pages that own those tasks.
Entity: the thing behind the phrase.
Identity
Name the distinct thing and state what the page means by that name.
Type
Classify the entity as a person, organization, product, service, place, event, concept, technology, topic, or another supported type.
Attributes
Record the facts, properties, roles, features, or traits that make the identity specific.
Relationships
State how the entity connects to people, organizations, products, places, concepts, or pages.
Context
Keep the intended meaning close to the name so readers and systems do not have to guess.
Keyword, term, entity, attribute, and relationship are different jobs.
Keeping these units separate stops a definition page from treating every related word as the same kind of signal.
| Unit | What it is | Example | Page planning question |
|---|---|---|---|
| Keyword or query phrase | Language a person may type or that a page may use. | “MIRENA SEO” | Which user question or demand does the phrase represent? |
| Defined term | A word or phrase given a formal definition in a glossary, classification, or concept page. | “entity salience” | What exact definition and scope does this page own? |
| Entity | The distinct thing that the name or phrase refers to. | MIRENA | What is it, which type fits, and which page owns the identity? |
| Attribute | A property, fact, role, feature, category, date, or location that describes the entity. | 20-agent workflow | Is the detail supported, useful, and placed near the entity it describes? |
| Relationship | A connection between two entities. | Kevin Maguire created MIRENA. | Which source supports the connection and which page owns it? |
An entity can be tangible, abstract, commercial, personal, local, or technical.
The type should describe the thing shown on the page. It should not be selected only because a markup type exists.
Kevin Maguire
A named individual with a role, work, relationships, and identity routes.
Semantec SEO
A company or brand with a stable home, founder, contact details, and product relationships.
MIRENA
A named software product with a creator, provider, category, working lanes, and limits.
SEO audit
A service with a provider, user job, scope, delivery model, and support path.
County Kildare
A physical location that can relate to a person, organization, event, or service area.
Workshop
A named occurrence with dates, status, location or access details, organizer, and audience.
Semantic SEO
An abstract idea defined through scope, related concepts, examples, and distinctions.
JSON-LD
A technical format or system described through purpose, syntax, relationships, and supported use.
Entity SEO
A subject area that can own a hub while narrower concepts own separate pages.
Distinct thing
A valid identity may use another supported class after the thing and evidence are clear.
The same word can point to more than one entity.
Type, context, attributes, and relationships separate the intended meaning. Repeating the word does not.
Name alone: unclear. Two plausible meanings need different page homes, attributes, relationships, and supporting links.
Organization or brand
The page context would identify a company and connect it to products, people, industry, and official identity routes.
- Type
- Organization
- Attribute direction
- Products, founder, category, market
- Relationship direction
- Creates, employs, owns, provides
Fruit
The page context would identify a fruit and connect it to plant, variety, food, nutrition, or cultivation concepts.
- Type
- Food or biological thing
- Attribute direction
- Variety, colour, taste, growing conditions
- Relationship direction
- Grows on, belongs to, used in
One entity leads. The others support or route elsewhere.
The hierarchy stops the definition page from competing with the pages for attributes, relationships, salience, and entity maps.
Page owner
The entity that owns the title, H1, opening answer, and dominant page job.
Close supporting entities
The concepts needed to explain the main entity through important headings, comparisons, or relationships.
Attributes, examples, and routes
The facts and nearby concepts that add clarity without taking over the page.
How the hierarchy changes this page
“Entity in SEO” owns the definition. Keywords, attributes, relationships, disambiguation, salience, entity maps, internal links, and structured data support that definition.
- Give the direct definition early.
- Use one short distinction table.
- Show one ambiguity example.
- Route specialist tasks to their own pages.
- Keep the commercial action after the definition, method, and limits.
What the public technical sources support.
Official documentation supports entity search, explicit page clues, and formal definitions. It does not turn a content checklist into a ranking promise.
Entity search
Google’s Knowledge Graph Search API can search for entities such as people, places, and things and returns structured results using Schema.org types and JSON-LD.
Read the Knowledge Graph API documentation ↗Explicit page clues
Structured data gives explicit clues about page meaning. The markup should describe the content of the page where it appears.
Read the structured-data introduction ↗Defined terms
DefinedTerm is a Schema.org type for a word, name, acronym, or phrase with a formal definition. It can describe a glossary or classification term.
Read the DefinedTerm specification ↗No automatic outcome
Clear entity copy and valid markup do not guarantee crawling, indexing, rankings, rich results, Knowledge Graph inclusion, or a Knowledge Panel.
Read how Google Search works ↗Seven decisions turn an entity name into a page operating plan.
The workflow settles identity before it expands the page. It ends with visible-copy and route checks before candidate markup can move forward.
Name the entity
Choose the stable name and useful aliases. Do not begin with a loose cluster label when one distinct thing owns the page.
Assign the entity type
Classify the thing in plain language before choosing page structure or a markup type.
State the intended meaning
Write one context sentence that separates this entity from other meanings, names, products, or nearby concepts.
List defining attributes
Add only the properties that help identify, explain, compare, or verify the entity on this page.
Map relationships
Connect the entity to the people, organizations, products, concepts, pages, or evidence routes that genuinely belong.
Assign the page role and entity home
Decide which page owns the identity and which sibling pages explain attributes, relationships, salience, or support.
Check visible copy, links, and candidate markup
Confirm that names, facts, routes, and relationships agree before any structured data becomes active.
MIRENA is the product. Semantec SEO is the organization. Kevin Maguire is the person.
Separating those identities gives each entity a stable role, a clear page home, and relationships that can be stated without mixing product, company, and person facts.
MIRENA identity packet
This example uses current first-party Semantec SEO product and founder copy. It still needs human review before markup or publication.
- Name
- MIRENA
- Type
- Product or SoftwareApplication candidate
- Current product home
- https://semantecseo.com/
- Working description
- 20-agent SEO operating system with site planning, page brief, and draft or rewrite lanes
- Outcome boundary
- No ranking guarantee; human review required
Move from the definition into the page that owns the next decision.
This page defines the model. The cluster pages below handle identity choice, detail, relationships, ambiguity, hierarchy, prominence, and full-page review.
Choose the primary entity
Decide which one concept owns the title, H1, opening answer, and page purpose.
Open Main Entity Selection →Map defining attributes
Place the facts, roles, properties, and features that make the entity clear.
Open Entity Attributes →State entity relationships
Show how people, organizations, products, places, concepts, and pages connect.
Open Entity Relationships →Separate competing meanings
Use type, context, attributes, naming, and routes to make the intended identity clear.
Open Entity Disambiguation →Set the entity hierarchy and prominence
Assign primary, secondary, and supporting roles, then check which entity stands out.
Open Entity Hierarchy →Build or review the entity map
Join identity, attributes, relationships, hierarchy, page ownership, routes, and review notes.
Open Entity Map →Entity SEO FAQ
What is an entity in SEO?
An entity in SEO is a distinct person, organization, product, place, event, concept, technology, topic, or other identifiable thing that a page refers to in a clear context.
Is an entity the same as a keyword?
No. A keyword is a word or phrase used in a query or page. An entity is the thing that the word or phrase refers to. One phrase can point to several entities.
Is every noun an entity?
No. A noun can be generic or unclear. Entity work starts when the page identifies a distinct thing, assigns a type, and supplies enough context, attributes, or relationships to make the intended meaning clear.
What can count as an entity?
Common entity types include people, organizations, brands, products, services, places, events, technologies, and concepts. The correct type depends on the thing described and the visible evidence on the page.
What are entity attributes?
Entity attributes are the properties or facts that describe an entity, such as a person's role, an organization's founder, a product's category, or a place's location.
What are entity relationships?
Entity relationships state how one entity connects to another. A product can be created by a person, provided by an organization, built for a task, or related to a wider concept.
What is entity salience?
Entity salience is the prominence of an entity within a page or passage. In page planning, it helps the team check which entity leads and which entities support it.
How do you disambiguate an entity?
State the entity type and intended meaning, place defining attributes nearby, use clear relationships, keep naming stable, and route readers to the page that owns that identity.
Do entities replace keyword research?
No. Query research shows the language and demand around a need. Entity planning clarifies the thing being discussed and how that thing connects to the page, site, and user task.
Can structured data create an entity?
Structured data can provide explicit clues about visible page content, but it does not create truth, prove an identity, or guarantee inclusion in a knowledge system. Visible facts and stable page identity come first.
Does entity SEO guarantee rankings or a Knowledge Panel?
No. Clear entity work can improve page planning and interpretation, but it does not guarantee crawling, indexing, rankings, rich results, Knowledge Graph inclusion, or a Knowledge Panel.
What should I do after identifying an entity?
Map the entity's attributes and relationships, choose the primary and supporting hierarchy, assign a stable page home, add contextual internal routes, and review the complete page before activating markup.
Settle the entity before the page starts to drift.
Build the local packet, copy the full MIRENA prompt, attach the source material, then route the result into an entity map, brief, audit, or rewrite.