跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

seo-content-strategy

Turn customer questions and observed search demand into a prioritized content brief with original evidence, internal links, and a measurement plan. Use for content planning or improving an existing resource; technical blockers should be diagnosed first.

ronaldships · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add ronaldships/foundvia-discovery --skill seo-content-strategy

技能说明


name: seo-content-strategy description: Turn customer questions and observed search demand into a prioritized content brief with original evidence, internal links, and a measurement plan. Use for content planning or improving an existing resource; technical blockers should be diagnosed first.

Content grounded in customer demand

Inspect the product, intended customer, existing pages, support questions, and authorized search data. Distinguish supplied evidence from assumptions. If demand data is missing, propose a small experiment instead of claiming a keyword volume.

Choose a useful page

Define the reader's problem and what they should be able to do afterward. Prefer improving a relevant existing page when it already answers the same question. Differentiate a tutorial, product explanation, comparison, and documentation by purpose, not a publishing quota.

Use the brief template to specify the question, original proof, direct answer, supporting sections, relevant links, next action, owner, and measurement window. Include actual examples, tested steps, limitations, and checked source dates. Length follows the information needed; word counts are not ranking requirements.

Keep publication truthful

Use real publication and significant-update records. Shared dates are valid. Do not reset dates on every build or invent a percentage-change threshold. Do not publish fabricated testimonials, pricing, usage figures, or author credentials. Explain AI assistance when material to the reader; review generated claims before publication.

Schema must describe visible content. FAQ sections can help readers, but FAQ markup is not a discovery prerequisite and Google's FAQ rich-result feature has been removed. Serialize JSON-LD safely in implementations.

Measure the experiment

Define one page, its reader question, conversion event, and a follow-up date. Keep impressions, clicks, sessions, activation, and revenue separate. Evaluate whether the resource helped rather than attributing every change to one edit. Deliver the brief and proposed draft within the requested scope; posting and deployment require authorization.

Sources: helpful content, current structured-data changes.