Number of Distinct Entities Used counts how many entities from the analysis run’s entity list appear at least once in the target page body — a measure of topical breadth, not repetition. It returns a whole-number count, and a value of 0 can mean either that no entities matched or that no entity list was available for the run, so read a 0 carefully before acting on it.
| Factor ID | RG-ENT-018 |
|---|---|
| Family | Entities |
| Measurement | Distinct-item count |
| Measured zone | Rendered page body |
What it measures
This factor counts how many entities from the run’s entity list appear at least once in the target page body. Entities can represent people, organizations, places, products, concepts, or other named subjects associated with the query. The signal is about breadth of coverage — how much of the relevant entity set the page touches. Repeating the same recognized entity does not raise the count; each distinct entity is counted once whether it appears a single time or many times.
How RankGear measures it
RankGear receives or derives an entity list for the search run, lowercases the rendered, script-free page body, and checks whether each list entry appears as a substring of that text. Every entity that appears contributes one to the result. If the entity list is empty or the configured entity provider returned no data, the factor returns 0. Because the check uses substring presence, it can occasionally recognize an entity string that sits inside a longer piece of text.
How to read it
| If the value is… | Read it as |
|---|---|
| 0 | Either no listed entities appear in the body, or no entity list was available for the run. Confirm which before treating it as a coverage gap. |
| Low relative to the ranking field | Competitors cover entities this page omits. Identify the ones genuinely central to the subject and search intent, then add them with real explanation. |
| High but padded with off-topic names | Breadth without relevance. Irrelevant entities dilute topical focus rather than help — prune or contextualize them. |
How to optimize it
Compare the target page’s entity coverage with the ranking field and identify entities that are missing yet genuinely important to the subject and search intent. Add them through useful explanations, relationships, examples, citations, specifications, or supporting sections. Prioritize entities that help a reader understand the topic — explain what each one is and why it matters rather than inserting names without context. Treat the count as an observation about coverage, not a target to inflate: more entities are not automatically better.
Important considerations
- A value of 0 can mean no entities were found, but it can also mean no entity list was available for the run.
- More entities are not automatically better; irrelevant names can dilute clarity and topical focus.
- The factor does not verify factual accuracy or whether an entity is discussed meaningfully.
- Entity recognition depends on the specific list used for that run, and substring matching can occasionally catch an entity string inside longer text.
- Use competitor adoption, correlation, and the selected target to decide whether a coverage gap is actionable. This is a prioritization signal that relates to position within a measured result set — it does not by itself make a page rank or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.