Entity SEO breaks when your company name, services, people, locations and profiles drift apart. The homepage says one thing. Schema says another. A former employee is still listed as the expert. An old address survives in a directory. Search engines and customers are left to reconcile your mess.
This SOP gives the work an owner, a source of truth and a completion test.
The short answer
Run the procedure whenever a material entity fact changes:
- identify the entity and authoritative owner;
- freeze every public representation;
- reconcile the canonical fact record;
- map first-party pages and structured relationships;
- correct external profiles and citations;
- validate rendered facts, schema and crawl access;
- record unresolved conflicts and retest.
Schema validation is one control. It is not the outcome.
The Searchmaxxed entity SEO playbook connects this procedure to the wider work of building clear organization, person, service and location relationships.
Scope
Use this SOP for:
- organizations and trading brands;
- founders, executives, authors and practitioners;
- products and services;
- offices, stores, campuses and service areas;
- parent, subsidiary, brand and partner relationships;
- official profiles and public business records.
Use a separate regulated-content or legal review where a fact concerns licensing, accreditation, healthcare, finance or another controlled claim.
If the entity model itself is unfamiliar, start with how search engines distinguish your brand, then return here to run the work.
Required roles
| Role | Decision |
|---|---|
| entity owner | approves the canonical public fact |
| source owner | controls the authoritative internal or official record |
| website owner | updates copy, links and content models |
| technical owner | updates schema, templates, redirects and crawl controls |
| profile owner | updates external profiles and listings |
| reviewer | checks that every public surface now tells the same supported story |
One person may hold several roles. No field should have no owner.
Required evidence
Before editing, collect:
- legal or official business record where relevant;
- approved trading and public names;
- current website and canonical URLs;
- service or product catalog;
- people and role approvals;
- location and contact records;
- official profile URLs;
- current structured data;
- screenshots or exports of material external profiles;
- relevant regulator, association or partner sources.
Treat a directory as evidence of what the directory says, not automatic proof that the directory is correct.
Step 1: Open the entity register
Create one row per real entity.
| Field | Required decision |
|---|---|
entity_id |
stable internal identifier |
entity_type |
organization, person, service, product, place or brand |
canonical_name |
approved public name |
alternate_names |
genuine abbreviations, former names or trading names |
canonical_url |
primary defining page |
description |
approved plain-language definition |
relationships |
explicit links to parent, founder, employer, brand, offer or location |
official_profiles |
profiles controlled by or formally representing the entity |
claim_owner |
person authorised to approve material facts |
last_verified |
date and evidence used |
update_triggers |
events that force this SOP to run again |
Do not use a keyword as an entity record. “Best SEO agency” is a query or claim. Searchmaxxed is an organization.
Step 2: Freeze the current footprint
Search the site and public profiles for:
- canonical and alternate names;
- old descriptions;
- phone numbers and addresses;
- titles and roles;
- service names;
- location or service-area claims;
- logos and brand references;
- profile URLs;
- structured-data IDs and relationships.
Record:
| Surface | Current fact | Source | Correct? | Action |
|---|---|---|---|---|
| homepage | ||||
| company/about | ||||
| person/profile page | ||||
| service/product page | ||||
| contact/location page | ||||
| structured data | ||||
| official profile | ||||
| relevant directory or register |
Freeze the source and rendered state before changing it. That preserves the evidence needed to prove the correction and catch accidental losses.
Step 3: Resolve conflicts by source authority
Do not average conflicting facts.
Use the narrowest authoritative source:
- legal name from the legal record;
- public trading name from approved brand canon;
- role from the current employment or leadership owner;
- service availability from the operating catalog;
- address from the current location record;
- credential from the issuing body;
- partnership from an authorised agreement or public partner source.
If the winning source cannot be determined, mark the fact hold and remove or lower the public claim until it is resolved.
Record the losing source as stale. Otherwise the same contradiction will return.
For a deeper method covering brand-fact conflicts, Organization schema and knowledge-panel limits, use the knowledge graph SEO guide.
Step 4: Assign a defining page
Every important entity should have one page that carries the primary public definition.
| Entity | Defining page |
|---|---|
| organization | homepage or company/about page |
| founder or expert | dedicated profile page |
| service | service page |
| product | product page |
| physical location | location/contact page |
| brand | brand page or organization page, depending on the relationship |
The defining page should state:
- full canonical name;
- what the entity is;
- its relationship to the organization;
- current scope or role;
- relevant location;
- verifiable proof;
- links to related entities;
- last-review ownership for changing facts.
Do not force every staff member, product variation or service-area phrase into an indexable page. Create a defining page only when it serves users and can be maintained.
Step 5: Reconcile sitewide language and links
Update:
- navigation and footer;
- titles, H1s and visible copy;
- bylines and author modules;
- service and product cards;
- contact and location modules;
- case studies and proof references;
- metadata and social previews;
llms.txtor public text manifests if used;- sitemaps and internal links.
Use descriptive anchors that state the relationship. “Brenden, founder of Searchmaxxed” contains more useful relationship information than “learn more.”
Preserve established query ownership. An entity correction should not casually remove a service, location or category phrase a page legitimately owns.
Step 6: Build a coherent schema graph
Use structured data that reflects the visible page and current Google guidance.
For an organization, check:
- stable organization
@id; name,urland logo;- official alternate name only when genuine;
- address and contact facts;
- founder or employee relationships only when current and relevant;
- official profile references;
- parent, sub-organization or brand relationships;
- page-level reference back to the organization.
For a person profile, check:
- stable person
@id; - current name and role;
- organization relationship;
- profile image and URL;
- same-person profile references;
- authored or reviewed content only when the page visibly supports it.
Google documents Organization and ProfilePage structured data. Schema.org supplies the vocabulary. Neither source authorises hidden facts, fake relationships or irrelevant sameAs links.
Validate syntax, then inspect the rendered page. A technically valid graph with the wrong person, role or address fails.
Step 7: Reconcile official profiles
Prioritize profiles the entity controls or that materially influence discovery:
- Google Business Profile where eligible;
- LinkedIn company or person pages;
- relevant social and video profiles;
- industry associations;
- regulator or professional registers;
- product or marketplace profiles;
- high-value directories.
For each profile, check:
- name;
- category;
- description;
- URL;
- phone and address;
- hours;
- service area;
- people or brand relationship;
- duplicate or former profiles.
Google's Business Profile guidelines require real-world representation and contain specific rules for names, addresses, service areas and categories. Follow the current platform rule rather than forcing website language into a field that has a different policy.
Do not create profiles merely to manufacture corroboration.
Step 8: Handle sameAs correctly
Use sameAs for a URL that unambiguously identifies the same entity.
Suitable candidates can include:
- the organization's official profile;
- the person's official professional profile;
- an authoritative registry record for that same entity.
Do not use:
- a news article that merely mentions the company;
- a customer page;
- an unrelated directory category;
- a competitor comparison;
- a page about a different branch or person.
Use ordinary links and citations for related evidence that is not the same entity.
Step 9: Check crawler access and page posture
For every defining page, verify:
- HTTP 200;
- intended robots state;
- self-consistent canonical;
- server-rendered defining facts;
- crawlable internal links;
- sitemap inclusion when indexable;
- no duplicate defining page;
- structured data visible in rendered output.
OpenAI's publisher guidance says OAI-SearchBot access affects whether public content can be discovered and clearly cited in ChatGPT search. Access does not guarantee selection. Record it as a technical state, not an AI-visibility result.
Step 10: Validate identity questions
Test the questions a customer or machine needs answered:
- What is this organization?
- What does it offer?
- Who leads or authored this work?
- Where does it operate?
- Which profile belongs to it?
- Is this the same company or person as the similarly named result?
- Which facts are official and which are third-party claims?
Check conventional search, the defining page and relevant answer surfaces. Capture contradictions, not just positive appearances.
For AI-search testing, separate:
fetchable -> fetched -> mentioned -> cited -> linked -> visited -> converted
An accurate unlinked description is not a citation. A citation is not a visit.
Step 11: Record release acceptance
| Gate | Passing evidence |
|---|---|
| canonical fact | approved source and owner recorded |
| first-party parity | defining and supporting pages match |
| relationship clarity | organization, person, service and location links are explicit |
| schema parity | markup matches visible current facts |
| profile parity | priority official profiles match or conflicts are logged |
| technical posture | status, robots, canonical, rendering and links pass |
| stale-source action | losing or former records are corrected, redirected, annotated or held |
| retest | exact identity questions and affected surfaces were checked |
Do not close the task at updated. Close it at verified, or record the external dependency preventing verification.
Step 12: Set update triggers
Run this SOP again after:
- rebrand or trading-name change;
- merger, acquisition or new subsidiary;
- domain or canonical change;
- leadership or author-role change;
- new or retired service;
- new, moved or closed location;
- phone or contact change;
- new credential or expired accreditation;
- CMS, schema or profile-template change;
- material public misinformation.
A quarterly review may catch drift. Event-driven ownership prevents it.
Frequently asked questions
What is entity SEO?
Entity SEO is the work of making real organizations, people, products, services and places distinct and correctly related across pages, structured data and public sources. It supports search understanding but does not replace relevance, authority or useful content.
Is entity SEO just schema markup?
No. Schema can express the entity record, but visible copy, page ownership, internal links, official profiles and external facts must agree with it.
Does structured data guarantee better rankings?
No. Structured data may help search systems understand page information and enable supported search features when eligibility rules are met. It does not guarantee rankings.
Which pages should we fix first?
Start with the defining page for the organization, the highest-value services or products, the people carrying important expertise and any location or profile causing material confusion.
Should every directory listing match word for word?
Core identity facts should agree, but platforms have different fields and policies. Keep the entity, category and contact information consistent while adapting descriptions to the legitimate context.
How should we handle a former company or person name?
Preserve it only where it helps disambiguation or historical accuracy, label the relationship clearly and avoid presenting the former fact as current. Redirect or update stale first-party pages deliberately.
How often should entity SEO be reviewed?
Run the SOP whenever a controlled fact changes or a technical/template release affects entity output. Use a recurring audit to catch drift, but do not wait for the calendar after a rebrand, move or leadership change.
Can this improve ChatGPT visibility?
It can improve the accuracy and accessibility of the public source layer. ChatGPT search inclusion, citation or recommendation still depends on the query, retrieval, sources and platform behavior. Test each state separately, then use the ChatGPT entity optimization guide to diagnose recommendation-specific gaps.
Fix the entity conflict before publishing more content
If your brand, people, services or locations contradict one another, more pages will multiply the problem. We will build the entity register, identify the winning source, repair the defining pages and schema, then verify the affected public surfaces.