Foundations

What Is a Central Entity?

A central entity is the one entity a website is about, defined in a single sentence that every page inherits. The central entity sets the homepage H1, the predicates the site uses, and the first attribute set the topical map covers.

Central entity, illustrated
Flow from business lines to source context to the central entity, then to central search intent and the homepage H1
The central entity sits between what the business sells and what the homepage says. Source context shapes it, and the H1 states it.

How do you identify the central entity of a website?

The central entity is the one entity that every service, product, and page on the site describes or connects to.

Start with what the business earns from. List every service or product line, then find the entity they all share. Digital Vikingz sells audits, architecture, content production, and development, and all four describe one entity: semantic SEO. A dental clinic's implants, crowns, and hygiene visits share one entity too: dental treatment.

Test the candidate with one sentence. The sentence names the business, the entity type, the audience, and the market in under twenty-five words. A candidate that needs two sentences or two entity types is too broad. A candidate that leaves out a line the business earns from is too narrow.

The central entity is a thing, not a phrase. Search demand confirms the choice but does not make it. A high-volume keyword that the business touches only at the edge is an attribute or a separate topic.

How do source context and central search intent shape a central entity?

Source context is the angle a site speaks from, and central search intent is the task users bring to its central entity.

Two sites share a central entity and still differ in source context. An agency, a course provider, and a software vendor all publish about semantic SEO. The agency sells implementation, the course provider sells learning, and the vendor sells a tool. Each source ranks different attributes first and uses different verbs.

Central search intent follows from the source context. An agency's users want someone to do the work. A course provider's users want to learn the work themselves. The homepage H1 matches that one intent, and every core page serves a step of it.

Both terms come from Koray Tuğberk Gübür's semantic SEO framework. Source context also decides which content the site leaves unpublished. A page written from a different angle spends trust that the main angle earned.

How does the central entity set the homepage H1 and the predicates?

The homepage H1 joins the central entity to the central search intent, and predicates are the verbs linking the entity to its audience.

The H1 reads as the query a user types to reach the business. The first sentence after it names the brand, the entity type, the audience, and the market. A project management SaaS opens with the product name, the category, and the teams it serves. The homepage, the About page, and the main service pages each target a different query, so they never compete.

Predicates come from the source context. An agency audits, maps, writes, and builds. A clinic examines, treats, and restores. The site picks one verb per relationship and records it before writing, and the source term vector holds the full list.

The predicate set also shapes the core pages. Each core page states one relationship between the central entity and an attribute, using the recorded verb. A service page about audits uses audits in its H1, its first sentence, and its section openers. Readers and parsers meet the same verb for the same relationship everywhere.

What is the first attribute set of a central entity?

The first attribute set is the short list of properties buyers ask about the central entity before any other question.

A service entity usually carries five: what it is, what it includes, who it is for, how it runs, and what sets its price. A project management SaaS carries features, integrations, pricing, and alternatives. Each attribute in the first set becomes a node in the core section of the topical map.

The first set is not the full set. Secondary attributes, related entities, and definitions belong to the outer section and link inward. Attributes rank by how often buyers ask about them, and that rank sets the order of sections on the homepage.

Each first-set attribute needs a value the business confirms before writing. A service with no stated scope or pricing basis leaves the attribute empty. An empty attribute gives search engines nothing to match.

How does a business with more than one line choose its central entity?

A business with several lines keeps one central entity when the lines share an audience and verbs, and separates them otherwise.

Shared audience and shared predicates mean one entity with sub-entities. An agency that sells semantic SEO and website development serves the same buyer, and development is how the SEO work ships. Development becomes an attribute of the central entity, not a second one.

Different audiences and different predicates mean two sources. A dental clinic that also sells supplies to other clinics speaks to patients in one line and to equipment buyers in the other. The clinic treats, and the shop sells. Those lines need separate sections with separate vocabularies at minimum, and often separate domains.

Forcing two unrelated lines under one central entity produces a homepage H1 that serves neither. The vocabulary drifts between the two. Internal links then pass signals across topics that share no buyers.

What does Google's entity metrics patent describe about entity types?

A Google patent on ranking search results by entity metrics describes combining relatedness, notable type, contribution, and prize metrics, weighted per entity type.

The patent draws those metrics from a knowledge graph. The weights differ for each entity type. A clinic and a software product are therefore scored on different mixes of the same metrics.

The patent describes a method, not a confirmed ranking factor. The design logic it supports is plain. A site states its entity type in the first sentence and keeps that type the same on every page. The agency reads a central entity typed three ways as three weak entities instead of one clear one.

A site controls how it connects its central entity to related entities. Consistent connections on every page state one set of relationships. Mixed connections state several, and none of them clearly.

Questions about what is a central entity

Is the central entity the same as the brand name?
Sometimes. A product company's brand is often its central entity, typed by its category. A service business treats the service as the central entity and the brand as the source that provides it.
Should a SaaS site use the product or the category as its central entity?
The product, typed by its category. The first sentence names the product and the category together, so the site owns the product and connects it to the category buyers search. Comparison and alternatives pages then sit in the core section as attributes of the product.
Can the central entity of a site change?
Yes, when demand or the business moves. A change rewrites the homepage H1, the predicate set, and the core section of the topical map. The change runs as a planned architecture update, never as a quiet edit.
Does a local business put the location in its central entity?
No. The location qualifies the central entity rather than replacing it. The homepage H1 pairs the service with the market users name, and the service stays the entity every page describes.
Who decides the central entity in an engagement?
The founder or product owner decides it with the strategist. Two working sessions produce the written definition and the first vocabulary list. The definition is signed off before any page is planned.
What does a written central entity definition contain?
One paragraph that states what the business is, for whom, and where. An alias list follows, with every other name the entity goes by. The predicate set closes the document, one verb per relationship.
What happens when a site has no clear central entity?
Pages compete for loosely related queries, and none carries enough weight to rank consistently. The vocabulary drifts, and internal links point in every direction. An audit usually finds the problem in the homepage's first sentence.
Does every page need to name the central entity?
No. Every page states an attribute of the central entity or connects it to another entity. The name appears where that relationship is stated. Repetition beyond that adds tokens without adding facts.
Does a central entity need a knowledge panel?
No. Many service businesses have no knowledge panel. The site defines the entity through consistent statements across its pages and identical name, address, and category details in directory listings.
Does a multilingual site keep one central entity?
Yes. One central entity and one topical map serve every language. A native editor writes the definition and the vocabulary for each language, and the page decisions stay the same.
Is a central entity the same as a primary keyword?
No. A primary keyword is a string with a search volume. A central entity is a thing with a type, attributes, and relationships, and many keywords point to it.
Usman Ishaq, founder and CEO of Digital Vikingz
Written by Usman IshaqFounder and CEO, Digital Vikingz. Koray Tuğberk Gübür Semantic SEO Fundamentals certified. Mechanical engineering background.Reviewed September 2026. Profile
Book a callWhatsApp