Entity Schema Markup
Schema markup doesn't directly boost rankings, but it is how you tell Google and LLMs exactly which real-world entities your content is about. Learn the workflow, including sameAs rules.
What you'll learn
- Understand what entity schema markup does and doesn't do for rankings
- Learn the step-by-step workflow: TextRazor → entity selection → sameAs → implementation
- Know the strict rules for when sameAs can and cannot be used
- Understand the WordPress tag-based scaling method for entity markup
What Schema Does — and Doesn't — Do
Schema markup does not directly boost rankings. What it does is remove ambiguity: it tells Google precisely which real-world entities a page discusses, which raises the odds of correct Knowledge Graph association, correct citation in AI Overviews, and correct interpretation by ChatGPT/Gemini/Perplexity. Sites without explicit entity markup consistently lose ground to competitors who have it, even though schema itself isn't a "ranking factor" in the traditional sense.
When It's Worth the Manual Effort
Because entity markup is manual work, prioritize: commercial or high-value pages, content built for E-E-A-T (author pages, About pages), and complex/YMYL topics (finance, medical, legal, betting) where entity clarity matters most.
The Implementation Workflow
- Analyze the page through TextRazor (textrazor.com/demo) to extract candidate entities with a relevance score.
- Select 1-2 main entities — the highest-scoring, most central ones. Don't over-annotate.
- Get the entity's canonical address — click into the entity within TextRazor's output to reach its reference page (e.g., Wikipedia).
- Add it to markup as a
ThingwithsameAspointing to that canonical source. - Validate with Google's Rich Results Test before shipping to developers as a ticket.
The sameAs Rule: Only for True Identity
Use sameAs only for Wikipedia, Wikidata, or an official profile (LinkedIn company page, Crunchbase, GitHub org). Never use it for a merely similar topic, a general article about something, or an expert's writing about a subject. When in doubt, leave it out.
Scaling Entity Markup on WordPress
Rather than hand-coding schema per page, map each entity to a WordPress tag. Assigning that tag to a post automatically attaches the entity's schema — no developer involvement needed per page, and any number of relevant entities can be attached just by selecting tags in the admin panel. Test the approach first on 4 thematically related articles with 5-10 entities each before scaling site-wide.
Key Takeaways
- Schema doesn't directly boost rankings — it removes ambiguity about which entities a page is about
- Prioritize entity markup on commercial pages, E-E-A-T pages, and complex/YMYL topics
- Workflow: TextRazor entity extraction → select 1-2 top entities → find canonical source → add via sameAs → validate
- sameAs is strictly for true identity (Wikipedia/Wikidata/official profiles) — never for "related to" content
- A WordPress tag-to-entity mapping scales markup without per-page developer work