Token导航 LogoToken导航

Agent Skill · 研究检索

seo-geo-playbook(SEO GEO playbook 搜索)

seo-geo-playbook 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

seo-geo-playbook 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 18,519。

总安装 6,045周安装 257GitHub Stars 公开资料未说明下载 2,118核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.1.2

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:seo-geo-playbook(SEO GEO playbook 搜索)
来源仓库:https://github.com/gingiris/seo-geo-playbook
安装命令:
openclaw skills install seo-geo-playbook
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install seo-geo-playbook

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

SEO GEO Playbook 提供双重 SEO 与地理定位优化策略,提升在 Google 及 AI 模型中的排名。适用于希望被 ChatGPT、Perplexity 等平台引用的内容创作者。基于成功产品发布经验构建,含可复用的内容框架与传播路径。安装后需根据实际业务调整本地化与品牌调性。

建议定期更新策略以匹配算法变化与用户需求演进。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install seo-geo-playbook;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

seo-geo-playbook 怎么安装?

在终端执行 openclaw skills install seo-geo-playbook。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

seo-geo-playbook 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

seo-geo-playbook 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

seo-geo-playbook 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

seo-geo-playbook 用的人多吗?

公开数据是累计安装 6,045 次,近一周安装 257 次,下载 2,118 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

seo-geo-playbook 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
seo-geo-playbook

SEO GEO playbook 搜索 · 本页

6,045—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
SEO & GEO (Generative Engine Optimization) Playbook
version
1.0.2
description
|
Keywords
seo, geo, generative engine optimization, ai seo, perplexity seo, chatgpt seo, perplexity seo guide, e-e-a-t, indexnow, schema markup, seo article template, seo writing, content marketing, content marketing for startups, search engine optimization, seo strategy, seo checklist, seo audit, seo tools, seo tools for developers, seo for startups, seo for developers, perplexity optimization, bing copilot seo, chatgpt search optimization, seo playbook, seo guide, seo tutorial

SEO & GEO Playbook

Built from 30+ Product Hunt #1 launches and 10k+ GitHub stars campaigns by Iris (@gingiris) — AFFiNE former COO, 2022-2026

TL;DR

  • GEO ≠ SEO — AI engines cite differently than Google ranks
  • Structure beats keywords — tables, FAQ, direct answers get cited
  • Founder voice > AI voice — authenticity signals are the #1 GEO factor
  • IndexNow — push URLs to Bing instantly, Bing trains AI on fresh content
  • Build TOFU→BOFU content funnels — high-intent pages convert 10x better

📊 GEO vs SEO: Two Games, One Content

DimensionSEO (Traditional)GEO (AI Search)
GoalRank on Google/BingBe cited in AI answers
Core SignalBacklinks + keywordsStructure + E-E-A-T
Content FormatH2/H3 + long-tailDirect answers + tables + FAQ
TechnicalSitemap + Core Web VitalsIndexNow + Schema + robots.txt
MeasurementGA4 traffic + rankingManual AI citation check
SpeedWeeks to monthsHours with IndexNow

Key insight: Structure your content for BOTH. Schema markup and tables serve both games simultaneously.


🎯 The GEO Core Three (Your Technical Stack)

1. IndexNow — Real-Time Bing Push

Bing uses IndexNow to train AI models on fresh content. Every new article → push immediately.

# Push new URL to Bing (and Bing shares with AI engines)
curl "https://www.bing.com/indexnow?url=YOUR_URL&key=YOUR_KEY"

# Batch push (multiple URLs)
curl -X POST "https://www.bing.com/indexnow" \
  -H "Content-Type: application/json" \
  -d '{"host":"your-site.com","key":"YOUR_KEY","urlList":["url1","url2"]}'

Setup: Get your key from Bing Webmaster Tools → IndexNow → Generate Key

When to push:

  • New article published
  • Significant content update
  • Product launch / major announcement

2. Schema Markup — Structured Data

<!-- Article Schema -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "author": {"@type": "Person", "name": "Your Name"},
  "datePublished": "2026-04-09",
  "dateModified": "2026-04-09",
  "publisher": {"@type": "Organization", "name": "Your Brand"}
}
</script>

<!-- FAQPage Schema (HIGH citation rate) -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is GEO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "GEO (Generative Engine Optimization) is the practice..."
      }
    }
  ]
}
</script>

Schema priority for citation:

  1. FAQPage (highest — AI loves Q&A format)
  2. Article/BlogPosting
  3. SoftwareApplication (for tools/products)
  4. Organization + Person (brand authority)

3. AI-Friendly Content Format

AI engines extract "citation-ready" content blocks. Structure your articles for extraction:

The QAE Pattern (Question → Answer → Evidence):

## How to launch on Product Hunt?

**[Direct answer in 1-2 sentences]**
The best time to launch is Tuesday–Thursday, 9 AM GMT. The key is having 50+ upvotes in the first 2 hours.

**[Then evidence/data]**
Based on analyzing 30 Product Hunt launches:
- Tuesday launches: avg 280 upvotes
- Thursday launches: avg 260 upvotes
- Weekend launches: avg 80 upvotes

**[Then action]**
Prepare your hunter outreach list 2 weeks before launch...

Table format increases citation ~35%:

| Platform | Traffic Share | Citation Rate |
|----------|--------------|---------------|
| YouTube | High | +25% cited by AI |
| GitHub | Very High | Highest AI citation |
| Reddit | Medium-High | AI summarizable |

✍️ The Founder Voice System (E-E-A-T Secret)

AI engines prioritize content with authenticity signals. Generic AI content gets penalized. The fix: inject "founder voice."

Voice Elements That Signal Realness

  1. Time + Place Anchoring — "It was 2 AM on a Thursday in August 2022..."

- Instead of: "In my experience..."

  1. Parenthetical Aside — "(I made this mistake once. Not twice.)"

- Shows personal accountability

  1. Em-dash Contrast — "Reddit gave us volume — HN gave us trust."

- Creates rhythm and depth

  1. Specific Numbers — "28 appearances on GitHub Trending"

- Instead of: "appeared many times"

  1. Mistakes + Lessons — "We tried X. It failed. Here's why."

- Shows lived experience

Key Stats Table (Every Article)

Every article should have this near the top:

| Metric | Value |
|--------|-------|
| Results achieved | [Specific number] |
| Timeframe | [Specific period] |
| Cost | [$X or "free"] |
| Team size | [N people] |
| Win rate | [% or ratio] |

AI engines love extracting and citing these.

The Pattern: Specific → General

WRONG: "Many startups struggle with launch strategy."

RIGHT: "When AFFiNE launched on Product Hunt in August 2022, 
we got 180 upvotes on day one. Most startups get 20-40. 
The difference wasn't luck — it was a specific sequence of 
actions that we refined across 30 subsequent launches."

📝 SEO Article Template

Frontmatter

---
title: "[Target Keyword]: [Specific Benefit] in 2026"
description: "[100-160 chars, include keyword + CTA]"
date: YYYY-MM-DD
tags: [tag1, tag2]
canonical: https://original-url.com
---

Article Structure

<!-- TL;DR block — AI engines love these -->
## TL;DR
- Key point 1
- Key point 2
- Key point 3

<!-- Key Stats table — place early -->
| Metric | Value |
|--------|-------|

## [H2: Question/Problem Form]

[Direct answer — 2 sentences max]
[Evidence/data/case study]
[Action step]

## [H2: Next Topic]

... (repeat pattern)

## Key Takeaways
1. 
2. 
3.

## Related Tools / Resources
- [Tool 1](link) — 1-sentence description
- [Tool 2](link) — 1-sentence description

SEO Title Formulas

TypeFormulaExample
How-to"How to [Task] in 2026: [N] [Methods]""How to launch on Product Hunt in 2026: 5 Proven Strategies"
Comparison"[Product A] vs [Product B]: Which is Better in 2026?""Notion vs AFFiNE: Which is Better in 2026?"
List"[N] [Category] Tools for [Use Case] in 2026""15 Open Source Alternatives to Notion in 2026"
Problem"How to Solve [Problem]: [Solution] Guide""How to Solve Content Marketing: The 2026 Playbook"

🔍 Keyword Funnel Strategy

TOFU (Awareness) → MOFU (Consideration) → BOFU (Decision)

TOFU: "how to improve team collaboration"
  → Blog posts, guides, educational content
  → Low intent, high volume

MOFU: "best collaboration software 2026"  
  → Comparison articles, list posts, category pages
  → Medium intent

BOFU: "[Product] pricing / reviews / vs [competitor]"
  → Product pages, pricing, reviews
  → High intent, lowest volume, highest conversion

Priority: Build BOFU pages first.

Even with 10 monthly searches, a BOFU page converts 10x better than TOFU.

Keyword Research Framework

  1. Seed keywords — your product category, use case
  2. Expand with — competitor names, tool alternatives, "[product] vs"
  3. Long-tail gems — KD 30-50, specific use cases, "for [audience]"
  4. Filter — must have commercial or informational intent (not navigate)

🚀 Multi-Platform Distribution SOP

Step 1: Publish to Main Site

  • Jekyll/GitHub Pages, Hugo, or any static site
  • Include Article Schema + FAQ Schema
  • Verify: https://search.google.com/test/rich-results

Step 2: IndexNow Push (immediately)

curl "https://www.bing.com/indexnow?url=NEW_URL&key=YOUR_KEY"

Step 3: Dev.to Cross-Post

curl -X POST "https://dev.to/api/articles" \
  -H "api-key: $DEVTO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "article": {
      "title": "...",
      "body_markdown": "...",
      "canonical_url": "https://your-site.com/post-slug",
      "tags": ["tag1", "tag2"],
      "published": true
    }
  }'

Critical: Set canonical_url to your main site — this passes SEO value to your domain.

Step 4: Hashnode (optional, for tech audience)

  • Same canonical_url strategy

Step 5: GitHub README Update (for tools)

  • Add article link to README "Related Content" section
  • This creates a backlink + signals active maintenance

✅ GEO Audit Checklist

Before publishing any page, verify:

Technical

  • [ ] robots.txt allows AI crawlers:
  User-agent: GPTBot
  User-agent: ChatGPT-User
  User-agent: OAI-SearchBot
  Allow: /
  • [ ] IndexNow key registered and tested
  • [ ] sitemap.xml includes this page
  • [ ] Canonical URL set correctly

Content

  • [ ] FAQPage Schema added (5+ questions)
  • [ ] Article Schema added (author, date, publisher)
  • [ ] Key Stats table in first 100 words
  • [ ] H2 headings are questions or benefit statements
  • [ ] Each H2 section starts with 2-sentence direct answer
  • [ ] Internal links to 2+ related pages
  • [ ] External links to 2+ high-authority sources

Distribution

  • [ ] IndexNow push executed
  • [ ] Dev.to cross-posted with canonical_url
  • [ ] GitHub README updated (if tool/product)

📚 Prompt Templates

Prompt: GEO Article Writer

You are a SEO + GEO content writer for [brand]. 

Write an article targeting: "[target keyword]"

Requirements:
1. Opening: Time + place anchor, then Key Stats table
2. Structure: H2 = questions, first 2 sentences = direct answers
3. Include FAQPage Schema (5+ questions)
4. Include Article Schema
5. Founder voice: parenthetical asides, specific numbers, lessons from mistakes
6. Internal links to [related pages]
7. External links to 2 high-authority sources
8. Key Takeaways section at end

Output: Full markdown article ready to publish.

Prompt: GEO Audit

Audit [URL] for GEO optimization. Check:
1. robots.txt — AI bots allowed?
2. FAQPage Schema — present + valid?
3. Article Schema — present + complete?
4. Opening 100 words — Key Stats table present?
5. H2 structure — questions, direct answers first?
6. Table count — at least 1 comparison table?
7. Internal/external links — balanced?
8. Canonical URL — set correctly?

For each issue: severity (high/medium/low) + fix recommendation.

Prompt: Keyword Research

Research keywords for [product/category]:
- Find 10 MOFU keywords (KD 30-50, monthly volume 100-500)
- Find 5 BOFU keywords (product comparisons, pricing, "[product] vs")
- For each: search volume, KD, intent type, content angle

Prioritize keywords where [product] has clear differentiation.

📊 Real Results

This methodology produced:

  • 30+ Product Hunt daily #1 launches
  • 10k+ GitHub stars for open source projects (0 → 33k in 18 months)
  • GitHub Trending 28+ appearances
  • Top 3 rankings on Google for competitive terms like "github marketing playbook"

🔗 Resources

Free Playbooks (GitHub):

  • gingiris-launch: https://github.com/Gingiris/gingiris-launch
  • gingiris-opensource: https://github.com/Gingiris/gingiris-opensource
  • gingiris-b2b-growth: https://github.com/Gingiris/gingiris-b2b-growth

Growth Tools:

  • https://gingiris.github.io/growth-tools/

Author: Iris (@gingiris) — AFFiNE former COO, open source growth consultant

平台分布

OpenClaw

96.23%
按下载量换算2,038

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills