web-content
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseWeb Content Skill
Web内容技能
Load with: base.md + ui-web.md
For creating web content optimized for both traditional SEO and AI discovery (ChatGPT, Perplexity, Claude, Gemini).
Philosophy
核心理念
SEO gets clicks. GEO gets citations.
Traditional SEO optimizes for Google rankings. Generative Engine Optimization (GEO) optimizes for being cited by AI assistants. Modern content needs both:
- SEO: Rank on search results pages
- GEO: Be cited in AI-generated answers (ChatGPT, Perplexity, Claude, Gemini)
AI traffic grew 1,200% between July 2024 and February 2025. Google's search share dropped below 90% for the first time in a decade. Optimize for both.
SEO带来点击量,GEO带来引用量。
传统SEO针对谷歌排名进行优化。生成式引擎优化(GEO)针对被AI助手引用进行优化。现代内容需要兼顾两者:
- SEO:在搜索结果页面获得排名
- GEO:在AI生成的回答中被引用(ChatGPT、Perplexity、Claude、Gemini)
2024年7月至2025年2月期间,AI流量增长了1200%。谷歌的搜索份额十年来首次跌破90%。请同时针对两者进行优化。
Content Structure for AI + SEO
AI + SEO优化的内容结构
The Golden Rule
黄金法则
Write for humans, structure for machines.
AI systems prefer:
- Short, clear, fact-based content
- Clean formatting (headers, bullets, tables)
- Standalone sections that can be quoted
- Direct answers to questions
为人类写作,为机器结构化。
AI系统偏好:
- 简短、清晰、基于事实的内容
- 简洁的格式(标题、项目符号、表格)
- 可单独引用的独立板块
- 问题的直接答案
Page Types & Templates
页面类型与模板
Homepage
主页
markdown
undefinedmarkdown
undefinedHomepage Structure
主页结构
Above the Fold
首屏区域
- Headline: Clear value proposition (what you do + for whom)
- Subheadline: How you deliver that value
- Primary CTA: One clear action
- Trust signals: Logos, testimonials, stats
- 标题:清晰的价值主张(你提供什么服务+服务对象)
- 副标题:你如何传递该价值
- 主要行动召唤(CTA):一个明确的行动
- 信任信号:品牌标志、客户评价、数据统计
Content Sections
内容板块
- Problem Statement: Pain point you solve
- Solution Overview: How you solve it (3-4 key features)
- Social Proof: Testimonials, case studies, logos
- How It Works: 3-step process (simple)
- Pricing Preview: Or link to pricing page
- FAQ Section: 5-7 common questions (GEO gold)
- Final CTA: Repeat primary action
- 问题陈述:你解决的痛点
- 解决方案概述:你如何解决问题(3-4个核心功能)
- 社交证明:客户评价、案例研究、品牌标志
- 工作流程:简单的3步流程
- 定价预览:或链接到定价页面
- FAQ板块:5-7个常见问题(GEO的黄金内容)
- 最终行动召唤:重复主要行动
Schema Required
必需的Schema
- Organization schema (name, logo, founding date, social links)
- WebSite schema with SearchAction
- FAQ schema for questions section
undefined- Organization schema(名称、标志、成立日期、社交链接)
- 包含SearchAction的WebSite schema
- 问题板块的FAQ schema
undefinedProduct/Service Page
产品/服务页面
markdown
undefinedmarkdown
undefinedProduct Page Structure
产品页面结构
Hero Section
英雄区域
- Product Name: Clear, descriptive
- One-line Description: What it does in 10 words or less
- Key Benefit: Primary value proposition
- CTA: Buy/Try/Demo
- 产品名称:清晰、描述性强
- 一句话描述:10字以内说明功能
- 核心优势:主要价值主张
- 行动召唤(CTA):购买/试用/演示
Content Sections
内容板块
- TL;DR Box: 3-5 bullet summary (AI-quotable)
- Problem → Solution: What problem, how solved
- Features Grid: 4-6 features with icons
- Comparison Table: vs. alternatives (GEO loves these)
- Use Cases: Who uses it and how
- Testimonials: Real names, photos, companies
- Pricing: Clear tiers if applicable
- FAQ: Product-specific questions
- TL;DR框:3-5个项目符号摘要(适合AI引用)
- 问题→解决方案:解决什么问题,如何解决
- 功能网格:4-6个带图标功能
- 对比表格:与竞品对比(GEO非常喜欢这类内容)
- 使用场景:谁在使用以及如何使用
- 客户评价:真实姓名、照片、公司
- 定价:适用的话展示清晰的套餐
- FAQ:产品相关问题
Schema Required
必需的Schema
- Product schema (name, description, price, availability)
- Review schema (aggregate rating)
- FAQ schema
- BreadcrumbList schema
undefined- Product schema(名称、描述、价格、库存状态)
- Review schema(综合评分)
- FAQ schema
- BreadcrumbList schema
undefinedBlog Post / Article
博客文章 / 文章
markdown
undefinedmarkdown
undefinedBlog Post Structure
博客文章结构
Opening (First 100 words)
开篇(前100字)
- TL;DR: Direct answer to the title's question
- What you'll learn: Bullet list of takeaways
- This section should be quotable standalone
- TL;DR:直接回答标题中的问题
- 你将学到:要点项目符号列表
- 该板块应可单独引用
Body Structure
正文结构
- H2 sections: Main topics (5-7 per article)
- H3 subsections: Supporting points
- Bullet lists: For scanability
- Stat boxes: Highlight key numbers
- Comparison tables: When comparing options
- H2板块:主要主题(每篇文章5-7个)
- H3子板块:支撑论点
- 项目符号列表:提升可读性
- 数据框:突出关键数字
- 对比表格:比较选项时使用
Content Elements
内容元素
- Definition boxes ("What is X?")
- Step-by-step instructions
- Code examples (if technical)
- Original statistics/research
- Expert quotes with attribution
- 定义框(“什么是X?”)
- 分步说明
- 代码示例(如果是技术内容)
- 原创统计数据/研究
- 带署名的专家引用
Closing
结尾
- Summary: Key takeaways (bulleted)
- Next steps: What reader should do
- Related content: Internal links
- 摘要:要点(项目符号)
- 下一步行动:读者应采取的行动
- 相关内容:内部链接
Metadata Required
必需的元数据
- Author name + bio + photo
- Publication date
- Last updated date (visible!)
- Reading time
- Article schema with author
undefined- 作者姓名+简介+照片
- 发布日期
- 最后更新日期(需可见!)
- 阅读时长
- 带作者信息的Article schema
undefinedFAQ Page
FAQ页面
markdown
undefinedmarkdown
undefinedFAQ Page Structure
FAQ页面结构
Organization
组织方式
- Group questions by category
- Most common questions first
- Direct, concise answers
- Link to detailed pages for more info
- 按类别分组问题
- 最常见的问题放在前面
- 直接、简洁的答案
- 链接到详细页面获取更多信息
Question Format
问题格式
Q: [Exact question users ask]
A: [Direct answer in first sentence, then elaboration]
Q: [用户实际提出的问题]
A: [第一句直接回答,然后展开说明]
Schema Required
必需的Schema
- FAQPage schema (critical for AI discovery)
- Each Q&A as Question/Answer schema
undefined- FAQPage schema(对AI发现至关重要)
- 每个问答对应Question/Answer schema
undefinedLanding Page
着陆页
markdown
undefinedmarkdown
undefinedLanding Page Structure
着陆页结构
Single Focus
单一焦点
- One offer
- One audience
- One CTA (repeated)
- 一个优惠
- 一个目标受众
- 一个行动召唤(重复出现)
Sections
板块
- Headline: Benefit-focused, specific
- Problem Agitation: Pain points
- Solution: Your offer
- Proof: Testimonials, stats, logos
- Features: 3-5 key benefits
- Objection Handling: FAQ or guarantee
- CTA: Clear, urgent
- 标题:聚焦收益、具体明确
- 痛点强化:突出痛点
- 解决方案:你的优惠
- 证明:客户评价、数据统计、品牌标志
- 功能:3-5个核心优势
- 异议处理:FAQ或保证
- 行动召唤:清晰、带有紧迫感
No Navigation
无导航
- Remove header nav (reduce exits)
- Single path: read → convert
---- 移除头部导航(减少退出)
- 单一路径:阅读→转化
---AI-Optimized Content Formats
AI优化的内容格式
TL;DR Boxes
TL;DR框
html
<div class="tldr-box">
<h3>TL;DR</h3>
<ul>
<li>Key point 1 with specific detail</li>
<li>Key point 2 with number/stat</li>
<li>Key point 3 with actionable insight</li>
</ul>
</div>Place at top of articles. AI systems extract these for summaries.
html
<div class="tldr-box">
<h3>TL;DR</h3>
<ul>
<li>带具体细节的要点1</li>
<li>带数字/数据的要点2</li>
<li>带可操作见解的要点3</li>
</ul>
</div>放置在文章顶部。AI系统会提取这些内容用于生成摘要。
Definition Blocks
定义块
markdown
undefinedmarkdown
undefinedWhat is [Term]?
什么是[术语]?
[Term] is [concise definition in one sentence]. It [what it does] by [how it works].
Key characteristics:
- Characteristic 1
- Characteristic 2
- Characteristic 3
Start with "What is X?" - AI systems look for this pattern.[术语]是[一句话简洁定义]。它通过[工作原理]来[实现功能]。
核心特征:
- 特征1
- 特征2
- 特征3
以“什么是X?”开头——AI系统会寻找这种模式。Comparison Tables
对比表格
markdown
| Feature | Product A | Product B | Our Product |
|---------|-----------|-----------|-------------|
| Price | $99/mo | $149/mo | $79/mo |
| Feature 1 | ✓ | ✗ | ✓ |
| Feature 2 | ✗ | ✓ | ✓ |
| Best For | Enterprise | Startups | SMBs |AI loves structured comparisons. Include in product and review pages.
markdown
| 功能 | 产品A | 产品B | 我们的产品 |
|---------|-----------|-----------|-------------|
| 价格 | $99/月 | $149/月 | $79/月 |
| 功能1 | ✓ | ✗ | ✓ |
| 功能2 | ✗ | ✓ | ✓ |
| 适用场景 | 企业 | 初创公司 | 中小企业 |AI喜欢结构化的对比内容。在产品和评测页面中使用。
Stat Boxes
数据框
html
<div class="stat-box">
<span class="stat-number">73%</span>
<span class="stat-label">of users prefer AI search for complex queries</span>
<span class="stat-source">Source: Adobe Analytics, 2024</span>
</div>Original statistics with sources get cited by AI.
html
<div class="stat-box">
<span class="stat-number">73%</span>
<span class="stat-label">的用户在复杂查询时偏好AI搜索</span>
<span class="stat-source">来源:Adobe Analytics,2024</span>
</div>带来源的原创统计数据会被AI引用。
Step-by-Step Guides
分步指南
markdown
undefinedmarkdown
undefinedHow to [Do Thing]
如何[完成操作]
Step 1: [Action Verb] [Object]
步骤1:[动作动词] [对象]
[Explanation of what to do]
Example:
[Concrete example]
[操作说明]
示例:
[具体示例]
Step 2: [Action Verb] [Object]
步骤2:[动作动词] [对象]
[Explanation]
[操作说明]
Step 3: [Action Verb] [Object]
步骤3:[动作动词] [对象]
[Explanation]
Result: [What user achieves]
Use HowTo schema markup for these.
---[操作说明]
结果: [用户将获得什么]
为这类内容使用HowTo schema标记。
---Schema Markup (Critical for AI)
Schema标记(对AI至关重要)
Organization Schema
Organization Schema
json
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"foundingDate": "2020",
"description": "One sentence description",
"sameAs": [
"https://twitter.com/yourcompany",
"https://linkedin.com/company/yourcompany",
"https://github.com/yourcompany"
],
"contactPoint": {
"@type": "ContactPoint",
"email": "hello@yoursite.com",
"contactType": "customer service"
}
}json
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company",
"url": "https://yoursite.com",
"logo": "https://yoursite.com/logo.png",
"foundingDate": "2020",
"description": "One sentence description",
"sameAs": [
"https://twitter.com/yourcompany",
"https://linkedin.com/company/yourcompany",
"https://github.com/yourcompany"
],
"contactPoint": {
"@type": "ContactPoint",
"email": "hello@yoursite.com",
"contactType": "customer service"
}
}Article Schema
Article Schema
json
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title",
"description": "Meta description",
"image": "https://yoursite.com/article-image.jpg",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://yoursite.com/team/author-name",
"jobTitle": "Role at Company",
"sameAs": [
"https://linkedin.com/in/author",
"https://twitter.com/author"
]
},
"publisher": {
"@type": "Organization",
"name": "Your Company",
"logo": {
"@type": "ImageObject",
"url": "https://yoursite.com/logo.png"
}
},
"datePublished": "2025-01-15",
"dateModified": "2025-01-20"
}json
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title",
"description": "Meta description",
"image": "https://yoursite.com/article-image.jpg",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://yoursite.com/team/author-name",
"jobTitle": "Role at Company",
"sameAs": [
"https://linkedin.com/in/author",
"https://twitter.com/author"
]
},
"publisher": {
"@type": "Organization",
"name": "Your Company",
"logo": {
"@type": "ImageObject",
"url": "https://yoursite.com/logo.png"
}
},
"datePublished": "2025-01-15",
"dateModified": "2025-01-20"
}FAQ Schema
FAQ Schema
json
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is your product?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Direct answer here. Keep concise but complete."
}
},
{
"@type": "Question",
"name": "How much does it cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Pricing starts at $X/month for basic plan..."
}
}
]
}json
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is your product?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Direct answer here. Keep concise but complete."
}
},
{
"@type": "Question",
"name": "How much does it cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Pricing starts at $X/month for basic plan..."
}
}
]
}Product Schema
Product Schema
json
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Product Name",
"description": "Product description",
"image": "https://yoursite.com/product.jpg",
"brand": {
"@type": "Brand",
"name": "Your Company"
},
"offers": {
"@type": "Offer",
"price": "29.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "127"
}
}json
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Product Name",
"description": "Product description",
"image": "https://yoursite.com/product.jpg",
"brand": {
"@type": "Brand",
"name": "Your Company"
},
"offers": {
"@type": "Offer",
"price": "29.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "127"
}
}HowTo Schema
HowTo Schema
json
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Set Up Your Account",
"description": "Step-by-step guide to getting started",
"step": [
{
"@type": "HowToStep",
"name": "Create account",
"text": "Go to signup page and enter your email"
},
{
"@type": "HowToStep",
"name": "Verify email",
"text": "Click the link in the verification email"
}
]
}json
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Set Up Your Account",
"description": "Step-by-step guide to getting started",
"step": [
{
"@type": "HowToStep",
"name": "Create account",
"text": "Go to signup page and enter your email"
},
{
"@type": "HowToStep",
"name": "Verify email",
"text": "Click the link in the verification email"
}
]
}Platform-Specific Optimization
平台特定优化
ChatGPT Optimization
ChatGPT优化
markdown
✅ DO:
- TL;DR sections at top of articles
- Consistent formatting (headers, bullets)
- Named authors with credentials
- Original research and statistics
- Multi-intent content (covers related questions)
❌ AVOID:
- Thin content without substance
- Missing author attribution
- Outdated information (no dates)markdown
✅ 建议:
- 文章顶部设置TL;DR板块
- 格式统一(标题、项目符号)
- 带资质的署名作者
- 原创研究和统计数据
- 多意图内容(覆盖相关问题)
❌ 避免:
- 无实质内容的单薄内容
- 缺少作者署名
- 过时信息(无日期)Perplexity Optimization
Perplexity优化
markdown
✅ DO:
- Original statistics with sources
- Comparison tables and structured data
- Clean URL slugs (/topic-name not /p=123)
- Short, declarative statements
- Images, charts, diagrams
- YouTube videos (Perplexity shows these)
❌ AVOID:
- Generic content without unique insights
- Missing citations/sources
- Poor URL structuremarkdown
✅ 建议:
- 带来源的原创统计数据
- 对比表格和结构化数据
- 简洁的URL路径(/topic-name而非/p=123)
- 简短、陈述性的语句
- 图片、图表、示意图
- YouTube视频(Perplexity会展示这些)
❌ 避免:
- 无独特见解的通用内容
- 缺少引用/来源
- 糟糕的URL结构Claude Optimization
Claude优化
markdown
✅ DO:
- Well-structured, logical content
- Clear definitions and explanations
- Technical accuracy
- Balanced perspectives
- Proper citations
❌ AVOID:
- Misleading or sensational content
- Missing context
- Outdated technical informationmarkdown
✅ 建议:
- 结构清晰、逻辑严谨的内容
- 清晰的定义和解释
- 技术准确性
- 平衡的观点
- 恰当的引用
❌ 避免:
- 误导性或耸人听闻的内容
- 缺少上下文
- 过时的技术信息Gemini Optimization
Gemini优化
markdown
✅ DO:
- Rich schema markup
- Detailed image alt-text
- YouTube content (Google-owned)
- Multimedia (video, audio with transcripts)
❌ AVOID:
- Missing structured data
- Images without alt-text
- Text-only contentmarkdown
✅ 建议:
- 丰富的Schema标记
- 详细的图片替代文本
- YouTube内容(谷歌旗下)
- 多媒体(带文字转录的视频、音频)
❌ 避免:
- 缺少结构化数据
- 无替代文本的图片
- 纯文本内容E-E-A-T for AI Discovery
AI发现的E-E-A-T原则
Experience
经验(Experience)
- First-person case studies
- "We tested X and found Y"
- Original screenshots and data
- User testimonials with real details
- 第一人称案例研究
- “我们测试了X,发现Y”
- 原创截图和数据
- 带真实细节的用户评价
Expertise
专业知识(Expertise)
- Author bios with credentials
- Link to author's other work
- Industry-specific terminology
- Technical depth appropriate to topic
- 带资质的作者简介
- 链接到作者的其他作品
- 行业特定术语
- 符合主题的技术深度
Authoritativeness
权威性(Authoritativeness)
- Backlinks from trusted sources
- Mentions in industry publications
- Citations from other experts
- Social proof (followers, engagement)
- 来自可信来源的反向链接
- 行业出版物中的提及
- 其他专家的引用
- 社交证明(粉丝数、互动量)
Trustworthiness
可信度(Trustworthiness)
- Contact information visible
- About page with team details
- Privacy policy and terms
- Secure site (HTTPS)
- Accurate, up-to-date info
- 可见的联系信息
- 带团队详情的关于我们页面
- 隐私政策和条款
- 安全站点(HTTPS)
- 准确、最新的信息
Content Freshness
内容新鲜度
Visible Dates (Required)
可见日期(必需)
html
<article>
<header>
<h1>Article Title</h1>
<div class="meta">
<span class="author">By John Smith</span>
<span class="published">Published: January 15, 2025</span>
<span class="updated">Last updated: January 20, 2025</span>
</div>
</header>
</article>AI systems prefer recent content. Show dates prominently.
html
<article>
<header>
<h1>Article Title</h1>
<div class="meta">
<span class="author">By John Smith</span>
<span class="published">发布日期:2025年1月15日</span>
<span class="updated">最后更新:2025年1月20日</span>
</div>
</header>
</article>AI系统偏好近期内容。请突出显示日期。
Update Schedule
更新计划
| Content Type | Update Frequency |
|---|---|
| Product pages | On feature changes |
| Pricing | Immediately on change |
| Blog posts | Quarterly review |
| Statistics | When new data available |
| Guides | Semi-annually |
| 内容类型 | 更新频率 |
|---|---|
| 产品页面 | 功能变更时更新 |
| 定价 | 变更后立即更新 |
| 博客文章 | 每季度审核更新 |
| 统计数据 | 有新数据时更新 |
| 指南 | 每半年更新 |
Analytics for AI Traffic
AI流量分析
GA4 Regex Filter
GA4正则过滤器
regex
.*chatgpt\.com.*|.*perplexity\.ai.*|.*gemini\.google\.com.*|.*copilot\.microsoft\.com.*|.*openai\.com.*|.*claude\.ai.*|.*poe\.com.*|.*you\.com.*|.*phind\.com.*regex
.*chatgpt\.com.*|.*perplexity\.ai.*|.*gemini\.google\.com.*|.*copilot\.microsoft\.com.*|.*openai\.com.*|.*claude\.ai.*|.*poe\.com.*|.*you\.com.*|.*phind\.com.*Track AI Referrals
追踪AI推荐来源
javascript
// Check for AI referrer
const aiReferrers = [
'chatgpt.com',
'chat.openai.com',
'perplexity.ai',
'claude.ai',
'gemini.google.com',
'copilot.microsoft.com',
'poe.com',
'you.com',
'phind.com'
];
const referrer = document.referrer;
const isAIReferral = aiReferrers.some(ai => referrer.includes(ai));
if (isAIReferral) {
analytics.track('ai_referral', {
source: referrer,
page: window.location.pathname
});
}javascript
// 检查是否为AI推荐来源
const aiReferrers = [
'chatgpt.com',
'chat.openai.com',
'perplexity.ai',
'claude.ai',
'gemini.google.com',
'copilot.microsoft.com',
'poe.com',
'you.com',
'phind.com'
];
const referrer = document.referrer;
const isAIReferral = aiReferrers.some(ai => referrer.includes(ai));
if (isAIReferral) {
analytics.track('ai_referral', {
source: referrer,
page: window.location.pathname
});
}Survey for AI Discovery
AI发现调查
Add to forms:
markdown
How did you hear about us?
- [ ] Google Search
- [ ] ChatGPT
- [ ] Perplexity
- [ ] Claude
- [ ] Social Media
- [ ] Referral
- [ ] Other添加到表单中:
markdown
你是如何了解到我们的?
- [ ] 谷歌搜索
- [ ] ChatGPT
- [ ] Perplexity
- [ ] Claude
- [ ] 社交媒体
- [ ] 推荐
- [ ] 其他Content Checklist
内容检查清单
Before Publishing
发布前
markdown
undefinedmarkdown
undefinedSEO Checklist
SEO检查清单
- Title tag (50-60 chars) with primary keyword
- Meta description (150-160 chars) with CTA
- URL slug is clean and descriptive
- H1 matches title intent
- H2/H3 hierarchy is logical
- Images have descriptive alt-text
- Internal links to related content
- External links to authoritative sources
- 标题标签(50-60字符)包含主关键词
- 元描述(150-160字符)包含行动召唤
- URL路径简洁且描述性强
- H1与标题意图匹配
- H2/H3层级逻辑清晰
- 图片带描述性替代文本
- 指向相关内容的内部链接
- 指向权威来源的外部链接
GEO Checklist
GEO检查清单
- TL;DR or summary at top
- Direct answer to main question in first paragraph
- Stat boxes with sources
- Comparison tables where applicable
- FAQ section with schema
- Author name, bio, and credentials
- Publication and last-updated dates visible
- Schema markup validated
- Content can be quoted standalone
- Original insights or data included
undefined- 顶部有TL;DR或摘要
- 第一段直接回答主要问题
- 带来源的数据框
- 适用的地方使用对比表格
- 带Schema的FAQ板块
- 作者姓名、简介和资质
- 可见的发布和最后更新日期
- Schema标记已验证
- 内容可单独引用
- 包含原创见解或数据
undefinedSchema Validation
Schema验证
bash
undefinedbash
undefinedValidate schema markup
验证Schema标记
---
---Project Structure
项目结构
project/
├── content/
│ ├── pages/
│ │ ├── home.md
│ │ ├── about.md
│ │ ├── pricing.md
│ │ └── contact.md
│ ├── blog/
│ │ ├── post-1.md
│ │ └── post-2.md
│ └── legal/
│ ├── privacy.md
│ └── terms.md
├── components/
│ ├── SchemaMarkup.tsx
│ ├── TLDRBox.tsx
│ ├── StatBox.tsx
│ ├── FAQSection.tsx
│ └── AuthorBio.tsx
└── lib/
└── schema.ts # Schema generatorsproject/
├── content/
│ ├── pages/
│ │ ├── home.md
│ │ ├── about.md
│ │ ├── pricing.md
│ │ └── contact.md
│ ├── blog/
│ │ ├── post-1.md
│ │ └── post-2.md
│ └── legal/
│ ├── privacy.md
│ └── terms.md
├── components/
│ ├── SchemaMarkup.tsx
│ ├── TLDRBox.tsx
│ ├── StatBox.tsx
│ ├── FAQSection.tsx
│ └── AuthorBio.tsx
└── lib/
└── schema.ts # Schema生成器Anti-Patterns
反模式
- No dates - AI deprioritizes undated content
- Anonymous content - No author = no E-E-A-T
- Walls of text - Break up with headers, bullets, boxes
- Generic content - Add original insights, data, opinions
- Missing schema - Invisible to structured data crawlers
- Outdated info - Update quarterly minimum
- No FAQ - Missing easy GEO win
- Poor URL structure - Use /topic-name not /p=12345
- 无日期 - AI会优先排除无日期内容
- 匿名内容 - 无作者=无E-E-A-T
- 文字墙 - 用标题、项目符号、框体拆分内容
- 通用内容 - 添加原创见解、数据、观点
- 缺少Schema - 对结构化数据爬虫不可见
- 过时信息 - 至少每季度更新一次
- 无FAQ - 错失简单的GEO机会
- 糟糕的URL结构 - 使用/topic-name而非/p=12345
Quick Reference
快速参考
Content Formats AI Loves
AI偏好的内容格式
- TL;DR summaries
- Definition boxes ("What is X?")
- Comparison tables
- Step-by-step guides
- FAQ sections
- Stat boxes with sources
- Listicles with numbers
- TL;DR摘要
- 定义框(“什么是X?”)
- 对比表格
- 分步指南
- FAQ板块
- 带来源的数据框
- 带数字的列表文章
Required Schema by Page Type
各页面类型必需的Schema
| Page Type | Schema |
|---|---|
| Homepage | Organization, WebSite |
| Blog Post | Article, Author, FAQ |
| Product | Product, Review, FAQ |
| FAQ | FAQPage |
| How-to | HowTo |
| About | Organization, Person |
| 页面类型 | Schema |
|---|---|
| 主页 | Organization, WebSite |
| 博客文章 | Article, Author, FAQ |
| 产品 | Product, Review, FAQ |
| FAQ | FAQPage |
| 指南 | HowTo |
| 关于我们 | Organization, Person |