Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Optimize content to rank in AI search engines (AI Overviews, Perplexity, ChatGPT) via generative engine optimization (GEO), citability audits, and schema markup.
$ npx skills add borghei/Claude-Skills --skill ai-seo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills ai-seo --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/ai-seo .claude/skills/ai-seo && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ai-seo" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/ai-seo into .claude/skills/ai-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-seo", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/marketing/ai-seoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill ai-seo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills ai-seo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/ai-seo .agents/skills/ai-seo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ai-seo" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/ai-seo into .agents/skills/ai-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-seo", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill ai-seo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills ai-seo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/ai-seo .cursor/skills/ai-seo && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ai-seo" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/ai-seo into .cursor/skills/ai-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-seo", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path marketing/ai-seo--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill ai-seo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills ai-seo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/ai-seo .gemini/skills/ai-seo && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ai-seo" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/ai-seo into .gemini/skills/ai-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-seo", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills ai-seoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill ai-seo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/ai-seo .github/skills/ai-seo && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ai-seo" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/ai-seo into .github/skills/ai-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-seo", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill ai-seo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills ai-seo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/ai-seo .opencode/skills/ai-seo && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ai-seo" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/ai-seo into .opencode/skills/ai-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ai-seo", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ai-seoOptimize content to rank in AI search engines (AI Overviews, Perplexity, ChatGPT) via generative engine optimization (GEO), citability audits, and schema markup.
AI SEO is an agent skill from borghei/Claude-Skills. Optimize content to rank in AI search engines (AI Overviews, Perplexity, ChatGPT) via generative engine optimization (GEO), citability audits, and schema markup. Use when optimizing for AI search, generative search, or LLM visibility.
Its SKILL.md is about 7.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/content_scorer.py`, `scripts/keyword_analyzer.py` and `scripts/serp_simulator.py`).
It sits in Marketing & SEO, covering AI search optimization. It works with OpenAI and Perplexity. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
schema.orgAlso links to:
developers.google.comsupport.google.comdevelopers.openai.comsupport.claude.comdocs.perplexity.aiFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
AI SEO loads about 7.3k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 3,354 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 3,354 words, ~7,258 tokens.
.claude/skills/ai-seo/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Generative engine optimization (GEO) for getting cited by AI search platforms — not just ranked in traditional results.
AI SEO, generative engine optimization, GEO, AI overviews, Google SGE, ChatGPT citations, Perplexity SEO, Claude citations, AI search optimization, semantic search, entity optimization, LLM visibility, AI-generated answers, structured data, schema markup, content extractability, AI citability, GPTBot, PerplexityBot, ClaudeBot, answer engine optimization
Before optimizing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Traditional SEO gets your page ranked. AI SEO gets your content cited. These are different optimization targets.
| Dimension | Traditional SEO | AI SEO |
|---|---|---|
| Goal | Rank on page 1 | Get cited in AI-generated answers |
| Success metric | Click-through rate | Citation frequency |
| Content priority | Keyword density | Answer extractability |
| Authority signal | Backlinks + domain authority | Backlinks + answer quality + attribution |
| User interaction | User clicks your link | AI extracts your answer; user may never visit |
| Content format | Long-form comprehensive | Self-contained extractable blocks |
| Optimization unit | The page | The paragraph or section |
AI systems pull content in chunks. They find the paragraph, list, or definition that directly answers a query and extract it. Your content must be structured so answers are self-contained.
Extractability requirements:
Anti-patterns that kill extractability:
AI systems do not just extract the most relevant answer — they extract the most credible one.
Authority signals in the AI era:
AI systems must be able to find and index your content.
Technical requirements:
Step 1: Bot Access Verification
Check robots.txt for AI crawler permissions:
# Search / retrieval crawlers — blocking these removes you from that platform's AI answers:
Googlebot # Google Search, incl. AI Overviews and AI Mode
OAI-SearchBot # ChatGPT search
Claude-SearchBot # Claude search
PerplexityBot # Perplexity search
# Training crawlers — blocking these does NOT remove you from AI search answers:
GPTBot # OpenAI model training
ClaudeBot # Anthropic model training
Google-Extended # Gemini training + grounding (not AI Overviews / AI Mode)
Applebot-Extended # Apple Intelligence trainingIf a search/retrieval crawler is blocked, that is the single highest priority fix — zero visibility on that platform until resolved. A blocked training crawler is a policy choice, not a visibility bug. See Bot Access Configuration for the full matrix.
Step 2: Citation Testing
Test top 10 target queries on each platform:
| Platform | How to Test | What to Record |
|---|---|---|
| Perplexity | Search at perplexity.ai, check Sources panel | Cited? Which competitors cited? Content format winning? |
| ChatGPT | Web browsing enabled, check citations | Same |
| Google AI Overviews | Google query, check AI Overview panel | Same |
| Microsoft Copilot | Search at copilot.microsoft.com, check source cards | Same |
| Claude | Web search enabled queries | Same |
Step 3: Content Extractability Scoring
Score each key page (0-7):
Interpretation: 0-3 = needs major restructuring. 4-5 = good baseline. 6-7 = strong.
Step 4: Competitive Citation Analysis
For each target query, document:
Step 1: Lead with the Answer
The first paragraph must contain the core answer to the target query. No preamble, no context-setting, no "In today's landscape..." openers.
Step 2: Structure Self-Contained Sections
Every H2 section must be answerable as a standalone excerpt:
Step 3: Add Extractable Content Blocks
Insert 2-3 of these per key page:
Step 4: Replace Vague with Specific
Find and replace every vague claim:
Step 5: Add Schema Markup
Implement JSON-LD in the page head:
| Content Type | Schema | Impact (as of September 2026) |
|---|---|---|
| Articles and posts | Article | Medium — Article rich result + clear author/date signals |
| Product pages | Product (+ Review snippet) | Medium — Product rich results; product comparison queries |
| Company pages | Organization | Medium — entity authority, logo/knowledge panel signals |
| All pages | BreadcrumbList | Low-Medium — Breadcrumb rich result, site hierarchy |
| Author pages | Person / ProfilePage | Low-Medium — author credibility signal |
| FAQ sections | FAQPage | Low — FAQ rich results removed from Google Search (May 2026); valid vocabulary, no Google search feature |
| Step-by-step guides | HowTo | Low — HowTo rich results removed from Google Search (2023); no Google search feature |
The visible on-page structure (Q&A headings, numbered steps) is what AI systems extract. Google states no special schema is required for AI features — do not sell FAQPage/HowTo markup as an AI-citation lever.
Step 1: Define Your Entity
Ensure your brand exists as a recognized entity across the web:
Step 2: Build Entity Associations
Connect your entity to relevant topics:
Step 3: Strengthen the Citation Chain
Create a network of credible references:
**[Term]** is [concise definition in 1-2 sentences]. [One sentence of context
explaining why it matters or how it differs from related concepts].Place within the first 200 words. No hedging, no preamble.
Requirements for AI extraction:
Two-column or multi-column tables with clean headers:
| Dimension | Option A | Option B |
|-----------|----------|----------|
| Price | $X/mo | $Y/mo |
| Key Feature | Description | Description |
| Best For | Use case | Use case |Explicit Q&A pairs. Questions should match natural language queries:
### What is [topic]?
[Direct answer in 1-2 sentences.]
### How does [topic] work?
[Step-by-step explanation.]The visible Q&A structure is what matters for extraction. FAQPage markup is optional — Google no longer shows FAQ rich results (removed May 2026).
According to [Source Name] ([Year]), X% of [population] [finding].Complete attribution is critical. Unattributed statistics get deprioritized because AI cannot verify the source.
"[Quote]" — [Name], [Role] at [Organization]Named experts with credentials produce citable units AI systems pick up.
Google states that no special schema.org markup is needed to appear in AI Overviews or AI Mode (AI features and your website). Prioritize schema that still produces Google rich results or clarifies entities (Article, Product, Organization, BreadcrumbList); treat FAQPage and HowTo as optional vocabulary.
FAQPage Schema (optional — FAQ rich results removed from Google Search in May 2026):
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is [topic]?",
"acceptedAnswer": {
"@type": "Answer",
"text": "[Direct answer]"
}
}
]
}HowTo Schema (optional — HowTo rich results removed from Google Search in 2023):
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to [do thing]",
"step": [
{
"@type": "HowToStep",
"name": "Step name",
"text": "Step description"
}
]
}Article Schema (still eligible for rich results; establishes author and date signals):
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Title",
"author": {
"@type": "Person",
"name": "Author Name",
"url": "https://author-page"
},
"datePublished": "2026-01-15",
"dateModified": "2026-03-01"
}Validate all schema at schema.org/validator before deployment.
The major AI vendors now split crawling by purpose, so search visibility and training can be controlled separately.
| Vendor | User agent | Purpose | Blocking it means | Honors robots.txt |
|---|---|---|---|---|
| OpenAI | GPTBot | Model training | Content excluded from future training | Yes |
| OpenAI | OAI-SearchBot | ChatGPT search index | Not surfaced/cited in ChatGPT search answers | Yes |
| OpenAI | ChatGPT-User | Fetches a page when a user's request needs it | User-initiated; OpenAI says robots.txt rules "may not apply" | Not guaranteed |
| Anthropic | ClaudeBot | Model training | Future content excluded from training | Yes |
| Anthropic | Claude-SearchBot | Claude search index | Reduced visibility in Claude search answers | Yes |
| Anthropic | Claude-User | Fetches a page when a Claude user asks | Claude cannot retrieve your page for users | Yes |
| Perplexity | PerplexityBot | Perplexity search index | Not surfaced/linked in Perplexity answers | Yes |
| Perplexity | Perplexity-User | Fetches a page for a user's question | Perplexity says this fetcher generally ignores robots.txt | No |
Googlebot | Google Search, including AI Overviews and AI Mode | Removes you from Google Search entirely | Yes | |
Google-Extended (robots.txt token, not a separate crawler) | Gemini training and grounding in some Google systems; also limits training of the models behind Search generative AI features | Does not remove you from Google Search, ranking, AI Overviews or AI Mode | Yes |
Sources: OpenAI crawlers, Anthropic crawlers, Perplexity crawlers, Google common crawlers.
Google AI Overviews / AI Mode opt-out: Google-Extended does not control appearance in them — they are served from Googlebot's index. Your options (as of September 2026):
nosnippet, data-nosnippet, max-snippet limit what can be shown, but also limit how the page appears in regular Search results.noindex — removes the page from Google Search entirely.# Allow AI search / retrieval crawlers (visibility)
User-agent: OAI-SearchBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: PerplexityBot
Allow: /
# Training crawlers — Allow or Disallow per your content policy;
# this choice does not affect AI search citation
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: Google-Extended
Allow: /
User-agent: Applebot-Extended
Allow: /Allowing AI citation while blocking training is enforceable for OpenAI, Anthropic, and Perplexity: allow the search crawler (OAI-SearchBot, Claude-SearchBot, PerplexityBot) and disallow the training crawler (GPTBot, ClaudeBot). Blocking one does not block the other.
Google works differently: Google-Extended limits training and Gemini grounding but not appearance in AI Overviews or AI Mode. To keep regular Search visibility but leave AI Overviews / AI Mode, use the Search Console Search generative AI control (as of September 2026); snippet controls and noindex also work but cost regular Search presentation.
Recommendation: Always allow the search/retrieval crawlers if you want AI citation visibility; decide on training crawlers as a separate content-licensing policy.
Test top 10 target queries on Perplexity and ChatGPT:
There is no "AI Overviews" search-type filter in the Performance report. Clicks and impressions from AI Overviews and AI Mode are counted inside the standard Web search type, blended with regular results (AI features and your website).
As of September 2026, Search Console also has a dedicated Generative AI performance report (announced June 2026, rolled out to all sites by August 31, 2026; sites need enough impressions to see data) (announcement, help):
For clicks, use the Web search type in the Performance report plus landing-page analytics; AI-feature clicks cannot be isolated there.
| Signal | What to Check | Tool |
|---|---|---|
| Perplexity citations | Top 10 queries | Manual testing |
| ChatGPT citations | Top 10 queries | Manual testing |
| Google AI Overviews / AI Mode | Impressions (Generative AI report); clicks only blended into Web search type | Google Search Console |
| Copilot citations | Top 5 queries | Manual testing |
| AI bot crawl activity | Crawl frequency and pages | Server logs / Cloudflare |
| Competitor citations | Who is getting cited for your queries | Manual testing |
| Content freshness | Date signals on key pages | Content audit |
Diagnostic checklist when you lose a citation:
Optimize at the section level, not just the page level — AI extracts paragraphs and sections, not entire pages. Every H2 block should be independently citable.
Lead with the answer, always — The first 200 words determine whether AI systems find your content useful. Put the answer there.
Attribute everything — Unattributed statistics, unnamed experts, and sourceless claims reduce your citability. Name names.
Update quarterly — AI systems prefer recent content. Update publish dates and refresh data points every 90 days.
Build entity presence — The stronger your brand's entity recognition across the web, the more AI systems trust and cite you.
Do not choose between traditional SEO and AI SEO — They are complementary. Many optimization signals overlap. Run both.
Test on multiple platforms — A page cited on Perplexity may not be cited on ChatGPT. Optimize for the platforms your audience uses.
Monitor competitors monthly — Track who gets cited for your target queries and study what content patterns they use.
Avoid JavaScript-rendered content for key answers — AI crawlers may not execute JavaScript. Ensure important content is in the initial HTML.
Implement schema accurately, not as a hack — Article, Product, Organization, and BreadcrumbList markup that matches visible content helps entity understanding. Google says no special schema is required for AI features, and FAQ/HowTo rich results no longer display.
| Problem | Likely Cause | Fix |
|---|---|---|
| Content not cited despite high DA | Poor extractability — answers buried in prose | Restructure with definition blocks, numbered steps, and FAQ pairs in first 200 words |
| Cited on Perplexity but not ChatGPT | Different crawling and indexing pipelines per platform | Verify bot access for all AI crawlers; test rendering without JavaScript |
| AI Overview shows competitor instead | Competitor has more extractable, better-attributed content | Audit competitor's cited content format and match or exceed specificity |
| Citation dropped after site update | Page restructure broke the extraction pattern AI was using | Compare old vs new page structure; restore extractable blocks |
| OAI-SearchBot / PerplexityBot blocked in robots.txt unknowingly | CMS update or security plugin overwrote robots.txt | Audit robots.txt after every CMS or plugin update; set up monitoring |
| Schema markup present but no rich results | Missing required fields or content-markup mismatch | Validate with Google Rich Results Test; ensure schema matches visible page content |
| AI cites your data but not your brand | Missing entity signals — no Organization schema or sameAs links | Implement Organization schema with sameAs to Wikidata, LinkedIn, and social profiles |
In scope:
Out of scope:
Known limitations:
ChatGPT-User, Perplexity-User) may not honor robots.txt# Analyze content for AI citability signals
python scripts/content_scorer.py page.html --json
# Simulate how content might appear in AI search results
python scripts/serp_simulator.py --query "what is cloud cost optimization" --content page.md
# Analyze keyword opportunities for AI search visibility
python scripts/keyword_analyzer.py --keywords keywords.csv --json© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in marketing/ai-seo of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
AI SEO next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| AI SEO this skillborghei/Claude-Skills | 886 | — | ~7.3k | Automated safety check: Pass | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 9 repos | ~861 | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude | 11k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Fire Your SEO Agencyleopard627/fire-your-seo-agency | 708 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 538 | — | ~2.5k | Automated safety check: Pass | MIT |
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
leopard627/fire-your-seo-agency
SEO·AEO·GEO·LLMO·NEO(네이버) 다섯 레인을 진단하고 직접 구현하며, 인용되는 콘텐츠를 계속 생산하는 서브 블로그·콘텐츠 운영 파이프라인까지 세팅하는 스킬.
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
Ryze-AI-Adgent/open-seo-mcp-skills
Measure real AI-engine visibility — traffic from ChatGPT, Perplexity, Claude, Gemini and which pages they cite — from actual GA4 referral data, not prompt sampling.
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Works with
Categories
Optimize content to rank in AI search engines (AI Overviews, Perplexity, ChatGPT) via generative engine optimization (GEO), citability audits, and schema markup. AI SEO is an agent skill from borghei/Claude-Skills. Optimize content to rank in AI search engines (AI Overviews, Perplexity, ChatGPT) via generative engine optimization (GEO), citability audits, and schema markup.
AI SEO fits situations like: optimizing for AI search; generative search.
Run `npx skills add borghei/Claude-Skills --skill ai-seo -a claude-code`. Or copy the skill folder (marketing/ai-seo in borghei/Claude-Skills) into .claude/skills/ai-seo in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill ai-seo -a codex`. Or copy the skill folder (marketing/ai-seo in borghei/Claude-Skills) into .agents/skills/ai-seo in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill ai-seo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ai-seo, .gemini/skills/ai-seo, .github/skills/ai-seo and .opencode/skills/ai-seo in your project.
Going by SKILL.md and its folder, AI SEO needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
SKILL.md names 6 domains. In commands or code: schema.org; the agent is likely to contact it when it follows the instructions. As links in the text: developers.google.com, support.google.com, developers.openai.com, support.claude.com and docs.perplexity.ai. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
AI SEO is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 7.3k tokens (SKILL.md is roughly 29k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with AI SEO: Geo Fundamentals (wasp-lang/wasp, 19k stars), SEO Geo (ReScienceLab/opc-skills, 1.8k stars), GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars) and Fire Your SEO Agency (leopard627/fire-your-seo-agency, 708 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.