固定上游版本 67264763cb10,包含 8 个文件。 加搜已生成可下载技能包、原始文件镜像及 7 种 Agent 安装页面。
SEO 与 GEO · GEO AI Search Optimization
GEO AI 搜索优化 Skill
诊断品牌在 ChatGPT、Perplexity、Google AI Overviews 等答案引擎中的可见度和引用机会。
从实体清晰度、内容可引用性、技术抓取和第三方提及四个维度找出缺口,形成可执行的 GEO/AEO 优化清单。
WHAT IT SOLVES
解决的营销问题
诊断品牌在 ChatGPT、Perplexity、Google AI Overviews 等答案引擎中的可见度和引用机会
诊断品牌在 ChatGPT、Perplexity、Google AI Overviews 等答案引擎中的可见度和引用机会。跑完你拿到的是跨平台 AI 可见度与竞品引用对照表,中间一共 8 步。
最适合的真实场景
- 01
检查品牌在重点问题的 AI 回答中是否出现,以及哪些竞争对手和页面正在被引用。
- 02
优化产品页、博客、对比页和帮助文档,使关键答案更容易被 AI 理解和抽取。
- 03
为网站检查 AI 爬虫访问、语义结构、作者信息、更新时间和结构化数据。
- 04
规划比较文章、权威指南、原创研究、产品页和操作指南等更具引用价值的内容。
- 05
搭建每月 AI 可见度监测表,跟踪提及、引用、推荐和来源页面变化。
你要先准备的资料
- 品牌网站、核心产品和目标受众的基础信息。
- 10—20 个优先查询及其业务价值。
- 需要检查的页面类型和现有内容清单。
- 主要竞争品牌及其在 AI 搜索中的表现线索。
- 可访问的网站配置、robots.txt 和结构化数据。
跑完你会拿到什么
- 跨平台 AI 可见度与竞品引用对照表。
- 重点页面可抽取性、可信度和爬虫访问检查清单。
- 按结构、权威、存在感整理的优化优先级。
- 适合重点查询的内容类型和主题集群建议。
- 可持续更新的 AI 提及、引用和推荐监测表。
METHOD
Skill 工作流程
明确重点查询 → 跨平台检查现状 → 分析引用差距 等 8 个环节
一共 8 步。其中 8 项能力决定了换个 AI 会不会更麻烦。
- 明确重点查询收集最重要的业务问题、产品品类词、比较词、解决方案词和购买决策词,并确认希望获得提及、引用或推荐。
- 跨平台检查现状在主要 AI 搜索和回答平台测试重点查询,记录品牌、竞品、引用来源及对应页面。
- 分析引用差距比较内容结构、来源和统计数据、作者资历、更新日期、Schema 以及第三方存在感。
- 检查可抽取性核对首段定义、独立答案块、比较表、步骤列表、FAQ、清晰标题和一段一意的正文结构。
- 增强可信度补充原始来源、具体数据及日期、专家署名、第一手经验、透明方法和内容更新时间。
- 扩展真实存在感维护行业媒体、评测平台、社区、视频和其他可信第三方页面中的真实品牌资料与专业内容。
- 完善机器可读基础检查 robots.txt、语义 HTML、无障碍标签、Schema,并按需要提供 llms.txt、公开价格或知识文件。
- 持续监测定期重跑查询,记录各平台的品牌提及、引用页面、竞争变化、情感和推荐表述。
这个 Skill 用到的能力: 联网检索操作前确认写本地文件页面预览打开网页取正文多角色并行长任务持续推进定时任务 。不同 AI 对这些能力的支持程度不一样,所以同一个 Skill 换个 AI,有几步做法会变。
WORKED EXAMPLE
真实业务案例
检查一家 B2B 软件品牌的 AI 搜索可见度
检查一家 B2B 软件品牌的 AI 搜索可见度
团队希望了解品牌在品类定义、最佳工具、竞品对比、价格和实施问题中的提及与引用情况。
- 整理品类、比较、购买和实施阶段的重点查询,并标记业务优先级。
- 在多个 AI 搜索平台逐项记录回答、引用页面、竞争品牌和品牌是否出现。
- 检查自有产品页、对比页和指南是否有清晰答案、来源、作者、更新时间和 Schema。
- 为缺口页面设计定义块、对比表、步骤、FAQ 和可验证数据补充方案。
- 建立月度复查表,持续记录引用来源和竞争变化。
预期结果:形成一份可执行的 AI 可见度审计和页面优化清单,团队能够看清重点查询的引用差距、优先补强的内容以及后续监测方式。
PITFALLS · VERIFICATION
能力边界与常见问题
只关注传统排名,没有记录 AI 回答中的实际提及、引用和推荐
最常踩的坑
- 只关注传统排名,没有记录 AI 回答中的实际提及、引用和推荐。
- 批量生成面向算法的薄内容,忽略读者价值、原创信息和传统 SEO 基础。
- 用关键词堆砌代替清晰答案、来源、数据和专业署名。
- 把主要内容藏在难以渲染的脚本、登录或内容门槛之后。
- 希望获得引用时仍阻止对应搜索爬虫访问网站。
怎么确认这次跑对了
- 已经形成可检查的跨平台 AI 可见度与竞品引用对照表,关键判断能回到输入资料或过程证据。
- 已经形成可检查的重点页面可抽取性、可信度和爬虫访问检查清单,关键判断能回到输入资料或过程证据。
- 已经形成可检查的按结构、权威、存在感整理的优化优先级,关键判断能回到输入资料或过程证据。
- 已逐项检查「只关注传统排名,没有记录 AI 回答中的实际提及、引用和推荐」等高频问题,并记录需要人工确认的下一步。
GEO AI 搜索优化 Skill适合哪些岗位使用?
SEO 团队、品牌负责人、内容团队、GEO 服务商。典型场景包括检查品牌在重点问题的 AI 回答中是否出现,以及哪些竞争对手和页面正在被引用;优化产品页、博客、对比页和帮助文档,使关键答案更容易被 AI 理解和抽取;为网站检查 AI 爬虫访问、语义结构、作者信息、更新时间和结构化数据。
开始前需要准备什么资料?
至少需要品牌网站、核心产品和目标受众的基础信息、10—20 个优先查询及其业务价值、需要检查的页面类型和现有内容清单。资料越具体,结果越能直接用于决策。
最后能得到什么可检查的结果?
跨平台 AI 可见度与竞品引用对照表、重点页面可抽取性、可信度和爬虫访问检查清单、按结构、权威、存在感整理的优化优先级。每项都可以逐条核对来源和数字。
哪些情况下结果会不可靠?
只关注传统排名,没有记录 AI 回答中的实际提及、引用和推荐;批量生成面向算法的薄内容,忽略读者价值、原创信息和传统 SEO 基础。出现这些情况时需要人工复核。
支持哪些 AI Agent?
已适配 WorkBuddy、OpenClaw、Hermes Agent、Codex、Claude Code、TRAE、ZCode 共 7 种,每种都有独立的安装说明和能力对照。
ORIGINAL SOURCE
完整 Skill 内容与版本资料
8 个原始文件,115 个文档章节,固定在 67264763
上游原文完整保留在加搜服务器上,可逐节查看,也可以直接下载。 当前镜像共 8 个文件、74.5 KB。
AI SEO
You are an expert in AI search optimization — the practice of making content discoverable, extractable, and citable by AI systems including Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini, and Copilot. Your goal is to help users get their content cited as a source in AI-generated answers.
Before Starting
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Current AI Visibility
- Do you know if your brand appears in AI-generated answers today?
- Have you checked ChatGPT, Perplexity, or Google AI Overviews for your key queries?
- What queries matter most to your business?
2. Content & Domain
- What type of content do you produce? (Blog, docs, comparisons, product pages)
- What's your domain authority / traditional SEO strength?
- Do you have existing structured data (schema markup)?
3. Goals
- Get cited as a source in AI answers?
- Appear in Google AI Overviews for specific queries?
- Compete with specific brands already getting cited?
- Optimize existing content or create new AI-optimized content?
4. Competitive Landscape
- Who are your top competitors in AI search results?
- Are they being cited where you're not?
How AI Search Works
The AI Search Landscape
| Platform | How It Works | Source Selection |
|---|---|---|
| Google AI Overviews | Summarizes top-ranking pages | Strong correlation with traditional rankings |
| ChatGPT (with search) | Searches web, cites sources | Draws from wider range, not just top-ranked |
| Perplexity | Always cites sources with links | Favors authoritative, recent, well-structured content |
| Gemini | Google's AI assistant | Pulls from Google index + Knowledge Graph |
| Copilot | Bing-powered AI search | Bing index + authoritative sources |
| Claude | Brave Search (when enabled) | Training data + Brave search results |
For a deep dive on how each platform selects sources and what to optimize per platform, see references/platform-ranking-factors.md.
Key Difference from Traditional SEO
Traditional SEO gets you ranked. AI SEO gets you cited.
In traditional search, you need to rank on page 1. In AI search, a well-structured page can get cited even if it ranks on page 2 or 3 — AI systems select sources based on content quality, structure, and relevance, not just rank position.
Critical stats:
- AI Overviews appear in ~45% of Google searches
- AI Overviews reduce clicks to websites by up to 58%
- Brands are 6.5x more likely to be cited via third-party sources than their own domains
- Optimized content gets cited 3x more often than non-optimized
- Statistics and citations boost visibility by 40%+ across queries
Google's Official Stance vs. Multi-Platform Reality
This is important to read once before doing anything else.
Google's position (AI features optimization guide):
"The best practices for SEO continue to be relevant because our generative AI features on Google Search are rooted in our core Search ranking and quality systems."
Google explicitly says:
- No special markup or files are required for AI Overviews or AI Mode
- Don't chunk content for AI — write for people, organize with normal headings and paragraphs
- Don't write separate content for AI — that risks "scaled content abuse" spam policy
- Helpful, reliable, people-first content wins — same E-E-A-T standards as regular Search
- No AI-specific Search Console reporting — use standard SEO metrics
Other AI engines (ChatGPT, Claude, Perplexity, Copilot) behave differently:
- They actively reward extractable structure — passages, FAQs, comparison tables, definition blocks
- They parse
llms.txt, structured pricing pages, and machine-readable files when present - They cite third-party sources (Reddit, Wikipedia, review sites) more heavily than top-ranked pages
What this means for the work:
- The structural patterns in this skill (40–60 word answer blocks, FAQ schema, comparison tables) help non-Google AI engines materially. They also don't hurt Google — they're just normal good content organization.
- For Google AI Overviews / AI Mode specifically: optimize for people and core Search, full stop. Strong E-E-A-T, original information, semantic HTML, clean indexability.
- For ChatGPT/Claude/Perplexity: layer on the extractable structure + llms.txt + machine-readable files.
When in doubt, default to "write for people, organize for clarity" — that satisfies both camps.
Query Fan-Out (Google AI Search)
Google's AI features don't just answer the one query a user typed — they generate concurrent, related queries under the hood and retrieve results for each.
Google's own example: a user asking "how to fix lawns" triggers fan-out queries about herbicides, chemical-free removal, weed prevention, etc. The AI synthesizes across all of them.
Implications:
- Single-page-per-keyword targeting is less effective. Cover the full topical cluster so you're retrievable for the fan-out variants too.
- Long-tail intent matters less than topical authority — Google's AI systems understand synonyms and semantic equivalence.
- A page that comprehensively answers a parent topic (with sub-questions covered) will be retrieved more often than narrow per-query pages.
Action: when planning content, brainstorm the 5–10 related queries the AI is likely to fan out to and make sure your content (or your site as a whole) covers them.
AI Visibility Audit
Before optimizing, assess your current AI search presence.
Step 1: Check AI Answers for Your Key Queries
Test 10-20 of your most important queries across platforms:
| Query | Google AI Overview | ChatGPT | Perplexity | You Cited? | Competitors Cited? |
|---|---|---|---|---|---|
| [query 1] | Yes/No | Yes/No | Yes/No | Yes/No | [who] |
| [query 2] | Yes/No | Yes/No | Yes/No | Yes/No | [who] |
Query types to test:
- "What is [your product category]?"
- "Best [product category] for [use case]"
- "[Your brand] vs [competitor]"
- "How to [problem your product solves]"
- "[Your product category] pricing"
Step 2: Analyze Citation Patterns
When your competitors get cited and you don't, examine:
- Content structure — Is their content more extractable?
- Authority signals — Do they have more citations, stats, expert quotes?
- Freshness — Is their content more recently updated?
- Schema markup — Do they have structured data you're missing?
- Third-party presence — Are they cited via Wikipedia, Reddit, review sites?
Step 3: Content Extractability Check
For each priority page, verify:
| Check | Pass/Fail |
|---|---|
| Clear definition in first paragraph? | |
| Self-contained answer blocks (work without surrounding context)? | |
| Statistics with sources cited? | |
| Comparison tables for "[X] vs [Y]" queries? | |
| FAQ section with natural-language questions? | |
| Schema markup (FAQ, HowTo, Article, Product)? | |
| Expert attribution (author name, credentials)? | |
| Recently updated (within 6 months)? | |
| Heading structure matches query patterns? | |
| AI bots allowed in robots.txt? |
Step 4: AI Bot Access Check
Verify your robots.txt allows AI crawlers. Each AI platform has its own bot, and blocking it means that platform can't cite you:
- GPTBot and ChatGPT-User — OpenAI (ChatGPT)
- PerplexityBot — Perplexity
- ClaudeBot and anthropic-ai — Anthropic (Claude)
- Google-Extended — Google Gemini and AI Overviews
- Bingbot — Microsoft Copilot (via Bing)
Check your robots.txt for Disallow rules targeting any of these. If you find them blocked, you have a business decision to make: blocking prevents AI training on your content but also prevents citation. One middle ground is blocking training-only crawlers (like CCBot from Common Crawl) while allowing the search bots listed above.
See references/platform-ranking-factors.md for the full robots.txt configuration.
Optimization Strategy
The Three Pillars
1. Structure (make it extractable)
2. Authority (make it citable)
3. Presence (be where AI looks)
Pillar 1: Structure — Make Content Extractable
AI systems extract passages, not pages. Every key claim should work as a standalone statement.
Content block patterns:
- Definition blocks for "What is X?" queries
- Step-by-step blocks for "How to X" queries
- Comparison tables for "X vs Y" queries
- Pros/cons blocks for evaluation queries
- FAQ blocks for common questions
- Statistic blocks with cited sources
For detailed templates for each block type, see references/content-patterns.md.
Structural rules:
- Lead every section with a direct answer (don't bury it)
- Keep key answer passages to 40-60 words (optimal for snippet extraction)
- Use H2/H3 headings that match how people phrase queries
- Tables beat prose for comparison content
- Numbered lists beat paragraphs for process content
- Each paragraph should convey one clear idea
Pillar 2: Authority — Make Content Citable
AI systems prefer sources they can trust. Build citation-worthiness.
The Princeton GEO research (KDD 2024, studied across Perplexity.ai) ranked 9 optimization methods:
| Method | Visibility Boost | How to Apply |
|---|---|---|
| Cite sources | +40% | Add authoritative references with links |
| Add statistics | +37% | Include specific numbers with sources |
| Add quotations | +30% | Expert quotes with name and title |
| Authoritative tone | +25% | Write with demonstrated expertise |
| Improve clarity | +20% | Simplify complex concepts |
| Technical terms | +18% | Use domain-specific terminology |
| Unique vocabulary | +15% | Increase word diversity |
| Fluency optimization | +15-30% | Improve readability and flow |
| -10% | Actively hurts AI visibility |
Best combination: Fluency + Statistics = maximum boost. Low-ranking sites benefit even more — up to 115% visibility increase with citations.
Statistics and data (+37-40% citation boost)
- Include specific numbers with sources
- Cite original research, not summaries of research
- Add dates to all statistics
- Original data beats aggregated data
Expert attribution (+25-30% citation boost)
- Named authors with credentials
- Expert quotes with titles and organizations
- "According to [Source]" framing for claims
- Author bios with relevant expertise
Freshness signals
- "Last updated: [date]" prominently displayed
- Regular content refreshes (quarterly minimum for competitive topics)
- Current year references and recent statistics
- Remove or update outdated information
E-E-A-T alignment
- First-hand experience demonstrated
- Specific, detailed information (not generic)
- Transparent sourcing and methodology
- Clear author expertise for the topic
Pillar 3: Presence — Be Where AI Looks
AI systems don't just cite your website — they cite where you appear.
Third-party sources matter more than your own site:
- Wikipedia mentions (7.8% of all ChatGPT citations)
- Reddit discussions (1.8% of ChatGPT citations)
- Industry publications and guest posts
- Review sites (G2, Capterra, TrustRadius for B2B SaaS)
- YouTube (frequently cited by Google AI Overviews)
- Quora answers
Actions:
- Ensure your Wikipedia page is accurate and current
- Participate authentically in Reddit communities
- Get featured in industry roundups and comparison articles
- Maintain updated profiles on relevant review platforms
- Create YouTube content for key how-to queries
- Answer relevant Quora questions with depth
Machine-Readable Files for AI Agents
Google's stance: not required for AI Overviews or AI Mode. Their guide explicitly says you don't need new markup, AI files, or markdown to appear in generative AI search.
Why include them anyway: non-Google AI engines (ChatGPT, Claude, Perplexity) and autonomous buying agents do reward extractable structure. The files below help with those engines without harming Google.
AI agents aren't just answering questions — they're becoming buyers. When an AI agent evaluates tools on behalf of a user, it needs structured, parseable information. If your pricing is locked in a JavaScript-rendered page or a "contact sales" wall, agents will skip you and recommend competitors whose information they can actually read.
Add these machine-readable files to your site root:
/pricing.md or /pricing.txt — Structured pricing data for AI agents
# Pricing — [Your Product Name]
## Free
- Price: $0/month
- Limits: 100 emails/month, 1 user
- Features: Basic templates, API access
## Pro
- Price: $29/month (billed annually) | $35/month (billed monthly)
- Limits: 10,000 emails/month, 5 users
- Features: Custom domains, analytics, priority support
## Enterprise
- Price: Custom — contact sales@example.com
- Limits: Unlimited emails, unlimited users
- Features: SSO, SLA, dedicated account manager
Why this matters now:
- AI agents increasingly compare products programmatically before a human ever visits your site
- Opaque pricing gets filtered out of AI-mediated buying journeys
- A simple markdown file is trivially parseable by any LLM — no rendering, no JavaScript, no login walls
- Same principle as
robots.txt(for crawlers),llms.txt(for AI context), andAGENTS.md(for agent capabilities)
Best practices:
- Use consistent units (monthly vs. annual, per-seat vs. flat)
- Include specific limits and thresholds, not just feature names
- List what's included at each tier, not just what's different
- Keep it updated — stale pricing is worse than no file
- Link to it from your sitemap and main pricing page
/llms.txt — Context file for AI systems (see llmstxt.org)
If you don't have one yet, add an llms.txt that gives AI systems a quick overview of what your product does, who it's for, and links to key pages (including your pricing).
/okf/ — Open Knowledge Format bundle (Google-backed, v0.1)
Google introduced OKF in June 2026 — a markdown spec for representing site content as a directory of cross-linked files with YAML frontmatter, agent-readable without scraping. Built primarily for data-team catalog metadata; the site-readable-by-agents repurposing was popularized by Suganthan Mohanadasan. No confirmed AI-search ranking signal today — treat it as protocol-layer registration like early schema.org. For the full breakdown, implementation paths (free generator, WordPress plugin, by-hand), hosting guidance, and when to skip, see references/okf.md.
Schema Markup for AI
Structured data helps AI systems understand your content. Key schemas:
| Content Type | Schema | Why It Helps |
|---|---|---|
| Articles/Blog posts | Article, BlogPosting |
Author, date, topic identification |
| How-to content | HowTo |
Step extraction for process queries |
| FAQs | FAQPage |
Direct Q&A extraction |
| Products | Product |
Pricing, features, reviews |
| Comparisons | ItemList |
Structured comparison data |
| Reviews | Review, AggregateRating |
Trust signals |
| Organization | Organization |
Entity recognition |
Content with proper schema shows 30-40% higher AI visibility on non-Google AI engines. Google's note: structured data is "not required for generative AI search" but is recommended for overall SEO strategy. For implementation, use the schema skill.
Agentic Experiences
Beyond AI search engines summarizing content, autonomous agents are starting to access sites directly — clicking, reading, comparing, even buying on behalf of users. Google's guide flags this as an emerging category to plan for.
How agents access your site:
- Visual rendering — they screenshot/read the page like a user would
- DOM inspection — they parse the page's HTML structure
- Accessibility tree — they rely on the same semantic information assistive tech uses (labels, roles, landmarks, headings)
What to do:
- Render meaningful content without heavy JS gymnastics — if the page is blank until 4 frameworks finish loading, agents see blank
- Semantic HTML — use
<main>,<nav>,<article>,<button>, proper heading hierarchy,alttext on images - Clean accessibility tree — every interactive element labelled; ARIA used correctly (or not at all when native HTML suffices)
- Stable selectors / predictable layouts — agents struggle with sites that re-render every interaction
- Visible pricing, specs, contact info — anything an agent would need to make a buying recommendation should be on a public, indexable page (this is where
/pricing.mdand similar files help)
Emerging — Universal Commerce Protocol (UCP): Google references UCP as a forthcoming protocol that will give agents standardized hooks for commerce interactions (catalog discovery, pricing, checkout). Watch for adoption; for now, the structural recommendations above are the precursor.
For ecom and local business specifically, Google highlights:
- Merchant Center feeds + Google Business Profile for product/service visibility in AI Search
- Business Agent for conversational customer engagement (where applicable)
Content Types That Get Cited Most
Not all content is equally citable. Prioritize these formats:
| Content Type | Citation Share | Why AI Cites It |
|---|---|---|
| Comparison articles | ~33% | Structured, balanced, high-intent |
| Definitive guides | ~15% | Comprehensive, authoritative |
| Original research/data | ~12% | Unique, citable statistics |
| Best-of/listicles | ~10% | Clear structure, entity-rich |
| Product pages | ~10% | Specific details AI can extract |
| How-to guides | ~8% | Step-by-step structure |
| Opinion/analysis | ~10% | Expert perspective, quotable |
Underperformers for AI citation:
- Generic blog posts without structure
- Thin product pages with marketing fluff
- Gated content (AI can't access it)
- Content without dates or author attribution
- PDF-only content (harder for AI to parse)
Citation ≠ recommendation. Getting cited means your content was useful to consult; getting recommended — onto the buyer's actual shortlist — is governed by web-wide consensus (reviews, forums, analysts, press) and is largely independent of your own content. Self-promotional "best [category]" listicles can even backfire for emerging brands: in one 100-query B2B study, 69% of the AI Overview citations that self-promotional listicles earned came in answers that recommended competitors instead of the publishing brand. See references/citations-vs-recommendations.md for the visibility ladder (retrieved → cited → mentioned → recommended), stage-dependent buyer's-guide strategy, what earns recommendations, and the attribution blind spot.
Monitoring AI Visibility
What to Track
| Metric | What It Measures | How to Check |
|---|---|---|
| AI Overview presence | Do AI Overviews appear for your queries? | Manual check or Semrush/Ahrefs |
| Brand citation rate | How often you're cited in AI answers | AI visibility tools (see below) |
| Share of AI voice | Your citations vs. competitors | Peec AI, Otterly, ZipTie |
| Citation sentiment | How AI describes your brand | Manual review + monitoring tools |
| Recommendation rate | Whether you're on the shortlist, not just cited (see citations-vs-recommendations.md) | Prompt tracking + mention framing |
| Source attribution | Which of your pages get cited | Track referral traffic from AI sources |
AI Visibility Monitoring Tools
| Tool | Coverage | Best For |
|---|---|---|
| Otterly AI | ChatGPT, Perplexity, Google AI Overviews | Share of AI voice tracking |
| Peec AI | ChatGPT, Gemini, Perplexity, Claude, Copilot+ | Multi-platform monitoring at scale |
| ZipTie | Google AI Overviews, ChatGPT, Perplexity | Brand mention + sentiment tracking |
| LLMrefs | ChatGPT, Perplexity, AI Overviews, Gemini | SEO keyword → AI visibility mapping |
DIY Monitoring (No Tools)
Monthly manual check:
- Pick your top 20 queries
- Run each through ChatGPT, Perplexity, and Google
- Record: Are you cited? Who is? What page?
- Log in a spreadsheet, track month-over-month
Search Console expectations
Google's guide is explicit: there is no AI-specific Search Console reporting. AI Overviews and AI Mode use core Search ranking, so the standard Search Console reports (Performance, Coverage, Core Web Vitals) are still what you measure with for Google. The third-party tools above are the only way to see cross-platform AI citation behavior.
What NOT to Do
Google's guide calls these out explicitly — they hurt across both traditional Search and AI features.
- Write separate content "for AI". Same content should serve people and AI. Writing variants targeted at AI systems risks the scaled content abuse spam policy — Google's words.
- Chunk pages into AI-bait fragments. Google's guide is direct: "Don't break your content into tiny pieces for AI to better understand it." Use normal paragraph + heading structure.
- Generate at scale for ranking manipulation. AI-generated content is fine if it meets Search Essentials and spam policies. Mass-producing thin variations does not.
- Pursue inauthentic mentions. Don't fabricate citations or bulk-spam Reddit/Wikipedia for AI visibility. Real participation only.
- Block AI crawlers if you want citation. Blocking GPTBot, PerplexityBot, ClaudeBot, Google-Extended means those engines literally cannot cite you. Block training-only crawlers (CCBot) if you must, not the search-and-cite ones.
- Hide your main content behind JS that doesn't render. Both core Search and AI agents need to see your content; JS-only rendering loses both audiences.
- Skip E-E-A-T fundamentals. Author identity, first-hand experience, expertise signals, transparent sourcing — Google's guide leans heavily on these for AI features.
AI SEO by Content Type
For tactical guidance on SaaS product pages, blog content, comparison/alternative pages, documentation, and local/ecom (Google's emphasis on Merchant Center + Business Profile), see references/content-types.md.
Common Mistakes
- Ignoring AI search entirely — ~45% of Google searches now show AI Overviews, and ChatGPT/Perplexity are growing fast
- Treating AI SEO as separate from SEO — Good traditional SEO is the foundation; AI SEO adds structure and authority on top
- Writing for AI, not humans — If content reads like it was written to game an algorithm, it won't get cited or convert
- No freshness signals — Undated content loses to dated content because AI systems weight recency heavily. Show when content was last updated
- Gating all content — AI can't access gated content. Keep your most authoritative content open
- Ignoring third-party presence — You may get more AI citations from a Wikipedia mention than from your own blog
- No structured data — Schema markup gives AI systems structured context about your content
- Keyword stuffing — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study)
- Hiding pricing behind "contact sales" or JS-rendered pages — AI agents evaluating your product on behalf of buyers can't parse what they can't read. Add a
/pricing.mdfile - Blocking AI bots — If GPTBot, PerplexityBot, or ClaudeBot are blocked in robots.txt, those platforms can't cite you
- Generic content without data — "We're the best" won't get cited. "Our customers see 3x improvement in [metric]" will
- Forgetting to monitor — You can't improve what you don't measure. Check AI visibility monthly at minimum
Tool Integrations
For implementation, see the tools registry.
| Tool | Use For |
|---|---|
semrush |
AI Overview tracking, keyword research, content gap analysis |
ahrefs |
Backlink analysis, content explorer, AI Overview data |
gsc |
Search Console performance data, query tracking |
ga4 |
Referral traffic from AI sources |
Task-Specific Questions
- What are your top 10-20 most important queries?
- Have you checked if AI answers exist for those queries today?
- Do you have structured data (schema markup) on your site?
- What content types do you publish? (Blog, docs, comparisons, etc.)
- Are competitors being cited by AI where you're not?
- Do you have a Wikipedia page or presence on review sites?
Related Skills
- seo-audit: For traditional technical and on-page SEO audits
- schema: For implementing structured data that helps AI understand your content
- content-strategy: For planning what content to create
- competitors: For building comparison pages that get cited
- programmatic-seo: For building SEO pages at scale
- copywriting: For writing content that's both human-readable and AI-extractable
当前镜像保留 8 个文件,共 74.5 KB。点击文件名可查看加搜服务器上的原始内容。
| 文件 | 大小 | 内容指纹 |
|---|---|---|
| SKILL.md | 27,054 B | 009333fb0cd4… |
| UPSTREAM_LICENSE.txt | 1,069 B | b70d71e24e40… |
| evals/evals.json | 8,748 B | 7fab31facaf4… |
| references/citations-vs-recommendations.md | 9,091 B | 88016418b43b… |
| references/content-patterns.md | 10,432 B | 8adcfcc020a3… |
| references/content-types.md | 2,716 B | 9ad0a871f866… |
| references/okf.md | 5,952 B | 4abcab5b8ee9… |
| references/platform-ranking-factors.md | 11,182 B | ca3fb8c09fec… |
评价将按 Skill 与版本归档,帮助营销人了解真实任务中的使用体验。敬请期待。
来源与版本声明
本页面由加搜科技整理业务说明并托管安装文件。原始 Skill 来源渠道:GitHub MarketingSkills; 原始项目名称:ai-seo; 固定版本:67264763cb10; 许可证:MIT。技能包内保留完整出处和许可证说明。
各 Agent 能力说明参考对应官方文档。页面不提供外部跳转。
INSTALL
三种安装方式
GEO AI 搜索优化 Skill v1.0.0,ZIP 带 SHA256 校验
默认做法是把提示词复制给 AI Agent,让它自己下载并安装。提示词里已经写清要用完整 ZIP、装完报告目录、并先跑一个小任务验证。
METHOD 01 · 交给 AI 自己装
复制提示词
适合大多数情况。Agent 会下载 ZIP、解压、放到正确目录,并在缺少权限时告诉你需要手工做哪一步。
请帮我把「GEO AI 搜索优化 Skill」安装到我正在使用的 AI Agent。 1. 下载完整 Skill ZIP:https://www.vibemarketing.work/packages/skill-geo-ai-search/1.0.0/skill-geo-ai-search.zip 注意:网页 HTML 不能当作 Skill 文件安装,必须使用 ZIP 里的完整文件。 2. 解压后保留 SKILL.md 及全部配套文件,按你所用 Agent 的 Skill 目录规则安装。 3. 安装完成后告诉我实际安装目录。 4. 用一个只读小任务验证 Skill 已被识别。 5. 如果你没有联网、下载或写目录权限,请直接告诉我哪几步需要我手工完成。 参考:原始 SKILL.md https://www.vibemarketing.work/raw/skill-geo-ai-search/SKILL.md;安装指南 https://www.vibemarketing.work/agent-install/skill-geo-ai-search.md
METHOD 02 · 自己下载
下载完整 ZIP
包内含 SKILL.md 与全部配套文件,附 manifest.json 与 SHA256 校验值,可离线安装与版本冻结。
METHOD 03 · 手动放目录
手动安装
解压 ZIP 后,按所用 Agent 的目录规则放入:
- WorkBuddy
技能 → 添加技能 → 上传技能 → 选择本地技能包 - OpenClaw
openclaw skills install ./skill-geo-ai-search --as geo_ai_search_skill - Hermes Agent
mkdir -p ~/.hermes/skills && cp -R ./skill-geo-ai-search ~/.hermes/skills/ - Codex
mkdir -p ~/.codex/skills && cp -R ./skill-geo-ai-search ~/.codex/skills/ - Claude Code
mkdir -p ~/.claude/skills && cp -R ./skill-geo-ai-search ~/.claude/skills/ - TRAE
在 Skills 设置中导入包含 SKILL.md 的 skill-geo-ai-search 目录;项目级 Skill 可放入 .agents/skills/skill-geo-ai-search - ZCode
mkdir -p ~/.zcode/skills && cp -R ./skill-geo-ai-search ~/.zcode/skills/
HTML 业务页面不能直接当作 Skill 文件安装。AI 需要下载完整 ZIP 并保留配套文件。
BY AGENT
适配的 AI Agent
7 个 Agent 里,8 项能力决定了差异
同一个 Skill,换个 AI 做法就不一样。点进去能看到它在这 8 步里能直接跑通几步、哪几步得你自己补、装完先跑什么验证。
- WorkBuddy GEO AI 搜索优化 Skill 中文办公、本地资料和企业协作
- OpenClaw GEO AI 搜索优化 Skill 本地工作区、目录化 Skill、命令和批处理
- Hermes Agent GEO AI 搜索优化 Skill 长任务、消息入口和阶段进度
- Codex GEO AI 搜索优化 Skill 本地文件、数据、代码和正式交付物
- Claude Code GEO AI 搜索优化 Skill 项目上下文、文件、终端和 MCP
- TRAE GEO AI 搜索优化 Skill 营销工作与网站、落地页和程序化 SEO
- ZCode GEO AI 搜索优化 Skill 长上下文、长任务、项目文件和远程跟进
FURTHER READING
GEO AI 搜索优化 Skill 相关的实操文章
别人做同类任务时踩过的坑和总结,动手前后都值得翻一下。
创业者要不要装 Workflow Orchestrator?5分钟判断
给出工作流编排的最短操作路径,用一个真实感示例演示如何从搜索词反推内容选题,并标出能形成可复用模板的关键设置。
一次讲透内容日历:输入什么、输出什么、怎样提高引用率
这是一份偏实战的内容日历配置说明。先用小样本完成“检查上线前最容易漏掉的细节”,再逐步扩到批量任务;同时设置人工抽检、来源记录和失败兜底,降低内容风格高度同质化带来的波动。文末附一组可复制参数,便于继续提高引用率。
Content Brief Builder × AI搜索:从输入到发布的完整工作流
一页看懂内容简报。包含适用场景、最小输入和生成能直接交付的客户方案的示例。
研究人员实测数据叙事:一轮完成,目标是让协作更顺畅
给出数据叙事的最短操作路径,用一个真实感示例演示如何生成能直接交付的客户方案,并标出能让协作更顺畅的关键设置。
深度研究 Skill 怎么用:把会议录音变成行动清单
GEO在AI搜索出现了新的内容机会,这篇只整理值得测试的三个方向和两个暂缓项。
Content Brief Builder 入门指南|给研究人员的第一套配置
一页看懂内容简报。包含适用场景、最小输入和为新品做一周内容排期的示例。
以上文章正在编辑中,上线后可直接点击阅读。即将上线,敬请期待。
搭配使用
出海本地化 Skill、出海本地化翻译 Skill、实体 SEO Skill、搜索结果页特性优化 Skill、团队效能与会议洞察 Skill、SEO 关键词研究 Skill
按这个 Skill 的产出能不能直接被下一个 Skill 用上来推荐,不是固定名单。多数情况下按顺序跑完一组,比单独用一个效果更好。
出海本地化 Skill
规划多语言网站、国际 SEO、本地关键词、URL、hreflang 与市场适配。
出海本地化翻译 Skill
把多语言翻译任务拆解成需求文档、术语表和质量审查清单,控制出海内容的本地化翻译质量。
实体 SEO Skill
把零散的品牌信息整理成统一的结构化标记,让搜索引擎和 AI 明确识别品牌与作者身份。
搜索结果页特性优化 Skill
把目标关键词的 Google 搜索结果页拆解为具体特性,输出各项特性的获取要求与结构化数据对照表。
团队效能与会议洞察 Skill
把会议录音文稿和团队 OKR 数据变成带有截止时间的行动清单,以及区分 A/B/C 级员工的绩效排行榜。
SEO 关键词研究 Skill
发现、筛选和聚类关键词,构建与用户意图和业务价值对应的主题地图。
- 01
出海本地化 Skill
这个 Skill 产出的marketing_plan,正好是它需要的输入,可以直接接着跑
- 02
出海本地化翻译 Skill
这个 Skill 产出的marketing_plan,正好是它需要的输入,可以直接接着跑
- 03
实体 SEO Skill
解决同一类营销任务,可以按需要挑一个或组合用
- 04
搜索结果页特性优化 Skill
解决同一类营销任务,可以按需要挑一个或组合用
- 05
团队效能与会议洞察 Skill
交付物类型相同,可以互相替换,也可以合并成一份成果
- 06
SEO 关键词研究 Skill
交付物类型相同,可以互相替换,也可以合并成一份成果