Overview
INLINECODE0 is a GEO (Generative Engine Optimization) conversion-focused skill.
Its purpose is to help you systematically optimize content for both:
- - AI / GEO performance: structure, clarity, citability, schema, FAQ sections, etc.
- Real-world conversion: sign-ups, purchases, demo requests, bookings, downloads, or other business KPIs.
This skill exists to avoid the trap of “content that AIs love but humans never convert on”.
Whenever you are asked to optimize or create content for GEO, explicitly consider and protect conversion quality using this skill.
INLINECODE1 can be used alone or together with other geo-* skills
such as geo-schema-gen, geo-bulk-processor, and content-focused GEO optimizers.
When to use this skill
Always consider geo-conversion-optimizer when:
- - The user mentions conversion, sign-ups, leads, sales, bookings, trial activations, or ROI.
- The goal is to change or create content for:
- Landing pages and product pages.
- Pricing pages and comparison pages.
- Long-form articles with embedded calls to action.
- Local / location pages that ultimately need calls, bookings, or visits.
- - The user is worried about trade-offs like:
- “Will this hurt my conversion rate?”
- “This feels written for bots, not people.”
- “We optimized for AI but leads went down.”
If the task is purely informational (for example, an internal knowledge base article
with no conversion goal), you may not need this skill. But whenever business outcomes
are in scope, prefer to invoke geo-conversion-optimizer.
High-level workflow
When this skill is invoked, follow this structured workflow:
- 1. Clarify business and conversion goals
- Map user and AI intents
- Audit current content (if it exists)
- Design a dual-track GEO + conversion strategy
- Redesign structure, messaging, and CTAs
- Plan measurement, experiments, and safeguards
- Produce concrete deliverables and implementation notes
Each step is described below.
1. Clarify business and conversion goals
Always start with the business outcome, not just “improve GEO”.
-
Primary conversion goal (e.g., demo request, free trial, add to cart, book appointment).
-
Secondary goals (newsletter sign-up, add to wishlist, download content, account creation).
-
Constraints:
- Brand tone and visual identity.
- Legal / compliance requirements.
- Traffic sources and existing funnels.
- - Ask (or infer) the time horizon:
- Short-term campaign vs. always-on evergreen content.
- Need for quick uplift vs. long-term learning and optimization.
Document these clearly in the plan so all later choices can be traced back.
2. Map user and AI intents
GEO content must serve two overlapping but distinct “consumers”:
- A specific problem, job to be done, or context.
- A stage in the funnel (awareness, consideration, decision, post-purchase).
- Needs clear structure, unambiguous facts, and stable patterns.
- Prefers well-defined entities, relationships, and FAQs.
Actions:
- - Define the top 3–7 user intents this page/content should satisfy.
- For each intent, note:
- Funnel stage.
- Desired
next action (what good looks like).
- Potential
AI queries or prompts that should surface this content.
- - Identify where human and AI needs overlap, and where they diverge.
3. Audit current content (if applicable)
If the content already exists (e.g., a landing page or product page):
- - Evaluate GEO readiness:
- Clear headings and structure?
- Concise, factual sections suitable for AI summarization?
- FAQs and schema present where appropriate?
- - Evaluate conversion readiness:
- Clear primary CTA above the fold?
- Compelling value propositions and social proof?
- Friction points (confusing copy, missing information, trust gaps)?
- - Identify points of conflict:
- Overloaded with keywords and robotic language.
- Walls of text that harm scannability and decision-making.
Summarize issues as tensions (e.g., “explains features well for AI, but hides pricing and CTAs”).
4. Design a dual-track GEO + conversion strategy
For this skill, every recommendation should explicitly show how it serves both tracks:
- Improve structure, clarity, and citability.
- Ensure important entities, relationships, and FAQs are explicit.
- Align with relevant schemas (Article, Product, LocalBusiness, FAQPage, etc.).
- Prioritize information architecture that mirrors the decision journey.
- Make CTAs, proof, and risk reducers visible and compelling.
- Support multiple entry points (e.g., from AI answers deep-linking into sections).
Define:
- - Key sections and their roles for both GEO and conversion.
- Message hierarchy (what must be seen first vs. later).
- Non-negotiables:
- “These CTAs must remain above the fold.”
- “These trust elements (logos, reviews) must be clearly visible.”
5. Redesign structure, messaging, and CTAs
For the page or content in scope:
- - Propose a section-by-section structure:
- Top hero: clear value proposition + primary CTA.
- Problem / pain section.
- Solution / product overview.
- Proof (logos, testimonials, case snippets).
- Detailed comparison, pricing, or feature breakdown.
- FAQs (designed for both AI and human objections).
- Supporting resources / long-form content if relevant.
- - For each section, specify:
-
GEO role: what entities, phrases, or queries it should help with.
-
Conversion role: what objection it answers, what action it nudges.
-
Design notes: any requirements for clarity, brevity, or visual emphasis.
- - Design CTAs and microcopy:
- Primary and secondary CTAs with clear labels.
- Contextual microcopy that reduces friction and fear (e.g., “no credit card required”, “cancel anytime”).
Avoid sacrificing conversion just to “sound more GEO-friendly”. If a GEO change
risks hurting clarity or trust, flag it and propose safer alternatives.
6. Plan measurement, experiments, and safeguards
Always include a measurement and experimentation plan:
- GEO / AI metrics: AI citation presence/coverage if available, impressions or traffic proxies.
- Conversion metrics: CR%, CTR to CTA, lead quality indicators, downstream revenue where available.
- A/B or multivariate tests on key elements (hero message, CTAs, FAQ section).
- Controlled rollouts (e.g., a subset of traffic or a subset of pages).
- Baseline snapshots before changes.
- Guardrail metrics (e.g., “do not accept a GEO uplift that causes >X% drop in CR”).
Make sure the plan is practical for the user’s team and tools (e.g., GA, experimentation platform, internal dashboards).
7. Produce concrete deliverables and implementation notes
Outputs should be ready to act on, not just high-level advice. Examples:
- - Conversion-aware content blueprint:
- Section list, brief description, and GEO vs. conversion role per section.
- - Copy and content recommendations:
- Example headlines, CTAs, FAQ questions and answers, proof elements.
- - Integration notes for other
geo-* skills:
- Where to call
geo-schema-gen for structured data.
- How to align with
geo-bulk-processor if many similar pages must be optimized.
- - Rollout and testing checklist:
- Steps for implementation, QA, and measurement.
Be explicit about what is opinionated guidance vs. what is strictly required.
Input and output expectations
Inputs
Expect to work with:
- - URLs, HTML/Markdown content, or copy drafts.
- Screenshots, wireframes, or descriptions of current pages.
- Conversion data (if shared) such as:
- Current conversion rates.
- Click maps, scroll depth summaries, or common user complaints.
- - Business constraints (e.g., mandatory legal text, forbidden claims).
If information is missing, state reasonable assumptions instead of getting blocked,
and clearly mark them as assumptions.
Outputs
Unless the user asks for something very specific, default to the following structures:
- - Conversion-aware GEO optimization report
- Executive summary.
- Business goals and constraints.
- Main recommendations with GEO vs. conversion rationale.
- Section-by-section outline.
- Key messages, CTAs, and proof elements.
- GEO and schema notes.
- - Experiment and measurement plan
- Proposed tests.
- Metrics and guardrails.
- Rollout and iteration approach.
If the user wants directly usable copy, produce draft copy that already
embeds both GEO and conversion principles.
Use of bundled resources
This skill ships with additional resources:
- Contains patterns and checklists for balancing GEO and conversion
across common page types (landing pages, product pages, blogs, local pages).
- Provides ready-made section archetypes and objection-handling patterns.
- Contains simple data models and helper functions for representing
page blueprints, CTAs, and experiments at a structured level.
- Can be used as inspiration for how teams might represent and track
conversion-aware GEO changes across many pages.
Use these resources when you need more concrete examples or templates
to structure your recommendations.
Style and collaboration guidelines
- - Think like a performance marketer plus GEO architect.
- Protect user clarity, trust, and intent-to-buy while also serving AI needs.
- When a suggestion helps GEO but may harm conversion (or vice versa),
make the trade-off explicit and offer alternatives.
- - Be concrete and operational.
- Favor checklists, sections, and examples that can be implemented directly.
- - Respect domain constraints.
- For regulated industries (health, finance, legal), be extra cautious
about claims and wording. Encourage review by legal/compliance teams.
The mission of geo-conversion-optimizer is to make GEO work for the
business, not just for rankings or AI citations in isolation.
概述
geo-conversion-optimizer 是一项专注于 GEO（生成式引擎优化）转化的技能。
其目的是帮助您系统地优化内容，使其同时满足以下两方面需求：
- - AI / GEO 性能：结构、清晰度、可引用性、结构化数据、常见问题解答部分等。
- 真实世界转化：注册、购买、演示请求、预订、下载或其他业务关键绩效指标。
这项技能的存在是为了避免陷入“AI 喜欢但人类从不转化的内容” 的陷阱。
每当您被要求为 GEO 优化或创建内容时，请使用此技能明确考虑并保护转化质量。
geo-conversion-optimizer 可以单独使用，也可以与其他 geo-* 技能（如 geo-schema-gen、geo-bulk-processor 以及专注于内容的 GEO 优化器）结合使用。
何时使用此技能
在以下情况下，始终考虑使用 geo-conversion-optimizer：
- - 用户提到转化、注册、线索、销售、预订、试用激活或投资回报率。
- 目标是更改或创建以下内容：
- 着陆页和产品页面。
- 定价页面和对比页面。
- 嵌入行动号召的长篇文章。
- 最终需要电话、预订或访问的本地/位置页面。
- “这会损害我的转化率吗？”
- “这感觉像是为机器人写的，而不是为人写的。”
- “我们为 AI 优化了，但线索却下降了。”
如果任务是纯粹信息性的（例如，没有转化目标的内部知识库文章），您可能不需要此技能。但只要涉及业务成果，就应优先调用 geo-conversion-optimizer。
高级工作流程
当调用此技能时，请遵循此结构化工作流程：
- 1. 明确业务和转化目标
- 映射用户和 AI 意图
- 审计现有内容（如果存在）
- 设计双轨 GEO + 转化策略
- 重新设计结构、信息和行动号召
- 规划衡量、实验和保障措施
- 生成具体可交付成果和实施说明
每个步骤如下所述。
1. 明确业务和转化目标
始终从业务成果开始，而不仅仅是“改进 GEO”。
-
主要转化目标（例如，演示请求、免费试用、加入购物车、预约）。
-
次要目标（新闻通讯注册、加入愿望清单、下载内容、创建账户）。
-
约束条件：
- 品牌调性和视觉形象。
- 法律/合规要求。
- 流量来源和现有漏斗。
- 短期活动 vs. 常青的长期内容。
- 需要快速提升 vs. 长期学习和优化。
在计划中清晰记录这些内容，以便所有后续选择都可以追溯。
2. 映射用户和 AI 意图
GEO 内容必须服务于两个重叠但不同的“消费者”：
- 特定问题、待完成工作或背景。
- 漏斗中的阶段（认知、考虑、决策、购买后）。
- 需要清晰的结构、明确的事实和稳定的模式。
- 更喜欢定义明确的实体、关系和常见问题解答。
操作：
- - 定义此页面/内容应满足的前 3-7 个用户意图。
- 对于每个意图，注明：
- 漏斗阶段。
- 期望的
下一步行动（理想结果）。
- 应使此内容浮现的潜在
AI 查询或提示。
- - 确定人类和 AI 需求重叠的地方，以及它们分歧的地方。
3. 审计现有内容（如适用）
如果内容已存在（例如，着陆页或产品页面）：
- 清晰的标题和结构？
- 适合 AI 总结的简洁、事实性部分？
- 在适当位置存在常见问题解答和结构化数据？
- 首屏上方有清晰的主要行动号召？
- 有说服力的价值主张和社会证明？
- 摩擦点（令人困惑的文案、缺失的信息、信任差距）？
- 关键词过载和机器人语言。
- 影响可扫描性和决策的文本墙。
将问题总结为张力（例如，“为 AI 很好地解释了功能，但隐藏了定价和行动号召”）。
4. 设计双轨 GEO + 转化策略
对于此技能，每项建议都应明确显示它如何服务于两条轨道：
- 改进结构、清晰度和可引用性。
- 确保重要的实体、关系和常见问题解答是明确的。
- 与相关结构化数据（文章、产品、本地企业、常见问题解答页面等）保持一致。
- 优先考虑反映决策旅程的信息架构。
- 使行动号召、证明和风险降低因素可见且具有说服力。
- 支持多个入口点（例如，从 AI 答案深度链接到各个部分）。
定义：
- - 关键部分及其对 GEO 和转化的作用。
- 信息层级（必须首先看到什么 vs. 稍后看到什么）。
- 不可妥协项：
- “这些行动号召必须保持在首屏上方。”
- “这些信任元素（标志、评论）必须清晰可见。”
5. 重新设计结构、信息和行动号召
对于范围内的页面或内容：
- 顶部英雄区：清晰的价值主张 + 主要行动号召。
- 问题/痛点部分。
- 解决方案/产品概述。
- 证明（标志、推荐、案例片段）。
- 详细对比、定价或功能分解。
- 常见问题解答（为 AI 和人类异议而设计）。
- 支持资源/长篇内容（如相关）。
-
GEO 作用：它应帮助哪些实体、短语或查询。
-
转化作用：它回答了什么异议，它推动了什么行动。
-
设计说明：任何关于清晰度、简洁性或视觉强调的要求。
- 带有清晰标签的主要和次要行动号召。
- 减少摩擦和恐惧的上下文微文案（例如，“无需信用卡”、“随时取消”）。
避免为了“听起来更 GEO 友好”而牺牲转化。如果 GEO 更改有损害清晰度或信任的风险，请标记它并提出更安全的替代方案。
6. 规划衡量、实验和保障措施
始终包含衡量和实验计划：
- GEO / AI 指标：AI 引用存在/覆盖率（如可用）、展示次数或流量代理。
- 转化指标：转化率%、行动号召点击率、线索质量指标、下游收入（如可用）。
- 对关键元素（英雄区信息、行动号召、常见问题解答部分）进行 A/B 或多变量测试。
- 受控发布（例如，一部分流量或一部分页面）。
- 更改前的基线快照。
- 护栏指标（例如，“不接受导致转化率下降超过 X% 的 GEO 提升”）。
确保计划对用户的团队和工具（例如，GA、实验平台、内部仪表板）是实用的。
7. 生成具体可交付成果和实施说明
输出应可立即执行，而不仅仅是高级建议。示例：
- 部分列表、简要描述以及每个部分的 GEO vs. 转化作用。
- 示例标题、行动号召、常见问题解答问题和答案、证明元素。
- 在何处调用 geo-schema-gen 以获取结构化数据。
- 如果必须优化许多类似页面，如何与 geo-bulk-processor 保持一致。
- 实施、质量保证和衡量的步骤。
明确说明哪些是有观点的指导，哪些是严格要求的。
输入和输出期望
输入
期望处理：
- - URL、HTML/Markdown 内容或文案草稿。
- 当前页面的截图、线框图或描述。
- 转化数据（如果共享），例如：
- 当前转化率。
- 点击图、滚动深度摘要或常见用户投诉。
- - 业务约束（例如，强制性法律文本、禁止的声明）。
如果信息缺失，陈述合理的假设而不是停滞不前，并明确将其标记为假设。
输出
除非用户要求非常具体的内容，否则默认使用以下结构：
- 执行摘要。
- 业务目标和约束。
- 主要建议及 GEO vs. 转化理由。
