What Is Entity SEO? Entities, the Knowledge Graph and sameAs

Entities, the Knowledge Graph and key terms

An entity is a single, distinct thing that can be identified: a person, an organisation, a place, a product, a book, an event or a concept. "Taj Mahal" is an entity; so is "Reserve Bank of India". What makes something an entity is not the words used to name it but the fact that it can be told apart from everything else.

Google announced its Knowledge Graph in 2012 with the phrase "things, not strings". It is a large database of entities and the relationships between them, such as who founded a company or which city a monument stands in. Google uses it to understand queries and to show information panels. The semantic SEO guide explains how this meaning-based approach shapes the way pages are interpreted.

"Entity SEO" itself is an industry term, not an official Google programme. Google does not publish a list of entity signals, so treat the advice here as good practice for clarity rather than a ranking formula.

How search engines recognise and disambiguate entities

When a crawler reads a page, language-processing systems look for names and phrases that match known entities. The hard part is ambiguity. "Mercury" might be a planet, a chemical element or a car brand. "Apollo" might be a hospital group, a space programme or a Greek god. Search systems use the surrounding words, the topic of the whole site, links to and from the page and structured data to decide which one is meant.

For a small business, the risk is usually the opposite: the search engine has never connected your name to a single, clear entity at all. If your company appears as "Sharma Tutorials", "Sharma Tutorial Classes" and "STC Jaipur" on different sites, those may look like three unrelated things. Consistency across your own site and other profiles gives systems more chances to link the mentions together.

Examples: Organization and Person schema with sameAs

Schema.org structured data lets you state entity facts explicitly. The sameAs property lists URLs of other pages that unambiguously represent the same entity, such as an official social profile, a Wikipedia article or a Wikidata item. Add it in JSON-LD as described in the schema markup guide.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.in/#organization",
  "name": "Sharma Tutorials",
  "url": "https://www.example.in/",
  "logo": "https://www.example.in/images/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example-sharma-tutorials",
    "https://www.youtube.com/@example-sharma-tutorials"
  ]
}
</script>

A person who writes for the site can be described the same way, with a link back to the organisation through worksFor. The @id values give each entity a stable identifier that other markup on the site can refer to.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://www.example.in/team/anita-sharma/#person",
  "name": "Anita Sharma",
  "jobTitle": "Founder",
  "worksFor": { "@id": "https://www.example.in/#organization" },
  "sameAs": ["https://www.linkedin.com/in/example-anita-sharma"]
}
</script>

Step by step: building your entity footprint

1. Choose one canonical name for the organisation and each key person, and use it the same way everywhere: site header, footer, profiles and business listings.
2. Build an entity home page: usually the About page for an organisation and an author page for a person. It should state plainly who or what the entity is, what it does, where it is based and how it connects to other entities.
3. Add structured data on that page with Organization or Person, a stable @id and sameAs links.
4. Align external profiles such as your Google Business Profile, LinkedIn and industry directories so the name, address and description match. This overlaps heavily with local search work.
5. Link internally from articles to the author page and from product or service pages to the relevant topic pages, so the site itself maps the relationships.
6. Earn independent mentions on relevant, trustworthy sites, as covered in the off-page SEO guide.

Knowledge Panels and internal linking around entities

A Knowledge Panel is generated automatically from the Knowledge Graph. You cannot buy or request one into existence. If a panel already appears for you or your organisation, Google offers a verification process so an authorised representative can claim it and suggest corrections through the feedback option. Corrections are reviewed, not applied instantly.

Inside your own site, internal links act as statements about relationships. An article about GST filing that links to a "GST" topic hub, and to the author page of the chartered accountant who wrote it, tells crawlers how the topic, the content and the expert fit together. The internal linking guide covers anchor text and site structure in more depth, and the E-E-A-T guide explains why clear authorship helps readers judge trust.

Good practice for entity clarity

• Describe each entity in plain words on its home page before adding any markup. Structured data should repeat what the page says, not replace it.
• Keep contact details, founding year and leadership names identical across the site and external profiles.
• Use the full entity name at least once on key pages, then shorter forms, so the link between them is clear.
• Cover the topics your organisation is known for in depth, which supports the topical authority that makes the entity easier to associate with a subject.
• Validate markup with Google's Rich Results Test or the Schema Markup Validator after every template change.

Practical exercise: map and mark up one entity

Pick a real organisation you are allowed to work on, such as your employer, a family business or your own portfolio site.

1. Search for the organisation's name and list every variant of the name you find across the first two pages of results and its social profiles.
2. Decide on the canonical name and write a two-sentence description of the entity.
3. Write Organization JSON-LD with @id, name, url, logo and at least two accurate sameAs URLs.
4. Test it in the Schema Markup Validator and fix every error.

You are done when you have a written list of name variants with a plan to align each one, and valid JSON-LD that matches the visible About page. Entity and structured data work is also part of the advanced SEO course at SkillNewton.

Common mistakes

• Using several versions of the business name across the site, listings and social profiles.
• Adding sameAs links to profiles that are inactive, belong to someone else or describe a different entity.
• Marking up facts in JSON-LD that do not appear anywhere on the visible page.
• Treating a Knowledge Panel as something that can be requested or bought rather than earned through clear, consistent information.
• Publishing articles without named authors or author pages, which leaves the person entity undefined.

Frequently asked questions