Entity SEO and Schema Markup
Entity SEO is the work of making search engines recognise your business, its people and its offers as distinct, well-described entities, and schema markup is the structured data that states those facts in a vocabulary machines read. The outcome is one consistent identity across your site and the wider web, so search engines describe you accurately.
Signs you need Entity SEO and Schema Markup
- Google shows the wrong logo, phone number or address for us.
- Searching our name brings up a different business with a similar name.
- We installed a schema plugin, but we have no idea what it outputs.
- Our attorneys aren’t connected to the firm anywhere online.
- We rebranded, and the old name still appears in search.
- Our markup passes every test, but nothing changes in search.
- Competitors have a knowledge panel and we don’t.
Results to expect
- Search engines identify your business, people and services without ambiguity
- The same facts about you on your site, profiles and directories
- Structured data that validates and matches what each page shows
- The groundwork a knowledge panel needs, for the brand or its key people
What is entity SEO?
Entity SEO is the work of making search engines certain who a business is, which people and places belong to it and what it offers, so that every mention of it across the web resolves to one well-understood entity. An entity is anything a search engine can identify uniquely: a company, a person, a facility, a product or a service. Schema markup is the tool that states those identities in a vocabulary machines read. Entity SEO is the strategy that decides what the markup should say.
I’m Qaim Raza, and I treat entity work as the identity layer of semantic SEO. Content shows what a business knows; the entity layer shows who is saying it. That matters most in YMYL fields, short for “your money or your life”, where bad information can harm someone’s finances, health or safety, such as law, and in categories search engines treat warily, such as kratom and CBD.
How do search engines decide two mentions are the same business?
Search engines decide two mentions refer to the same business by comparing identifying details and checking that they agree: name, address, phone number, website, logo, the people associated with it and the profiles that point to one another. When the details match, the mentions merge into one entity and the evidence about it adds up. When they don’t, the evidence splits between two weaker entities or attaches to the wrong one.
Names alone are rarely enough. Two firms called “Harbor Law” can exist in different states, and a jewelry store called “Diamond District” shares its name with a famous street. What separates them is the combination of attributes: this address, this phone number, these attorneys, this founding date. The more of those attributes appear identically in more places, the less a search engine has to guess.
This is also where knowledge-based trust begins: the idea that a source is judged by whether its facts agree with what a search engine already holds to be true. A business whose own details conflict fails that test before it is compared with anyone else.
Not sure where to start?
Get a free audit. In 1 to 2 days you’ll know what’s holding your site back and what to fix first.
What makes a page an entity home?
A page becomes an entity home when it is the one place on the web that defines the entity authoritatively and other descriptions point back to it. For a business, that is usually the About page. For an attorney or a founder, it is their profile page on the company’s site. The homepage can work, but it is usually busy selling, and an entity home needs to be busy describing.
A strong entity home states the facts other sources should agree with: legal and trading names, what the business does and for whom, where it operates, when it was founded, who leads it, the licences or registrations that apply, and links to its official profiles elsewhere. Those profiles link back to it. When a search engine finds the same facts on the entity home, in its markup and on the profiles, the loop closes.
Which profiles belong in a sameAs list?
Only profiles that are about the same entity belong in sameAs, the schema.org property that lists other URLs which unambiguously identify it. Pages that merely mention the business, such as a news article or a “best movers” roundup, don’t belong there, however good they look.
Official social profiles the business controls and keeps current.
Professional and industry listings that identify it uniquely, such as a Better Business Bureau profile for a mover.
Reference databases such as Wikidata or Wikipedia, only where an entry genuinely exists.
For people: professional profiles such as LinkedIn, plus author pages on publications they write for.
A sameAs list is only as good as the profiles it points to. Before adding a URL, I check that its name, address, phone number and description match the entity home. Linking to a profile with an old address tells search engines the conflict is official.
Why must your Business Profile, directories and social profiles agree?
They have to agree because each one is a separate witness to the same facts, and contradictions lead search engines to discount all of them. Consistency rarely breaks through one big error. It drifts: an office move updated on the website but not in directories, call-tracking numbers copied into listings, a rebrand applied to social profiles but not to the Google Business Profile, or a data aggregator still distributing details from years back.
Multi-location businesses drift fastest. Each location’s profile should link to that location’s own page, not the homepage, so the location entity on the site and the one on Maps connect. Managing the profiles themselves is part of local SEO. The entity work is making sure every profile tells the same story as the site.
How do @id connections turn markup into one graph?
An @id gives each entity in the markup a permanent identifier, usually a URL with a fragment such as /about/#organization, so every page can refer to the same entity instead of describing it again. Without @id values, a fifty-page site can present fifty slightly different versions of the business. With them, the markup forms one connected graph that mirrors how the business is actually organised.
For a law firm with two offices, the graph I build looks like this:
Organization
for the firm, defined once on the entity home, with its logo, sameAs list and identifiers.
LegalService
for each office, with its own address and hours, linked to the firm through parentOrganization.
Person
for each attorney, linked to the firm through worksFor.
Service
for each practice area, with provider pointing to the firm and areaServed naming the jurisdiction.
WebPage
and BreadcrumbList on every page, stating which entity the page is about and where it sits in the site’s hierarchy.
schema.org itself describes the older Attorney type as deprecated in favour of LegalService, so I use LegalService for the firm and its offices and describe individual lawyers as Person entities. Every other niche follows the same pattern, using the most specific type schema.org offers.
What can schema markup do, and what can’t it?
Schema markup can make facts unambiguous, connect entities to one another and make some pages eligible for rich results, but it cannot make a page rank on its own or force any feature to appear in search.
Rich results change more often than most people expect. Google now shows FAQ rich results only for a limited set of well-known, authoritative government and health websites, and it has retired HowTo rich results. FAQPage markup is still valid, and I still use it on pages with genuine question-and-answer content, because it labels each question and answer clearly for any system reading the page. What it no longer does for most businesses is add expandable answers under the listing, and anyone selling it on that promise is out of date.
I treat every visual feature as a possible bonus. The lasting value is understanding: a search engine that knows exactly which firm, which attorney and which office a page is about has less to guess.
When does a knowledge panel appear?
A knowledge panel appears when Google is confident enough about an entity to summarise it from its Knowledge Graph, and nobody can request or buy one. A knowledge panel is the box of facts shown alongside results for a recognised person, organisation or thing. It is different from the Business Profile a local business manages for Maps, even though the two can look alike in search results.
Readiness comes from the evidence described above plus independent confirmation: coverage in news or trade publications, listings with professional bodies and mentions on sites the business doesn’t control. That last part sits within authority building. For a law firm, attorneys with published commentary, bar listings and speaking credits give search engines independent evidence about the people behind the firm.
How is entity work measured?
Entity work is measured by checking directly whether search engines describe the business correctly and consistently, rather than inferring it from rankings.
Knowledge Graph presence
Google’s Knowledge Graph Search API shows whether the business or a key person exists as an entity, with an identifier and a confidence score.
Branded results
Searches for the business name show the right logo, phone number, address and sitelinks, and no other business takes the panel.
Entity recognition on key pages
Google’s Natural Language API picks out the business and its services as the most prominent entities on its own pages.
AI descriptions
Assistants such as ChatGPT and Gemini describe the business with current, accurate details, a check shared with AI search optimisation.
Which schema mistakes confuse search engines?
The schema mistakes that do the most damage give search engines conflicting answers about who the business is.
Invented addresses for service areas
Marking up a business with an address in every city a mover serves creates locations that don’t exist. Cities served belong in areaServed.
People who have left
An attorney who moved firms but still appears in worksFor ties the old firm to someone else’s career.
Hard-coded facts
Hours, prices or phone numbers typed into markup once drift away from the page as the business changes. Markup generated from the same CMS fields as the visible text can’t drift.
Several versions of the business
A theme, a plugin and a tag manager each output their own Organization, with different names or logos, and the search engine has to pick one.
What you receive with Entity SEO and Schema Markup
Lists the business, locations, people, services and products as entities, with their key facts and identifiers.
Gives the business one authoritative page that every profile and markup block points back to.
Shows which external profiles describe you, where details conflict and which to fix or claim.
Maps how every entity connects before any code is written.
Output the right markup on every page type without hand-editing pages.
Records Rich Results Test and Schema Markup Validator results for each template.
Fixes names, addresses, descriptions and links on the profiles you control.
How Entity SEO and Schema Markup works, step by step
Entity inventory
Days 1–3I list every entity the site should describe and collect the facts about each one. You confirm legal names, addresses, founding details and the key people.
Off-site consistency check
Week 1I compare those facts across your Google Business Profile, directories, social profiles and any existing knowledge panel. You give me access to the profiles you control.
Entity home and graph design
Week 2The entity home is written or rewritten, and the schema graph is designed with a stable identifier for every entity.
Implementation
Weeks 2–4JSON-LD is added to each template. This step needs theme or developer access.
Validation and profile fixes
Weeks 3–5Every template is validated, and conflicting external profiles are corrected or reported to the platforms that host them.
Upkeep
MonthlyMarkup is updated when services, people or locations change, and new templates are checked before they launch.
Entity SEO and Schema Markup in the industries I specialise in
Kratom
Kratom vendors have to show search engines a real, accountable business, because search engines and payment providers are cautious about the category. The entity home states the legal name, address, contact details and policies, and those match the site footer, checkout pages and any marketplace profiles. Product markup covers format, weight, price and availability exactly as the page and its certificate of analysis do, with no effect claims in descriptions.
CBD
CBD brands often sell through their own store, marketplaces and wholesale partners, and each describes the brand slightly differently. I align the Organization entity across them and use Product markup that states cannabinoid content, size and spectrum type exactly as the label does. Descriptions stay free of disease or cure claims, since structured data repeats whatever the page says to every system that reads it.
Movers
For movers, the entity has to prove the company is a genuine carrier or broker in a category crowded with lead-generation sites. The entity home states the USDOT number so anyone can check it on the FMCSA register, and MovingCompany markup describes each depot as its own location linked to the parent company. The business name in markup and on profiles matches the name registered with the FMCSA exactly, so the records connect.
Self storage
Each storage facility is a clear entity with fixed attributes, which makes self storage a good fit for entity work. Every facility page gets SelfStorage markup with its own address, hours and amenities, connected to the operator by a shared identifier. That structure helps search engines tell your facility apart from the aggregator listings that repeat your name and address.
Jewelry stores
A jewelry store is often two entities at once: a local showroom and a brand that sells products online. I mark up the showroom as a JewelryStore linked to the organisation, and products with metal, carat weight and certification stated exactly as on the page and the grading report. Designers and gemologists can be Person entities too, which shows real expertise behind a high-value purchase.
Law firms
Law firms gain more from entity work than any other niche I serve, because clients choose a lawyer as much as a firm. Each attorney’s sameAs points to their state bar listing where one exists, and practice areas are tied to the states where that attorney is admitted. Credentials are stated as plain facts, never as a “specialist” claim where state bar rules restrict it.
Who this is for, and who it isn’t
A good fit if you…
- Law firms with several attorneys, offices or practice areas
- Multi-location businesses such as storage operators and movers
- Brands that share a name with another business or person
- Businesses that have rebranded, merged or moved
- Founders and experts who want to be recognised as people, not only as a company
Not the right fit if you…
- Anyone who expects schema alone to lift rankings
- Sites whose visible pages don’t yet state the facts the markup would describe
- Businesses that want markup for reviews, ratings or prices that aren’t on the page
- Anyone who wants a guaranteed knowledge panel
Ways we can work together
Entity and schema setup
Best for: Sites with no structured data, or markup nobody has checked
- Entity inventory and graph design
- Entity home page
- JSON-LD for every template
- Validation and profile corrections
Schema for your developer
Best for: Teams with a developer who can implement
- Graph design and annotated JSON-LD examples
- Field mapping for your CMS
- Review and validation of the build
Ongoing entity upkeep
Best for: Growing firms that add people, services or locations
- Markup updates as the business changes
- Profile consistency reviews
- Checks on new templates before launch
Tools I use
- Schema Markup Validator
- Rich Results Test
- Google Search Console
- Google Knowledge Graph Search API
- Google Cloud Natural Language API
- Screaming Frog SEO Spider
- Wikidata
Entity SEO and Schema Markup questions
Does schema markup improve rankings?
Not directly. Google’s representatives have said structured data isn’t a general ranking factor. What markup does is remove ambiguity: it tells search engines exactly which business, person, service or product a page describes, and it can make a page eligible for rich results. Those effects help indirectly, through better understanding and more useful listings, but markup on a weak page won’t make it rank.
Can I get review stars for my business in search results?
Usually not from reviews on your own website. Google doesn’t show review stars for LocalBusiness or Organization markup when a business publishes reviews about itself, which it calls self-serving reviews. Stars can still appear for products with genuine customer reviews on the page. For a local business, the reviews that matter most are the ones on its Google Business Profile.
Can I edit my knowledge panel?
Not directly, but you can influence it. Once a panel exists, an official representative can usually claim it through Google’s verification process and then suggest changes, which Google reviews. The more reliable fix is upstream: correct the entity home, the markup and the profiles the panel draws on, because a suggestion that contradicts those sources is unlikely to stick.
Should my business be on Wikidata or Wikipedia?
Only if it meets their notability rules, and Wikipedia discourages people from writing about their own organisations. Wikidata items for businesses without independent coverage are often deleted, and an entry that’s removed helps nobody. Where a business has genuine press coverage, a carefully sourced Wikidata item can strengthen its sameAs list. Otherwise, the time is better spent on profiles and mentions it can earn.
Is JSON-LD better than microdata?
For most sites, yes. Google supports JSON-LD, microdata and RDFa, and recommends JSON-LD because it sits in one block, separate from the visible HTML. That makes it easier to generate, review and maintain without touching the page layout. Microdata isn’t wrong, but it’s woven through the template, so a small design change can break it without anyone noticing.
Can I keep using my SEO plugin’s schema?
Usually, yes. Plugins such as Yoast SEO and Rank Math already output a connected graph for the website, the organisation and each page, and both can be extended by a developer. I build on that graph, adding locations, people, services and products with matching @id references, rather than replacing it. Replacing it is only worth doing when the plugin’s output can’t be corrected.
What should an attorney’s Person markup include?
The facts a prospective client would check: full name, job title, education through alumniOf, bar admissions as credentials, and practice areas through knowsAbout. Memberships in professional associations can be added through memberOf. Every one of those facts must also appear on the attorney’s visible bio page, in the same wording, or the markup describes something the page doesn’t support.
What happens to our entity when we rebrand?
The old and new names need to be connected rather than swapped. I add the former name as an alternateName in the markup, redirect the old domain page by page, update every profile you control, and state the change on the entity home so search engines and people can follow it. Old directory listings are the slowest part, and some take months to correct.
Can schema markup get my site penalised?
Yes, if it misleads. Google can issue a manual action for spammy structured data, such as markup describing reviews, prices or content visitors can’t see, and affected pages lose their rich result eligibility. Markup that accurately describes what’s on the page carries no such risk. Validation tools won’t catch the problem, because markup can be technically valid and still misleading.
Let’s make Google see you as the expert.
Request a free SEO audit, or message me directly. I reply within one working day.