$22
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionai-seoExecute the skills CLI command in your project's root directory to begin installation:
Fetches ai-seo from coreyhaines31/marketingskills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ai-seo. Access via /ai-seo in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
19.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
19.2K
stars
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.
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md 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):
| 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.
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:
Before optimizing, assess your current AI search presence.
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:
When your competitors get cited and you don't, examine:
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? |
Verify your robots.txt allows AI crawlers. Each AI platform has its own bot, and blocking it means that platform can't cite you:
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.
1. Structure (make it extractable)
2. Authority (make it citable)
3. Presence (be where AI looks)
AI systems extract passages, not pages. Every key claim should work as a standalone statement.
Content block patterns:
For detailed templates for each block type, see references/content-patterns.md.
Structural rules:
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)
Expert attribution (+25-30% citation boost)
Freshness signals
E-E-A-T alignment
AI systems don't just cite your website — they cite where you appear.
Third-party sources matter more than your own site:
Actions:
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 [email protected]
- Limits: Unlimited emails, unlimited users
- Features: SSO, SLA, dedicated account manager
Why this matters now:
robots.txt (for crawlers), llms.txt (for AI context), and AGENTS.md (for agent capabilities)Best practices:
/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).
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. For implementation, use the schema-markup skill.
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:
| 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 |
| Source attribution | Which of your pages get cited | Track referral traffic from AI sources |
| 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 |
Monthly manual check:
Goal: Get cited in "What is [category]?" and "Best [category]" queries.
Optimize:
/pricing.md file so AI agents can parse your plans without rendering your page (see "Machine-Readable Files" above)Goal: Get cited as an authoritative source on topics in your space.
Optimize:
Goal: Get cited in "[X] vs [Y]" and "Best [X] alternatives" queries.
Optimize:
Goal: Get cited in "How to [X] with [your product]" queries.
Optimize:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
coreyhaines31/marketingskills
laguagu/claude-code-nextjs-skills
kostja94/marketing-skills
kostja94/marketing-skills
sickn33/antigravity-awesome-skills
mindrally/skills
We added ai-seo from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
ai-seo reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in ai-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: ai-seo is focused, and the summary matches what you get after install.
ai-seo has been reliable in day-to-day use. Documentation quality is above average for community skills.
ai-seo reduced setup friction for our internal harness; good balance of opinion and flexibility.
ai-seo fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added ai-seo from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for ai-seo matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: ai-seo is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 65