EntitySEO.wikiThe Entity SEO Reference

Finding entities

From EntitySEO.wiki, the entity SEO reference · Published · Updated · By · Published by Local Blitz · How we research

To find the entities that matter for a topic, combine six methods: look up candidates in Google’s Knowledge Graph Search API and in Wikidata, run your and competitors’ text through Google Cloud’s Natural Language API, inspect search results and knowledge panels, read competitors’ structured data, and list the related entities that keep appearing together. Then record each entity with its identifier in an entity map.

Which methods should you use?

MethodBest forCostGuide
Knowledge Graph Search APIDoes Google have this entity? What ID and type?API keyGuide to With the Knowledge Graph API
WikidataIDs, properties, official links, relationshipsFreeGuide to With Wikidata
Natural Language APIWhich entities a text mentions and how central they arePaid beyond free tierGuide to With Google’s Natural Language API
SERP and knowledge panelsHow Google presents an entity to searchersFreeGuide to In SERPs and knowledge panels
Competitor schemaWhich entities competitors declare in JSON-LDFreeGuide to In competitors’ schema
Related entitiesWhat a complete page on a topic must mentionFreeGuide to Related entities and co-occurrence

What should you look for?

What is a practical workflow?

  1. List seed topics and your own entities.
  2. Look each up in the Knowledge Graph Search API and Wikidata; record IDs.
  3. Search Google for each and note panels, “People also ask” questions and related searches (SERP inspection).
  4. Run the top-ranking pages and your page through the Natural Language API; compare entity lists.
  5. Extract competitors’ JSON-LD (competitor schema).
  6. Group everything in an entity map and assign entities to pages.

This workflow is practitioner practice; no search engine publishes an official entity-research method. Practitioner practice

What are the pitfalls?

Finding entities with the Natural Language API

Google Cloud’s Natural Language API extracts entities from text. Send a document to the analyzeEntities method and you get each entity’s name, type (PERSON, ORGANIZATION, LOCATION and others), mentions and, in the v1 API, a salience score from 0 to 1 showing how central it is, plus a Knowledge Graph MID and Wikipedia URL when one is known. It is a useful proxy, not Google Search’s own analysis.

What does analyzeEntities return?

Per Google Cloud’s documentation:[1][3][4] Officially documented

The v2 reference describes a probability on mentions rather than salience, so use the v1 endpoint if you need salience.[4]

How do you run it?

  1. Enable the Cloud Natural Language API in a Google Cloud project and set up credentials.[1]
  2. Send the page’s main text (not the navigation) to the endpoint:
POST https://language.googleapis.com/v1/documents:analyzeEntities
{"document": {"type": "PLAIN_TEXT", "content": "Local Blitz is a marketing agency in Encinitas, California..."},
"encodingType": "UTF8"}
  1. Sort entities by salience and note which have a mid.
  2. Repeat for the top-ranking pages on the same query and compare.

How do you read the results?

ObservationPossible action
Your main entity is not the most salientName and define it earlier; make it the subject of sentences
Entity has no midThe API could not link it to a known entity; add context such as location or type
Competitors mention entities you do notCheck whether they belong in a complete answer (related entities)
Wrong entity linked (same name)Add disambiguating attributes in the text

These actions are practitioner interpretations. Practitioner practice Chasing a salience number is not a goal in itself; see entity salience.

What are the limits?

Finding entities in SERPs and knowledge panels

Search results show how Google interprets an entity. Search the name (and variations), then record whether a knowledge panel appears and what it says, which related entities and questions are shown, what sources Google cites, and whether AI Overviews describe the entity correctly. Repeat in a private window and from relevant locations.

What should you record?

SERP featureWhat it tells you
Knowledge panelGoogle has an entity; check type, description, facts, image and source links[5]
Business ProfileLocal entity details: name, category, address, reviews[6]
“People also ask”Questions searchers link to the entity; candidates for H2s and FAQs
Related searchesAssociated entities and attributes
Carousels and listsEntities Google groups together (for example people in a company)
Top organic resultsWhich sources Google trusts for the entity: profiles, directories, press
AI OverviewsHow AI answers summarise the entity and which pages they cite[7]

How do you run a SERP entity check?

  1. Search the exact name, then the name plus a qualifier (city, industry, role).
  2. Use a private window, since results can be personalised by history and location.[8]
  3. Screenshot the panel and note every fact and its source link.
  4. List the domains ranking for your brand name; these are the sources engines associate with you.
  5. Note any same-named entities appearing instead of yours.
  6. Repeat monthly and log changes (measuring entity SEO).

This routine is practitioner practice. Practitioner practice

How do you read a knowledge panel for entity clues?

Can you check AI answers the same way?

Yes. Ask Google AI Mode, ChatGPT search and others who or what the entity is, and note errors and cited sources. See entities in AI search.

Finding entities in competitors’ schema

Competitors’ structured data shows which entities they explicitly declare: their Organization or LocalBusiness details, authors, sameAs profiles, services, and about or mentions properties. Extract it with Google’s Rich Results Test, the Schema Markup Validator or your browser’s view-source, then compare types, properties and entity links with your own markup.

How do you extract competitor schema?

  1. Schema Markup Validator (validator.schema.org): paste a URL to see all schema.org data, including types Google does not use for rich results.[9]
  2. Rich Results Test: shows which Google rich result types are detected and any errors.[10][11]
  3. View source: search for application/ld+json to read the raw JSON-LD.

All three are Officially documented tools. JSON-LD added by JavaScript may only appear in the rendered view.[12]

What should you record?

Look atWhy
@typeHow they classify themselves (for example a specific LocalBusiness subtype)
@idWhether they build a connected entity graph
sameAsWhich profiles and databases they link as identity references
author, founder, employeeWhich people they connect to the brand
about, mentionsTopic entities they declare, sometimes with Wikidata or Wikipedia links
areaServed, knowsAboutService areas and claimed expertise

How do you use what you find?

Only mark up what is true and visible on your own pages; Google’s guidelines prohibit misleading or irrelevant markup.[8] Officially documented Competitors’ markup can be wrong, so check claims against Google’s documentation.[13]

A worked example from Google’s documentation

Google Cloud’s entity-analysis guide describes the method as inspecting text “for known entities (proper nouns such as public figures, landmarks, etc.)” and returning information about them.[3] Its sample sentence is: “President Trump will speak from the White House, located at 1600 Pennsylvania Ave NW, Washington, DC, on October 7.” In the guide’s sample output:[3]

The sample also shows that linking is uneven: the street “Pennsylvania Ave NW” (type LOCATION) comes back with a mid but no wikipedia_url, while the White House and Washington, D.C. have both.[3] For your own audits (inference): a mid or wikipedia_url means the system linked the name to something it knows; its absence means the name was typed but not linked. Practitioner practice Google says each document needs its own request, so audit page by page.[3]

Frequently asked questions

What is the easiest free way to find entities?

Search Google and Wikidata for the topic, note the knowledge panel, related searches and Wikidata properties, and read the top pages' structured data.

Do I need paid tools?

No. The Knowledge Graph Search API needs an API key and the Natural Language API has usage costs beyond its free allowance, but Wikidata, SERP inspection and schema extraction are free.

Does Google Search use the Natural Language API?

Google has not said so. Treat the API as an approximation of how a machine reads your text, not as Google Search's view.

What is a good salience score?

There is no target. Salience is relative within one document; what matters is that the main entity is clearly the subject.

Why is there no salience in my results?

The v2 API reference replaces salience with mention probability. Use the v1 endpoint if you need salience.

Why do different people see different panels?

Google tailors results using factors such as location, language and search history, so results vary.

What if a competitor's panel shows for my brand name?

That signals a disambiguation problem. Strengthen your entity home, use consistent naming and add distinguishing facts; see entity disambiguation.

Is it OK to copy a competitor's schema?

Copy the structure, never the facts. Your markup must describe your own visible content accurately.

Why does the Rich Results Test show less than the validator?

The Rich Results Test only reports types Google supports for rich results; the Schema Markup Validator shows all schema.org data.

References

Pages accessed September 29, 2026 unless a date is given. See all sources and our editorial policy.

  1. ^ "Natural Language API basics". Google Cloud.
  2. ^ "Google Knowledge Graph Search API". Google for Developers.
  3. ^ "Analyzing entities". Google Cloud.
  4. ^ "Entity (REST reference, v1)". Google Cloud.
  5. ^ "About knowledge panels". Google Knowledge Panel Help.
  6. ^ "Tips to improve your local ranking on Google". Google Business Profile Help.
  7. ^ "AI features and your website". Google Search Central. Last updated December 10, 2025.
  8. ^ "General structured data guidelines". Google Search Central.
  9. ^ "Schema Markup Validator". Schema.org.
  10. ^ "Rich Results Test". Google Search.
  11. ^ "Rich Results Test (help)". Search Console Help.
  12. ^ "Generate structured data with JavaScript". Google Search Central.
  13. ^ "Introduction to structured data markup in Google Search". Google Search Central.