entity-optimizer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Entity Optimizer

实体优化工具

This skill audits, builds, and maintains entity identity across search engines and AI systems. Entities — the people, organizations, products, and concepts that search engines and AI systems recognize as distinct things — are the foundation of how both Google and LLMs decide what you are and whether to cite you.

Why entities matter for SEO + GEO:

SEO: Google's Knowledge Graph powers Knowledge Panels, rich results, and entity-based ranking signals. A well-defined entity earns SERP real estate.
GEO: AI systems resolve queries to entities before generating answers. If an AI can't identify your entity, it can't cite you — no matter how good your content is.

本工具可在搜索引擎和AI系统中审计、构建并维护实体身份。实体——即搜索引擎和AI系统识别为独立对象的人物、组织、产品和概念——是Google和大语言模型（LLMs）判断「你是什么」以及「是否引用你」的基础。

实体对SEO + GEO的重要性：

SEO：Google知识图谱为知识面板、富媒体结果和基于实体的排名信号提供支持。定义清晰的实体可在搜索结果页（SERP）中占据更多展示空间。
GEO：AI系统在生成答案前会先将查询解析为实体。如果AI无法识别你的实体，无论你的内容质量多高，都不会被引用。

When to Use This Skill

适用场景

Establishing a new brand/person/product as a recognized entity
Auditing current entity presence across Knowledge Graph, Wikidata, and AI systems
Improving or correcting a Knowledge Panel
Building entity associations (entity ↔ topic, entity ↔ industry)
Resolving entity disambiguation issues (your entity confused with another)
Strengthening entity signals for AI citation
After launching a new brand, product, or organization
Preparing for a site migration (preserving entity identity)
Running periodic entity health checks

将新品牌/人物/产品确立为被认可的实体
审计知识图谱、Wikidata和AI系统中当前的实体存在感
改进或修正知识面板
构建实体关联（实体 ↔ 主题、实体 ↔ 行业）
解决实体消歧问题（你的实体与其他实体被混淆）
强化实体信号以提升AI引用率
新品牌、产品或组织推出后
网站迁移前（保留实体身份）
定期进行实体健康检查

What This Skill Does

工具功能

Entity Audit: Evaluates current entity presence across search and AI systems
Knowledge Graph Analysis: Checks Google Knowledge Graph, Wikidata, and Wikipedia status
AI Entity Resolution Test: Queries AI systems to see how they identify and describe the entity
Entity Signal Mapping: Identifies all signals that establish entity identity
Gap Analysis: Finds missing or weak entity signals
Entity Building Plan: Creates actionable plan to establish or strengthen entity presence
Disambiguation Strategy: Resolves confusion with similarly-named entities

实体审计：评估搜索和AI系统中当前的实体存在感
知识图谱分析：检查Google知识图谱、Wikidata和Wikipedia的状态
AI实体解析测试：查询AI系统，观察它们如何识别和描述实体
实体信号映射：识别所有可确立实体身份的信号
差距分析：找出缺失或薄弱的实体信号
实体构建计划：创建可操作的计划以确立或强化实体存在感
消歧策略：解决与同名实体的混淆问题

How to Use

使用方法

Entity Audit

实体审计

Audit entity presence for [brand/person/organization]

How well do search engines and AI systems recognize [entity name]?

Audit entity presence for [brand/person/organization]

How well do search engines and AI systems recognize [entity name]?

Build Entity Presence

构建实体存在感

Build entity presence for [new brand] in the [industry] space

Establish [person name] as a recognized expert in [topic]

Build entity presence for [new brand] in the [industry] space

Establish [person name] as a recognized expert in [topic]

Fix Entity Issues

修复实体问题

My Knowledge Panel shows incorrect information — fix entity signals for [entity]

AI systems confuse [my entity] with [other entity] — help me disambiguate

My Knowledge Panel shows incorrect information — fix entity signals for [entity]

AI systems confuse [my entity] with [other entity] — help me disambiguate

Data Sources

数据源

See CONNECTORS.md for tool category placeholders.

With ~~knowledge graph + ~~SEO tool + ~~AI monitor + ~~brand monitor connected: Query Knowledge Graph API for entity status, pull branded search data from ~~SEO tool, test AI citation with ~~AI monitor, track brand mentions with ~~brand monitor.

With manual data only: Ask the user to provide:

Entity name, type (Person, Organization, Brand, Product, Creative Work, Event)
Primary website / domain
Known existing profiles (Wikipedia, Wikidata, social media, industry directories)
Top 3-5 topics/industries the entity should be associated with
Any known disambiguation issues (other entities with same/similar name)

Without tools, Claude provides entity optimization strategy and recommendations based on information the user provides. The user must run search queries, check Knowledge Panels, and test AI responses to supply the raw data for analysis.

Proceed with the audit using public search results, AI query testing, and SERP analysis. Note which items require tool access for full evaluation.

工具类别占位符请参见 CONNECTORS.md。

连接~~知识图谱工具 + ~~SEO工具 + ~~AI监控工具 + ~~品牌监控工具后： 查询知识图谱API获取实体状态，从~~SEO工具提取品牌搜索数据，通过~~AI监控工具测试AI引用情况，使用~~品牌监控工具追踪品牌提及。

仅使用手动数据时： 请用户提供：

实体名称、类型（人物、组织、品牌、产品、创意作品、活动）
主网站/域名
已知的现有档案（Wikipedia、Wikidata、社交媒体、行业目录）
实体应关联的前3-5个主题/行业
任何已知的消歧问题（其他同名或近似名称的实体）

无工具支持时，Claude会根据用户提供的信息提供实体优化策略和建议。用户需自行运行搜索查询、检查知识面板并测试AI响应，以提供分析所需的原始数据。

可通过公开搜索结果、AI查询测试和SERP分析进行审计。注意哪些项目需要工具支持才能完成全面评估。

Instructions

操作步骤

When a user requests entity optimization:

当用户请求实体优化时：

Step 1: Entity Discovery

步骤1：实体发现

Establish the entity's current state across all systems.

markdown

undefined

确立实体在所有系统中的当前状态。

markdown

undefined

Entity Profile

实体档案

Entity Name: [name] Entity Type: [Person / Organization / Brand / Product / Creative Work / Event] Primary Domain: [URL] Target Topics: [topic 1, topic 2, topic 3]

实体名称：[名称] 实体类型：[人物 / 组织 / 品牌 / 产品 / 创意作品 / 活动] 主域名：[URL] 目标主题：[主题1, 主题2, 主题3]

Current Entity Presence

当前实体存在感

Platform	Status	Details
Google Knowledge Panel	✅ Present / ❌ Absent / ⚠️ Incorrect	[details]
Wikidata	✅ Listed / ❌ Not listed	[QID if exists]
Wikipedia	✅ Article / ⚠️ Mentioned only / ❌ Absent	[notability assessment]
Google Knowledge Graph API	✅ Entity found / ❌ Not found	[entity ID, types, score]
Schema.org on site	✅ Complete / ⚠️ Partial / ❌ Missing	[Organization/Person/Product schema]

平台	状态	详情
Google知识面板	✅ 存在 / ❌ 不存在 / ⚠️ 信息错误	[详情]
Wikidata	✅ 已收录 / ❌ 未收录	[若存在则提供QID]
Wikipedia	✅ 有独立条目 / ⚠️ 仅被提及 / ❌ 未收录	[知名度评估]
Google知识图谱API	✅ 找到实体 / ❌ 未找到	[实体ID、类型、分数]
网站Schema.org标记	✅ 完整 / ⚠️ 部分存在 / ❌ 缺失	[组织/人物/产品Schema]

AI Entity Resolution Test

AI实体解析测试

Note: Claude cannot directly query other AI systems or perform real-time web searches without tool access. When running without ~~AI monitor or ~~knowledge graph tools, ask the user to run these test queries and report the results, or use the user-provided information to assess entity presence.

Test how AI systems identify this entity by querying:

"What is [entity name]?"
"Who founded [entity name]?" (for organizations)
"What does [entity name] do?"
"[entity name] vs [competitor]"

AI System	Recognizes Entity?	Description Accuracy	Cites Entity's Content?
ChatGPT	✅ / ⚠️ / ❌	[accuracy notes]	[yes/no/partially]
Claude	✅ / ⚠️ / ❌	[accuracy notes]	[yes/no/partially]
Perplexity	✅ / ⚠️ / ❌	[accuracy notes]	[yes/no/partially]
Google AI Overview	✅ / ⚠️ / ❌	[accuracy notes]	[yes/no/partially]

undefined

注意：若无工具支持，Claude无法直接查询其他AI系统或执行实时网络搜索。当无~~AI监控工具或~~知识图谱工具时，请用户运行以下测试查询并报告结果，或使用用户提供的信息评估实体存在感。

通过以下查询测试AI系统对该实体的识别情况：

"What is [entity name]?"
"Who founded [entity name]?"（针对组织）
"What does [entity name] do?"
"[entity name] vs [competitor]"

AI系统	能否识别实体？	描述准确性	是否引用实体内容？
ChatGPT	✅ / ⚠️ / ❌	[准确性说明]	[是/否/部分引用]
Claude	✅ / ⚠️ / ❌	[准确性说明]	[是/否/部分引用]
Perplexity	✅ / ⚠️ / ❌	[准确性说明]	[是/否/部分引用]
Google AI Overview	✅ / ⚠️ / ❌	[准确性说明]	[是/否/部分引用]

undefined

Step 2: Entity Signal Audit

步骤2：实体信号审计

Evaluate entity signals across 6 categories. For the detailed 47-signal checklist with verification methods, see references/entity-signal-checklist.md.

markdown

undefined

评估6大类实体信号。包含验证方法的详细47项信号清单，请参见 references/entity-signal-checklist.md。

markdown

undefined

Entity Signal Audit

实体信号审计

1. Structured Data Signals

1. 结构化数据信号

Signal	Status	Action Needed
Organization/Person schema on homepage	✅ / ❌	[action]
sameAs links to authoritative profiles	✅ / ❌	[action]
logo, foundingDate, founder properties	✅ / ❌	[action]
Consistent @id across pages	✅ / ❌	[action]
Product/Service schema on relevant pages	✅ / ❌	[action]
Author schema with sameAs on articles	✅ / ❌	[action]

信号	状态	需执行操作
首页的组织/人物Schema	✅ / ❌	[操作内容]
指向权威档案的sameAs链接	✅ / ❌	[操作内容]
logo、成立日期、创始人属性	✅ / ❌	[操作内容]
页面间@id一致	✅ / ❌	[操作内容]
相关页面的产品/服务Schema	✅ / ❌	[操作内容]
文章中带sameAs的作者Schema	✅ / ❌	[操作内容]

2. Knowledge Base Signals

2. 知识库信号

Signal	Status	Action Needed
Wikidata entry with complete properties	✅ / ❌	[action]
Wikipedia article (or notability path)	✅ / ❌	[action]
CrunchBase profile (organizations)	✅ / ❌	[action]
Industry directory listings	✅ / ❌	[action]
Government/official registries	✅ / ❌	[action]

信号	状态	需执行操作
包含完整属性的Wikidata条目	✅ / ❌	[操作内容]
Wikipedia条目（或知名度提升路径）	✅ / ❌	[操作内容]
CrunchBase档案（针对组织）	✅ / ❌	[操作内容]
行业目录收录	✅ / ❌	[操作内容]
政府/官方注册信息	✅ / ❌	[操作内容]

3. Consistent NAP+E Signals (Name, Address, Phone + Entity)

3. 一致的NAP+E信号（名称、地址、电话 + 实体）

Signal	Status	Action Needed
Consistent entity name across all platforms	✅ / ❌	[action]
Same description/tagline everywhere	✅ / ❌	[action]
Matching logos and visual identity	✅ / ❌	[action]
Social profiles all linked bidirectionally	✅ / ❌	[action]
Contact info consistent across directories	✅ / ❌	[action]

信号	状态	需执行操作
所有平台上实体名称一致	✅ / ❌	[操作内容]
所有平台描述/口号一致	✅ / ❌	[操作内容]
logo和视觉标识一致	✅ / ❌	[操作内容]
社交档案双向链接	✅ / ❌	[操作内容]
所有目录中联系信息一致	✅ / ❌	[操作内容]

4. Content-Based Entity Signals

4. 基于内容的实体信号

Signal	Status	Action Needed
About page with entity-rich structured content	✅ / ❌	[action]
Author pages with credentials and sameAs	✅ / ❌	[action]
Topical authority (content depth in target topics)	✅ / ❌	[action]
Entity mentions in content (natural co-occurrence)	✅ / ❌	[action]
Branded anchor text in backlinks	✅ / ❌	[action]

信号	状态	需执行操作
包含丰富实体内容的关于页	✅ / ❌	[操作内容]
带资质和sameAs的作者页面	✅ / ❌	[操作内容]
主题权威性（目标主题的内容深度）	✅ / ❌	[操作内容]
内容中自然提及实体	✅ / ❌	[操作内容]
反向链接中的品牌锚文本	✅ / ❌	[操作内容]

5. Third-Party Entity Signals

5. 第三方实体信号

Signal	Status	Action Needed
Mentions on authoritative sites (news, industry)	✅ / ❌	[action]
Co-citation with established entities	✅ / ❌	[action]
Reviews and ratings on third-party platforms	✅ / ❌	[action]
Speaking engagements, awards, publications	✅ / ❌	[action]
Press coverage with entity name	✅ / ❌	[action]

信号	状态	需执行操作
权威网站（新闻、行业）提及	✅ / ❌	[操作内容]
与已确立实体的共引关系	✅ / ❌	[操作内容]
第三方平台的评论和评分	✅ / ❌	[操作内容]
演讲、奖项、出版物	✅ / ❌	[操作内容]
提及实体名称的新闻报道	✅ / ❌	[操作内容]

6. AI-Specific Entity Signals

6. AI专属实体信号

Signal	Status	Action Needed
Clear entity definition in opening paragraphs	✅ / ❌	[action]
Unambiguous entity name (or disambiguation strategy)	✅ / ❌	[action]
Factual claims about entity are verifiable	✅ / ❌	[action]
Entity appears in AI training data sources	✅ / ❌	[action]
Entity's content is crawlable by AI systems	✅ / ❌	[action]

undefined

信号	状态	需执行操作
开篇段落有清晰的实体定义	✅ / ❌	[操作内容]
明确的实体名称（或消歧策略）	✅ / ❌	[操作内容]
关于实体的事实声明可验证	✅ / ❌	[操作内容]
实体出现在AI训练数据源中	✅ / ❌	[操作内容]
实体内容可被AI系统抓取	✅ / ❌	[操作内容]

undefined

Step 3: Report & Action Plan

步骤3：报告与行动计划

markdown

undefined

markdown

undefined

Entity Optimization Report

实体优化报告

Overview

概述

Entity: [name]
Entity Type: [type]
Audit Date: [date]

实体：[名称]
实体类型：[类型]
审计日期：[日期]

Signal Category Summary

信号类别总结

Category	Status	Key Findings
Structured Data	✅ Strong / ⚠️ Gaps / ❌ Missing	[key findings]
Knowledge Base	✅ Strong / ⚠️ Gaps / ❌ Missing	[key findings]
Consistency (NAP+E)	✅ Strong / ⚠️ Gaps / ❌ Missing	[key findings]
Content-Based	✅ Strong / ⚠️ Gaps / ❌ Missing	[key findings]
Third-Party	✅ Strong / ⚠️ Gaps / ❌ Missing	[key findings]
AI-Specific	✅ Strong / ⚠️ Gaps / ❌ Missing	[key findings]

类别	状态	关键发现
结构化数据	✅ 良好 / ⚠️ 存在差距 / ❌ 缺失	[关键发现]
知识库	✅ 良好 / ⚠️ 存在差距 / ❌ 缺失	[关键发现]
一致性（NAP+E）	✅ 良好 / ⚠️ 存在差距 / ❌ 缺失	[关键发现]
基于内容	✅ 良好 / ⚠️ 存在差距 / ❌ 缺失	[关键发现]
第三方	✅ 良好 / ⚠️ 存在差距 / ❌ 缺失	[关键发现]
AI专属	✅ 良好 / ⚠️ 存在差距 / ❌ 缺失	[关键发现]

Critical Issues

关键问题

[List any issues that severely impact entity recognition — disambiguation problems, incorrect Knowledge Panel, missing from Knowledge Graph entirely]

[列出严重影响实体识别的问题——消歧错误、知识面板信息错误、完全未收录于知识图谱等]

Top 5 Priority Actions

前5项优先行动

Sorted by: impact on entity recognition × effort required

[Signal] — [specific action]
- Impact: [High/Medium] | Effort: [Low/Medium/High]
- Why: [explanation of how this improves entity recognition]
[Signal] — [specific action]
- Impact: [High/Medium] | Effort: [Low/Medium/High]
- Why: [explanation]

3–5. [Same format]

排序依据：对实体识别的影响 × 实施难度

[信号] — [具体操作]
- 影响：[高/中] | 难度：[低/中/高]
- 原因：[此项操作如何提升实体识别的说明]
[信号] — [具体操作]
- 影响：[高/中] | 难度：[低/中/高]
- 原因：[说明]

3–5. [相同格式]

Entity Building Roadmap

实体构建路线图

Week 1-2: Foundation (Structured Data + Consistency)

第1-2周：基础搭建（结构化数据 + 一致性）

Implement/fix Organization or Person schema with full properties
Add sameAs links to all authoritative profiles
Audit and fix NAP+E consistency across all platforms
Ensure About page is entity-rich and well-structured

实现/修复包含完整属性的组织或人物Schema
为所有权威档案添加sameAs链接
审计并修复所有平台上的NAP+E一致性
确保关于页包含丰富实体内容且结构清晰

Month 1: Knowledge Bases

第1个月：知识库搭建

Create or update Wikidata entry with complete properties
Ensure CrunchBase / industry directory profiles are complete
Build Wikipedia notability (or plan path to notability)
Submit to relevant authoritative directories

创建或更新包含完整属性的Wikidata条目
确保CrunchBase / 行业目录档案完整
构建Wikipedia知名度（或规划知名度提升路径）
提交至相关权威目录

Month 2-3: Authority Building

第2-3个月：权威性构建

Secure mentions on authoritative industry sites
Build co-citation signals with established entities
Create topical content clusters that reinforce entity-topic associations
Pursue PR opportunities that generate entity mentions

获得权威行业网站的提及
构建与已确立实体的共引信号
创建强化实体-主题关联的主题内容集群
寻求可获得实体提及的公关机会

Ongoing: AI-Specific Optimization

持续优化：AI专属优化

Test AI entity resolution quarterly
Update factual claims to remain current and verifiable
Monitor AI systems for incorrect entity information
Ensure new content reinforces entity identity signals

每季度测试AI实体解析情况
更新事实声明以保持时效性和可验证性
监控AI系统中关于实体的错误信息
确保新内容强化实体身份信号

Cross-Reference

交叉参考

CORE-EEAT relevance: Items A07 (Knowledge Graph Presence) and A08 (Entity Consistency) directly overlap — entity optimization strengthens Authority dimension
CITE relevance: CITE I01-I10 (Identity dimension) measures entity signals at domain level — entity optimization feeds these scores
For content-level audit: content-quality-auditor
For domain-level audit: domain-authority-auditor

undefined

CORE-EEAT相关性：A07项（知识图谱存在感）和A08项（实体一致性）直接重叠——实体优化可强化权威性维度
CITE相关性：CITE I01-I10项（身份维度）在域名层面衡量实体信号——实体优化可为这些评分提供支持
内容层面审计：content-quality-auditor
域名层面审计：domain-authority-auditor

undefined

Validation Checkpoints

验证检查点

Input Validation

输入验证

Entity name and type identified
Primary domain/website confirmed
Target topics/industries specified
Disambiguation context provided (if entity name is common)

已确定实体名称和类型
已确认主域名/网站
已指定目标主题/行业
已提供消歧背景（若实体名称常见）

Output Validation

输出验证

Example

示例

User: "Audit entity presence for CloudMetrics, our B2B SaaS analytics platform at cloudmetrics.io"

Output:

markdown

undefined

用户："Audit entity presence for CloudMetrics, our B2B SaaS analytics platform at cloudmetrics.io"

输出：

markdown

undefined

Entity Optimization Report

实体优化报告

Entity Profile

实体档案

Entity Name: CloudMetrics Entity Type: Organization (B2B SaaS) Primary Domain: cloudmetrics.io Target Topics: analytics platform, business intelligence, enterprise analytics

实体名称：CloudMetrics 实体类型：组织（B2B SaaS） 主域名：cloudmetrics.io 目标主题：分析平台、商业智能、企业分析

AI Entity Resolution Test

AI实体解析测试

Queries tested with results reported by user:

Query	Result	Assessment
"What is CloudMetrics?"	Described as "an analytics tool" with no further detail	Partial recognition -- generic description, no mention of B2B focus or key features
"Best analytics platforms for enterprises"	CloudMetrics not mentioned in any AI response	Not recognized as a player in the enterprise analytics space
"CloudMetrics vs Datadog"	Correctly identified as a competitor to Datadog, but feature comparison was incomplete and partially inaccurate	Partial -- entity is associated with the right category but attributes are thin
"Who founded CloudMetrics?"	No answer found by any AI system tested	Entity leadership not present in AI knowledge bases

用户报告的测试查询结果：

查询内容	结果	评估
"What is CloudMetrics?"	被描述为「一款分析工具」，无更多细节	部分识别——描述通用，未提及B2B定位或核心功能
"Best analytics platforms for enterprises"	所有AI响应均未提及CloudMetrics	未被视为企业分析领域的参与者
"CloudMetrics vs Datadog"	被正确识别为Datadog的竞争对手，但功能对比不完整且部分信息不准确	部分识别——实体归属于正确类别，但属性信息不足
"Who founded CloudMetrics?"	所有测试的AI系统均无法给出答案	实体领导层信息未纳入AI知识库

Entity Health Summary

实体健康总结

Signal Category	Status	Key Findings
Knowledge Graph	❌ Missing	No Wikidata entry exists; no Google Knowledge Panel triggers for branded queries
Structured Data	⚠️ Partial	Organization schema present on homepage with name, url, and logo; missing Person schema for CEO and leadership team; no sameAs links to external profiles
Web Presence	✅ Strong	Consistent NAP across LinkedIn, Twitter/X, G2, and Crunchbase; social profiles link back to cloudmetrics.io; branded search returns owned properties in top 5
Content-Based	⚠️ Partial	About page exists but opens with marketing copy rather than an entity-defining statement; no dedicated author pages for leadership
Third-Party	⚠️ Partial	Listed on G2 and Crunchbase; 2 industry publication mentions found; no awards or analyst coverage
AI-Specific	❌ Weak	AI systems have only surface-level awareness; entity definition is not quotable from any authoritative source

信号类别	状态	关键发现
知识图谱	❌ 缺失	无Wikidata条目；品牌查询无Google知识面板触发
结构化数据	⚠️ 部分存在	首页有包含名称、网址和logo的组织Schema；缺少CEO和领导层的人物Schema；无指向外部档案的sameAs链接
网络存在感	✅ 良好	LinkedIn、Twitter/X、G2和Crunchbase上的NAP信息一致；社交档案均链接至cloudmetrics.io；品牌搜索结果前5位均为自有资产
基于内容	⚠️ 部分存在	关于页存在，但开篇为营销文案而非实体定义性陈述；无领导层专属作者页面
第三方	⚠️ 部分存在	已收录于G2和Crunchbase；找到2篇行业出版物提及；无奖项或分析师报道
AI专属	❌ 薄弱	AI系统仅具备表面认知；无权威来源可引用的实体定义

Top 3 Priority Actions

前3项优先行动

Create Wikidata entry with key properties: instance of (P31: business intelligence software company), official website (P856: cloudmetrics.io), inception (P571), country (P17)
- Impact: High | Effort: Low
- Why: Wikidata is the foundational knowledge base that feeds Google Knowledge Graph, Bing, and AI training pipelines; without it, the entity cannot be formally resolved
Add Person schema for leadership team on the About/Team page, including name, jobTitle, sameAs links to LinkedIn profiles, and worksFor pointing to the Organization entity
- Impact: High | Effort: Low
- Why: Addresses the "Who founded CloudMetrics?" gap directly; Person schema for key people creates bidirectional entity associations that strengthen organizational identity
Build Wikipedia notability through independent press coverage -- target 3-5 articles in industry publications (TechCrunch, VentureBeat, Analytics India Magazine) that mention CloudMetrics by name with verifiable claims
- Impact: High | Effort: High
- Why: Wikipedia notability requires coverage in independent reliable sources; press mentions simultaneously feed AI training data, build third-party entity signals, and create the citation foundation for a future Wikipedia article

创建Wikidata条目，包含核心属性：实例类型（P31: 商业智能软件公司）、官方网站（P856: cloudmetrics.io）、成立时间（P571）、国家（P17）
- 影响：高 | 难度：低
- 原因：Wikidata是为Google知识图谱、Bing和AI训练管道提供数据的基础知识库；若无此条目，实体无法被正式解析
在关于/团队页面添加领导层人物Schema，包含姓名、职位、指向LinkedIn档案的sameAs链接，以及指向组织实体的worksFor属性
- 影响：高 | 难度：低
- 原因：直接解决「Who founded CloudMetrics?」的信息缺口；核心人物的人物Schema可创建双向实体关联，强化组织身份
通过独立新闻报道构建Wikipedia知名度——目标在3-5篇行业出版物（TechCrunch、VentureBeat、Analytics India Magazine）中获得提及CloudMetrics名称且包含可验证声明的报道
- 影响：高 | 难度：高
- 原因：Wikipedia知名度需要独立可靠来源的报道；新闻提及同时可为AI训练数据提供支持、构建第三方实体信号，并为未来创建Wikipedia条目奠定引用基础

Cross-Reference

交叉参考

CORE-EEAT: A07 (Knowledge Graph Presence) scored Fail, A08 (Entity Consistency) scored Pass -- entity optimization should focus on knowledge base gaps rather than consistency
CITE: I-dimension weakest area is I01 (Knowledge Graph Presence) -- completing Wikidata entry and earning Knowledge Panel directly improves domain identity score

undefined

CORE-EEAT：A07项（知识图谱存在感）得分不合格，A08项（实体一致性）得分合格——实体优化应聚焦于知识库缺口而非一致性问题
CITE：身份维度最薄弱的是I01项（知识图谱存在感）——完成Wikidata条目并获得知识面板可直接提升域名身份得分

undefined

Tips for Success

成功技巧

Start with Wikidata — It's the single most influential editable knowledge base; a complete Wikidata entry with references often triggers Knowledge Panel creation within weeks
sameAs is your most powerful Schema.org property — It directly tells search engines "I am this entity in the Knowledge Graph"; always include Wikidata URL first
Test AI recognition before and after — Query ChatGPT, Claude, Perplexity, and Google AI Overview before optimizing, then again after; this is the most direct GEO metric
Entity signals compound — Unlike content SEO, entity signals from different sources reinforce each other; 5 weak signals together are stronger than 1 strong signal alone
Consistency beats completeness — A consistent entity name and description across 10 platforms beats a perfect profile on just 2
Don't neglect disambiguation — If your entity name is shared with anything else, disambiguation is the first priority; all other signals are wasted if they're attributed to the wrong entity
Pair with CITE I-dimension for domain context — Entity audit tells you how well the entity is recognized; CITE Identity (I01-I10) tells you how well the domain represents that entity; use both together

从Wikidata入手——它是影响力最大的可编辑知识库；包含完整引用的Wikidata条目通常可在数周内触发知识面板的创建
sameAs是最强大的Schema.org属性——它直接告诉搜索引擎「我是知识图谱中的这个实体」；请优先包含Wikidata链接
优化前后测试AI识别情况——优化前后分别查询ChatGPT、Claude、Perplexity和Google AI Overview；这是最直接的GEO指标
实体信号具有叠加效应——与内容SEO不同，来自不同来源的实体信号可相互强化；5个弱信号的组合强于1个强信号
一致性优于完整性——10个平台上一致的实体名称和描述，强于仅2个平台上的完美档案
不要忽视消歧——若你的实体名称与其他对象重复，消歧是首要任务；若信号被归因于错误实体，其他所有信号都将无效
结合CITE身份维度获取域名上下文——实体审计告诉你实体的识别程度；CITE身份（I01-I10）告诉你域名对该实体的代表程度；请结合使用两者

Entity Type Reference

实体类型参考

Entity Types and Key Signals

实体类型与核心信号

Entity Type	Primary Signals	Secondary Signals	Key Schema
Person	Author pages, social profiles, publication history	Speaking, awards, media mentions	Person, ProfilePage
Organization	Registration records, Wikidata, industry listings	Press coverage, partnerships, awards	Organization, Corporation
Brand	Trademark, branded search volume, social presence	Reviews, brand mentions, visual identity	Brand, Organization
Product	Product pages, reviews, comparison mentions	Awards, expert endorsements, market share	Product, SoftwareApplication
Creative Work	Publication record, citations, reviews	Awards, adaptations, cultural impact	CreativeWork, Book, Movie
Event	Event listings, press coverage, social buzz	Sponsorships, speaker profiles, attendance	Event

实体类型	核心信号	次要信号	关键Schema
人物	作者页面、社交档案、出版记录	演讲、奖项、媒体提及	Person、ProfilePage
组织	注册记录、Wikidata、行业目录收录	新闻报道、合作伙伴、奖项	Organization、Corporation
品牌	商标、品牌搜索量、社交存在感	评论、品牌提及、视觉标识	Brand、Organization
产品	产品页面、评论、对比提及	奖项、专家推荐、市场份额	Product、SoftwareApplication
创意作品	出版记录、引用、评论	奖项、改编、文化影响	CreativeWork、Book、Movie
活动	活动列表、新闻报道、社交热度	赞助、演讲者档案、参与人数	Event

Disambiguation Strategy by Situation

不同场景的消歧策略

Situation	Strategy
Common name, unique entity	Strengthen all signals; let signal volume resolve ambiguity
Name collision with larger entity	Add qualifier consistently (e.g., "Acme Software" not just "Acme"); use sameAs extensively; build topic-specific authority that differentiates
Name collision with similar entity	Geographic, industry, or product qualifiers; ensure Schema @id is unique and consistent; prioritize Wikidata disambiguation
Abbreviation/acronym conflict	Prefer full name in structured data; use abbreviation only in contexts where entity is already established
Merged or renamed entity	Redirect old entity signals; update all structured data; create explicit "formerly known as" content; update Wikidata

场景	策略
名称常见，实体独特	强化所有信号；通过信号数量解决歧义
与更大实体重名	始终添加限定词（如「Acme软件」而非仅「Acme」）；广泛使用sameAs；构建可区分的主题特定权威性
与相似实体重名	地理、行业或产品限定词；确保Schema @id唯一且一致；优先解决Wikidata消歧
缩写/首字母缩写冲突	在结构化数据中优先使用全名；仅在实体已确立的语境中使用缩写
实体合并或更名	重定向旧实体信号；更新所有结构化数据；创建明确的「曾用名」内容；更新Wikidata

Knowledge Panel Optimization

知识面板优化

Claiming and Editing

认领与编辑

Google Knowledge Panel: Claim via Google's verification process (search for entity → click "Claim this knowledge panel")
Bing Knowledge Panel: Driven by Wikidata and LinkedIn — update those sources
AI Knowledge: Driven by training data — ensure authoritative sources describe entity correctly

Google知识面板：通过Google验证流程认领（搜索实体 → 点击「Claim this knowledge panel」）
Bing知识面板：由Wikidata和LinkedIn驱动——更新这些来源
AI知识库：由训练数据驱动——确保权威来源对实体的描述准确

Common Knowledge Panel Issues

常见知识面板问题

Issue	Root Cause	Fix
No panel appears	Entity not in Knowledge Graph	Build Wikidata entry + structured data + authoritative mentions
Wrong image	Image sourced from incorrect page	Update Wikidata image; ensure preferred image on About page and social profiles
Wrong description	Description pulled from wrong source	Edit Wikidata description; ensure About page has clear entity description in first paragraph
Missing attributes	Incomplete structured data	Add properties to Schema.org markup and Wikidata entry
Wrong entity shown	Disambiguation failure	Strengthen unique signals; add qualifiers; resolve Wikidata disambiguation
Outdated info	Source data not updated	Update Wikidata, About page, and all profile pages

问题	根本原因	修复方案
无知识面板	实体未收录于知识图谱	构建Wikidata条目 + 结构化数据 + 权威提及
图片错误	图片来源页面不正确	更新Wikidata图片；确保关于页和社交档案使用首选图片
描述错误	描述来自错误来源	编辑Wikidata描述；确保关于页开篇有清晰的实体描述
属性缺失	结构化数据不完整	为Schema.org标记和Wikidata条目添加属性
显示错误实体	消歧失败	强化独特信号；添加限定词；解决Wikidata消歧
信息过时	源数据未更新	更新Wikidata、关于页和所有档案页面

Wikidata Best Practices

Wikidata最佳实践

Creating a Wikidata Entry

创建Wikidata条目

Check notability: Entity must have at least one authoritative reference
Create item: Add label, description, and aliases in relevant languages
Add statements: instance of, official website, social media links, founding date, founders, industry
Add identifiers: official website (P856), social media IDs, CrunchBase ID, ISNI, VIAF
Add references: Every statement should have a reference to an authoritative source

Important: Wikipedia's Conflict of Interest (COI) policy prohibits individuals and organizations from creating or editing articles about themselves. Instead of directly editing Wikipedia: (1) Focus on building notability through independent reliable sources (press coverage, industry publications, academic citations); (2) If you believe a Wikipedia article is warranted, consider engaging an independent Wikipedia editor through the Requested Articles process; (3) Ensure all claims about the entity are verifiable through third-party sources before any Wikipedia involvement.

检查知名度：实体需至少有一个权威引用来源
创建条目：添加相关语言的标签、描述和别名
添加声明：实例类型、官方网站、社交媒体链接、成立日期、创始人、行业
添加标识符：官方网站（P856）、社交媒体ID、CrunchBase ID、ISNI、VIAF
添加引用：每项声明均需有权威来源的引用

重要提示：Wikipedia的利益冲突（COI）政策禁止个人和组织创建或编辑关于自身的条目。请勿直接编辑Wikipedia，而是：(1) 通过独立可靠来源（新闻报道、行业出版物、学术引用）构建知名度；(2) 若你认为应创建Wikipedia条目，可通过Requested Articles流程聘请独立Wikipedia编辑；(3) 在涉及Wikipedia之前，确保所有关于实体的声明均可通过第三方来源验证。

Key Wikidata Properties by Entity Type

按实体类型划分的关键Wikidata属性

Property	Code	Person	Org	Brand	Product
instance of	P31	human	organization type	brand	product type
official website	P856	yes	yes	yes	yes
occupation / industry	P106/P452	yes	yes	—	—
founded by	P112	—	yes	yes	—
inception	P571	—	yes	yes	yes
country	P17	yes	yes	—	—
social media	various	yes	yes	yes	yes
employer	P108	yes	—	—	—
developer	P178	—	—	—	yes

属性	代码	人物	组织	品牌	产品
实例类型	P31	人类	组织类型	品牌	产品类型
官方网站	P856	是	是	是	是
职业 / 行业	P106/P452	是	是	—	—
创始人	P112	—	是	是	—
成立日期	P571	—	是	是	是
国家	P17	是	是	—	—
社交媒体	多种	是	是	是	是
雇主	P108	是	—	—	—
开发者	P178	—	—	—	是

AI Entity Optimization

AI实体优化

How AI Systems Resolve Entities

AI系统解析实体的流程

User query → Entity extraction → Entity resolution → Knowledge retrieval → Answer generation

AI systems follow this pipeline:

Extract entity mentions from the query
Resolve each mention to a known entity (or fail → "I'm not sure")
Retrieve associated knowledge about the entity
Generate response citing sources that confirmed the entity's attributes

用户查询 → 实体提取 → 实体解析 → 知识检索 → 答案生成

AI系统遵循以下流程：

提取查询中的实体提及
解析每个提及为已知实体（或失败 →「不确定」）
检索与实体相关的知识
生成引用确认实体属性的来源的响应

Signals AI Systems Use for Entity Resolution

AI系统用于实体解析的信号

Signal Type	What AI Checks	How to Optimize
Training data presence	Was entity in pre-training corpus?	Get mentioned in high-quality, widely-crawled sources
Retrieval augmentation	Does entity appear in live search results?	Strong SEO presence for branded queries
Structured data	Can entity be matched to Knowledge Graph?	Complete Wikidata + Schema.org
Contextual co-occurrence	What topics/entities appear alongside?	Build consistent topic associations across content
Source authority	Are sources about entity trustworthy?	Get mentioned by authoritative, well-known sources
Recency	Is information current?	Keep all entity profiles and content updated

信号类型	AI检查内容	优化方法
训练数据存在性	实体是否在预训练语料库中？	在高质量、广泛抓取的来源中获得提及
检索增强	实体是否出现在实时搜索结果中？	品牌查询的SEO存在感强
结构化数据	实体能否与知识图谱匹配？	完整的Wikidata + Schema.org
上下文共现	哪些主题/实体与该实体同时出现？	在所有内容中构建一致的主题关联
来源权威性	关于实体的来源是否可信？	获得权威知名来源的提及
时效性	信息是否最新？	保持所有实体档案和内容更新

Entity-Specific GEO Tactics

实体专属GEO策略

Define clearly: First paragraph of About page and key pages should define the entity in a way AI can quote directly
Be consistent: Use identical entity description across all platforms
Build associations: Create content that explicitly connects entity to target topics
Earn mentions: Third-party authoritative mentions are stronger entity signals than self-description
Stay current: Outdated entity information causes AI to lose confidence and stop citing

明确定义：关于页和关键页面的第一段应以AI可直接引用的方式定义实体
保持一致：在所有平台使用完全相同的实体描述
构建关联：创建明确将实体与目标主题关联的内容
获得提及：第三方权威提及比自我描述的实体信号更强
保持最新：过时的实体信息会导致AI失去信任并停止引用

Reference Materials

参考资料

Detailed guides for entity optimization:

references/entity-signal-checklist.md — Complete signal checklist with verification methods
references/knowledge-graph-guide.md — Wikidata, Wikipedia, and Knowledge Graph optimization playbook

实体优化详细指南：

references/entity-signal-checklist.md — 包含验证方法的完整信号清单
references/knowledge-graph-guide.md — Wikidata、Wikipedia和知识图谱优化手册