Back to Details

article-page-generator

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Pages: Article (Single Post)

页面：文章（单篇帖子）

Guides structure, SEO, and UX for individual article pages — one blog post, one guide, one piece of long-form content. Distinct from blog-page-generator, which covers the blog index/listing page.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Output workflow: Always output in order: 0. Research Phase (keywords, search intent, competitors) → 1. Intent Analysis → 2. Content Analysis → 3. Recommendations. Do not skip steps. When Research Phase was performed via web search, show the search results and findings.
为独立文章页面提供结构、SEO和UX指南——单篇博客帖子、单篇指南、单份长内容。与覆盖博客索引/列表页的blog-page-generator不同。
调用规则：首次使用时如果合适，可以先用1-2句话介绍这个技能覆盖的范围和价值，再提供核心输出。如果是后续调用或者用户要求跳过介绍，直接输出核心内容即可。
输出工作流：始终按以下顺序输出：0. 调研阶段（关键词、搜索意图、竞品）→ 1. 意图分析 → 2. 内容分析 → 3. 优化建议，不得跳过步骤。如果调研阶段通过网页搜索完成，需要展示搜索结果和发现。

Optimization Foundation: Four Inputs

优化基础：四项输入

Article analysis and creation rest on four inputs. Gather or infer them before outputting recommendations:
InputPurposeSource
ProductProduct connection, features, use cases, CTA placementproduct-marketing-context (Sections 1–4, 9–11); article content; web search
KeywordsTarget keyword, primary/secondary placementproduct-marketing-context Section 6; keyword-research; article
Article intentInformational, commercial, transactional, navigational; drives structure, CTA, SEO depthproduct-marketing-context Section 6 (target intent); article orientation; content type
Competitor articlesStructure to adopt, content gaps, length target, keyword opportunitiesUser-provided URLs; product-marketing-context Section 11; web search
When any input is missing: Proactively ask or search. For article analysis: perform Research Phase (keyword search, search intent, competitor articles) by default — see Research Phase section. For product/keywords/intent, infer from article or prompt user to add product-marketing-context.
文章分析和创作基于四项输入，在输出优化建议前需要收集或推导这些信息：
输入项用途来源
产品产品关联、功能、使用场景、CTA位置product-marketing-context（第1-4节、9-11节）；文章内容；网页搜索
关键词目标关键词、主/次关键词布局product-marketing-context第6节；keyword-research；文章内容
文章意图信息类、商业类、交易类、导航类；决定结构、CTA、SEO深度product-marketing-context第6节（目标意图）；文章定位；内容类型
竞品文章可参考的结构、内容缺口、目标篇幅、关键词机会用户提供的URL；product-marketing-context第11节；网页搜索
缺少任意输入时：主动询问用户或者通过搜索补充。如果是文章分析场景，默认执行调研阶段（关键词搜索、搜索意图、竞品文章分析），详见调研阶段章节。如果缺少产品/关键词/意图信息，可以从文章内容推导，或者提示用户补充product-marketing-context。

Before Analysis: Gather Context

分析前：收集上下文

1. Product / company context
Use available context to give tailored analysis:
SourceUse for
product-marketing-context.mdKeywords (Section 6), competitors (Section 7), content strategy (Section 11), product connection
Article contentExtract product name, features, URLs; infer target keyword and audience
Web searchWhen analyzing a known brand: search for "[product] features", "[product] vs competitors", company positioning — use to validate product connection, suggest missing features/use cases, and improve competitor gap analysis
If no product-marketing-context exists, infer from the article and optionally search for company/product info to enrich recommendations.
1. 产品/公司上下文
利用现有上下文提供定制化分析：
来源用途
product-marketing-context.md关键词（第6节）、竞品（第7节）、内容策略（第11节）、产品关联
文章内容提取产品名称、功能、URL；推导目标关键词和受众
网页搜索分析已知品牌时，搜索「[产品名] features」、「[产品名] vs competitors」、公司定位，用于验证产品关联、建议缺失的功能/使用场景、优化竞品缺口分析
如果没有product-marketing-context，可以从文章内容推导，也可以选择搜索公司/产品信息来丰富建议。

Research Phase: Keyword, Search Intent, Competitor (Required for Article Analysis)

调研阶段：关键词、搜索意图、竞品（文章分析必填）

Lightweight research for article analysis—keyword extraction, intent check, competitor structure. For deep keyword research, topical mapping, or content planning, use keyword-research and content-strategy.
When analyzing or auditing an article, perform the following searches and output the results in the analysis. Skip only if user explicitly asks to skip (e.g. "skip search").
为文章分析提供轻量调研——关键词提取、意图校验、竞品结构分析。如果需要深度关键词调研、主题映射或内容规划，请使用keyword-research和content-strategy。
当分析或审核文章时，执行以下搜索并在分析中输出结果，仅当用户明确要求跳过时可省略（例如「skip search」）。

1. Keyword Search

1. 关键词搜索

  • Extract seed keywords from article (title, H1, H2s, meta keywords, first 100 words).
  • Search the web for related keywords and opportunity: 
    • "[primary keyword]"
      or 
      "[primary keyword] related keywords"
    • "[primary keyword]" site:competitor.com
      (if competitors known)
    • Google autocomplete / "People also ask" style queries for the topic
  • Output: Primary keyword, secondary keywords, keyword opportunities (terms top rankers use that this article misses).
  • 从文章中提取种子关键词（标题、H1、H2、meta关键词、前100字）。
  • 网页搜索相关关键词和机会： 
    • "[主关键词]"
      或 
      "[主关键词] related keywords"
    • "[主关键词]" site:competitor.com
      （如果已知竞品）
    • 对应主题的Google自动补全/「用户还问了」类查询
  • 输出：主关键词、次关键词、关键词机会（高排名内容使用但本文缺失的术语）。

2. Search Intent Analysis

2. 搜索意图分析

  • Determine intent for primary and secondary keywords:
    • Informational: How-to, what is, why, guides → blog, FAQ
    • Commercial: Comparison, best, review → comparison pages, product pages
    • Transactional: Buy, pricing, sign up → product, pricing, CTA
    • Navigational: Brand name, login → brand pages
  • Search the web if needed: 
    "[keyword]"
    to see SERP result types (blogs, product pages, etc.) and infer intent. See serp-features for SERP feature types.
  • Output: Intent for primary keyword, intent for top 2–3 secondary keywords, whether article matches intent.
  • 确定主关键词和次关键词的意图：
    • 信息类：操作指南、是什么、为什么、教程 → 博客、FAQ
    • 商业类：对比、最佳推荐、评测 → 对比页、产品页
    • 交易类：购买、定价、注册 → 产品页、定价页、CTA
    • 导航类：品牌名、登录 → 品牌页面
  • 必要时网页搜索：搜索
    "[关键词]"
    查看SERP结果类型（博客、产品页等）推导意图，可参考serp-features了解SERP功能类型。
  • 输出：主关键词意图、Top2-3次关键词意图、文章是否匹配意图。

3. Competitor Article Search

3. 竞品文章搜索

  • If user provides URLs: Use them for competitor analysis.
  • If user does not provide URLs: By default, search for top-ranking articles:
    • Web search: 
      "[target keyword]"
      or 
      "[primary keyword]"
    • Fetch 2–3 top-ranking pages via mcp_web_fetch or WebSearch
    • Analyze: word count, H2 structure, keyword placement, content gaps, CTA, schema
  • If user explicitly asks to skip: Omit competitor search; note "Competitor analysis skipped" in output.
  • Output: Competitor URLs, brief structure comparison, content gaps, length target, keyword opportunities.
  • 如果用户提供URL：直接用这些URL做竞品分析。
  • 如果用户未提供URL：默认搜索高排名文章：
    • 网页搜索：
      "[目标关键词]"
      或 
      "[主关键词]"
    • 通过mcp_web_fetch或WebSearch获取2-3个排名最高的页面
    • 分析：字数、H2结构、关键词布局、内容缺口、CTA、schema
  • 如果用户明确要求跳过：省略竞品搜索，在输出中标注「Competitor analysis skipped」。
  • 输出：竞品URL、简要结构对比、内容缺口、目标篇幅、关键词机会。

Scope

适用范围

  • Single article page: One post, one URL (e.g. 
    /blog/how-to-optimize-seo
    )
  • Not the blog index, category pages, or archive pages — see blog-page-generator for those
  • 单篇文章页面：单篇帖子、单个URL（例如 
    /blog/how-to-optimize-seo
    ）
  • 不适用博客索引页、分类页、归档页——这类页面请参考blog-page-generator

Initial Assessment

初始评估

Check for product marketing context first: If 
.claude/product-marketing-context.md
or 
.cursor/product-marketing-context.md
exists, read it for topics, audience, keywords, and Section 11 (Content/Blog/Article Strategy).
Identify:
  1. Product connection: How does this article support the product? (educate on problem, introduce features, nurture leads)
  2. Keyword basis: Target keyword from product context or keyword research — see keyword-research
  3. Content type: Blog post, guide, tutorial, news, evergreen
  4. Length: Short (<1,000 words), medium (1,000–2,500), long (2,500+)
  5. Intent: Informational, commercial, problem-aware
Product-linked content: Articles should tie to the product (problem it solves, features, use cases). Avoid purely generic content with no product relevance. Link to product/feature pages naturally in conclusion or when context fits.
优先检查产品营销上下文：如果存在
.claude/product-marketing-context.md
或
.cursor/product-marketing-context.md
，读取其中的主题、受众、关键词和第11节（内容/博客/文章策略）。
识别以下信息：
  1. 产品关联：这篇文章如何为产品提供支持？（问题科普、功能介绍、线索培育）
  2. 关键词基础：来自产品上下文或关键词调研的目标关键词，参考keyword-research
  3. 内容类型：博客帖子、指南、教程、新闻、长效内容
  4. 篇幅：短篇（<1000字）、中篇（1000-2500字）、长篇（2500字以上）
  5. 意图：信息类、商业类、问题感知类
产品关联内容：文章应该和产品挂钩（产品解决的问题、功能、使用场景），避免完全和产品无关的通用内容。在结论或上下文合适的位置自然链接到产品/功能页面。

Article Orientations

文章定位

Not all articles share the same goal. Choose structure, SEO depth, and schema based on orientation and primary objective.
不是所有文章的目标都一致，根据定位和核心目标选择结构、SEO深度和schema。

Article Types by Orientation

按定位划分的文章类型

OrientationExamplesPrimary GoalSEO Priority
Funding / PRFunding rounds, acquisitions, executive hiresBrand awareness, press, investor relationsLow — thin content, few search queries
Product updatesFeature launches, release notes, changelogsUser education, product adoptionLow–medium — internal announcements rarely rank
Guides / How-toTutorials, step-by-step, best practicesEducation, lead nurture, authorityHigh — matches search intent
News / TrendingIndustry news, hot topics, seasonalEngagement, social shares, topical relevanceMedium — quick traffic spikes, short shelf life
EvergreenPillar guides, glossaries, comparisonsLong-term traffic, backlinks, authorityHigh — compounds over time
定位示例核心目标SEO优先级
融资/公关融资轮次、收购、高管任命品牌曝光、媒体传播、投资者关系低——内容较浅、搜索量少
产品更新功能发布、发版说明、更新日志用户教育、产品 adoption低-中——内部公告很少获得排名
指南/操作教程教程、分步指南、最佳实践教育、线索培育、权威性高——匹配搜索意图
新闻/热点内容行业新闻、热门话题、季节性内容互动、社交分享、话题相关性中——流量增长快但生命周期短
长效内容支柱指南、术语表、对比内容长期流量、外链、权威性高——价值随时间累积

SEO-Driven vs Non-SEO-Driven

SEO驱动 vs 非SEO驱动

  • SEO-driven: How-to guides, listicles, comparisons, pillar content. Target keywords, optimize structure, invest in GEO. Goal: organic traffic.
  • Non-SEO-driven: Funding announcements, product updates, company news. Goal: brand, PR, existing audience. Don't expect rankings; focus on clarity, shareability, and internal linking to SEO content.
  • Hybrid: Product launch posts can include SEO-friendly sections (e.g., "How to use [feature]" with keyword targeting) while the main goal remains announcement.
  • SEO驱动：操作指南、清单文、对比内容、支柱内容。目标关键词、优化结构、投入GEO优化，目标是获取自然流量。
  • 非SEO驱动：融资公告、产品更新、公司新闻。目标是品牌、公关、服务现有受众。不要期望获得排名，重点关注清晰度、可分享性，以及到SEO内容的内部链接。
  • 混合类：产品发布帖可以包含SEO友好的板块（例如带关键词的「如何使用[功能]」章节），同时核心目标仍然是公告。

Evergreen vs Timely Content

长效内容 vs 时效性内容

AttributeEvergreenTimely
RelevanceYear-round; foundational topicsWeeks to months; trends, news, seasonal
TrafficSteady, compounds over timeSpikes then decline
Examples"How to write a business plan," "Best SEO strategies"Holiday guides, trending microtrends, breaking news
MaintenanceRefresh every 6–12 months; update statsOften one-and-done; may archive or redirect
Schema
Article
or 
BlogPosting
NewsArticle
for time-sensitive news
Recommended mix: 70/30 or 60/40 evergreen-to-timely. Too much evergreen = blog feels outdated; too much timely = irregular traffic, constant churn. Use timely content to link into evergreen pillar articles.
Date display: For timely content, 
datePublished
matters more; for evergreen, prefer 
dateModified
when visible (see Date Display below).
属性长效内容时效性内容
相关性全年适用；基础主题数周到数月；趋势、新闻、季节性内容
流量稳定、随时间累积短期 spike 后下降
示例《如何撰写商业计划书》、《最佳SEO策略》节日指南、热门微趋势、突发新闻
维护每6-12个月更新一次；更新数据通常发布后无需维护；可归档或重定向
Schema
Article
或 
BlogPosting
时效性新闻使用 
NewsArticle
推荐内容比例：70/30或60/40的长效内容:时效性内容。长效内容过多会让博客显得过时；时效性内容过多会导致流量不稳定、内容更新压力大。可以通过时效性内容链接到长效支柱文章。
日期展示：时效性内容更看重
datePublished
；长效内容如果展示日期优先展示
dateModified
（详见下文日期展示章节）。

Competitor Article Analysis

竞品文章分析

Performed as part of Research Phase (see above). When competitor articles are obtained:
  1. Obtain articles: URLs from user or product context (Section 11), or search web for 
    "[keyword]"
    to find top-ranking pages (default for analysis)
  2. Fetch content: mcp_web_fetch, WebSearch, or user-provided text
  3. Analyze: Content Analysis dimensions + word count, H2 structure, keyword placement, content gaps, CTA, schema
  4. Output: In Research Phase (Section 0) + add to Recommendations — structure to adopt, sections to add, length target, keyword opportunities, content gaps to fill
作为调研阶段的一部分执行（见上文）。获取竞品文章后：
  1. 获取文章：来自用户提供的URL、产品上下文（第11节），或网页搜索
    "[关键词]"
    找到高排名页面（分析场景默认操作）
  2. 获取内容：通过mcp_web_fetch、WebSearch或用户提供的文本
  3. 分析维度：内容分析维度 + 字数、H2结构、关键词布局、内容缺口、CTA、schema
  4. 输出：放在调研阶段（第0节）+ 补充到优化建议中——可采纳的结构、需要新增的章节、目标篇幅、关键词机会、需要填补的内容缺口

Article Page Structure

文章页面结构

SectionPurpose
Hero/HeaderTitle (H1), author, single date (see Date Display below), reading time (word count ÷ 200; round up), featured image, share buttons
TL;DR or Key TakeawaysChoose one: TL;DR = 50–100 word bold summary paragraph; Key Takeaways = 5–7 bullet points; placed after intro; supports GEO/AI citation
Introduction40–120 words; hook in first 1–2 sentences (pain point, stat, or question); primary keyword in first 100 words; readers decide in ~8 seconds
BodyH2–H3 hierarchy; QAE pattern (see GEO below); scannable (lists, short paragraphs 40–80 words, visuals)
ConclusionSummary, CTA (newsletter, related content, product — link to product/feature when relevant)
Related posts3–6 contextual links; end-of-article recommendations
Author bioE-E-A-T; credentials, photo, link to author page — see eeat-signals
板块用途
Hero/头部标题（H1）、作者、单个日期（详见下文日期展示）、阅读时长（字数÷200，向上取整）、特色图、分享按钮
TL;DR或核心要点二选一：TL;DR = 50-100字加粗摘要段落；核心要点 = 5-7个要点列表；放在引言之后；支持GEO/AI引用
引言40-120字；前1-2句设置钩子（痛点、数据、问题）；前100字包含主关键词；读者通常在8秒内决定是否继续阅读
正文H2-H3层级结构；QAE模式（见下文GEO）；易扫描（列表、40-80字短段落、可视化内容）
结论总结、CTA（订阅 newsletter、相关内容、产品——相关时链接到产品/功能页）
相关文章推荐3-6个上下文相关链接；文章末尾推荐
作者简介E-E-A-T；资质、照片、作者页链接——参考eeat-signals

Featured Image

特色图

The hero image displayed at the top of the article. Same image typically used for Schema, Open Graph, and Twitter Cards.
AttributeGuideline
Dimensions1200–1600px wide; proportional height; 1200×630px for social (og:image)
File sizeUnder 200 KB; compress (WebP preferred)
FormatWebP, JPEG, PNG; avoid oversized originals
Alt textDescriptive; include keyword when natural; accessibility + Google Images
File nameDescriptive (e.g. 
seo-checklist-2025.webp
); keyword when natural
RelevanceMust align with article topic; articles with relevant images get ~94% more views
LCPSet 
width
and 
height
attributes to prevent CLS; use 
srcset
/
sizes
for responsive
Schema and Open Graph require the same image (min 1200px wide, absolute URL). See open-graph, twitter-cards.
文章顶部展示的Hero图，通常Schema、Open Graph和Twitter Cards使用同一张图。
属性规范
尺寸宽度1200-1600px；高度按比例；社交图（og:image）尺寸为1200×630px
文件大小200 KB以内；压缩（优先使用WebP）
格式WebP、JPEG、PNG；避免过大的原文件
Alt文本描述性内容；自然包含关键词；兼顾可访问性和Google图片搜索
文件名描述性命名（例如
seo-checklist-2025.webp
）；自然包含关键词
相关性必须和文章主题匹配；带相关图片的文章浏览量高约94%
LCP优化设置
width
和
height
属性避免CLS；使用
srcset
/
sizes
适配响应式
Schema和Open Graph需要使用同一张图（最小宽度1200px，绝对URL），参考open-graph、twitter-cards。

Social Sharing

社交分享

  • Add share buttons (X, LinkedIn, Facebook, etc.) — see social-share-generator
  • Place after intro and/or end of article; sticky sidebar for long-form
  • Requires Open Graph and Twitter Cards for rich previews when shared
  • 添加分享按钮（X、LinkedIn、Facebook等）——参考social-share-generator
  • 放在引言之后和/或文章末尾；长文可设置悬浮侧边栏
  • 需要配置Open Graph和Twitter Cards才能在分享时展示富预览

GEO / AI Optimization (Generative Engine Optimization)

GEO/AI优化（生成式引擎优化）

Optimize for AI citation (ChatGPT, Perplexity, Google AI Overviews). Content structured for GEO is cited ~35% more frequently.
ElementGuideline
TL;DR or Key TakeawaysChoose one: TL;DR = 50–100 word summary paragraph; Key Takeaways = 5–7 bullet points; placed after intro; supports GEO
QAE patternQuestion (H2) → Answer (2 sentences) → Evidence (data, examples, lists)
Answer-firstDirect answer in first 40–60 words after each H2
Answer blocks100–200 words per section; direct answer + context + evidence + nuance
Structured formatsLists, tables, numbered steps increase citation rate
See generative-engine-optimization for full GEO strategy.
优化以便被AI引用（ChatGPT、Perplexity、Google AI Overviews），按GEO规范结构化的内容被引用的频率高约35%。
元素规范
TL;DR或核心要点二选一：TL;DR = 50-100字摘要段落；核心要点 = 5-7个要点列表；放在引言之后；支持GEO
QAE模式问题（H2）→ 答案（2句话）→ 证据（数据、示例、列表）
答案前置每个H2之后的前40-60字直接给出答案
答案块每个章节100-200字；直接答案+上下文+证据+细节补充
结构化格式列表、表格、编号步骤可以提升引用率
完整GEO策略参考generative-engine-optimization。

Paragraph Length & Content

段落长度和内容

ElementGuideline
Paragraph length2–4 sentences; 40–80 words per paragraph; avoid walls of text
Break long blocksUse lists, subheadings (H3), images, callout boxes every 2–3 paragraphs
Answer blocks100–200 words per H2 section; direct answer + context + evidence
ScannabilityShort sentences; one idea per paragraph; front-load key info (F-pattern: readers scan top, then left); bold key phrases for Featured Snippets; see featured-snippet
元素规范
段落长度2-4句话；每段40-80字；避免大段文字
拆分长内容块每2-3段插入列表、子标题（H3）、图片、提示框进行拆分
答案块每个H2章节100-200字；直接答案+上下文+证据
易扫描性短句；每段一个核心观点；关键信息前置（F型阅读模式：读者先扫描顶部，再扫描左侧）；加粗关键短语以便获得精选摘要；参考featured-snippet

Long-Form (1,000+ words)

长文（1000字以上）

  • Add table of contents (TOC) after intro — see toc-generator
  • Use jump links for major sections
  • Break text with images, lists, definition boxes, mini-FAQs
  • 引言之后添加目录（TOC）——参考toc-generator
  • 主要章节添加锚点跳转链接
  • 用图片、列表、定义框、迷你FAQ拆分文字

SEO Best Practices

SEO最佳实践

Title & Meta

标题和Meta

ElementGuideline
Title55 chars; primary keyword near start; power words
Meta description150–160 chars; CTA; primary keyword
H1One per page; matches title; primary keyword naturally
元素规范
Title55字符以内；主关键词靠近开头；使用有吸引力的词
Meta描述150-160字符；包含CTA；包含主关键词
H1每页仅1个；和标题匹配；自然包含主关键词

Keyword Placement

关键词布局

  • Title: 1× primary keyword
  • First 100 words: 1× primary keyword
  • Body: 2–3× naturally; avoid stuffing
  • At least one H2: Include primary or related keyword
  • 标题：包含1次主关键词
  • 前100字：包含1次主关键词
  • 正文：自然出现2-3次；避免堆砌
  • 至少1个H2：包含主关键词或相关关键词

Content Quality

内容质量

  • Readability: Grade 8–10 (Flesch-Kincaid); short sentences, clear language
  • Depth: 2,500+ words for pillar content; 1,000+ for cluster articles
  • Originality: Unique angle, data, examples; avoid thin or rehashed content
  • E-E-A-T: Author bio, citations, changelog, expert quotes — see eeat-signals for full guidance
  • 可读性：Flesch-Kincaid得分8-10年级水平；短句、语言清晰
  • 深度：支柱内容2500字以上；集群文章1000字以上
  • 原创性：独特角度、数据、示例；避免低质或洗稿内容
  • E-E-A-T：作者简介、引用、更新日志、专家引用——完整指南参考eeat-signals

Common Mistakes to Avoid

需要避免的常见错误

  • Multiple H1s; skipping heading levels (H2→H4); keyword stuffing in headings
  • Neglecting conclusion or CTA; no internal links to related content
  • Walls of text; generic "click here" anchors
  • 多个H1；跳过头层级（例如H2直接到H4）；标题中堆砌关键词
  • 忽略结论或CTA；没有指向相关内容的内部链接
  • 大段文字；使用通用的「点击这里」作为锚文本

URL

URL

Use url-slug-generator for slug creation. Key rules:
  • Slug: 3–5 words; under 60 chars; primary keyword; lowercase, hyphens
  • Example: 
    /blog/ai-people-search
    not 
    /blog/ai-search-engine-finding-people-speed-discovery-outreach
  • Avoid: Date in path (
    /blog/2025/01/15/article-title
    ); copy-pasting full title
使用url-slug-generator创建slug，核心规则：
  • Slug：3-5个词；60字符以内；包含主关键词；小写、用连字符分隔
  • 示例：
    /blog/ai-people-search
    而非 
    /blog/ai-search-engine-finding-people-speed-discovery-outreach
  • 避免：路径中包含日期（
    /blog/2025/01/15/article-title
    ）；直接复制完整标题作为slug

Date Display (Critical for CTR)

日期展示（对CTR至关重要）

Google recommends: Minimize the presence of other dates on the page. If both 
datePublished
and 
dateModified
are shown, Google may pick the wrong date for SERP display.
  • Search Engine Land case: A site showing both dates saw 22% CTR drop — Google chose the outdated date.
  • Best practice: Show only one date on the page — prefer 
    dateModified
    if it exists, otherwise 
    datePublished
    .
  • Schema: Keep both 
    datePublished
    and 
    dateModified
    in JSON-LD; the rule applies to visible date only.
Google建议：尽量减少页面上其他日期的展示。如果同时展示
datePublished
和
dateModified
，Google可能在SERP中展示错误的日期。
  • Search Engine Land案例：同时展示两个日期的站点CTR下降了22%——Google选择了过时的日期展示。
  • 最佳实践：页面上仅展示一个日期——如果有更新日期优先展示
    dateModified
    ，否则展示
    datePublished
    。
  • Schema：JSON-LD中可以同时保留
    datePublished
    和
    dateModified
    ；该规则仅适用于可见的日期。

Schema (Article / BlogPosting / NewsArticle)

Schema（Article / BlogPosting / NewsArticle）

Choose the most specific type that matches content:
TypeUse case
BlogPostingInformal blog posts; individual authors; regularly updated
ArticleFormal, evergreen content; tool intros; encyclopedic
NewsArticleTime-sensitive news; recognized publishers
选择和内容最匹配的最具体的类型：
类型适用场景
BlogPosting非正式博客帖子；独立作者；定期更新的内容
Article正式的长效内容；工具介绍；百科类内容
NewsArticle时效性新闻；正规发布方的内容

Required Properties

必填属性

  • headline (max 110 chars; often = H1)
  • image (min 1200px wide; absolute URL)
  • datePublished (ISO 8601)
  • author (Person or Organization)
  • publisher (Organization with logo)
  • headline（最多110字符；通常等于H1）
  • image（最小宽度1200px；绝对URL）
  • datePublished（ISO 8601格式）
  • author（个人或组织）
  • publisher（带logo的组织）

Recommended Properties

推荐属性

  • dateModified — signals freshness
  • description — brief summary
  • mainEntityOfPage — canonical URL
  • dateModified——标识内容新鲜度
  • description——简要摘要
  • mainEntityOfPage——规范URL

JSON-LD Example

JSON-LD示例

json
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "The Ultimate SEO Checklist for 2025",
  "description": "A complete guide to optimizing blog posts for search and AI.",
  "image": "https://example.com/image.jpg",
  "datePublished": "2025-01-15T09:00:00Z",
  "dateModified": "2025-02-01T14:30:00Z",
  "author": { "@type": "Person", "name": "Jane Doe", "url": "https://example.com/author/jane" },
  "publisher": { "@type": "Organization", "name": "Example", "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" } }
}
Place in 
<head>
via 
<script type="application/ld+json">
. Validate with Rich Results Test.
json
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "The Ultimate SEO Checklist for 2025",
  "description": "A complete guide to optimizing blog posts for search and AI.",
  "image": "https://example.com/image.jpg",
  "datePublished": "2025-01-15T09:00:00Z",
  "dateModified": "2025-02-01T14:30:00Z",
  "author": { "@type": "Person", "name": "Jane Doe", "url": "https://example.com/author/jane" },
  "publisher": { "@type": "Organization", "name": "Example", "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" } }
}
通过
<script type="application/ld+json">
放在
<head>
中，使用Rich Results Test验证。

Open Graph for Articles

文章Open Graph配置

Use 
og:type: article
for article pages (not 
website
):
html
<meta property="og:type" content="article">
<meta property="og:article:published_time" content="2025-01-15T09:00:00Z">
<meta property="og:article:modified_time" content="2025-02-01T14:30:00Z">
<meta property="og:article:author" content="https://example.com/author/jane">
文章页面使用
og:type: article
（而非
website
）：
html
<meta property="og:type" content="article">
<meta property="og:article:published_time" content="2025-01-15T09:00:00Z">
<meta property="og:article:modified_time" content="2025-02-01T14:30:00Z">
<meta property="og:article:author" content="https://example.com/author/jane">

Internal Linking

内部链接

ElementGuideline
Volume3–5 contextual links in body + 3–6 in Related posts = 6–11 total per article
First paragraph1 link to pillar or key related content
Body2–4 contextual links; one per major section when relevant
Related posts3–6 end-of-article links; same topic cluster
Anchor textDescriptive (e.g. "SEO checklist for 2025", "how to optimize meta tags"); avoid "click here", "learn more", "read more"
VariationMix exact-match, partial-match, branded anchors; avoid over-optimization
Orphan preventionEvery article has ≥1 internal link from hub/pillar or nav
元素规范
数量正文中3-5个上下文相关链接 + 相关文章板块3-6个链接 = 单篇文章总共6-11个内部链接
第一段：1个指向支柱内容或核心相关内容的链接
正文：2-4个上下文相关链接；每个主要章节相关时添加1个
相关文章：文章末尾3-6个链接；属于同一个主题集群
锚文本：描述性文本（例如「2025年SEO清单」、「如何优化meta标签」）；避免「点击这里」、「了解更多」、「阅读更多」
多样性：混合完全匹配、部分匹配、品牌锚文本；避免过度优化
防止孤儿页：每篇文章至少有1个来自Hub/支柱内容或导航的内部链接

Outbound Links (External)

出站链接（外部）

ElementGuideline
Volume2–5 external links per article; cite authoritative sources
When to useStatistics, research, definitions, tool comparisons, expert quotes
Anchor textDescriptive (e.g. "Google's Search Quality Guidelines", "SEO study"); link to source
Same URLCounts once per page for link equity; no need to repeat
E-E-A-TExternal links to reputable sources signal trust — see eeat-signals
元素规范
数量：每篇文章2-5个外部链接；引用权威来源
使用场景：统计数据、研究、定义、工具对比、专家引用
锚文本：描述性文本（例如「Google搜索质量指南」、「SEO研究报告」）；链接到来源
相同URL：每页仅计算一次链接权重；无需重复添加
E-E-A-T：指向权威来源的外部链接可以传递信任信号——参考eeat-signals

References / Citations

参考/引用

ScenarioRecommendation
Data or statisticsCite source inline (e.g. "According to Source, 72% of…") or in a References section
Expert quotesAttribute; link to source or profile
Reference sectionFor pillar/evergreen content with 5+ citations; list at end before Related posts
FormatInline links preferred; numbered refs (e.g. [1], [2]) for academic-style pieces
When to includeAny claim that benefits from authority (stats, studies, definitions); strengthens E-E-A-T — see eeat-signals
场景建议
数据或统计信息：行内引用来源（例如「根据来源，72%的…」）或者放在参考章节
专家引用：标注来源；链接到来源或作者主页
参考章节：引用超过5次的支柱/长效内容可以添加；放在文章末尾、相关文章板块之前
格式：优先行内链接；学术风格内容可以使用编号引用（例如[1]、[2]）
添加时机：任何需要权威性支撑的观点（数据、研究、定义）；可以强化E-E-A-T——参考eeat-signals

AI-Assisted Content

AI辅助内容

When content is AI-assisted: human review before publish; verify facts and add citations; original insights or data; avoid generic phrasing. See eeat-signals for E-E-A-T and AI content guidance.
如果内容是AI辅助生成的：发布前人工审核；核实事实并添加引用；添加原创见解或数据；避免通用表述。E-E-A-T和AI内容指南参考eeat-signals。

Technical

技术优化

  • Core Web Vitals: LCP < 1.0s on mobile
  • Images: WebP, compressed; descriptive alt text; keyword in filename when natural
  • IndexNow: For fast indexing of new posts
  • Canonical: Self-referencing canonical on article page
  • Core Web Vitals：移动端LCP < 1.0s
  • 图片：WebP格式、压缩；描述性alt文本；文件名自然包含关键词
  • IndexNow：新文章快速索引
  • Canonical：文章页面添加自引用规范链接

Post-Publication

发布后

  • Refresh: Update every 6–12 months; refresh stats, add insights
  • Internal links: Add links from older posts to new articles
  • Monitor: GSC indexing, rankings, Core Web Vitals
  • 更新：每6-12个月更新一次；刷新数据、添加新见解
  • 内部链接：从旧文章添加指向新文章的链接
  • 监控：GSC索引状态、排名、Core Web Vitals

Content Analysis

内容分析

When auditing or optimizing an article, analyze content (beyond structure):
DimensionWhat to check
HookIntro opens with pain point, stat, or question?
Keyword in first 100 wordsPrimary keyword present?
QAE patternH2s as questions? Answer-first (40–60 words) in each section?
Word countMatches type? (300–600 news, 1,000–2,500 cluster, 2,500+ pillar)
Paragraph length40–80 words per paragraph? No walls of text?
MultimediaImages, tables, lists, stats; alt text; scannability
Product connectionTies to product? Natural links to features/pricing?
CTAPlacement (conclusion, mid-article); clarity; product link
Internal links3–5 in body + 3–6 Related? Descriptive anchor text? No "click here"?
Outbound links2–5 external links? Authoritative sources? Descriptive anchors?
ReferencesData/stats cited? Reference section for 5+ citations? E-E-A-T signal?
Data/evidenceOriginal data, citations, examples; avoid thin content
GapsWhat do top-ranking articles cover that this misses?
审核或优化文章时，除了结构还要分析以下内容维度：
维度检查项
钩子：引言开头是否有痛点、数据或问题？
前100字包含关键词：是否包含主关键词？
QAE模式：H2是否以问题形式呈现？每个章节是否前40-60字给出答案？
字数：是否匹配内容类型？（新闻300-600字、集群文章1000-2500字、支柱内容2500字以上）
段落长度：每段40-80字？没有大段文字？
多媒体：图片、表格、列表、数据；alt文本；易扫描性
产品关联：是否和产品挂钩？是否自然链接到功能/定价页？
CTA：位置（结论、文中）；清晰度；产品链接
内部链接：正文中3-5个 + 相关文章3-6个？锚文本是描述性的？没有「点击这里」？
出站链接：2-5个外部链接？是权威来源？锚文本是描述性的？
参考：数据/统计是否有引用？引用超过5次是否有参考章节？E-E-A-T信号？
数据/证据：原创数据、引用、示例；避免低质内容
内容缺口：高排名文章覆盖但本文缺失的内容是什么？

Output Format

输出格式

0. Research Phase (output first, when analysis/audit is performed)

0. 调研阶段（执行分析/审核时优先输出）

When analyzing or auditing an article, output this section before Intent Analysis. Include search sources and findings. If user asked to skip search, note that and infer from article only.
SectionOutput
Keyword SearchPrimary keyword (from article or search), secondary keywords, keyword opportunities (from SERP/competitor analysis). If search was performed: query used, top results observed.
Search IntentIntent for primary keyword (Informational/Commercial/Transactional/Navigational), intent for 2–3 secondary keywords, whether article content matches intent. If search was performed: SERP snippet types observed.
Competitor ArticlesIf searched: 2–3 URLs, brief structure (word count, H2s), content gaps, length target. If user provided URLs: same. See competitor-research for full methodology. If skipped: "Competitor analysis skipped."
分析或审核文章时，在意图分析之前先输出本章节，包含搜索来源和发现。如果用户要求跳过搜索，标注说明并仅从文章内容推导。
板块输出内容
关键词搜索：主关键词（来自文章或搜索）、次关键词、关键词机会（来自SERP/竞品分析）。如果执行了搜索：使用的查询、观察到的Top结果。
搜索意图：主关键词意图（信息类/商业类/交易类/导航类）、2-3个次关键词的意图、文章内容是否匹配意图。如果执行了搜索：观察到的SERP片段类型。
竞品文章：如果执行了搜索：2-3个URL、简要结构（字数、H2）、内容缺口、目标篇幅。如果用户提供了URL：输出相同内容。完整方法参考competitor-research。如果跳过：输出「Competitor analysis skipped.」

1. Intent Analysis (output second)

1. 意图分析（第二个输出）

Before any recommendations, output a brief analysis:
DimensionOutput
OrientationFunding/PR, Product update, Guide, News, Evergreen
Primary goalBrand, PR, education, product adoption, organic traffic, …
SEO vs non-SEOSEO-driven / Non-SEO-driven / Hybrid
Evergreen vs timelyEvergreen / Timely
Implications1–2 sentences: e.g. "Low SEO priority → focus on clarity, shareability" or "SEO-driven → full keyword + GEO optimization"
给出任何建议之前，先输出简要分析：
维度输出内容
定位：融资/公关、产品更新、指南、新闻、长效内容
核心目标：品牌、公关、教育、产品 adoption、自然流量等
SEO vs 非SEO：SEO驱动 / 非SEO驱动 / 混合类
长效 vs 时效性：长效内容 / 时效性内容
影响：1-2句话，例如「SEO优先级低 → 重点关注清晰度、可分享性」或「SEO驱动 → 完整关键词+GEO优化」

2. Content Analysis (output third)

2. 内容分析（第三个输出）

Apply the Content Analysis table above. Output a brief assessment per dimension (✅ / ⚠️ / ❌ + one-line note).
应用上文的内容分析表格，每个维度输出简要评估（✅ / ⚠️ / ❌ + 一句话说明）。

3. Recommendations (output fourth, tailored to intent)

3. 优化建议（第四个输出，匹配意图定制）

Assign priority to each item: P0 (critical), P1 (high), P2 (medium), P3 (nice-to-have). Output as table or list with priority prefix.
PriorityUse when
P0Blocks GEO/SEO; missing core element (TL;DR or Key Takeaways, keyword in first 100 words, schema)
P1Significant impact on traffic, CTR, or conversion (title length, share buttons, CTA)
P2Improves UX or authority (related posts, author bio, internal links)
P3Polish (image optimization, readability tweaks)
Example: 
[P0] Add TL;DR or Key Takeaways — GEO, AI citation
  • Product connection (how article supports product; where to link)
  • Keyword (target from product context or keyword research)
  • Structure for article template (hero, TL;DR or Key Takeaways, intro, body, conclusion, related, author)
  • Paragraph length (40–80 words; break with lists, H3s; 100–200 words per H2 section)
  • Featured image (dimensions, alt, file size, og:image alignment)
  • GEO elements (TL;DR or Key Takeaways, QAE pattern) — skip or minimal for non-SEO-driven
  • SEO checklist (title, meta, H1, keyword placement) — skip or minimal for non-SEO-driven
  • Schema type and JSON-LD
  • Internal links (3–5 in body + 3–6 Related; anchor text suggestions; avoid "click here")
  • Outbound links (2–5 external; cite stats, research; anchor text for each)
  • References (inline citations vs Reference section; when to add for E-E-A-T)
  • Competitor analysis (when URLs provided or searched): content gaps vs top rankers, structure to adopt, length target, keyword opportunities — see competitor-research for methodology; Before Analysis to prompt user or search
每个建议标注优先级：P0（关键）、P1（高）、P2（中）、P3（可优化）。以表格或带优先级前缀的列表形式输出。
优先级适用场景
P0：阻塞GEO/SEO；缺失核心元素（TL;DR或核心要点、前100字关键词、schema）
P1：对流量、CTR或转化有显著影响（标题长度、分享按钮、CTA）
P2：提升UX或权威性（相关文章、作者简介、内部链接）
P3：细节优化（图片优化、可读性调整）
示例：
[P0] 添加TL;DR或核心要点 —— 优化GEO、AI引用
建议覆盖以下维度：
  • 产品关联（文章如何支持产品；链接放置位置）
  • 关键词（来自产品上下文或关键词调研的目标）
  • 文章模板结构（Hero、TL;DR或核心要点、引言、正文、结论、相关文章、作者）
  • 段落长度（40-80字；用列表、H3拆分；每个H2章节100-200字）
  • 特色图（尺寸、alt、文件大小、og:image对齐）
  • GEO元素（TL;DR或核心要点、QAE模式）——非SEO驱动内容可跳过或简化
  • SEO检查清单（标题、meta、H1、关键词布局）——非SEO驱动内容可跳过或简化
  • Schema类型和JSON-LD
  • 内部链接（正文中3-5个 + 相关文章3-6个；锚文本建议；避免「点击这里」）
  • 出站链接（2-5个外部链接；引用数据、研究；每个链接的锚文本）
  • 参考（行内引用 vs 参考章节；什么时候添加以提升E-E-A-T）
  • 竞品分析（提供URL或执行搜索时）：和高排名内容的差距、可采纳的结构、目标篇幅、关键词机会——方法参考competitor-research；需要用户补充或搜索时参考分析前章节

Related Skills

相关技能

  • content-marketing: Content types, formats, repurposing; articles as one format
  • eeat-signals: E-E-A-T implementation; author bio, citations, YMYL, AI content
  • competitor-research: Competitor content analysis; content gaps, structure, length target
  • blog-page-generator: Blog index/listing page; article pages live within blog
  • keyword-research: Keyword basis for articles; run before drafting
  • title-tag, meta-description: Article metadata
  • schema-markup: Article/BlogPosting/NewsArticle schema
  • heading-structure: H1–H6 structure for article body
  • content-optimization: Word count, H2 keywords, keyword density, tables, lists, multimedia
  • internal-links: Related posts, contextual links
  • open-graph, twitter-cards: Social previews for articles (required for share previews)
  • social-share-generator: Share buttons placement, platforms, intent URLs
  • url-slug-generator: URL slug creation for articles; 3–5 words, primary keyword
  • toc-generator: Table of contents for long articles
  • breadcrumb-generator: Breadcrumb (e.g. Home > Blog > Category > Post)
  • generative-engine-optimization: GEO strategy; AI citation optimization
  • content-marketing：内容类型、格式、复用；文章是其中一种格式
  • eeat-signals：E-E-A-T落地；作者简介、引用、YMYL、AI内容
  • competitor-research：竞品内容分析；内容缺口、结构、目标篇幅
  • blog-page-generator：博客索引/列表页；文章页面属于博客的一部分
  • keyword-research：文章的关键词基础；撰写前执行
  • title-tag, meta-description：文章元数据
  • schema-markup：Article/BlogPosting/NewsArticle schema
  • heading-structure：文章正文的H1-H6结构
  • content-optimization：字数、H2关键词、关键词密度、表格、列表、多媒体
  • internal-links：相关文章、上下文链接
  • open-graph, twitter-cards：文章社交预览（分享预览必填）
  • social-share-generator：分享按钮位置、平台、跳转URL
  • url-slug-generator：文章URL slug创建；3-5个词、包含主关键词
  • toc-generator：长文的目录
  • breadcrumb-generator：面包屑导航（例如 首页 > 博客 > 分类 > 帖子）
  • generative-engine-optimization：GEO策略；AI引用优化