Join our community of websites already using SEOJuice to automate the boring SEO work.
See what our customers say and learn about sustainable SEO that drives long-term growth.
Explore the blog →<p>A practical way to check whether a page is semantically centered on its main entity—useful for diagnostics, but not an official Google metric and not strong enough to drive strategy on its own.</p>
<p>Entity Salience Ratio (ESR) is an unofficial SEO metric that estimates how much of a page’s recognized meaning is concentrated around its primary entity. I use it as a semantic focus check—not as a confirmed Google ranking factor or a standalone KPI.</p>
Entity Salience Ratio (ESR) is an unofficial SEO diagnostic I use to estimate how much a page’s machine-readable meaning is concentrated around its main entity. It is not a Google ranking factor. It is a proxy for topical focus.
When a system parses this page, does the main thing I meant to write about actually look like the main thing?
That framing matters more than the formula.
I used to be much more skeptical of this whole category of analysis. A few years ago, if you had asked me about entity salience ratio, I probably would have said it was one more made-up metric SEO people use to feel precise. Then I spent an afternoon debugging a glossary template on a SaaS site where half the pages were drifting off-topic after repeated edits—product marketing added positioning copy, support added definitions, SEO added adjacent keyword sections, and suddenly pages aimed at one concept were semantically centered on something else. The keyword targeting looked fine. The pages still felt wrong. Entity extraction made that visible fast.
So I revised my opinion. Not because ESR became magic. Because it became useful.
A page about Shopify should usually read, to both humans and machines, as mostly being about Shopify and the closely related things that explain Shopify. If the extracted entities are spread all over the place—Amazon, WooCommerce, POS systems, dropshipping, random founders, generic e-commerce concepts—the page may be semantically diluted. Sometimes that is intentional. Often it is just drift.
A common way people approximate ESR is by running page text through an entity extraction tool such as Google Cloud Natural Language API and comparing the salience of the primary entity with the salience of the rest of the detected entities. Google’s documentation for the API describes salience as a measure of how central an entity is within the text: https://cloud.google.com/natural-language/docs/analyzing-entities.
Two important caveats—before anyone gets carried away:
That means I treat ESR as a content analysis heuristic. Helpful. Imperfect. Easy to misuse.
Imagine a page contains these detected entities:
If the page is supposed to be about Apple’s iPhone lineup, but the extracted meaning is spread pretty evenly across Apple, Samsung, Google, and market commentary, the page may not feel tightly centered on the intended entity.
If Apple and iPhone-related entities dominate, that is usually a sign of stronger semantic focus.
The simplified formula most people use is:
ESR = salience of primary entity / total salience of relevant detected entities
Some practitioners use a stricter version:
ESR = salience of primary entity / salience of all detected entities
And in actual SEO work, I usually prefer a clustered version:
ESR = combined salience of primary entity + directly supporting entities / total salience
That last version tends to map better to reality. A page about Inception should mention Christopher Nolan, Leonardo DiCaprio, science fiction, dreams, and the release year. That does not make the page unfocused. It usually makes it complete. (Quick caveat: if you make the supporting cluster too loose, you can justify almost anything. I have seen teams do exactly that.)
Because keyword-level review misses a lot.
Most teams I talk to still evaluate pages with a mental checklist built around terms, headings, and maybe internal links. Useful, yes. But entity SEO adds a different question: does the page have a clear semantic center?
That becomes useful when pages are:
I find ESR most helpful on:
It is usually less useful on comparison pages, news roundups, market overviews, or anything intentionally built around multiple entities. A “Notion vs Asana vs Trello” page should not pretend one entity is the hero. That would be bad writing—and bad diagnosis.
Not with ceremony. Just a workflow.
On one Shopify store we worked with, a set of collection pages kept underperforming despite decent links and solid technical hygiene. When I checked the copy, the issue was obvious in hindsight: the pages were trying to rank for the category, educate first-time buyers, explain shipping, answer support questions, and pitch adjacent products on the same URL. The entity profile was chaos. After tightening intros, removing tangents, and splitting support content into separate URLs, the pages became much clearer. ESR did not cause the lift. It surfaced the mess. Important difference.
That is my main advice with on-page entity analysis: use it to notice problems, not to manufacture confidence.
There is no universal benchmark. I wish there were. There is not.
A narrow product page may benefit from a high concentration around one entity. A broad educational guide may need a more distributed profile. A category page sits somewhere in the middle. So I do not treat ESR as a KPI with fixed thresholds. I treat it as a comparative internal metric.
Good comparisons look like this:
I used to think high ESR was automatically better for any page with a clear target term. My mental model was wrong. Some of the best-performing pages I have seen had a lower ratio because they covered the entity with enough surrounding context to be useful. Thin pages can score “clean.” Rich pages can look more distributed. (Edit, mid-thought—actually, that is especially true for educational and investigative content.)
So if you are chasing a single number, stop. If you are comparing patterns across page types, keep going.
This part gets overstated a lot.
Google Cloud Natural Language API provides entity salience in its output. That makes it a convenient input for semantic SEO metrics. But Google’s public documentation for the API does not say that this exact score is used in Search ranking. And Google’s Search guidance is still centered on helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content.
So the safest interpretation is:
I know that sounds less exciting. It is also the version I trust.
This is the big one. Pages drift over time. People add sections with good intentions. Suddenly a URL meant to rank for one concept is carrying five jobs. ESR is useful because it makes dilution visible. Fast.
Low focus is not always caused by extra noise. Sometimes the page just fails to mention the entities that make the main topic understandable. A page about Tesla that barely references EVs, batteries, Model Y, charging, or Autopilot may look oddly thin in semantic terms.
If the title promises one thing and the body emphasizes another, entity extraction often catches it before rankings do.
I am careful here because people overclaim fast. No single ratio guarantees better performance in AI-driven surfaces. Still, in my experience, pages with clear semantic organization are easier for systems to summarize, retrieve, and cite. (Side note: this got more noticeable once teams started evaluating pages through answer-engine lenses instead of just blue-link rankings.)
A B2B software site we reviewed had a page targeting an entity-style query around a specific platform feature. On paper, the page looked optimized: keyword in title, keyword in H1, FAQs at the bottom, internal links from the nav. Yet the body spent huge chunks of space talking about the company’s broader philosophy, other products, integrations, and competitor framing.
When I ran the copy through entity extraction, the main feature entity was present—but it was not dominant. Related entities that should have supported it were weak, while company-level and market-level entities took too much share. We rewrote the introduction, renamed a few headings, cut unrelated positioning copy, added direct supporting concepts, and moved comparison content to a different URL.
The result was not some cinematic overnight ranking jump. More boring than that. The page became easier to understand, matched query intent better, and eventually performed more like the pages that were already winning for similar terms. Boring is fine. Boring pays bills.
If a page genuinely lacks focus, I usually test a few simple fixes:
The goal is not to “raise the ratio.” The goal is to make the page easier to interpret. For humans first, then machines.
Small distinction. Big effect.
Start here: Is the page supposed to center on one primary entity?
Can you clearly name that primary entity in one sentence?
Does the page underperform or feel semantically messy after edits?
Is the main entity missing or weak in the output?
Does a low ratio come from useful supporting context or irrelevant tangents?
Before you act on entity salience ratio, ask yourself:
If you cannot answer those comfortably, do not trust the ratio yet.
No. It is an unofficial diagnostic used by practitioners to estimate semantic focus.
No public Google documentation says that it is. I would not frame it that way with clients.
Many people use Google Cloud Natural Language API because it returns entity salience, though other NLP tools can help with similar analysis.
There is no universal good score. The useful benchmark is usually comparative: similar pages, similar intent, similar templates.
Yes. Comparison pages, broad guides, and editorial roundups often need multiple entities by design.
Yes. A page can be tightly focused and still be thin, stale, biased, or unhelpful.
Only if the page is genuinely unclear. If the rewrite makes the prose robotic, you are solving the wrong problem.
It is one lens for checking whether a page’s semantic center matches its intended topic. It should sit alongside intent analysis, internal linking, factual completeness, and editing.
Entity Salience Ratio is useful when I need a quick read on semantic focus for entity-heavy pages. It can support entity optimization, topical focus SEO, and broader semantic SEO metrics work. But it is not official, not reliable enough to run a content strategy by itself, and not something I would optimize in isolation.
Use it as a diagnostic question, not a scoreboard: does this page clearly center on the entity it claims to be about? If ESR helps answer that, great. If it starts pushing you toward robotic writing, stop there…
https://cloud.google.com/natural-language/docs/analyzing-entities
What's happening: Google Cloud Natural Language API documentation shows how entity analysis works, including salience in the response output. This is one of the most direct canonical references for the underlying signal SEOs often use when approximating ESR.
What to do: Use this documentation to understand what salience means technically, how entities are returned, and what limitations may apply. Do not assume the API output is identical to Google Search ranking logic.
https://developers.google.com/search/docs/fundamentals/creating-helpful-content
What's happening: Google’s helpful content guidance explains what Google Search wants site owners to focus on: helpful, reliable, people-first content. It does not mention Entity Salience Ratio or suggest optimizing around a single semantic score.
What to do: Use this page as a strategic guardrail. If ESR-inspired edits improve clarity and usefulness, keep them. If they push writing away from user needs, follow Search guidance and prioritize helpfulness over the metric.
What's happening: Schema.org provides canonical definitions for structured data types such as Organization, Product, Person, Place, and Article. While structured data does not create ESR directly, it can clarify what an entity-centered page is about.
What to do: Check whether the page’s markup accurately reflects its main entity and context. Use structured data to reinforce clarity where appropriate, while keeping expectations realistic about direct ranking impact.
| Page type | Typical entity pattern | How ESR is best used | Main risk |
|---|---|---|---|
| Glossary entry | One dominant entity with a few supporting entities | Check whether the definition and examples stay centered on the term | Adding too many adjacent concepts and losing clarity |
| Product page | Primary product or brand entity plus features and use cases | Validate that the page is clearly about the product, not generic category filler | Overusing brand mentions and harming readability |
| Comparison page | Several intentionally prominent entities | Use ESR carefully, often at cluster level rather than single-entity level | Misreading healthy multi-entity coverage as dilution |
| Local service page | Business, service, and location entities together | Check that the location-service-business relationship is clear | Stuffing neighborhoods or city names unnaturally |
| Broad educational guide | Distributed salience across concept family | Use ESR mainly to spot major drift from the core topic | Forcing artificial narrowness and reducing completeness |
✅ Better approach: A frequent mistake is talking about Entity Salience Ratio as if Google publishes or uses it directly in Search. The term is an SEO invention. Even if you use salience data from a Google API, that does not convert the ratio into a confirmed ranking factor. Present it as an internal heuristic so teams do not build false certainty into strategy.
✅ Better approach: Some teams begin rewriting copy just to force repeated mentions of the main entity. That can make prose repetitive, unnatural, and less useful. A page should first satisfy user intent. If ESR rises because clarity improves, that is a side benefit. If the writing becomes robotic in pursuit of a score, the metric is hurting more than helping.
✅ Better approach: Not every page should have the same semantic concentration. A glossary page, category page, comparison page, and local service page each have different needs. Using one target ratio across all templates can create bad editorial decisions. Always judge ESR relative to the purpose of the page and the range of entities a user would reasonably expect to see.
✅ Better approach: NLP tools can miss entities, misclassify them, or confuse ambiguous terms. If the primary entity is absent from the output, the problem may be the tool rather than the page. Always inspect the extracted entities manually before making content decisions. This is especially important for brand names, acronyms, medical terms, and topics with multiple meanings.
✅ Better approach: A page can have a high ESR and still fail because it is thin, outdated, poorly structured, or misaligned with the query. Likewise, a lower ESR page may perform well if it satisfies broad informational intent. ESR should sit alongside stronger business and SEO signals such as conversions, engagement, internal link support, crawlability, and actual search visibility.
✅ Better approach: Writers sometimes remove related concepts because they think every non-primary entity lowers focus. That is backwards. Helpful supporting entities often improve comprehension and relevance. A page about a software platform may need pricing, integrations, founders, competitors, or use cases. The issue is not the presence of supporting entities; it is whether they serve the page’s core purpose.
Get expert SEO insights and automated optimizations with our platform.
Get Started Free