geo-platform-optimizer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGEO Platform Optimizer
GEO平台优化器
Core Insight
核心洞察
Only 11% of domains are cited by BOTH ChatGPT and Google AI Overviews for the same query. Each AI search platform uses different indexes, ranking logic, and source preferences. A page optimized for Google AI Overviews may be invisible to ChatGPT, and vice versa. Platform-specific optimization is not optional — it is the foundation of any serious GEO strategy.
只有11%的域名会在同一个查询中同时被ChatGPT和Google AI Overviews引用。每个AI搜索平台使用不同的索引、排名逻辑和来源偏好。针对Google AI Overviews优化的页面可能无法被ChatGPT发现,反之亦然。针对特定平台的优化并非可选选项——它是任何严谨GEO策略的基础。
How to Use This Skill
如何使用本Skill
- Collect the target URL and the site's primary topic/industry
- Run each platform checklist below against the site
- Score each platform on the 0-100 rubric
- Generate GEO-PLATFORM-OPTIMIZATION.md with per-platform scores, gaps, and action items
- 收集目标URL以及网站的核心主题/行业
- 对照以下各平台的检查清单对网站进行评估
- 按照0-100分的评分标准为每个平台打分
- 生成GEO-PLATFORM-OPTIMIZATION.md文件,包含各平台的得分、差距点和行动项
Platform 1: Google AI Overviews (AIO)
平台1:Google AI Overviews(AIO)
How AIO Selects Sources
AIO如何选择来源
- 92% of AIO citations come from pages already ranking in the top 10 organic results — traditional SEO is the gateway
- However, 47% of citations come from pages ranking below position 5 — AIO has its own selection logic favoring clarity and directness over raw rank
- AIO strongly favors pages with clean structure, direct answers, and scannable formatting
- Featured snippet optimization has ~70% overlap with AIO optimization
- AIO prefers concise, factual, unambiguous answers — hedging and filler reduce citation probability
- 92%的AIO引用来自已经在自然搜索前10名的页面——传统SEO是入门前提
- 然而,47%的引用来自排名第5位之后的页面——AIO有自己的选择逻辑,相较于单纯的排名,更青睐清晰直接的内容
- AIO非常偏好具有清晰结构、直接答案和易扫描格式的页面
- 精选摘要优化与AIO优化有约70%的重叠度
- AIO偏好简洁、真实、明确的答案——含糊其辞和冗余内容会降低被引用的概率
Optimization Checklist
优化检查清单
- Question-Based Headings: Use H2/H3 headings phrased as questions matching real user queries. Check Google's "People Also Ask" for the target topic and mirror those exact phrasings.
- Direct Answer in First Paragraph: After each question heading, provide a clear 1-2 sentence answer immediately. Then expand with supporting detail. The first sentence should be a standalone citation candidate.
- Tables and Structured Comparisons: AIO heavily cites tables. Convert any comparison, pricing, specification, or feature data into HTML tables. Use clear column headers.
- Ordered and Unordered Lists: Step-by-step processes should use ordered lists. Feature lists should use unordered lists. AIO extracts these directly.
- FAQ Sections: Add a dedicated FAQ section with 5-10 real questions. Use proper H3 headings for each question. While FAQPage schema rich results are restricted to govt/health sites since Aug 2023, the content pattern still helps AIO extraction.
- Definitions and Glossary Boxes: For any industry-specific term, provide a clear definition. Format: "[Term] is [concise definition]." AIO frequently cites definitions.
- Statistics with Sources: Include specific numbers with attribution. "According to [Source], [statistic]." AIO prefers citeable, specific claims over vague assertions.
- Publication Date: Include a visible publication date and last-updated date. AIO deprioritizes undated content for time-sensitive queries.
- Author Byline: Display author name with credentials. Link to an author page with bio, credentials, and sameAs links.
- Page Depth: Keep target pages within 3 clicks of homepage. AIO rarely cites deep, orphaned content.
- 基于问题的标题:使用以问题形式表述的H2/H3标题,匹配真实用户的查询。查看目标主题的Google“相关问题”,并直接复用这些表述。
- 首段直接给出答案:在每个问题标题后,立即提供1-2句清晰的答案,再展开补充细节。第一句话应能作为独立的引用候选内容。
- 表格与结构化对比:AIO大量引用表格内容。将任何对比、定价、规格或功能数据转换为HTML表格,使用清晰的列标题。
- 有序与无序列表:分步流程应使用有序列表,功能列表使用无序列表。AIO会直接提取这些内容。
- FAQ板块:添加包含5-10个真实问题的专属FAQ板块。每个问题使用合适的H3标题。尽管自2023年8月起,FAQPage结构化数据富结果仅对政府/医疗网站开放,但这种内容模式仍有助于AIO提取信息。
- 定义与术语框:对于任何行业特定术语,提供清晰的定义。格式为:“[术语] 是[简洁定义]。”AIO经常引用定义类内容。
- 带来源的统计数据:包含具体数字并注明出处。例如“根据[来源],[统计数据]。”AIO偏好可引用的具体声明,而非模糊断言。
- 发布日期:显示可见的发布日期和最后更新日期。对于时效性查询,AIO会降低无日期内容的优先级。
- 作者署名:显示作者姓名及资质。链接至包含个人简介、资质和sameAs链接的作者页面。
- 页面深度:目标页面应在距主页3次点击以内。AIO很少引用深层的孤立内容。
Scoring Rubric (0-100)
评分标准(0-100分)
| Criterion | Points | How to Score |
|---|---|---|
| Ranks in top 10 for target queries | 20 | 20 if yes, 10 if top 20, 0 if beyond |
| Question-based headings present | 10 | 2 points per question heading, max 10 |
| Direct answers after headings | 15 | 3 points per direct answer, max 15 |
| Tables present for comparison data | 10 | 10 if tables used appropriately, 5 if partial, 0 if absent |
| Lists for processes/features | 10 | 10 if present, 5 if partial |
| FAQ section with 5+ questions | 10 | 10 if 5+, 5 if 1-4, 0 if none |
| Statistics with citations | 10 | 2 points per cited stat, max 10 |
| Publication/updated date visible | 5 | 5 if both dates, 3 if one, 0 if none |
| Author byline with credentials | 5 | 5 if full byline, 3 if name only, 0 if none |
| Clean URL + heading hierarchy | 5 | 5 if H1>H2>H3 clean, 3 if minor issues, 0 if broken |
| 评估项 | 分值 | 评分方式 |
|---|---|---|
| 目标查询排名进入前10 | 20 | 是得20分,前20名得10分,之外得0分 |
| 存在基于问题的标题 | 10 | 每个问题标题得2分,最高10分 |
| 标题后有直接答案 | 15 | 每个直接答案得3分,最高15分 |
| 对比数据使用表格呈现 | 10 | 合理使用表格得10分,部分使用得5分,未使用得0分 |
| 流程/功能使用列表呈现 | 10 | 已使用得10分,部分使用得5分 |
| FAQ板块包含5个以上问题 | 10 | 5个及以上得10分,1-4个得5分,无得0分 |
| 带引用的统计数据 | 10 | 每个带引用的统计数据得2分,最高10分 |
| 可见发布/更新日期 | 5 | 两者都有得5分,仅有一个得3分,全无得0分 |
| 带资质的作者署名 | 5 | 完整署名得5分,仅有姓名得3分,无得0分 |
| 清晰的URL + 标题层级 | 5 | H1>H2>H3结构清晰得5分,小问题得3分,结构混乱得0分 |
Platform 2: ChatGPT Web Search
平台2:ChatGPT网页搜索
How ChatGPT Selects Sources
ChatGPT如何选择来源
- Uses Bing's search index as its foundation (not Google)
- Top citation sources by domain share: Wikipedia (47.9%), Reddit (11.3%), YouTube, major news outlets
- ChatGPT heavily weights entity recognition — if your brand exists as a structured entity (Wikipedia, Wikidata, Crunchbase), it is far more likely to be cited
- Prefers authoritative, well-established sources over new or niche sites
- Longer, more comprehensive articles get cited more often than short pieces
- ChatGPT tends to cite the most canonical source for a claim rather than the original
- 以Bing的搜索索引为基础(而非Google)
- 按域名占比排序的顶级引用来源:Wikipedia(47.9%)、Reddit(11.3%)、YouTube、主流新闻媒体
- ChatGPT非常重视实体识别——如果你的品牌是结构化实体(存在于Wikipedia、Wikidata、Crunchbase),被引用的概率会大幅提升
- 相较于新网站或小众网站,更偏好权威、成熟的来源
- 较长、更全面的文章比短内容更易被引用
- ChatGPT倾向于引用某一主张的最具代表性来源,而非原创来源
Optimization Checklist
优化检查清单
- Wikipedia Presence: Check if the brand/person/product has a Wikipedia article. If not, assess notability criteria. If notable, create a draft. If an article exists, ensure it is accurate and current.
- Wikidata Entity: Verify the entity exists on Wikidata (wikidata.org). If not, create a Wikidata item with key properties: instance of, official website, social media links, founding date, headquarters location.
- Bing Webmaster Tools: Verify the site is registered in Bing Webmaster Tools. Submit sitemap. Check for crawl errors.
- Bing Index Coverage: Use on Bing to verify key pages are indexed. Bing may have different indexed pages than Google.
site:domain.com - Reddit Authority: Check for brand mentions on Reddit. Identify relevant subreddits. Assess whether the brand participates authentically in discussions.
- YouTube Presence: Verify YouTube channel exists with relevant content. Video descriptions should contain full URLs and entity information.
- Authoritative Backlinks: ChatGPT/Bing weight .edu, .gov, and major publication backlinks heavily. Audit backlink profile for these sources.
- Entity Consistency: Brand name, founding date, leadership, and key facts must be consistent across Wikipedia, Crunchbase, LinkedIn, and the official website.
- Comprehensive Content: Pages targeting ChatGPT citation should be 2000+ words with thorough topic coverage. ChatGPT prefers single authoritative sources over combining multiple thin pages.
- Clear Attribution: Include "About" sections, company descriptions, and founding stories. ChatGPT uses these for entity grounding.
- Wikipedia存在感:检查品牌/人物/产品是否有Wikipedia条目。如果没有,评估是否符合关注度标准。若符合,创建草稿。若已有条目,确保内容准确且更新及时。
- Wikidata实体:验证实体是否存在于Wikidata(wikidata.org)。如果没有,创建Wikidata条目并填写关键属性:实例类型、官方网站、社交媒体链接、成立日期、总部位置。
- Bing网站管理员工具:确认网站已在Bing网站管理员工具中注册,提交站点地图,检查抓取错误。
- Bing索引覆盖范围:在Bing上使用验证核心页面是否已被索引。Bing的索引页面可能与Google不同。
site:domain.com - Reddit权威性:检查Reddit上的品牌提及,找到相关子版块,评估品牌是否在讨论中进行了真实参与。
- YouTube存在感:确认存在包含相关内容的YouTube频道。视频描述应包含完整URL和实体信息。
- 权威反向链接:ChatGPT/Bing非常看重.edu、.gov和主流媒体的反向链接。审计反向链接配置文件中是否有这些来源。
- 实体一致性:品牌名称、成立日期、领导层和关键信息必须在Wikipedia、Crunchbase、LinkedIn和官方网站上保持一致。
- 全面的内容:针对ChatGPT引用优化的页面应超过2000字,覆盖主题的所有方面。ChatGPT偏好单一权威来源,而非组合多个简短页面。
- 清晰的归属信息:添加“关于”板块、公司描述和创立故事。ChatGPT会用这些内容进行实体定位。
Scoring Rubric (0-100)
评分标准(0-100分)
| Criterion | Points | How to Score |
|---|---|---|
| Wikipedia article exists and is accurate | 20 | 20 if exists, 10 if stub, 0 if none |
| Wikidata entity with 5+ properties | 10 | 10 if complete, 5 if basic, 0 if none |
| Bing index coverage of key pages | 10 | 10 if full, 5 if partial, 0 if poor |
| Reddit brand mentions (positive) | 10 | 10 if active discussions, 5 if mentions, 0 if none |
| YouTube channel with relevant content | 10 | 10 if active, 5 if present but sparse, 0 if none |
| Authoritative backlinks (.edu, .gov, press) | 15 | 3 points per authoritative backlink category, max 15 |
| Entity consistency across platforms | 10 | 10 if consistent, 5 if minor discrepancies, 0 if major |
| Content comprehensiveness (2000+ words) | 10 | 10 if thorough, 5 if adequate, 0 if thin |
| Bing Webmaster Tools configured | 5 | 5 if verified, 0 if not |
| 评估项 | 分值 | 评分方式 |
|---|---|---|
| Wikipedia条目存在且准确 | 20 | 存在得20分, stub条目得10分,无得0分 |
| 包含5个以上属性的Wikidata实体 | 10 | 完整得10分,基础信息得5分,无得0分 |
| 核心页面的Bing索引覆盖 | 10 | 全覆盖得10分,部分覆盖得5分,覆盖差得0分 |
| Reddit上的正面品牌提及 | 10 | 有活跃讨论得10分,仅提及得5分,无得0分 |
| 包含相关内容的YouTube频道 | 10 | 活跃更新得10分,有内容但稀疏得5分,无得0分 |
| 权威反向链接(.edu、.gov、媒体) | 15 | 每个类别的权威反向链接得3分,最高15分 |
| 跨平台实体信息一致性 | 10 | 完全一致得10分,小差异得5分,大差异得0分 |
| 内容全面性(2000+字) | 10 | 内容详尽得10分,内容充足得5分,内容单薄得0分 |
| 已配置Bing网站管理员工具 | 5 | 已验证得5分,未配置得0分 |
Platform 3: Perplexity AI
平台3:Perplexity AI
How Perplexity Selects Sources
Perplexity如何选择来源
- Top citation sources: Reddit (46.7%), Wikipedia, YouTube, major publications
- Perplexity places the heaviest emphasis on community validation of all AI search platforms
- Strongly favors discussion threads where claims are debated, validated, or expanded by multiple participants
- Prefers recent content — publication date is a strong ranking signal
- Cites multiple sources per answer (typically 5-15), so there is more opportunity for mid-authority sites to appear
- Uses its own crawling infrastructure in addition to search APIs
- 顶级引用来源:Reddit(46.7%)、Wikipedia、YouTube、主流出版物
- 在所有AI搜索平台中,Perplexity最看重社区验证
- 非常青睐讨论帖,即有多名参与者对主张进行辩论、验证或拓展的内容
- 偏好近期内容——发布日期是重要的排名信号
- 每个答案通常引用5-15个来源,因此中等权威的网站有更多露脸机会
- 除了搜索API,还使用自有爬虫基础设施
Optimization Checklist
优化检查清单
- Active Reddit Presence: The brand or its representatives should participate authentically in relevant subreddit discussions. Not promotional — helpful, specific, and community-oriented.
- Reddit AMAs and Threads: Encourage or participate in AMAs, detailed discussion threads, and community Q&As. Perplexity treats these as high-signal content.
- Forum and Community Presence: Beyond Reddit, check Hacker News, Stack Overflow, Quora, and niche industry forums. Perplexity indexes these heavily.
- Discussion-Friendly Content: Publish content that invites discussion — opinion pieces, research findings, contrarian takes, original data. Content that gets shared and debated in communities ranks higher.
- Freshness Signals: Publish content with clear dates. Update content regularly. Perplexity deprioritizes stale content more aggressively than other platforms.
- Multiple Source Validation: Claims in your content should be supported by other sources. Perplexity cross-references and prefers claims it can verify from multiple origins.
- YouTube Video Content: Create video content that Perplexity can reference. Ensure video titles, descriptions, and transcripts contain target information.
- Direct, Quotable Passages: Write paragraphs that can stand alone as citations. Each paragraph should make one clear point with supporting evidence.
- Original Data and Research: Publish original surveys, benchmarks, case studies, or datasets. Perplexity heavily favors primary sources.
- Perplexity Pages: Check if Perplexity has created a "Page" about your topic/brand. These are curated summaries that influence future citations.
- 活跃的Reddit存在感:品牌或其代表应在相关子版块中真实参与讨论,而非进行推广——内容要实用、具体、贴合社区需求。
- Reddit AMA与讨论帖:鼓励或参与AMA、深度讨论帖和社区问答。Perplexity将这些视为高信号内容。
- 论坛与社区存在感:除Reddit外,检查Hacker News、Stack Overflow、Quora和小众行业论坛。Perplexity会大量索引这些平台的内容。
- 易引发讨论的内容:发布能激发讨论的内容——观点文章、研究发现、反向观点、原创数据。被分享和讨论的内容排名更高。
- 新鲜度信号:发布带有清晰日期的内容,定期更新。Perplexity比其他平台更积极地降低陈旧内容的优先级。
- 多来源验证:内容中的主张应得到其他来源的支持。Perplexity会交叉验证,更偏好能从多个来源核实的主张。
- YouTube视频内容:创建Perplexity可引用的视频内容,确保视频标题、描述和字幕包含目标信息。
- 直接可引用的段落:撰写可独立作为引用内容的段落,每个段落应围绕一个清晰观点展开并辅以证据。
- 原创数据与研究:发布原创调查、基准测试、案例研究或数据集。Perplexity非常青睐一手来源。
- Perplexity页面:检查Perplexity是否已创建关于你的主题/品牌的“Page”。这些是 curated摘要,会影响后续的引用。
Scoring Rubric (0-100)
评分标准(0-100分)
| Criterion | Points | How to Score |
|---|---|---|
| Active Reddit presence in relevant subreddits | 20 | 20 if active contributor, 10 if mentioned, 0 if absent |
| Forum/community mentions (HN, SO, Quora) | 10 | 10 if multiple platforms, 5 if one, 0 if none |
| Content freshness (updated within 6 months) | 10 | 10 if recent, 5 if within year, 0 if older |
| Original research/data published | 15 | 15 if original research, 10 if case studies, 5 if some data, 0 if none |
| YouTube content with transcripts | 10 | 10 if active channel, 5 if some videos, 0 if none |
| Quotable, standalone paragraphs | 10 | 2 points per well-structured quotable paragraph, max 10 |
| Multi-source claim validation | 10 | 10 if claims well-sourced, 5 if some sourcing, 0 if none |
| Discussion-generating content | 10 | 10 if content gets shared/discussed, 5 if some engagement, 0 if none |
| Wikipedia/Wikidata presence | 5 | 5 if present, 0 if absent |
| 评估项 | 分值 | 评分方式 |
|---|---|---|
| 在相关子版块中活跃参与Reddit讨论 | 20 | 活跃贡献者得20分,仅被提及得10分,无存在感得0分 |
| 论坛/社区提及(HN、SO、Quora) | 10 | 多平台提及得10分,单一平台得5分,无得0分 |
| 内容新鲜度(6个月内更新) | 10 | 近期更新得10分,1年内更新得5分,1年以上得0分 |
| 发布原创研究/数据 | 15 | 有原创研究得15分,有案例研究得10分,有部分数据得5分,无得0分 |
| 带字幕的YouTube内容 | 10 | 活跃频道得10分,有部分视频得5分,无得0分 |
| 可独立引用的段落 | 10 | 每个结构良好的可引用段落得2分,最高10分 |
| 多来源验证的主张 | 10 | 主张有充分来源支持得10分,部分有来源得5分,无得0分 |
| 引发讨论的内容 | 10 | 内容被分享/讨论得10分,有部分互动得5分,无得0分 |
| Wikipedia/Wikidata存在感 | 5 | 存在得5分,无得0分 |
Platform 4: Google Gemini
平台4:Google Gemini
How Gemini Selects Sources
Gemini如何选择来源
- Uses Google's search index plus strong weighting toward Google-owned properties
- YouTube content is weighted significantly more heavily than in standard Google Search
- Google Business Profile data is directly accessible to Gemini
- Gemini uses Google's Knowledge Graph directly — entity presence in Knowledge Graph is a major advantage
- Structured data (Schema.org) is consumed directly by Gemini for entity understanding
- Gemini multi-modal: can reference images, videos, and text together
- 以Google的搜索索引为基础,并大幅加权Google自有属性
- YouTube内容的权重远高于标准Google搜索
- Google商家档案数据可直接被Gemini访问
- Gemini直接使用Google知识图谱——知识图谱中的实体存在感是重大优势
- 结构化数据(Schema.org)会被Gemini直接用于实体理解
- Gemini支持多模态:可同时引用图片、视频和文本
Optimization Checklist
优化检查清单
- Google Knowledge Panel: Check if the brand has a Google Knowledge Panel. If not, claim it through Google Business Profile or structured data. Ensure all information is accurate.
- Google Business Profile: Complete and optimize GBP with all fields: hours, services, photos, posts, Q&A. Gemini pulls directly from GBP for local queries.
- YouTube Strategy: Create YouTube content for every key topic. Optimize titles, descriptions, timestamps, and closed captions. Gemini cites YouTube more than any other AI platform.
- YouTube Chapters and Timestamps: Use chapters (timestamps in description) so Gemini can reference specific segments of videos.
- Google Merchant Center: For e-commerce, ensure products are in Google Merchant Center. Gemini references product data directly.
- Structured Data (Schema.org): Implement comprehensive Schema.org markup. Gemini uses this for entity understanding more aggressively than other platforms.
- Google Sites Ecosystem: Ensure presence across Google ecosystem: Google Scholar (for research), Google News (for publishers), Google Maps (for local).
- Image Optimization: Gemini is multi-modal. Use descriptive alt text, structured image filenames, and high-quality images. Include relevant images with every piece of content.
- Google E-E-A-T Signals: All standard Google E-E-A-T signals apply with extra weight. Author pages, about pages, editorial policies, and expertise demonstrations.
- Chrome Web Store / Google Workspace Marketplace: For software companies, presence on Google platforms adds entity signals.
- Google知识面板:检查品牌是否有Google知识面板。如果没有,通过Google商家档案或结构化数据申请认领,确保所有信息准确。
- Google商家档案:完整优化Google商家档案的所有字段:营业时间、服务、照片、帖子、问答。Gemini会直接从GBP提取本地查询的信息。
- YouTube策略:为每个核心主题创建YouTube内容,优化标题、描述、时间戳和字幕。Gemini比其他任何AI平台都更常引用YouTube内容。
- YouTube章节与时间戳:使用章节(描述中的时间戳),以便Gemini可以引用视频的特定片段。
- Google Merchant Center:对于电商网站,确保产品已加入Google Merchant Center。Gemini会直接引用产品数据。
- 结构化数据(Schema.org):实施全面的Schema.org标记。Gemini比其他平台更积极地使用这些数据进行实体理解。
- Google生态系统存在感:确保在Google生态系统中布局:Google Scholar(针对研究)、Google News(针对出版商)、Google Maps(针对本地商家)。
- 图片优化:Gemini支持多模态,使用描述性alt文本、结构化图片文件名和高质量图片,每篇内容都要包含相关图片。
- Google E-E-A-T信号:所有标准的Google E-E-A-T信号权重更高,包括作者页面、关于页面、编辑政策和专业能力展示。
- Chrome网上应用店 / Google Workspace市场:对于软件公司,在Google平台上的存在感能增加实体信号。
Scoring Rubric (0-100)
评分标准(0-100分)
| Criterion | Points | How to Score |
|---|---|---|
| Google Knowledge Panel exists | 15 | 15 if complete, 10 if partial, 0 if none |
| Google Business Profile complete | 10 | 10 if fully optimized, 5 if basic, 0 if none |
| YouTube channel with topic-relevant content | 20 | 20 if active with chapters, 10 if present, 0 if none |
| Schema.org structured data implemented | 15 | 15 if comprehensive, 10 if basic, 5 if minimal, 0 if none |
| Google ecosystem presence (Scholar, News, Maps) | 10 | 10 if 3+, 5 if 1-2, 0 if none |
| Image optimization (alt text, filenames) | 10 | 10 if all images optimized, 5 if partial, 0 if none |
| E-E-A-T signals (author pages, about, editorial) | 10 | 10 if strong, 5 if partial, 0 if weak |
| Google Merchant Center (if e-commerce) | 5 | 5 if applicable and active, N/A otherwise |
| Multi-modal content (text + images + video) | 5 | 5 if rich multi-modal, 3 if some, 0 if text-only |
| 评估项 | 分值 | 评分方式 |
|---|---|---|
| Google知识面板存在 | 15 | 完整得15分,部分得10分,无得0分 |
| Google商家档案完整 | 10 | 完全优化得10分,基础完善得5分,无得0分 |
| 包含主题相关内容的YouTube频道 | 20 | 活跃且有章节得20分,仅存在得10分,无得0分 |
| 已实施Schema.org结构化数据 | 15 | 全面实施得15分,基础实施得10分,少量实施得5分,无得0分 |
| Google生态系统存在感(Scholar、News、Maps) | 10 | 3个及以上得10分,1-2个得5分,无得0分 |
| 图片优化(alt文本、文件名) | 10 | 所有图片都优化得10分,部分优化得5分,无得0分 |
| E-E-A-T信号(作者页面、关于页、编辑内容) | 10 | 信号强得10分,部分完善得5分,薄弱得0分 |
| Google Merchant Center(电商适用) | 5 | 适用且活跃得5分,否则不适用 |
| 多模态内容(文本+图片+视频) | 5 | 丰富多模态得5分,部分有得3分,纯文本得0分 |
Platform 5: Bing Copilot
平台5:Bing Copilot
How Copilot Selects Sources
Copilot如何选择来源
- Uses Bing's search index (shared infrastructure with ChatGPT but different ranking/selection)
- Supports IndexNow protocol for near-instant indexing of new and updated content
- Copilot tends to cite fewer sources per answer (typically 3-5) but gives more prominent attribution
- Microsoft ecosystem integration: LinkedIn, GitHub, Microsoft Learn content is weighted
- Copilot prefers pages with clear, structured markup and fast load times
- 使用Bing的搜索索引(与ChatGPT共享基础设施,但排名/选择逻辑不同)
- 支持IndexNow协议,可近乎实时地索引新内容和更新内容
- Copilot每个答案引用的来源数量更少(通常3-5个),但会给予更突出的署名
- 微软生态系统集成:LinkedIn、GitHub、Microsoft Learn内容会被加权
- Copilot偏好具有清晰结构化标记和加载速度快的页面
Optimization Checklist
优化检查清单
- Bing Webmaster Tools: Register and verify site. Submit XML sitemap. Review and fix any crawl issues.
- IndexNow Implementation: Implement the IndexNow protocol to notify Bing of content changes in real-time. Submit a key file at and ping the IndexNow API on content publish/update.
/.well-known/indexnow-key.txt - LinkedIn Company Page: Ensure the company LinkedIn page is complete with accurate description, employee connections, and regular posts. Copilot indexes LinkedIn content.
- GitHub Presence: For tech companies, maintain an active GitHub presence. Copilot references GitHub repos, documentation, and README files.
- Microsoft Learn / Documentation: If relevant, contribute to Microsoft Learn or ensure documentation is compatible with Microsoft's documentation standards.
- Bing Places for Business: Equivalent to Google Business Profile. Complete all fields for local search visibility in Copilot.
- Clear Meta Descriptions: Bing/Copilot weights meta descriptions more heavily than Google does. Write compelling, keyword-rich meta descriptions for every page.
- Social Signals: Bing has historically weighted social signals (shares, likes, engagement) more than Google. Maintain active social media presence.
- Exact-Match Keywords: Bing's algorithm is more literal about keyword matching than Google. Include exact target phrases in titles, headings, and body content.
- Fast Page Load: Copilot deprioritizes slow pages. Target sub-2-second load time. Optimize images, enable compression, minimize render-blocking resources.
- Bing网站管理员工具:注册并验证网站,提交XML站点地图,检查并修复抓取问题。
- IndexNow协议实施:实施IndexNow协议,实时通知Bing内容变更。在提交密钥文件,并在内容发布/更新时调用IndexNow API。
/.well-known/indexnow-key.txt - LinkedIn公司主页:确保公司LinkedIn主页完整,包含准确描述、员工关联和定期发布的帖子。Copilot会索引LinkedIn内容。
- GitHub存在感:对于科技公司,保持活跃的GitHub存在感。Copilot会引用GitHub仓库、文档和README文件。
- Microsoft Learn / 文档:若相关,贡献至Microsoft Learn或确保文档符合微软的文档标准。
- Bing商家信息:相当于Google商家档案,完整填写所有字段,以提升Copilot本地搜索的可见性。
- 清晰的元描述:Bing/Copilot比Google更看重元描述。为每个页面撰写有吸引力、含关键词的元描述。
- 社交信号:Bing历来比Google更看重社交信号(分享、点赞、互动),保持活跃的社交媒体存在感。
- 精确匹配关键词:Bing的算法比Google更注重关键词的字面匹配,在标题、标题标签和正文中包含目标精确短语。
- 页面加载速度快:Copilot会降低慢页面的优先级,目标是加载时间低于2秒。优化图片、启用压缩、减少阻塞渲染的资源。
Scoring Rubric (0-100)
评分标准(0-100分)
| Criterion | Points | How to Score |
|---|---|---|
| Bing Webmaster Tools verified + sitemap | 15 | 15 if verified, 5 if partial, 0 if not |
| IndexNow protocol implemented | 15 | 15 if active, 0 if not |
| Bing index coverage of key pages | 10 | 10 if full, 5 if partial, 0 if poor |
| LinkedIn company page (complete) | 10 | 10 if complete, 5 if basic, 0 if none |
| GitHub presence (if applicable) | 5 | 5 if active, N/A if not applicable |
| Meta descriptions optimized | 10 | 10 if all key pages, 5 if partial, 0 if missing |
| Social media engagement signals | 10 | 10 if active engagement, 5 if present, 0 if none |
| Exact-match keywords in titles/headings | 10 | 10 if well-optimized, 5 if partial, 0 if not |
| Page load speed < 2 seconds | 10 | 10 if < 2s, 5 if < 4s, 0 if > 4s |
| Bing Places configured (if local) | 5 | 5 if complete, N/A if not local |
| 评估项 | 分值 | 评分方式 |
|---|---|---|
| Bing网站管理员工具已验证 + 提交站点地图 | 15 | 已验证得15分,部分完成得5分,未配置得0分 |
| 已实施IndexNow协议 | 15 | 已启用得15分,未实施得0分 |
| 核心页面的Bing索引覆盖 | 10 | 全覆盖得10分,部分覆盖得5分,覆盖差得0分 |
| LinkedIn公司主页完整 | 10 | 完整得10分,基础完善得5分,无得0分 |
| GitHub存在感(适用时) | 5 | 活跃得5分,不适用则忽略 |
| 元描述已优化 | 10 | 所有核心页面都优化得10分,部分优化得5分,缺失得0分 |
| 社交媒体互动信号 | 10 | 互动活跃得10分,仅存在得5分,无得0分 |
| 标题/标题标签包含精确匹配关键词 | 10 | 优化良好得10分,部分包含得5分,未包含得0分 |
| 页面加载速度<2秒 | 10 | 低于2秒得10分,低于4秒得5分,超过4秒得0分 |
| Bing商家信息已配置(本地适用) | 5 | 完整得5分,不适用则忽略 |
Cross-Platform Summary
跨平台总结
Universal Optimization Actions (help ALL platforms)
通用优化行动(对所有平台都有帮助)
- Wikipedia/Wikidata entity presence
- YouTube channel with relevant content
- Comprehensive, well-structured content with clear headings
- Schema.org structured data (especially Organization + sameAs)
- Fast page load and clean HTML
- Author pages with credentials and sameAs links
- Regular content updates with visible dates
- Wikipedia/Wikidata实体存在感
- 包含相关内容的YouTube频道
- 结构清晰、标题明确的全面内容
- Schema.org结构化数据(尤其是Organization + sameAs)
- 页面加载速度快且HTML代码简洁
- 带资质和sameAs链接的作者页面
- 带可见日期的定期内容更新
Platform-Specific Priorities
平台专属优先级
| Priority | Google AIO | ChatGPT | Perplexity | Gemini | Copilot |
|---|---|---|---|---|---|
| #1 | Top-10 ranking | Wikipedia | Reddit presence | YouTube | IndexNow |
| #2 | Q&A structure | Entity graph | Original research | Knowledge Panel | Bing WMT |
| #3 | Tables/lists | Bing SEO | Freshness | Schema.org | |
| #4 | Featured snippets | Community forums | GBP | Meta descriptions |
| 优先级 | Google AIO | ChatGPT | Perplexity | Gemini | Copilot |
|---|---|---|---|---|---|
| #1 | 前10名排名 | Wikipedia | Reddit存在感 | YouTube | IndexNow |
| #2 | Q&A结构 | 实体图谱 | 原创研究 | 知识面板 | Bing WMT |
| #3 | 表格/列表 | Bing SEO | 新鲜度 | Schema.org | |
| #4 | 精选摘要 | 社区论坛 | GBP | 元描述 |
Output Format
输出格式
Generate GEO-PLATFORM-OPTIMIZATION.md with the following structure:
markdown
undefined生成GEO-PLATFORM-OPTIMIZATION.md文件,结构如下:
markdown
undefinedGEO Platform Optimization Report — [Domain]
GEO平台优化报告 — [域名]
Date: [Date]
日期: [日期]
Overall Platform Readiness
整体平台就绪度
- Combined GEO Score: XX/100 (average of all platform scores)
- 综合GEO得分: XX/100(所有平台得分的平均值)
Platform Scores
平台得分
| Platform | Score | Status |
|---|---|---|
| Google AI Overviews | XX/100 | [Strong/Moderate/Weak] |
| ChatGPT Web Search | XX/100 | [Strong/Moderate/Weak] |
| Perplexity AI | XX/100 | [Strong/Moderate/Weak] |
| Google Gemini | XX/100 | [Strong/Moderate/Weak] |
| Bing Copilot | XX/100 | [Strong/Moderate/Weak] |
Status thresholds: Strong = 70+, Moderate = 40-69, Weak = 0-39
| 平台 | 得分 | 状态 |
|---|---|---|
| Google AI Overviews | XX/100 | [良好/中等/薄弱] |
| ChatGPT网页搜索 | XX/100 | [良好/中等/薄弱] |
| Perplexity AI | XX/100 | [良好/中等/薄弱] |
| Google Gemini | XX/100 | [良好/中等/薄弱] |
| Bing Copilot | XX/100 | [良好/中等/薄弱] |
状态阈值: 良好 = 70+, 中等 = 40-69, 薄弱 = 0-39
Platform Details
平台详情
[Per-platform breakdown with score, gaps found, specific actions]
[各平台的得分、发现的差距、具体行动项]
Prioritized Action Plan
优先级行动方案
Quick Wins (this week)
快速见效(本周)
[Actions that improve multiple platform scores with minimal effort]
[只需少量投入就能提升多个平台得分的行动]
Medium-Term (this month)
中期目标(本月)
[Actions requiring content creation or technical changes]
[需要创建内容或进行技术调整的行动]
Strategic (this quarter)
战略规划(本季度)
[Actions requiring entity building, community development, or platform presence]
undefined[需要构建实体、发展社区或布局平台的行动]
undefined