@clawhub-kostja94-afbe7d43b7
When the user wants to optimize heading structure (H1-H6), fix heading hierarchy, or improve content structure. Also use when the user mentions "H1," "headin...
--- name: heading-structure description: When the user wants to optimize heading structure (H1-H6), fix heading hierarchy, or improve content structure. Also use when the user mentions "H1," "heading," "heading hierarchy," "content structure," "H2," "H3," "heading tags," "heading SEO," "multiple H1," or "heading structure." For SEO workflow, use seo-strategy. metadata: version: 1.0.1 --- # SEO On-Page: Heading Structure Guides heading (H1-H6) optimization for SEO and content structure. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope (On-Page SEO) - **H1 tag**: One per page; clear headline; matches content; primary keyword near start - **Header tags (H1-H6)**: Logical hierarchy; keyword in headers; one idea per heading ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for target keywords. Identify: 1. **Page type**: Homepage, article, product, etc. 2. **Primary keyword**: Target search query 3. **Content outline**: Main sections and subsections ## Best Practices ### H1 | Principle | Guideline | |-----------|-----------| | **One per page** | Single H1 per page | | **Primary keyword** | Include target keyword naturally | | **Descriptive** | Clearly describe page content | | **Match intent** | Align with title tag and user intent | ### H2-H6 Hierarchy | Principle | Guideline | |-----------|-----------| | **Logical order** | H1 -> H2 -> H3; don't skip levels | | **One idea per heading** | Each heading = one topic | | **Scannable** | Headings should summarize section content | | **Keyword variation** | Use related keywords in subheadings | ### Structure ``` H1 (page title) -> H2 (section 1) -> H3 (subsection) -> H3 -> H2 (section 2) -> H3 -> H2 (section 3) ``` ## Common Issues | Issue | Fix | |-------|-----| | Multiple H1s | Use single H1; use H2 for other sections | | Skipped levels | Use H2 after H1, H3 after H2 | | Generic headings | Make descriptive; avoid "Introduction," "Conclusion" | | Keyword stuffing | Natural language; avoid forced keywords | ## Output Format - **H1** recommendation (with keyword) - **H2-H6** outline for content - **Hierarchy** check - **References**: [Google headings](https://developers.google.com/search/docs/appearance/title-link) ## Related Skills - **featured-snippet**: H2/H3 for snippet extraction; semantic HTML for list/table snippets - **page-metadata**: Hreflang, meta robots; metadata complements heading structure - **content-optimization**: H2 keyword placement, quantity, tables, lists; complements heading structure - **article-page-generator**: Article page H1-H3 structure, intro/body/conclusion - **title-tag**: H1 should align with title tag - **schema-markup**: Article schema uses headline (often H1) - **content-strategy**: Content outline informs headings
When the user wants to optimize for Featured Snippets, Position Zero, or snippet extraction. Also use when the user mentions "featured snippet," "position ze...
---
name: featured-snippet
description: When the user wants to optimize for Featured Snippets, Position Zero, or snippet extraction. Also use when the user mentions "featured snippet," "position zero," "snippet optimization," "answer box," "definition box," "list snippet," "table snippet," "paragraph snippet," "PAA optimization," or "win position zero." For schema, use schema-markup.
metadata:
version: 1.0.1
---
# SEO On-Page: Featured Snippet
Guides optimization for Featured Snippets (Position Zero)—direct answers displayed above organic results. Featured snippets appear on ~19% of queries; by 2025, AI Overviews replaced many, but snippet optimization still supports AI citation and PAA. See **serp-features** for full SERP context.
**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
## Scope
- **Featured Snippet formats**: Paragraph, list, table
- **Content structure**: Answer-first, H2/H3, semantic HTML
- **Query targeting**: How, what, why; positions 2–5 opportunity
- **AI Overviews**: Layered content for both snippets and AI citation
## Current Landscape (2025–2026)
- Featured snippets appear on ~19% of search queries
- AI Overviews replaced 83%+ of featured snippets in many regions; appear in ~47% of US searches
- When AI Overviews show, 83% of searches may end without clicks (**zero-click**)—goal shifts to **citation** as well as CTR. Featured Snippets also cause zero-click when the answer suffices. See **serp-features** for zero-click by feature.
- Position zero still captures ~35% of clicks when snippets appear; pages with snippets see ~8% higher organic CTR
- Optimize for **both** traditional snippets and AI Overviews
### Featured Snippet vs AI Overview
**Not the same.** Featured snippets pull a direct passage from a single webpage. AI Overviews generate multi-source summaries using AI. When both appear, featured snippets still occupy a highly visible spot. Not every query triggers AI Overview—snippet optimization remains valuable. [Semrush](https://www.semrush.com/blog/featured-snippets/)
## Snippet Formats & Share
| Format | Share | Use | Optimization |
|--------|-------|-----|---------------|
| **Paragraph** | ~70% | Definition, "what is," "why" | 40–60 words; direct answer after H2 |
| **List** | ~19% | How-to, steps, options | `<ol>` or `<ul>`; semantic HTML |
| **Table** | ~6% | Comparisons, stats, specs | Clear headers; target keywords in column/row headers |
| **Video** | Rare | Visual how-to | Video schema; timestamps/chapters; see **video-optimization** |
**45 words** is the most common paragraph length. Answer-first format is critical. On mobile, featured snippets can occupy ~50% of the screen, pushing competitors below the fold. [Semrush](https://www.semrush.com/blog/featured-snippets/)
## Content Structure
### Answer-First Approach
- **Place direct answer** in first 1–2 sentences (40–60 words) before any other content
- **H2/H3**: Use clear headings; Google extracts from content under headings
- **Semantic HTML**: `<ol>`, `<ul>`, `<table>`, `<p>`—avoid divs styled as lists
- **Inverted pyramid**: Answer immediately (for snippet/AI), then add nuance/data that earns clicks
- **Objective tone**: Write like a dictionary entry—avoid personal opinions and emotional language; supports E-A-T
### HTML Structure
| Element | Use |
|---------|-----|
| **H2/H3** | Question or topic; Google recognizes and extracts; **list snippets can be compiled from headings** across the page—Google pulls H2s and converts to list items |
| **`<ol>`** | Steps, rankings, sequences; list snippets |
| **`<ul>`** | Non-sequential items; bullet snippets |
| **`<table>`** | Comparisons, specs; table snippets; clean rows/columns; H2/H3 intro; target keywords in heading and surrounding content; ensure data is relevant and scannable |
| **First paragraph** | 40–60 words; direct answer |
**Annotations matter**: Search engines use semantic labeling to identify relevant blocks ("Fraggles") and extract passages. Structure pages clearly—headings, lists, tables—so crawlers can annotate and pull the right content. Annotations can suggest relationships between blocks, enabling engines to stitch text from multiple parts. [SEJ / Bing](https://www.searchenginejournal.com/how-bing-q-and-a-featured-snippet-algorithm-works/362716/)
### Visual Elements
- Optimized images near answers can **double CTR** by capturing thumbnail slots
- **Alt text, captions, file names** support Image Pack and snippet thumbnails. See **image-optimization** for captions and full image SEO; **serp-features** for Image Pack context.
## Query Targeting
| Factor | Guidance |
|--------|-----------|
| **Query types** | "How," "what," "why" questions; definitional queries |
| **Long-tail** | Featured snippets typically appear for long-tail (specific) queries; short-tail is broad and less likely |
| **Ranking position** | Target positions 2–5; snippet ownership often comes from these (not always #1). **Prerequisite**: Must rank in top ~20 blue links to be considered; Q&A runs through top organic results |
| **Q&A memory** | Bing (and likely Google) memorize results; you may retain snippet even if blue link ranking drops—once earned, you don't necessarily need to maintain position |
| **Intent** | Informational; match user intent precisely |
| **Tools** | PAA (excellent for low-volume, snippet-triggering queries), AnswerThePublic, AlsoAsked, Semrush Keyword Magic Tool (SERP features filter: "Featured snippet") |
### How the Algorithm Works (Bing/Google)
- **Foundation**: Core algorithm ranks blue links; Q&A/Featured Snippet is a modular layer on top—same ranking foundation
- **Process**: 1) Take top blue link results; 2) Extract or create summary; 3) Identify implicit question each document answers; 4) Match user's question to best implicit question; 5) Feature that answer
- **E-A-T**: Snippets are E-A-T–based (Bing: "Relevancy" = accuracy/expertise). Correctness first—conforms to accepted opinion, document quality. Then authority and trust (document, author, publisher). See **eeat-signals** for E-E-A-T implementation.
- **Meta descriptions**: Do not affect ranking; engines generate descriptions on the fly. Over-optimized or missing meta descriptions lead engines to extract their own—structure helps them choose well. [SEJ](https://www.searchenginejournal.com/how-bing-q-and-a-featured-snippet-algorithm-works/362716/)
## GEO / AI Overviews
- **Layered content**: Clear definitions, lists, steps—AI can cite and summarize
- **Self-contained blocks**: Each answer readable alone; supports AI extraction
- **Schema**: FAQPage, HowTo, Article—helps machines understand structure
- See **generative-engine-optimization** for full GEO strategy
## Finding Opportunities
- **Manual**: Search target keyword; note if snippet appears and format (paragraph/list/table/video)
- **PAA**: People Also Ask questions often trigger snippets; use as H2 or dedicated page
- **Tools**: Semrush Keyword Magic Tool—filter by "Featured snippet" in SERP features; "Open SERP" to view current snippet
- **Best opportunities**: Keywords where you already rank on page 1 (positions 1–10)
## Monitoring
- **Google Search Console**: Identify snippet opportunities; track performance
- **Position Tracking** (e.g. Semrush): "Featured Snippets" tab—"Already featured" vs "Opportunities"
- **Rich Results Test**: Validate schema; ensure extraction eligibility
- **CTR benchmarks**: Snippets ~114% CTR increase vs position #1; adjust expectations when AI Overviews dominate
## Output Format
- **Target queries** (snippet-worthy)
- **Format** (paragraph/list/table) per query
- **Content structure** (H2, answer length, semantic HTML)
- **Schema** if applicable (FAQ, HowTo)
## Related Skills
- **serp-features**: SERP features overview; Featured Snippet in context
- **content-optimization**: H2 keywords, tables, lists; defers snippet-specific structure to this skill
- **faq-page-generator**: FAQ format and answer length; FAQ schema for PAA
- **schema-markup**: FAQPage, HowTo for rich results
- **heading-structure**: H2–H3 hierarchy
- **generative-engine-optimization**: AI citation; GEO strategy
- **eeat-signals**: E-E-A-T implementation; authority, trust, author
- **image-optimization**: Image SEO for snippet thumbnails; alt, captions, file names; captions support snippet context
- **video-optimization**: Video snippet format; VideoObject; timestamps/chapters
## References
- [How the Bing Q&A / Featured Snippet Algorithm Works](https://www.searchenginejournal.com/how-bing-q-and-a-featured-snippet-algorithm-works/362716/) (SEJ)—Bing algorithm, annotations, E-A-T, Q&A memory
- [Featured Snippets: What They Are & How to Earn Them](https://www.semrush.com/blog/featured-snippets/) (Semrush)—formats, optimization, PAA, tools
When the user wants to optimize the meta description or meta tag description. Also use when the user mentions "meta description," "meta desc," "page descript...
--- name: meta-description description: When the user wants to optimize the meta description or meta tag description. Also use when the user mentions "meta description," "meta desc," "page description," "SEO description," "search snippet," "SERP description," "description tag," "snippet for search," "meta description length," "rewrite meta description," or "description not showing." For title tag, use title-tag. For hreflang, robots, viewport, use page-metadata. metadata: version: 1.4.0 --- # SEO On-Page: Meta Description Guides optimization of the meta description tag for search engines and SERP display. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope (On-Page SEO) - **Meta description**: CTA; unique value; target keyword; unique per page ## Length by Language Google truncates by **pixel width** (~920px desktop, ~680px mobile), not character count. Character limits are approximate—CJK chars are wider (~2× Latin), so fewer fit in the same pixels. | Script / Language | Meta description (chars) | Notes | |-------------------|--------------------------|-------| | **Latin** (English, Spanish, French, etc.) | 150–160 | Desktop ~158; mobile ~120 | | **CJK** (Chinese, Japanese, Korean) | 75–100 | Full-width chars; 70–80 conservative; 90–100 on some locales/fonts; use pixel checker when available | | **Cyrillic** (Russian, etc.) | 140–155 | Slightly wider than Latin | | **Arabic, Hebrew** | 70–90 | RTL; variable width | **Pixel tools**: Use a pixel-accurate meta tag checker for CJK—font and locale affect display; character counts vary by source (65–80 to 90–120 in practice). **Multilingual**: Use locale-specific limits; localize, don't just translate. See **localization-strategy**, **translation**. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand voice and target keywords. Identify: 1. **Page type**: Homepage, landing, blog, product, etc. 2. **Primary keyword**: Target search query 3. **Language / script**: Apply length rule above 4. **CTA**: Primary action (sign up, learn more, buy, etc.) ## Best Practices | Item | Guideline | |------|-----------| | **Length** | Per language (see table above); ~150 chars sweet spot for Latin; truncates beyond pixel limit | | **Unique** | One per page; no duplicate descriptions | | **Intent** | Answer "why should I click?"; match search intent | | **CTA** | Include clear call-to-action when relevant | | **Keyword** | Naturally include target keyword | | **Content** | Include author, date, price where relevant | | **Impact** | Does not affect ranking; well-written descriptions improve CTR 5–10% | ## Output Format - **Recommended meta description** (with character count for target language) - **Alternatives** (if A/B testing) ## GSC-Driven Optimization For pages with low CTR despite good position, use google-search-console to identify opportunities. Optimize meta description for pages with CTR gap. ## Related Skills - **google-search-console**: CTR analysis, identify low-CTR pages for meta optimization - **title-tag**: Title pairs with description in SERP - **localization-strategy, translation**: Multilingual metadata; locale-specific length - **serp-features**: SERP features; standard result appearance in context - **heading-structure**: H1 should align with title; description summarizes content - **open-graph**: og:description for social sharing (often mirrors or extends meta description) - **keyword-research**: Keywords in content inform description
When the user wants to build backlinks, acquire links, or improve off-page SEO. Also use when the user mentions "link building," "backlinks," "off-page SEO,"...
--- name: link-building description: When the user wants to build backlinks, acquire links, or improve off-page SEO. Also use when the user mentions "link building," "backlinks," "off-page SEO," "link acquisition," "outreach," "guest posting," "broken link building," "link outreach," "acquire backlinks," "how to build backlinks," or "link building strategy." For profile audit, use backlink-analysis. metadata: version: 1.0.1 --- # SEO Off-Page: Link Building Guides link building strategy: acquiring quality backlinks to improve domain authority and rankings. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope (Off-Page SEO) - **Link building**: Acquire backlinks from relevant, authoritative sites - **Broken link building**: Find broken links on others' sites; suggest your content as replacement - **Unlinked brand mentions**: Turn mentions into links via outreach - **Guest posting**: Contribute to relevant publications; earn links - **Journalist requests**: Respond to #JournoRequest; provide quotes/assets - **Digital PR**: PR campaigns for backlinks and E-E-A-T — see **eeat-signals** ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and proof points. Identify: 1. **Current backlink profile**: Domain authority, referring domains 2. **Target keywords**: What to rank for 3. **Linkable assets**: Research, tools, guides, data, testimonials ## Link Building Strategies | Strategy | Description | |----------|-------------| | **Content marketing** | Create link-worthy content (guides, research, tools) | | **Guest posting** | Write for relevant sites with author bio link | | **Broken link building** | Find broken links, suggest your content as replacement | | **Unlinked brand mentions** | Turn mentions into links via outreach | | **Journalist requests** | Respond to #JournoRequest; provide quotes/assets | | **Directory and curated list submission** | Get listed on directories (Taaft, Product Hunt, G2) and curated "best-of" lists; cold-start channel—see **directory-submission** for submission workflow, **cold-start-strategy** for launch plan | | **Digital PR** | Press releases, news, expert quotes; earn authoritative links at scale | | **Partnerships** | Partner links, co-marketing | ## Quality Over Quantity | Factor | Good | Avoid | |--------|------|-------| | **Relevance** | Links from related sites | Irrelevant niches | | **Authority** | High-quality, trusted sites | Spammy, low-quality | | **Anchor text** | Natural, varied | Over-optimized, exact match | | **Context** | Editorial, contextual links | Footer, sidebar link farms | ## Outreach Best Practices - Personalize each outreach message - Offer value (content, data, quote) before asking for link - Follow up politely; don't spam - Track outreach in spreadsheet or tool ## Output Format - **Linkable asset** ideas - **Outreach** strategy and templates - **Target sites** (types, not specific URLs) - **Metrics** to track (referring domains, DA, traffic) ## Related Skills - **seo-strategy**: SEO workflow; link building is Off-Page phase - **backlink-analysis**: Analyze current backlink profile - **content-strategy**: Content strategy supports link building - **keyword-research**: Target keywords inform link targets - **cold-start-strategy**: Cold start and first-user acquisition; directory submission as part of launch - **parasite-seo**: Parasite SEO; high-authority platforms for backlinks - **github**: GitHub repos, gists, awesome lists for backlinks - **directory-submission**: Directory and curated list submission--preparation, platform-specific copy, Taaft/Product Hunt/G2; use when user wants to submit product to directories or get listed on best-of roundups - **eeat-signals**: E-E-A-T implementation; Digital PR supports authority
When the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit,"...
--- name: backlink-analysis description: When the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building. metadata: version: 1.0.1 --- # SEO Off-Page: Backlink Analysis Guides backlink profile analysis: assessing quality, identifying issues, and planning improvements. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope (Off-Page SEO) - **Backlink audit**: Analyze profile; toxic links; competitive analysis - **Authority Score**: Monitor domain/page authority; referring domains ## Initial Assessment Identify: 1. **Domain**: Site to analyze 2. **Tool access**: SEO tools (e.g. Ahrefs, Semrush) or free alternatives 3. **Goals**: Audit for issues, competitive analysis, or growth planning ## Key Metrics | Metric | Meaning | |--------|---------| | **Referring domains** | Number of unique sites linking | | **Backlinks** | Total number of links | | **Domain Rating (DR) / Domain Authority (DA)** | Domain strength score | | **Anchor text distribution** | Mix of branded, generic, exact match | | **Link velocity** | Rate of new links over time | ## Analysis Framework ### 1. Quality Assessment - **Relevance**: Do links come from related niches? - **Authority**: Are referring domains trusted? - **Context**: Editorial vs. footer/sidebar links? - **Anchor text**: Natural or over-optimized? ### 2. Risk Signals | Signal | Action | |--------|--------| | **Toxic links** | Consider disavow (use cautiously) | | **Spammy anchors** | Diversify anchor text naturally | | **Link schemes** | Remove or disavow | | **Sudden spike** | Investigate; may trigger penalty | ### 3. Competitive Comparison - Compare backlink profile to competitors - Identify link gaps (sites linking to competitors but not you) - Find link opportunities from competitor backlinks - See **competitor-research** for full methodology ## Disavow File - Use only when necessary (manual penalty, toxic links) - Submit via Google Search Console (see **google-search-console** for Links report and disavow submission) - **Caution**: Over-disavowing can harm; use sparingly - **References**: [Google Disavow](https://developers.google.com/search/docs/crawling-indexing/block-indexing#disavow-links) ## Output Format - **Profile summary**: Key metrics, trends - **Quality assessment**: Strengths and weaknesses - **Risk signals**: Toxic or suspicious links - **Recommendations**: Link building priorities, disavow if needed - **Competitive insights**: Link gap opportunities ## Related Skills - **google-search-console**: Links report, disavow file submission - **seo-monitoring**: Backlink metrics in full SEO monitoring; quality vs quantity, referral ROI - **link-building**: Use analysis to plan link building - **competitor-research**: Competitor backlink analysis; link gap methodology
When the user wants to optimize for local search, set up Google Business Profile, or build local citations. Also use when the user mentions "local SEO," "Goo...
--- name: local-seo description: When the user wants to optimize for local search, set up Google Business Profile, or build local citations. Also use when the user mentions "local SEO," "Google Business Profile," "Google Maps," "NAP," "citations," "local search," "local business," or "service area." For location pages, use programmatic-seo. metadata: version: 1.0.1 --- # SEO: Local Guides local SEO: Google Business Profile, NAP consistency, and citation building. Businesses with accurate NAP across 40+ authoritative sites see ~19% higher visibility in Google Maps. Use this skill when optimizing for local search, setting up GBP, or auditing citations. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 4 (Audience), 5 (Website). Identify: 1. **Business type**: Storefront vs service-area 2. **Location**: Single or multiple 3. **Current listings**: Existing GBP, directories ## NAP Consistency **NAP** = Name, Address, Phone. Critical for local rankings. | Rule | Guideline | |------|-----------| | **Exact match** | "Street" vs "St." or "LLC" inconsistency = Google may treat as different entities | | **Fix first** | Audit and fix inconsistencies before adding new citations | | **Tools** | BrightLocal, Whitespark, Moz Local for audit | ## Google Business Profile | Element | Guideline | |---------|-----------| | **Address** | Physical address; no P.O. boxes | | **Description** | 750 chars; primary keywords in first 100 | | **Hours** | Accurate; seasonal availability | | **Category** | Primary category matches business type | | **Service-area** | Hide address if no storefront; define service areas | ## Citation Building **Targeted precision** over submitting to every directory. **Priority order**: 1. Google Business Profile 2. Apple Maps 3. Yelp, Bing Places, Facebook 4. Better Business Bureau, Foursquare, Nextdoor 5. Niche directories (Healthgrades, Angi, etc.) ## Citation Audit - Incorrect or outdated data - Duplicate entries - Missing listings on key directories Fix before adding; compounding errors harm rankings. ## Output Format - **NAP** (exact format for consistency) - **GBP** optimization checklist - **Citation** priority list - **Audit** findings (if applicable) ## Related Skills - **geo**: GEO for AI search; local + AI overlap - **localization-strategy**: Multilingual; local + i18n - **directory-submission**: Directory listings; different from local citations
When the user wants to optimize for entity recognition, Knowledge Graph, or entity-based SEO. Also use when the user mentions "entity SEO," "entity optimizat...
--- name: entity-seo description: When the user wants to optimize for entity recognition, Knowledge Graph, or entity-based SEO. Also use when the user mentions "entity SEO," "entity optimization," "Knowledge Graph," "Knowledge Panel," "entity signals," "brand entity," "entity linking," "entity relationships," or "entity-first content." For structured data, use schema-markup. metadata: version: 1.0.1 --- # SEO: Entity SEO Guides entity-based SEO—making your brand, product, and authors recognizable as distinct entities in search engines' knowledge systems. Google moved from keyword-matching to meaning-based understanding (Hummingbird, RankBrain, BERT, MUM); entity understanding is central to how search processes queries. Content structured around entities can receive ~3.2× more visibility in AI-powered search. References: [Semrush](https://www.semrush.com/blog/entity-based-seo-strategy/), [Search Engine Land](https://searchengineland.com/guide/entity-first-content-optimization). **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **Entity definition**: Singular, unique, well-defined things (person, place, organization, product, event) - **Entity vs keyword**: Entities = underlying concepts; keywords = text strings - **Knowledge Graph**: Google's entity database; powers disambiguation and related concepts - **Implementation**: Schema (Organization, Person); entity signals in content; consistency across platforms ## What Is an Entity? An **entity** is a thing or concept that is singular, unique, well-defined, and distinguishable—e.g. person, place, organization, product, event. Entities have: | Attribute | Meaning | |----------|---------| | **Unique identity** | "Apple Inc." ≠ "apple (fruit)" despite same word | | **Attributes** | Founding date, location, industry | | **Relationships** | Connections to other entities (e.g. Apple Inc. → Steve Jobs, iPhone) | **Entity SEO** = optimizing so search engines can identify, categorize, and connect your brand/product/author within the knowledge graph. Keywords are ambiguous; entities maintain consistent meaning across contexts. ## Why Entity SEO Matters - **Search evolution**: Google uses entities to understand intent, not just match phrases - **Knowledge Graph**: Billions of entities and relationships; disambiguation, related concepts - **AI search**: Entity-optimized content ~3.2× more visible in AI results - **E-E-A-T**: Entity signals support Experience, Expertise, Authoritativeness, Trust. See **eeat-signals** - **GEO**: AI Overviews, Copilot, Perplexity cite entities; clear identity improves citation. See **generative-engine-optimization** ## Entity Signals (Content Best Practices) | Practice | Purpose | |----------|---------| | **Clear brand/product name** | Consistent naming; avoid confusion with similar entities | | **Author identity** | Person schema; author bio; link to author page | | **Organization identity** | Organization schema site-wide; logo, sameAs | | **Citable paragraphs** | Each block understandable on its own; supports AI extraction | | **Consistency** | Same name, description, logo across website, social, directories | ## Schema for Entity SEO ### Organization - **Placement**: **Minimum**—homepage; **Optimal**—root layout / global component (layout.tsx, _document, global header) so it appears on every page. Do **not** confine to About page; About uses AboutPage schema. See **schema-markup** for full placement table. - **Required**: `@id`, `name`, `url`; add `logo`, `sameAs` (social, Wikidata) - **Optional**: `description`, `address`, `contactPoint`; use most specific type (LocalBusiness, SoftwareApplication, etc.) when applicable **@id**: Use stable URL (e.g. `https://example.com/#organization`) for entity linking across pages. Link Organization ↔ WebSite on homepage for sitelinks searchbox. ### Person - **Use**: Author pages; Article author; team members - **Properties**: `name`, `url`; `affiliation` (Organization); `sameAs` (LinkedIn, Twitter) - **@id**: Enables entity linking; e.g. `https://example.com/author/jane/#person` See **schema-markup** for full VideoObject, Article, Product, etc.; Organization and Person are core for entity SEO. ## Knowledge Panel & Knowledge Card | Feature | Description | Obtainability | |---------|-------------|---------------| | **Knowledge Panel** | Entity info (brand, person, place) in SERP | WikiData, partnerships; most sites cannot directly obtain | | **Knowledge Card** | Top-of-SERP semantic answer | Same as Knowledge Panel | **Actions** (limited control): - **Claim**: Google Business Profile; suggest updates when available - **Consistency**: Same brand name, description, logo across all platforms - **Entity Home**: Authoritative About page as primary reference - **WikiData / Wikipedia**: Can support Knowledge Panel generation See **serp-features** for Knowledge Panel in SERP context; **multi-domain-brand-seo** for Hub-Spoke entity consistency. ## Entity & Multi-Domain / Brand When using multiple domains (Hub-Spoke): - **Consistency**: Same brand name, description, logo across Hub and Spoke - **Entity Home**: Authoritative About page on Hub as primary reference - **Schema**: Organization with subOrganization for related entities - **Entity confusion**: Avoid legacy brands, sub-brands, directories diluting brand perception See **multi-domain-brand-seo** for full strategy. ## GEO & AI Citation Entity signals strengthen GEO citation: - **Direct-answer format** + **entity signals** = clearer AI extraction - **Citable paragraphs** with clear brand/product/author identity - **Distribution**: Website, YouTube, forums, Reddit—consistent entity identity across platforms See **generative-engine-optimization** for full GEO strategy. ## Output Format - **Entity audit** (brand, product, author identity gaps) - **Schema** (Organization, Person; @id placement) - **Consistency** checklist (name, logo, description across touchpoints) - **Knowledge Panel** (claim if eligible; suggest updates) ## Related Skills - **schema-markup**: Organization, Person; @id for entity linking - **eeat-signals**: E-E-A-T; author bio; Person schema - **generative-engine-optimization**: GEO; entity signals for AI citation - **serp-features**: Knowledge Panel, Knowledge Card; SERP context - **multi-domain-brand-seo**: Entity & Knowledge Panel; Hub-Spoke consistency - **about-page-generator**: Entity Home; authoritative brand reference
When the user wants to research keywords, find target keywords, or analyze search intent. Also use when the user mentions "keyword research," "keyword tool,"...
--- name: keyword-research description: When the user wants to research keywords, find target keywords, or analyze search intent. Also use when the user mentions "keyword research," "keyword tool," "target keywords," "search volume," "search intent," "keyword difficulty," "topical map," "keyword clustering," "People Also Ask," "Google autocomplete," "autocomplete keywords," or "alphabet method." For clusters, use content-strategy. metadata: version: 1.3.1 --- # SEO Content: Keyword Research Guides keyword research for SEO: finding target keywords, assessing difficulty, understanding search intent, and building topical maps. ~95% of keywords get fewer than 10 searches/month; low-volume, high-intent terms often yield faster rankings and conversion. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and positioning. Identify: 1. **Product/service**: What you offer 2. **Audience**: Who searches for it 3. **Goals**: Traffic, conversions, brand 4. **Tool access**: Google Keyword Planner, Google Trends, or SEO tools ## Discovery Methods ### Base Discovery | Method | Purpose | |--------|---------| | **User perspective** | What pain points? What would they search? Customer language from product context | | **Tool expansion** | Related keywords, questions, suggestions; Google autocomplete, PAA, Related Searches | | **Competitor reverse** | Analyze competitor titles, H1, URL; identify topics they rank for; find gaps (#4–10 = opportunity) — see **competitor-research** | | **Google PAA** | People Also Ask and Related Searches; high-value signals from real user behavior | | **Extract from article** | When auditing existing content: extract seed keywords from title, H1, H2s, meta keywords, first 100 words; then search `"[primary keyword]"` or `"[primary keyword] related keywords"` for opportunities; use `"[primary keyword]" site:competitor.com` if competitors known | ### Google Autocomplete (Long-Tail Discovery) Google autocomplete reflects real user searches; suggestions only appear if queries have actual traffic. Free; often uncovers low-volume long-tail that keyword tools miss. ~70% of search traffic is long-tail; lower competition, higher conversion. **Alphabet method** (seed + space + letter): - Type seed keyword + space + each letter: `keyword a`, `keyword b`, ... `keyword z` - Record relevant suggestions; repeat with numbers 0-9 - Example: `SEO a` -> "SEO audit," "SEO agency"; `SEO b` -> "SEO basics," "SEO best practices" **Position variants** (seed in different positions): - **Prefix**: `a keyword`, `b keyword` (discover what users add before) - **Suffix**: `keyword a`, `keyword b` (most common; alphabet method) - **Middle**: `how to keyword a`, `best keyword for` (question + modifier combos) **Question modifiers**: - `how to keyword`, `what is keyword`, `why keyword`, `when to keyword`, `keyword vs` - `keyword for beginners`, `keyword for small business`, `keyword without` **Why it works**: Keyword tools filter low-volume terms; autocomplete only shows queries with real traffic. Use with PAA and Related Searches for full coverage. Categorize results by intent (informational, commercial, transactional). ### Incremental Discovery - **User feedback**: Support, community, reviews, NPS—high-frequency questions = unmet search demand - **Multi-platform search**: Reddit, Quora, X (Twitter), Hacker News—real questions and discussions ## Search Intent | Intent | Content type | Example | |--------|--------------|---------| | **Informational** | Blog, guide, FAQ | "how to optimize sitemap" | | **Navigational** | Brand page | "alignify login" | | **Commercial** | Comparison, review | "SEO tools comparison" | | **Transactional** | Product, pricing | "best SEO tool pricing" | ### Intent Identification **Modifier words** (often signal intent): | Intent | Modifiers | |--------|-----------| | Informational | "how," "what," "why," "guide," "tutorial" | | Commercial | "best," "compare," "vs," "review," "top" | | Transactional | "buy," "price," "cheap," "coupon," "free shipping" | | Local | Location names | **SERP check**: Search the term—knowledge cards/Wiki → informational; product lists/reviews → commercial; brand sites → navigational. Broader terms often show mixed SERP. See **serp-features** for feature types. ## Long-Tail Expansion - **Google Autocomplete**: Alphabet method, position variants, question modifiers; see above. Primary source for long-tail. - **Intent modifiers**: Core + "how," "best," "vs," "compare," "price" - **Question words**: "how to," "what is," "why," "when" - **Functional modifiers**: Core + "-er/-or" (e.g., "image optimizer" for tool-type queries); often higher conversion - **Clustering**: Group by SERP overlap (same top pages), semantic similarity, or intent. ## Keyword Clustering & Topical Map | Method | Use | |--------|-----| | **SERP overlap** | Keywords with overlapping top-ranking pages → same cluster | | **Semantic** | Group by meaning, LSI, related concepts | | **Intent-based** | Group by intent; separate pages if intent differs within cluster | **Pillar–cluster** (map keywords to structure): - **Pillar** (Hub): Broad topic page; links to clusters - **Cluster** (Spoke): Focused subtopic; links back to pillar - Target long-tail first; then pillar. Interlink clusters within topic. - See **content-strategy** for full pillar-cluster planning and implementation. ## Evaluate & Screen | Factor | Consider | |--------|----------| | **Search volume** | Monthly searches; ~100+/month typical floor; niche can relax | | **Keyword difficulty (KD)** | New sites target lower KD | | **CPC** | Higher CPC often = stronger commercial intent | | **SERP features** | Featured Snippet, PAA, zero-click; SERP features can satisfy intent without click—affects real traffic; see **serp-features** (Zero-Click section), **featured-snippet** | | **Screening order** | 1) Remove irrelevant 2) Filter very low volume 3) Assess achievability 4) Prioritize commercial/transactional | ## Product Positioning Test (SEO Fit) Test if positioning is clear enough for search: - **XXX + Function words**: Generator, Creator, Maker, Builder, Changer, Shortener, Scraper, Converter, Downloader, Translator, Extender, Summarizer, Resizer, Remover, Extractor, Recorder, Rewriter, Solver, Calculator; or Platform, Tool, Software, App, Provider, Assistant, Copilot - **Input + to + Output**: e.g., "image to video," "text to speech"—clear input/output signals intent **Agent/Copilot products**: Pure native Agent hard to grow via SEO; users rarely search "agent." Release related features first (e.g., CRM, sales bot for sales agent) to build traffic, then funnel to Agent product. ## Principles - **Core rule**: Someone must search it—validate with tools; avoid inventing terms - **Functional keywords**: Tool-type (-er/-or) often convert better; users are closer to action - **Multi-language**: Re-research in target language; don't translate existing lists. See **translation** for translation workflow. ## SEO–PPC Keyword Synergy Keyword research serves both SEO and Google Ads. Align both channels to avoid duplication, cannibalization, and wasted spend. | Data flow | Use | |-----------|-----| | **keyword-research → google-ads** | Keyword list, clusters, intent; support terms (login, forum, pricing) → negative keywords for PPC | | **google-ads → keyword-research** | PPC conversion rate, Search Terms report → SEO priority; high-converting PPC terms = worth ranking organically | | **keyword-research → landing-page** | Clusters → dedicated LP per intent; PAA questions → FAQ sections | | **GSC organic rank 4+** | If you rank well organically, consider reducing/pausing PPC on those terms to avoid cannibalization | **PPC data for SEO priority**: `SEO ROI ≈ (Organic clicks × PPC conversion rate × Customer value) − SEO cost`. Use PPC conversion data to validate which keywords to pursue in organic. **Reference**: [Backlinko – SEO and PPC: 8 Smart Ways to Align](https://backlinko.com/seo-and-ppc) ## Data Sources | Source | Use | |--------|-----| | **Ahrefs** | Keywords Explorer, Site Explorer | | **SEMrush** | Keyword Overview, Organic Research | | **GSC** | Search queries, impressions, clicks | | **GA** | Traffic by landing page | | **PostHog** | Feature/search usage | ## Report Workflow 1. **Parse** — Read Excel/CSV, infer keyword, volume, KD, intent, etc. from headers 2. **Enrich** — Web search, visit competitor/product pages; read `project-context.md` if present 3. **Build** — Structure data for report 4. **Generate** — Output report in chosen format ## Output Format - **Keyword list** with volume, KD, intent - **Keyword mapping** to pages/content - **Content gaps** (competitors rank, you don't) - **Priority** ranking for implementation - **Topical map** (cluster → pillar → page mapping) ### Report Structure Reference | Section | Content | |---------|---------| | Executive Summary | Priorities (top 3) | | Keyword Overview | Total keywords, primary intent, avg KD, content gaps count | | Keyword List | Keyword, volume, KD, intent, priority, target page | | Keyword Mapping | Page/URL, target keywords, status | | Content Gaps | Keywords competitors rank for that you don't | | Action Plan | Priority, action, impact, effort | | Appendix | Search intent reference (Informational, Commercial, Transactional, Navigational) | ## Related Skills - **seo-strategy**: SEO workflow, Product-Led SEO, audit approach; keyword research is Content phase - **google-ads**: Keywords inform Search targeting; PPC data feeds back into SEO priority - **paid-ads-strategy**: When to use paid vs organic; channel selection - **content-strategy**: Keywords inform content plan; topic clusters - **content-optimization**: Keyword placement, density vs stuffing, H2 keywords - **title-tag, meta-description**: Keywords in title, description - **heading-structure**: Keywords in H1, H2 - **link-building**: Keywords inform link targets - **serp-features**: SERP features in keyword screening; PAA, Featured Snippet - **featured-snippet**: Snippet-worthy query targeting - **competitor-research**: Competitor keyword/topic analysis; reverse engineering - **faq-page-generator**: PAA questions to FAQ sections; question-based keyword to FAQ content
When the user wants to improve E-E-A-T, add trust signals, or optimize for expertise and authority. Also use when the user mentions "E-E-A-T," "E-E-A-T signa...
--- name: eeat-signals description: When the user wants to improve E-E-A-T, add trust signals, or optimize for expertise and authority. Also use when the user mentions "E-E-A-T," "E-E-A-T signals," "experience expertise authority trust," "author bio," "YMYL," "trust signals," "expertise signals," "authority signals," "citations," "references," or "credibility." For headings, use heading-structure. metadata: version: 1.0.1 --- # SEO Content: E-E-A-T Signals Guides E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) implementation for SEO. E-E-A-T helps search engines and users assess content quality; YMYL topics (health, finance, legal) require higher E-E-A-T. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## What Is E-E-A-T | Element | Meaning | Implementation | |---------|---------|-----------------| | **Experience** | First-hand, real-world experience | Case studies, original research, user testimonials, "we tested" | | **Expertise** | Subject-matter knowledge | Author credentials, expert quotes, technical depth | | **Authoritativeness** | Recognition as a source | Backlinks, citations, author page, publisher reputation | | **Trustworthiness** | Accuracy, transparency | Citations, About page, contact, HTTPS, no misleading content | **E-A-T** (without Experience) is used in Featured Snippet context—Bing/Google emphasize correctness, document quality, then authority and trust. See **featured-snippet**. ## Author Bio | Element | Guideline | |---------|-----------| | **Placement** | End of article or sidebar; link to author page | | **Content** | Name, credentials, photo, brief expertise, link to author page | | **Author page** | Dedicated page per author; bio, other articles, social | | **Schema** | Person schema; link author to Article schema; see **entity-seo** | ## Citations & References | Scenario | Practice | |----------|----------| | **Data or statistics** | Cite source inline or in References section | | **Expert quotes** | Attribute; link to source or profile | | **Reference section** | For 5+ citations; list at end before Related posts | | **Format** | Inline links preferred; numbered refs for academic-style | | **When to include** | Any claim benefiting from authority (stats, studies, definitions) | | **External links** | Link to reputable sources; avoid low-quality sites | ## Experience Signals | Signal | Use | |--------|-----| | **Case studies** | Real customer outcomes; Challenge→Solution→Results | | **Original research** | First-party data, surveys, tests | | **First-hand testing** | "We tested X"; product reviews with real use | | **User testimonials** | Authentic quotes; link to full case study when available | ## YMYL (Your Money Your Life) Topics that can significantly impact health, financial stability, or safety require **higher E-E-A-T**: - **Health**: Medical, mental health, nutrition advice - **Finance**: Investment, tax, insurance, loans - **Legal**: Legal advice, regulations - **Safety**: Product safety, emergency procedures **Guidelines**: Author credentials, citations to authoritative sources, clear sourcing, regular updates, avoid speculation. ## AI-Assisted Content When content is AI-assisted: **human review** before publish; **verify facts** and add citations; **original insights** or data; avoid generic phrasing. Transparency and human refinement support E-E-A-T. ## Output Format - **E-E-A-T assessment** (gaps, strengths) - **Author bio** recommendation - **Citation** plan (where to add, what to cite) - **Experience** signals (case studies, original data) - **YMYL** considerations (if applicable) ## Related Skills - **article-page-generator**: Article page structure; author bio placement - **article-content**: Article body creation; citations, references format - **content-optimization**: Original images, content quality; E-E-A-T complements - **link-building**: Digital PR, E-E-A-T; backlinks signal authority - **featured-snippet**: E-A-T in snippet algorithm; correctness, authority - **backlink-analysis**: Authority assessment; E-E-A-T context - **customer-stories-page-generator**: Case studies as experience signal - **testimonials-generator**: User quotes as trust signal - **entity-seo**: Entity signals; Organization, Person schema; Knowledge Panel; E-E-A-T alignment
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content p...
---
name: content-strategy
description: When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.
metadata:
version: 1.1.1
---
# SEO Content: Content Strategy
Guides content strategy for SEO: topic clusters, pillar pages, cluster articles, and editorial planning. For content marketing across all channels (blog, email, social, video), see **content-marketing**. For translation workflow and multilingual content, see **translation**.
**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
## Initial Assessment
**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and proof points.
Identify:
1. **Keywords**: From keyword research — see **keyword-research** for discovery and clustering
2. **Existing content**: What already exists
3. **Resources**: Content capacity, tools
4. **Goals**: Traffic, conversions, authority
**Product-Led SEO**: Do SEO around product/users, not around industry/search engines. See **seo-strategy** for Product-Led SEO principle, products suited for SEO, and workflow order.
## Topic Clusters
Topic clusters organize content by **topic** rather than isolated keywords. A **pillar page** covers a broad core topic; **cluster articles** cover subtopics; all connect via internal links. This signals topical authority to search engines and AI systems.
### Structure
```
Pillar page (broad topic, 2,000-5,000+ words)
<-> internal links
Cluster 1 (subtopic, 800-2,500 words)
Cluster 2 (subtopic)
...
Cluster 6-12 (subtopics)
<-> cluster to cluster links
```
### Pillar Page
| Attribute | Guideline |
|-----------|-----------|
| **Length** | 2,000-5,000+ words; comprehensive guide |
| **Keyword** | Broad head term with search volume |
| **Role** | Hub; links to all cluster articles; targets primary topic |
| **Conversion** | Link to product/feature pages where relevant |
### Cluster Articles
| Attribute | Guideline |
|-----------|-----------|
| **Count** | 6-12 articles per pillar (minimum 6 for authority) |
| **Length** | 800-2,500 words each; focused on one subtopic |
| **Keyword** | Long-tail, specific intent per article |
| **Links** | Each cluster links to pillar; pillar links back; related clusters link to each other |
### Internal Linking Model
| Link type | Purpose |
|-----------|---------|
| **Pillar to Cluster** | Hub distributes authority; users discover subtopics |
| **Cluster to Pillar** | Signals relationship; passes equity to hub |
| **Cluster to Cluster** | Related subtopics; strengthens topical coverage |
### Structure and Content Equally Important
**Framework and body quality both matter**: TOC, chapter logic, and content depth are all essential for SEO and UX. Weak structure undermines strong writing; weak writing undermines strong structure. Plan both from the start.
### Why Topic Clusters Work
- **Topical authority**: Rank for multiple variations; comprehensive coverage signals expertise
- **Avoid cannibalization**: One page per topic/keyword; no competing pages
- **Better internal linking**: Clear logic; crawlers understand structure
- **AI citations**: Clustered content gets ~42% more AI citations than standalone
- **Traffic**: ~30% more organic traffic; rankings hold ~2.5x longer
### Implementation Steps
1. **Choose 3-7 core topics** -> business relevance, search demand, competitive opportunity
2. **Map subtopics** -> People Also Ask, competitor analysis, keyword tools
3. **Content audit** -> Identify existing pages that can become pillar or cluster; find gaps
4. **Build clusters first** (optional) -> Cluster pages often rank first; add pillar after
5. **Create pillar** -> Comprehensive guide; link to all clusters
6. **Establish links** -> Pillar <-> cluster; cluster <-> cluster
7. **Update quarterly** -> Maintain freshness and authority
### Example
- **Pillar**: "SEO Guide" (targets "SEO")
- **Clusters**: "Technical SEO," "On-Page SEO," "Link Building," "Content SEO," "Local SEO," "E-E-A-T"
## Content Types
| Type | Use | SEO Fit |
|------|-----|---------|
| **How-to guides** | Informational intent; high share potential | High -> matches search intent |
| **Comparisons** | Commercial intent; "X vs Y" | High |
| **List posts** | "Top 10," "Best X" | High |
| **Glossaries** | Definition queries; internal link hub | High |
| **Tools/calculators** | Linkable assets; engagement | High |
| **Case studies** | Proof; conversion support | Medium -> supports conversion |
| **Funding / PR** | Funding rounds, acquisitions | Low -> brand/PR, not search-driven |
| **Product updates** | Feature launches, release notes | Low -> internal audience |
| **News / Trending** | Industry news, hot topics | Medium -> quick spikes, short shelf life |
### Evergreen vs Timely Content Mix
- **Evergreen** (70-75%): Pillar guides, how-tos, comparisons, glossaries. Drives long-term traffic, backlinks, authority. Refresh every 6-12 months.
- **Timely** (25-30%): Seasonal, trending, news. Generates quick traffic, shows topical relevance. Link timely pieces into evergreen pillars.
- **Balance**: Too much evergreen = blog feels stale; too much timely = irregular traffic, constant content churn.
## Editorial Calendar
- Map keywords to content pieces
- Prioritize by opportunity (volume -> intent -> feasibility)
- Schedule by capacity
- Include update schedule for existing content
## Output Format
- **Topic cluster** map (pillar + 6-12 clusters)
- **Content calendar** (topics, keywords, deadlines)
- **Internal linking** plan
- **Update plan** for existing content
## Related Skills
- **content-marketing**: Content types, formats, channels, repurposing; SEO content is one channel
- **translation**: Multilingual content; translation workflow, glossary; avoid thin translations
- **seo-strategy**: SEO workflow order, Product-Led SEO, audit approach; use when planning SEO from scratch
- **website-structure**: Plan which pages to build; structure informs content clusters and pillar placement
- **keyword-research**: Keywords drive content plan
- **programmatic-seo**: Programmatic SEO for scaling pages with template + data; complements topic clusters
- **content-optimization**: Word count, H2 keywords, keyword density, multimedia, lists -> on-page content optimization
- **internal-links**: Clusters need internal linking
- **link-building**: Content strategy creates linkable assets
- **heading-structure**: Content structure uses headings
When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content...
--- name: content-optimization description: When the user wants to optimize content for SEO—word count, H2 keywords, keyword density, multimedia, tables, lists. Also use when the user mentions "content length," "word count," "keyword stuffing," "H2 keywords," "keyword density," "tables," "bullet points," or "content structure." For keywords, use keyword-research. metadata: version: 1.2.1 --- # SEO Content: Content Optimization Guides on-page content optimization: word count, heading keywords, keyword density vs stuffing, multimedia, tables, and lists. Complements **heading-structure** (structure) and **content-strategy** (planning). **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **Word count**: For articles, see **article-content** (word count by type). This skill covers generic content length strategy. - **H2 keywords**: Placement, quantity, variation - **Keyword density vs stuffing**: Natural use; avoid manipulation - **Multimedia**: Images, tables, lists, video for structure and Featured Snippets. See **featured-snippet** for snippet-specific optimization; **video-optimization** for video SEO. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for target keywords and content type. Identify: 1. **Content type**: Article, guide, listicle, pillar, news 2. **Target keyword**: Primary and secondary 3. **Competitors**: Top 10 average length and structure — see **competitor-research** --- ## Word Count **Google does not rank by word count.** Length should match search intent and topic depth. A 1,000-word post that satisfies intent can outrank a 3,000-word thin piece. ### Reference Ranges by Content Type For **article** word count by type (news, how-to, listicle, pillar, etc.), see **article-content**. Generic ranges: | Content type | Word count | Notes | |--------------|-------------|-------| | **News / announcements** | 300–600 | Time-sensitive; concise | | **Standard articles / how-tos** | 1,000–1,500 | Single topic; actionable | | **Listicles / guides** | 1,200–2,000 | "Top 10," "Best X" | | **Pillar / cornerstone** | 2,000–3,500+ | Comprehensive; cluster hub | ### Strategy 1. **Analyze top 10** for target keyword — average length and depth 2. **Match intent** — informational often needs ~40% longer than transactional 3. **Value over padding** — each section must add genuine value; avoid fluff 4. **Comprehensive coverage** — answer the query and related questions --- ## H2 Heading Keywords ### Placement - **Primary keyword**: Include naturally in at least one H2 when relevant - **Related keywords**: Use LSI and long-tail in other H2s for topical coverage - **Avoid stuffing**: Headings must stay clear and readable; organic placement only ### Quantity - **No strict limit** — one H2 per major section; structure follows content - **Typical article**: 4–8 H2s; pillar: 8–15+ H2s - **Hierarchy**: H1 → H2 (major sections) → H3 (subsections); don't skip levels ### Best Practices | Practice | Purpose | |----------|---------| | **Descriptive H2s** | Search engines understand context; users scan | | **Answer-first** | Place direct answer in first 40–50 words after H2 for Featured Snippets; see **featured-snippet** | | **Keyword variation** | Use related terms; avoid repeating exact phrase in every H2 | | **Logical flow** | H2s outline the article; support topical authority | --- ## Keyword Density vs Keyword Stuffing ### Definitions | Term | Meaning | |------|---------| | **Keyword density** | (Keyword count / Total words) × 100; a metric, not a ranking factor | | **Keyword stuffing** | Excessive, unnatural repetition to manipulate rankings; black-hat | ### Current Guidance - **Keyword density is not a direct ranking factor** — Google has stated since 2011 that repetition alone doesn't improve rankings - **Reference range**: 0.5%–1.5% for most content; some sources cite up to 2.5% - **Use density mainly to avoid stuffing** — if density exceeds ~2–3% and reads unnaturally, reduce - **Prioritize natural placement**: title, H1, first 100 words, 1–2 H2s, body; avoid forced repetition ### How to Avoid Stuffing - Write for users first; keywords should fit naturally - Use synonyms, related terms, and question phrasing - If a sentence sounds awkward with the keyword, rewrite - Monitor: if every paragraph repeats the exact phrase, simplify --- ## Multimedia: Images, Tables, Lists ### Images | Practice | Purpose | |----------|---------| | **Alt, file names, captions** | See **image-optimization** for full image SEO (alt, format, responsive, lazy loading, image sitemap, LCP, captions for Featured Snippets) | | **Original over stock** | Unique images signal E-E-A-T — see **eeat-signals** | **Content placement**: Put images near relevant text; captions support snippet thumbnails. See **image-optimization** for captions; **featured-snippet** for snippet context. ### Video | Practice | Purpose | |----------|---------| | **Embed + metadata** | VideoObject schema, video sitemap, thumbnail; see **video-optimization** | | **YouTube** | Google prioritizes YouTube in search; GEO citation; see **youtube-seo**, **generative-engine-optimization** | | **Featured Snippet (video)** | Video schema; timestamps/chapters; see **featured-snippet** | ### Tables - **Use for**: Comparisons, stats, specs, "X vs Y" - **Semantic HTML**: `<table>`, `<thead>`, `<tbody>`, clear column headers - **Featured Snippets**: ~6% of snippets are tables; optimize headers with target keywords. See **featured-snippet** - **Mobile**: Responsive; avoid horizontal scroll when possible - **Data quality**: No empty cells; consistent units; accurate, current data ### Lists: Ordered vs Unordered | Type | Use case | SEO / Snippet | |------|----------|---------------| | **Ordered (`<ol>`)** | Steps, rankings, sequences, "Top 10" | List snippets (~19% of Featured Snippets); how-to; see **featured-snippet** | | **Unordered (`<ul>`)** | Non-sequential items, features, options | Bullet snippets; definitions, options | **Best practices**: - Use semantic `<ol>` and `<ul>`; avoid divs styled as lists - **Answer-first**: For snippet targets, put the direct answer in the first 40–50 words after the heading - **Concise items**: List items should be scannable; expand in body if needed - **Logical order**: Ordered lists = sequence matters; unordered = no sequence ### GEO / AI Citation **Answer-first** (direct answer in first 40–60 words after H2) supports both Featured Snippets and GEO. For article-level GEO (TL;DR, Key Takeaways, QAE pattern), see **article-content** and **generative-engine-optimization**. For Featured Snippet formats and optimization, see **featured-snippet**. --- ## Content Audit Checklist For **article** content audit (hook, QAE, product connection, CTA, references, gaps), see **article-content**. This skill covers generic content optimization (H2 keywords, multimedia, keyword density). --- ## Output Format - **Word count** recommendation by content type - **H2 outline** with keyword placement - **Keyword density** check (avoid stuffing) - **Structure** (tables, lists) for Featured Snippet opportunity; see **featured-snippet** - **Multimedia** checklist (images per **image-optimization**; tables, lists) ## Related Skills - **heading-structure**: H1–H6 hierarchy; H2 keyword placement - **content-strategy**: Topic clusters, pillar + cluster - **keyword-research**: Target keywords inform placement - **featured-snippet**: Snippet formats, structure; answer-first - **eeat-signals**: E-E-A-T; original images, trust - **image-optimization**: Alt, captions, format, LCP, responsive, image sitemap - **video-optimization**: Video SEO; VideoObject; video sitemap - **competitor-research**: Competitor length and structure as reference - **article-content**: Article word count by type; Content Audit Checklist; article body creation
When the user wants to analyze competitors for SEO, content, backlinks, or positioning. Also use when the user mentions "competitor analysis," "competitor re...
--- name: competitor-research description: When the user wants to analyze competitors for SEO, content, backlinks, or positioning. Also use when the user mentions "competitor analysis," "competitor research," "competitor keywords," "competitor backlinks," "link gap," "content gap," "competitor content," "competitive analysis," or "competitor comparison." For content roadmap, use content-strategy. metadata: version: 1.2.1 --- # SEO Content: Competitor Research Guides competitor research for SEO, content, backlinks, and positioning. Use when planning content, auditing articles, building links, or evaluating market position. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Research Types | Type | Purpose | Output | |------|---------|--------| | **Keyword/topic** | Topics competitors rank for; gaps | Keyword opportunities; content ideas | | **Content** | Structure, length, gaps vs top rankers | Length target; H2 structure; content gaps | | **Backlink** | Link profile; sites linking to competitors | Link gap; outreach targets | | **Pricing** | Competitor pricing, positioning | Pricing context; differentiation | | **SEO metrics** | Organic traffic, rankings vs competitors | Benchmark; opportunity areas | ## Competitor Keyword / Topic Analysis | Method | Practice | |--------|----------| | **Reverse engineering** | Analyze competitor titles, H1, URL; identify topics they rank for | | **SERP overlap** | Keywords with overlapping top-ranking pages → same cluster; #4–10 = opportunity | | **site: operator** | `site:competitor.com` to see indexed pages | | **Tool** | Ahrefs, Semrush—competitor keyword overlap, gap analysis | **Output**: Keyword opportunities; topics competitors cover that you don't. ## Competitor Content Analysis | Element | Check | |---------|-------| | **Word count** | Top 10 average; length target for your content | | **H2 structure** | Topics covered; structure to adopt | | **Content gaps** | What top rankers cover that you miss | | **Keyword placement** | Primary keyword in title, H1, first 100 words | | **Format** | Lists, tables, FAQ; match or improve | **Use when**: Auditing or creating articles; see **article-page-generator** for Research Phase integration. ### Competitor Article Fetch Workflow (for Article Analysis) When analyzing or auditing a single article, use this lightweight workflow to obtain competitor articles: 1. **Obtain URLs**: From user, project-context Section 11, or web search for `"[target keyword]"` to find top-ranking pages 2. **Fetch content**: Use mcp_web_fetch or WebSearch to fetch 2–3 top-ranking pages 3. **Analyze**: Word count, H2 structure, keyword placement, content gaps, CTA, schema 4. **Output**: Competitor URLs, brief structure comparison, content gaps, length target, keyword opportunities **Output format**: Competitor URLs; word count and H2 structure per URL; content gaps vs your article; recommended length target; keyword opportunities (terms top rankers use that your article misses). ## Competitor Backlink Analysis | Action | Purpose | |--------|---------| | **Compare profiles** | Your backlinks vs competitors | | **Link gap** | Sites linking to competitors but not you | | **Opportunity** | Outreach to those sites; content they might link to | **Tools**: Ahrefs, Semrush—Link Intersect, competitor backlink reports. See **backlink-analysis**. ## Competitor Pricing | Use | Practice | |-----|----------| | **Positioning** | Where you sit vs competitors | | **Differentiation** | Value prop when price differs | | **Alternatives pages** | Who to include; how to position | See **pricing-strategy**, **alternatives-page-generator**. ## Data Sources | Source | Use | |--------|-----| | **SimilarWeb** | Traffic, engagement, traffic sources by domain | | **Ahrefs** | Competitor domains, backlinks, DR | | **SEMrush** | Organic competitors, traffic share | | **GA** | Referral traffic, acquisition by source | | **PostHog** | Competitor feature usage (if tracked) | ## Report Workflow 1. **Parse** — Read Excel/CSV, infer domain, visits, traffic sources, etc. from headers 2. **Enrich** — Web search, visit competitor sites; read `project-context.md` if present 3. **Build** — Structure data for report 4. **Generate** — Output report in chosen format ## Output Format - **Competitors** identified - **Research type** (keyword, content, backlink, pricing) - **Findings** (gaps, opportunities, benchmarks) - **Recommendations** (content to create, links to pursue, positioning) ### Report Structure Reference | Section | Content | |---------|---------| | Executive Summary | Key findings (top 3), top 3 recommendations | | Competitor Overview | Competitor, category, market position, key strength | | Product Comparison | Feature/capability vs Us vs Competitors | | SWOT Analysis | Our strengths/weaknesses/opportunities/threats; competitor deep dives | | Marketing & Messaging | Value prop, target audience, key channels | | Gaps & Opportunities | Gap, opportunity, priority | | Prioritized Recommendations | Recommendation, impact, effort, owner | ## Related Skills - **keyword-research**: Competitor reverse; keyword discovery - **article-page-generator**: Competitor article analysis in Research Phase - **content-strategy**: Competitor analysis for topic mapping - **content-optimization**: Competitor length and structure as reference - **backlink-analysis**: Competitor backlink comparison; link gap - **seo-monitoring**: Competitive comparison; organic vs competitors - **alternatives-page-generator**: Competitor selection; comparison framing - **migration-page-generator**: Competitor migration paths - **pricing-strategy**: Competitor pricing context - **affiliate-marketing**: Find affiliates promoting competitors - **directories**: Competitor info for directory submissions
When the user wants to optimize YouTube videos for search, create video descriptions, or improve channel visibility. Also use when the user mentions "YouTube...
--- name: youtube-seo description: When the user wants to optimize YouTube videos for search, create video descriptions, or improve channel visibility. Also use when the user mentions "YouTube SEO," "YouTube description," "YouTube tags," "YouTube thumbnail," "YouTube title," "YouTube channel," or "video SEO." For YouTube ads, use youtube-ads. metadata: version: 1.1.1 --- # Platforms: YouTube SEO Guides YouTube video and channel optimization for search and discovery. **Google now prioritizes YouTube video results** in search; YouTube + Reddit comprise ~78% of social media citations in AI Overviews. Title, description, and thumbnail form an interconnected system; channels using systematic keyword strategies see 156% longer view durations, 89% better CTR, and 312% higher search discovery. Use this skill when optimizing videos for YouTube search, Google search, and AI citation. For website-embedded video SEO, see **video-optimization**. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 6 (Keywords), 11 (Content Strategy). Identify: 1. **Video type**: Tutorial, review, vlog, Shorts 2. **Target keyword**: Primary and secondary 3. **Audience**: Subscribers vs casual viewers ## Video Titles | Rule | Guideline | |------|-----------| | **Length** | Under 60 characters; mobile may show partial | | **Keyword** | Primary keyword in first 5–55 characters | | **Structure** | Social proof/authority + emotional trigger + primary keyword | | **Style** | Conversational; avoid keyword stuffing | | **Avoid** | ALL CAPS except emphasis | ## Video Descriptions | Rule | Guideline | |------|-----------| | **First 2–3 sentences** | Primary and secondary keywords naturally; meta description under 160 chars | | **Links** | Website, store, relevant resources | | **Readability** | Natural flow; help search understand topic | ## Tags - Help YouTube understand content; titles and descriptions matter more - Use relevant tags; avoid over-optimization ## Thumbnails 90% of best-performing videos use custom thumbnails. | Rule | Guideline | |------|-----------| | **Contrast** | High contrast; readable fonts; bold colors | | **Composition** | Rule of thirds; simple, uncluttered | | **Audience** | Consider subscribers vs casual viewers | | **Test** | What works evolves; test styles | ## Title + Description + Thumbnail Reinforce the same core message across all three; target different algorithm aspects. ## Output Format - **Title** options (under 60 chars) - **Description** (first 160 chars + full) - **Tags** (relevant set) - **Thumbnail** guidance (elements, text, composition) ## YouTube in Google Search & GEO | Context | Implication | |---------|-------------| | **Google prioritization** | YouTube is core search infrastructure; 48.6B monthly visits; video results favored in main SERP, video mode, Discover | | **AI Overviews** | YouTube citations surged 25.21% since Jan 2025; instructional (+35.6%), visual demos (+32.5%); long-form (94%) dominates | | **GEO** | YouTube + Reddit = ~78% of social media citations; optimize for AI citation. See **generative-engine-optimization** | [Search Engine Land](https://searchengineland.com/youtube-seo-ai-overviews-467253), [OtterlyAI](https://otterly.ai/blog/the-youtube-citation-study-2026/) ## Related Skills - **video-marketing**: Video script, hook, structure - **video-optimization**: Website video SEO; VideoObject; video sitemap; embed optimization - **youtube-ads**: YouTube paid ads (TrueView, Bumper) - **content-marketing**: Video as content format - **parasite-seo**: YouTube as high-authority platform - **generative-engine-optimization**: GEO strategy; YouTube as distribution for AI citation
When the user wants to create X (Twitter) post copy, threads, or optimize for X platform. Also use when the user mentions "X post," "X thread," "Twitter post...
--- name: twitter-x-posts description: When the user wants to create X (Twitter) post copy, threads, or optimize for X platform. Also use when the user mentions "X post," "X thread," "Twitter post," "Twitter thread," "tweet," "tweet copy," "thread," "X marketing," "X content," "post to X," "create X post," or "X post copy." For long-form source, use article-content. metadata: version: 1.1.1 --- # Platforms: X (Twitter) Guides X post copy creation and optimization. Use for generating publish-ready posts, threads, and content that performs on X. Suitable for copy agents, design agents (image specs), and video agents (video post specs). **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Output: Publish-Ready Copy This skill enables agents to generate X post copy that can be published directly. Output includes character-counted text, thread structure, and platform-compliant formatting. ## Character Limits | Type | Limit | Notes | |------|-------|-------| | **Standard post** | 280 characters | Most users | | **Premium** | 25,000 characters | X Premium subscribers | | **URL** | Counts as 23 chars | t.co shortens all links | | **Emoji** | ~2 chars each | Varies by emoji | ## Optimal Lengths (Engagement) | Use Case | Characters | Purpose | |----------|------------|---------| | **General** | 71-100 | Sweet spot for engagement | | **Promotional** | 120-130 | Product/offer posts | | **Question** | 60-80 | Drive replies | | **Retweet-friendly** | ~116 | Leaves room for "RT @user:" | ## Thread Format - **Structure**: 3-5 connected posts; number as 1/5, 2/5, etc. - **First post**: Strong hook; no "thread" in first line - **Last post**: CTA, summary, or question - **Each post**: ~80 chars; can stand alone ## Post Structure (Hook + Value + CTA) | Part | Ratio | Guideline | |------|-------|-----------| | **Hook** | 10% | First 1-2 lines; question, fact, or emotion; ~50 chars | | **Value** | 70% | Practical info; use thread for depth | | **CTA** | 20% | Call for reply, question, or action | End with open question to drive replies. Thread structure can extend impressions ~10x. ## Algorithm (Grok AI) ### Signal Weights | Signal | Impact | |--------|--------| | **Replies** | Highest (~54-75x likes); quality > quantity | | **Author replies** | Active reply chains ~75x visibility | | **Bookmark** | 2026 signal; saves boost recommendation | | **Media** | Images/video ~2x; video 2-4x exposure | | **External links** | Reduce score ~50%; prefer internal refs | | **Post limit** | 5-8/day; >10/day reduces later visibility ~80% | **Content**: Open questions, controversial views, stories; avoid "RT if agree" bait. ### TweepCred | Threshold | Effect | |-----------|--------| | **< 65** | Only last 3 posts enter For You | | **New accounts** | Need +17 to appear in feed | | **Blue V** | Auto 100 points | Monitor account health; avoid spam, bulk ops, excessive links. ### Distribution Posts tested in small group first; early interaction (first 30 min) decides reach. Niche consistency helps SimClusters match. ## Link Optimization | Practice | Guideline | |----------|-----------| | **Penalty** | External links ~-50%; Regular accounts: link posts 0% engagement since 2025 | | **Placement** | Put link in reply, not main post | | **Ratio** | Max 1 link per 5 posts | | **Premium** | Premium+ safest for links (~0.25-0.3% engagement) | | **Preview** | Title ≤70 chars, description ≤200 chars; 1200×628 image | ## Premium Impact | Tier | Reach | Link posts | |------|-------|------------| | **Regular** | <100/post | 0% engagement | | **Premium ($8)** | ~600/post | ~0.25-0.3% | | **Premium+ ($40)** | ~1550/post | Safest for links | Premium ~10x reach vs Regular. If X is core channel, Premium helps. ## Video - **Exposure**: 2-4x vs text - **Length**: 8-30s short video preferred - **VQV**: High video completion boosts score 2-3x ## Content Ratio | Type | Share | Use | |------|-------|-----| | **Value** | 70% | Education, how-to, insights | | **Interaction** | 20% | Polls, questions, AMA | | **Promo** | 10% | Product, offers | ## Twitter Cards + SEO Cards (og:image, title, description) boost CTR ~64%, engagement ~26%. Use for Social SEO; X traffic can accelerate Google indexing. For programmatic SEO (template + data pages at scale), use programmatic-seo. ## Image Specs (for Design Agents) | Format | Dimensions | Use | |-------|------------|-----| | **Single image** | 1200×675 (16:9) | Best visibility; no crop | | **Square** | 800×800 | Single image | | **Profile** | 400×400 | Avatar | | **Header** | 1500×500 (3:1) | Banner | | **File** | ~5MB; JPG/PNG | Over 5MB may compress | ## Output Format When generating X copy, provide: 1. **Post text** with character count 2. **Hashtags** (if used; 1-3 recommended) 3. **Thread structure** (if thread) 4. **Image specs** (if design agent needs dimensions) ## Related Skills - **paid-ads-strategy**: X (Twitter) Ads for paid promotion; tech audiences, timely content; see Platform Selection - **influencer-marketing**: X is key influencer platform - **reddit-posts**: Alternative community channel - **programmatic-seo**: Programmatic SEO (template + data pages); X traffic can accelerate indexing - **open-graph, twitter-cards**: OG and Twitter Card tags for X link previews - **visual-content**: Cross-channel visual planning; X image specs in context
When the user wants to create TikTok video captions, scripts, or optimize for TikTok. Also use when the user mentions "TikTok post," "TikTok caption," "TikTo...
--- name: tiktok-captions description: When the user wants to create TikTok video captions, scripts, or optimize for TikTok. Also use when the user mentions "TikTok post," "TikTok caption," "TikTok video," "post to TikTok," "TikTok script," "TikTok content," "TikTok copy," "TikTok hashtags," or "TikTok marketing." For TikTok ads, use tiktok-ads. metadata: version: 1.0.1 --- # Platforms: TikTok Guides TikTok caption and video script creation. Use for generating publish-ready captions and video specs. Suitable for copy agents, video agents (format, length), and design agents (thumbnail). **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Output: Publish-Ready Copy This skill enables agents to generate TikTok captions and video scripts. Captions drive SEO, accessibility, and watch time (12-20% increase with captions). 80%+ watch without sound. ## Caption Structure | Element | Length | Purpose | |--------|--------|---------| | **Hook** | 5-7 words | Grab attention; create curiosity | | **Context** | 1-2 sentences | Size, price, backstory--info video doesn't show | | **CTA** | Optional | "Save this," "Link in bio" | **Hook examples**: "Stop scrolling if you sell on Etsy," "This took me 47 attempts," "Wait for the final result" ## Video Specs (for Video Agents) | Spec | Value | Notes | |------|-------|-------| | **Aspect ratio** | 9:16 (portrait) | Standard; fills mobile | | **Resolution** | 1080x1920 px | Recommended | | **Length** | 3 sec - 10 min | 15-60 sec for tips; 1-3 min for tutorials | | **Format** | MP4, MOV | H.264, AAC | | **File size** | <=5MB (Android), <=88MB (iOS) | Varies by device | ## Caption Best Practices - **Contrast**: Strong font/background contrast; 75% watch mute - **Auto-captions**: TikTok's built-in; algorithm rewards; edit for accuracy - **Keywords**: Improve search visibility - **Readability**: Test on multiple devices ## Content by Length | Length | Use | |--------|-----| | **15-60 sec** | Quick tips, humor, hooks | | **1-3 min** | Tutorials, storytelling | | **3-10 min** | Deep dives (longer format) | ## Output Format When generating TikTok content, provide: 1. **Caption** (hook + context + CTA) 2. **Video script** (if video agent) 3. **Video specs** (9:16, 1080x1920, length) 4. **Hashtags** (3-5; niche-relevant) ## Related Skills - **tiktok-ads**: Paid promotion on TikTok; In-Feed, Spark Ads (boost organic); video specs and captions align with organic content - **influencer-marketing**: TikTok is key influencer platform - **twitter-x-posts**: Cross-posting short-form video
When the user wants to create Reddit post copy, comments, or optimize for Reddit. Also use when the user mentions "Reddit post," "subreddit," "r/," "Reddit m...
--- name: reddit-posts description: When the user wants to create Reddit post copy, comments, or optimize for Reddit. Also use when the user mentions "Reddit post," "subreddit," "r/," "Reddit marketing," "post to Reddit," "Reddit thread," "Reddit comment," "Reddit copy," "Reddit content," or "Reddit engagement." For Reddit ads, use reddit-ads. metadata: version: 1.0.1 --- # Platforms: Reddit Guides Reddit post and comment creation. Use for generating publish-ready posts that follow subreddit norms. Suitable for copy agents. Design agents can use for image post context. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Output: Publish-Ready Copy This skill enables agents to generate Reddit post copy (title + body) that respects platform rules and community culture. Output is subreddit-aware and engagement-optimized. ## Core Rules | Rule | Practice | |------|----------| | **90/10 principle** | 90% value, 10% promotional | | **Self-promotion** | Max 1 in 6 posts promotional | | **Subreddit rules** | Always check sidebar before posting | | **Flair** | Required by many subs; wrong flair = removal | | **Title format** | Some subs require [tags]; check top posts | ## Post Structure ### Title - **Concise, specific, accurate**--no clickbait - Match subreddit format (e.g., [Discussion], [Question]) - Factual; save opinions for body/comments ### Body - **Value-first**: Lead with help, insight, or story - **Casual, friendly tone**--like talking to a friend - **Engagement**: Open-ended questions, invite discussion - **Formatting**: Markdown supported; use lists, headers for readability ## Content Types | Type | Use | |------|-----| | **Experience sharing** | Highest engagement; authentic stories | | **Q&A** | Build trust; answer questions | | **Case study** | Product value; must be transparent | | **Tool recommendation** | Context + honest pros/cons | ## Algorithm Factors - **Upvote/downvote ratio** matters more than raw score - **Early engagement** weighs more; post at peak hours - **Karma**: 100-1000+ recommended before promotional posts - **Author interaction**: Reply to comments; boosts ranking ## Formatting (Markdown) - **Bold**: `**text**` - **Italic**: `*text*` - **Lists**: `-` or `1.` - **Links**: `[text](url)` ## Output Format When generating Reddit copy, provide: 1. **Title** (subreddit-appropriate) 2. **Body** (value-driven, formatted) 3. **Suggested flair** (if known) 4. **Subreddit reminder**: "Verify rules before posting" ## Related Skills - **reddit-ads**: Paid promotion on Reddit; Promoted Posts, subreddit targeting; native creative aligns with organic post style - **twitter-x-posts**: Alternative platform - **cold-start-strategy**: Cold start; Reddit as launch channel - **parasite-seo**: Parasite SEO strategy; Reddit as high-authority platform - **grokipedia-recommendations**: Wiki/encyclopedia platform for GEO and parasite SEO - **community-forum**: Forum and community promotion; HN, Indie Hacker; community invitation tactics - **indie-hacker-strategy**: Indie hacker first 100 users; Reddit for niche products - **influencer-marketing**: Reddit can complement influencer outreach
When the user wants to create Pinterest Pins, optimize Pin descriptions, or grow Pinterest presence. Also use when the user mentions "Pinterest," "Pin," "Pin...
--- name: pinterest-posts description: When the user wants to create Pinterest Pins, optimize Pin descriptions, or grow Pinterest presence. Also use when the user mentions "Pinterest," "Pin," "Pinterest SEO," "Pinterest description," "Pinterest board," or "Pinterest marketing." For asset specs, use visual-content. metadata: version: 1.0.1 --- # Platforms: Pinterest Guides Pinterest Pin creation and optimization. Pinterest users search differently than Google; long-tail keywords like "easy fall dinner recipes" perform better than broad terms. Use this skill when creating Pins, optimizing boards, or planning Pinterest content. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 6 (Keywords), 11 (Content Strategy). Identify: 1. **Content type**: Product, recipe, tutorial, inspiration 2. **Board**: Where Pin will be saved first (shapes Pinterest's understanding) 3. **Goal**: Traffic, sales, email signups ## Pin Title | Rule | Guideline | |------|-----------| | **Length** | Up to 100 chars; first 40 visible in feeds | | **Keyword** | Primary keyword in first 40 chars | | **Business name** | In first sentence → 54% higher email signup conversion | ## Pin Description | Rule | Guideline | |------|-----------| | **Length** | 220–232 chars optimal | | **Keywords** | Main + 2–3 related; natural placement | | **CTA** | Clear, actionable → 70% signup boost, 6% sales lift | | **Price** | When relevant → 28% sales increase | ## Board SEO - **Board name** and description are ranking factors - **First save** board shapes Pinterest's content understanding - Use keywords in board title and description ## 2025 Algorithm Notes - **Fresh content**: New URL + new image + new board = max distribution - **Alt text**: Pins with alt text earn ~25% more impressions, 123% more clicks - **Consistency**: Keyword-optimized content to relevant boards ## Output Format - **Title** (under 100 chars) - **Description** (220–232 chars) - **Board** recommendation - **Alt text** suggestion ## Related Skills - **content-marketing**: Pinterest as channel - **display-ads**: Pinterest Ads (if paid) - **visual-content**: Cross-channel visual planning; Pinterest Pin specs in context - **url-slug-generator**: URL for landing page
When the user wants to write, publish, republish, or optimize posts on Medium.com (canonical tags, distribution, Medium SEO). Also use when the user mentions...
--- name: medium-posts description: When the user wants to write, publish, republish, or optimize posts on Medium.com (canonical tags, distribution, Medium SEO). Also use when the user mentions "Medium," "Medium article," "Medium story," "Medium publishing," "canonical Medium," or "publish on Medium." Not for general parasite SEO when Medium is not the target platform—use parasite-seo. For AI search visibility strategy, use generative-engine-optimization. metadata: version: 1.1.0 --- # Platforms: Medium Guides Medium publishing for parasite SEO and content distribution. Medium's domain authority helps content rank faster than on new sites; articles can reach page 1 within days. Use this skill when planning Medium content or republishing from your site. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 6 (Keywords), 11 (Content Strategy). Identify: 1. **Content**: Original or republish 2. **Canonical**: If republish, set canonical to original URL 3. **Goal**: Traffic, backlinks, AI citations ## Why Medium for Parasite SEO | Benefit | Detail | |---------|--------| | **Fast rankings** | Page 1 within days vs months on own domain | | **Authority** | Leverages Medium's domain authority | | **AI-friendly** | Frequently cited in AI search results | | **Backlinks** | Traffic-generating articles attract links | ## Canonical Links When republishing: Set canonical to your original URL in Medium settings. Prevents duplicate content penalties; signals original source. ## Content Best Practices - **Match intent**: Keyword-focused; solve problem or answer question - **Quality**: Same quality as on your site - **CTA**: Link to relevant site pages; don't over-promote ## Output Format - **Title** (keyword-optimized) - **Structure** (for original) or **canonical** setup (for republish) - **Internal links** to site - **CTA** placement ## Related Skills - **parasite-seo**: Parasite SEO strategy; Medium as platform - **article-page-generator**: Article structure for republish - **link-building**: Medium as backlink source - **grokipedia-recommendations**: GEO; AI search visibility
When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions "LinkedIn post," "LinkedIn article," "professional...
--- name: linkedin-posts description: When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions "LinkedIn post," "LinkedIn article," "professional post," "post to LinkedIn," "LinkedIn content," "LinkedIn copy," "B2B LinkedIn," "LinkedIn engagement," or "LinkedIn marketing." For LinkedIn ads, use linkedin-ads. metadata: version: 1.1.1 --- # Platforms: LinkedIn Guides LinkedIn post copy creation and optimization. Use for generating publish-ready professional content. Suitable for copy agents and design agents (image specs). **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Output: Publish-Ready Copy This skill enables agents to generate LinkedIn post copy optimized for engagement. Output includes character-counted text and structure for the "See more" threshold. ## Character Limits | Type | Limit | Notes | |------|-------|-------| | **Post** | 3,000 characters | Optimal: 1,300–1,600 | | **First line (critical)** | 210–235 chars | Visible before "See more"; 60–80% decide here | | **Short posts** | 100–200 chars | Polls, announcements, quotes | ## Optimal Length by Content Type | Type | Characters | Use | |------|------------|-----| | **Short** | 100–200 | Polls, announcements, quotes | | **Medium** | 300–1,200 | Case studies, tips, BTS | | **Long** | 1,200–2,000 | Thought leadership, analysis | | **Sweet spot** | 1,300–1,600 | Highest engagement | | **Avoid** | >2,000 | ~35% engagement drop | ## First Line (Hook) - **Place key message in first 140 chars** - **Strong openings**: Specific results, pain points, bold claims, surprising stats - **Avoid**: Vague teases, hashtag-first, generic greetings ## Image Specs (for Design Agents) | Format | Dimensions | Use | |--------|------------|-----| | **Single image** | 1200×627 (1.91:1) | Feed; link previews | | **Square** | 1200×1200 | Single image | | **Carousel** | Up to 20 images | Multi-image post | | **File** | ≤10 MB; JPG/PNG | Native uploads perform better | | **Vertical** | Preferred | 88% browse on mobile | ## Best Practices - **Mobile-first**: 88% users on mobile - **Polls & PDFs**: Highest reach - **Post frequency**: Weekly minimum for companies - **Alt text**: Add for accessibility ## Output Format When generating LinkedIn copy, provide: 1. **First line** (≤210 chars; hook) 2. **Full post** with character count 3. **Hashtags** (3→; end of post) 4. **Image specs** (if design agent needs dimensions) ## Related Skills - **linkedin-ads**: Paid promotion on LinkedIn; Sponsored Content, Lead Gen Forms; professional tone aligns with organic posts - **influencer-marketing**: LinkedIn influencers for B2B - **about-page-generator**: Professional brand alignment - **visual-content**: Cross-channel visual planning; LinkedIn image specs in context
When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "su...
---
name: grokipedia-recommendations
description: When the user wants to add recommendations, links, or content to Grokipedia. Also use when the user mentions "Grokipedia," "GEO wiki," "AI encyclopedia," "suggest Grokipedia article," "Grokipedia citation," "Grokipedia listing," "AI search citation," "GEO visibility," or "Grokipedia optimization." For multi-platform parasite SEO strategy, use parasite-seo. For broad AI search visibility, use generative-engine-optimization.
metadata:
version: 1.1.0
---
# Platforms: Grokipedia
Guides adding recommendations, links, or content to Grokipedia. Grokipedia is a high-authority platform for parasite SEO and GEO (AI citation visibility). See **parasite-seo** for parasite SEO strategy. Grokipedia is xAI's AI-generated encyclopedia; ChatGPT, Perplexity, and other AI tools cite it.
**On each invocation**: On **first use** in the conversation, output the complete response (Introduction, Importance, Methods, Rules, Avoid, Action). On **subsequent use** or when the user asks to skip (e.g., "just do it", "skip intro", "I already know"), go directly to Action.
**Growth channel value**: Grokipedia is worth investing in as a growth channel for GEO and backlinks. It is positioned as a potential future Wikipedia—Wikipedia's traffic and domain authority are well-established; Grokipedia, though newer, is already being cited by major AI products and its citation share is rising.
## Scope
- **Suggest Article**: Request new topics; Grok AI reviews and may create
- **Suggest Edit**: Propose corrections or additions to existing articles
- **Report Error**: Flag factual inaccuracies, outdated info, citation errors
- **Parasite SEO / GEO**: Use Grokipedia's authority for backlinks and AI citation (see **parasite-seo** for strategy)
## What Is Grokipedia
- **Platform**: AI-generated online encyclopedia by xAI (Grok); launched October 2025
- **Content**: ~6M+ articles; AI-generated, fact-checked by Grok; users cannot edit directly
- **GEO relevance**: ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot cite Grokipedia for factual queries
- **Parasite SEO**: High-authority domain; links from Grokipedia pass authority; content placement for distributed visibility (see **parasite-seo**)
### Why It Matters (Citation Data)
| Metric | Note |
|--------|------|
| ChatGPT citations | ~263K responses cited Grokipedia from 13.6M prompts; ~95K individual pages. Wikipedia: 2.9M responses—quite a way off, but impressive for how new they are. (Source: SEO tools, Jan 2026) |
| Citation share trend | ~0.01–0.02% of ChatGPT citations/day; steadily increasing since mid-Nov 2025 |
| AI product adoption | Spike in Google AI (Gemini, AI Overviews, AI Mode) and Copilot in Dec 2025; ChatGPT cites Grokipedia most |
| Use case | Niche, obscure, highly specific factual queries; ChatGPT often features Grokipedia as one of the first sources cited |
**Bottom line**: Grokipedia is still secondary to Wikipedia but growing. Early participation can capture future authority as AI citation becomes more central—similar to Wikipedia's dominance in traditional search.
## How to Contribute
### Prerequisites
- **Login required**: Google, X, Apple, or email account
- **URL**: grokipedia.com
### Foundation for Promotion
The basis for Grokipedia promotion is an **article published online** that includes your product and can be crawled by Grok. Grok discovers sources via web search when creating or editing articles; if your page is not indexable or does not mention the topic, it will not be cited. Higher SEO ranking improves discoverability but is not required—Grok may still find and cite relevant content that ranks lower.
### Suggest New Article
1. Click **bulb icon** on homepage, or search for a topic and click **"Request this article"**
2. Describe why Grokipedia should add the article
3. Include aspects you want covered
4. **Status flow**: Pending → In Progress → Processing → Created
5. Grok reviews; no guaranteed approval; review typically within ~2 hours
### Suggest Edit (Existing Articles)
1. **Highlight** problematic or incomplete text
2. Click **"Suggest Edit"** (pop-up form)
3. Provide correction and **supporting evidence** (URLs, sources)
4. Grok reviews; approved edits typically applied within ~2 hours
### Report Error
| Error type | Examples |
|------------|----------|
| Factual inaccuracies | Wrong dates, numbers, definitions |
| Outdated information | Obsolete facts |
| Misleading context | Framing issues |
| Citation errors | Broken links, unsupported claims |
| Technical bugs | Formatting, display |
### Grok Review Constraints
Grok AI evaluates all suggestions and is **strict**: it rejects promotional content and explicit third-party citation requests. Do not mention your brand or URL in Article Topic, Additional Details, Summary, or Edit content. The tactics below work by providing genuinely useful, factual content and letting Grok discover your source through "Add another source" (Suggest Edit) or web search (Suggest Article).
---
## Two Tactics for GEO & Citation (Field-Tested)
Two practical ways to get Grokipedia to cite your content: **Suggest Article** (new topic) and **Suggest Edit** (existing page). Both can lead to backlinks and AI citation when done well.
**When the user asks to promote a product/brand/topic**: Output the full response per the Required Output Structure (Introduction, Importance, Methods, Rules, Avoid, Action)—do not output only the action.
### Tactic 1: Suggest New Article —Induce Creation That Cites Your Content
**Goal**: Propose a topic so Grokipedia creates a new article; Grok will search for sources and may cite your page if it matches the query.
**Critical rule**: **Do not include your URL** in the suggestion. Grok flags direct URLs; use a "stealth" approach instead.
| Field | Best practice | Why it works |
|-------|---------------|---------------|
| **Article Topic** | Specific, encyclopedic (e.g., "3D Model Generator," "Virtual Staging Software," "Marie Curie") | Vague topics ("Technology") get rejected; precise topics pass AI validation and match Grokipedia's scope |
| **Additional Details** | Describe what aspects to cover, why the topic matters, and specific areas of interest | Grok uses this to shape the article and search for sources; your phrasing influences which queries it runs |
| **Content strategy** | Rewrite your article's key concepts as neutral, factual "aspects to cover"—definitions, use cases, types, history | Grok searches for these concepts; if your page ranks for them, it may be cited as a source |
**Tips for great suggestions** (from Grokipedia guidelines):
- Be specific about the topic or subject
- Explain why this article would be valuable
- Mention any specific areas of interest
**Stealth approach** —How to use your content without URLs:
1. Extract from your article: definitions, categories, use cases, technical terms, examples.
2. Turn them into "aspects to cover" and "areas of interest" in neutral, encyclopedic language.
3. Example: If your article covers "AI-powered 3D model generation for e-commerce," suggest: *"Cover types of 3D model generators (AI-based, photogrammetry, CAD), use cases in e-commerce and product visualization, and how they differ from traditional modeling."*
4. Grok will search for these terms; if your page is relevant and authoritative, it may be included as a source.
**Example structure** (desensitized):
```
Article Topic: [Specific topic, e.g., 3D Model Generator]
Additional Details: This topic is important because [reason]. Please cover: [definition], [types/categories], [use cases], [how it differs from X]. Specific areas of interest: [subtopics from your content, phrased neutrally].
```
---
### Tactic 2: Suggest Edit —Enrich Existing Articles to Cite Your Content
**Goal**: Improve an existing Grokipedia page so Grok adopts your article as a supporting source.
**Critical rule**: **Do not mention your brand or URL** in Summary or Edit content. Add your URL only in "Add another source" alongside other authoritative sources.
| Field | Best practice | Why it works |
|-------|---------------|---------------|
| **Summary** | Brief, factual (e.g., "Expanded Virtual Staging Methods section with additional techniques") | Sounds like a normal correction; avoids promotional tone |
| **Edit content** | Rich, creative, factually accurate—expand or replace the highlighted passage | Grok prefers substantive edits; generic text is less likely to be accepted |
| **Add another source** | Your URL + 1–2 other authoritative sources (industry reports, trade publications) | Grok validates against sources; mixing your URL with established sources improves acceptance |
**Tips for Edit content**:
- Use double quotes for exact phrases you want to add or replace (helps with Ctrl+F when applying).
- Expand thin sections (e.g., "showcase multiple style options") into fuller subsections (e.g., Virtual Staging Methods: furniture replacement, style variation, room redesign).
- Keep tone neutral and encyclopedic; avoid marketing language.
**Example** (desensitized—expanding a thin "Virtual Staging Methods" section):
| Field | Example |
|-------|---------|
| **Summary** | "Expanded Virtual Staging Methods with additional techniques and use cases" |
| **Edit content** | "Virtual staging methods include furniture replacement, style variation (e.g., modern, traditional, minimalist), and full room redesign. This approach enhances client engagement by providing immersive previews of potential designs, enabling designers to "present multiple style options efficiently" and help clients visualize spaces before physical staging. Common techniques include AI-assisted furniture placement, material and color swapping, and virtual renovation overlays." |
| **Add another source** | Your article URL + 1–2 authoritative sources (e.g., Forbes, TechCrunch, industry report) |
**Why this works**: Grok needs verifiable sources. By adding substantive, well-sourced content and including your URL in "Add another source" with other credible links, you increase the chance Grok will adopt your page as a reference.
### Reference Instances
Field-tested examples: a marketer's site was successfully cited as a source via Suggest Article and Suggest Edit. Products mentioned in the site's articles also appear in Grokipedia, enabling both backlinks and product visibility. Inspect these pages to see how content and sources are structured.
| Type | Example page |
|------|--------------|
| **Suggest Edit** | [AI browser](https://grokipedia.com/page/ai_browser) |
| **Suggest Article** | [Accent conversion](https://grokipedia.com/page/Accent_conversion), [AI Video Effects Tools](https://grokipedia.com/page/AI_Video_Effects_Tools), [Creator contest](https://grokipedia.com/page/Creator_contest), [Lifetime deal](https://grokipedia.com/page/Lifetime_deal), [Creator programs in AI and SaaS marketing](https://grokipedia.com/page/Creator_programs_in_AI_and_SaaS_marketing), [Web Animation Libraries](https://grokipedia.com/page/Web_Animation_Libraries) |
## Best Practices
| Practice | Purpose |
|----------|---------|
| **Provide sources** | Citations improve approval; use authoritative URLs |
| **Be factual** | Grok evaluates accuracy; avoid promotional language |
| **Relevant links** | When suggesting additions, include your site only if genuinely relevant and cited |
| **Topic alignment** | Request articles that fit encyclopedic scope; avoid pure product pages |
| **Patience** | Review is AI-driven; typically within ~2 hours |
| **No URL in Suggest Article** | Grok detects and may reject direct URLs; embed concepts as "aspects to cover" instead |
| **Brand-free Summary/Edit** | For Suggest Edit, keep Summary and Edit content brand-neutral; add your URL only in "Add another source" |
## Parasite SEO & GEO Context
- **Parasite SEO**: See **parasite-seo** for full strategy. Grokipedia fits Tier 6 (Wiki & Structured Knowledge) in distributed authority frameworks.
- **GEO**: AI tools cite Grokipedia; having your brand, product, or expertise represented can influence AI-generated answers.
- **Risk**: Google's Site Reputation Abuse policy (2024) targets manipulative third-party content. Ensure contributions are genuinely useful, not purely for link/mention manipulation.
## Output Format
**When this skill is invoked**, always output a **complete response** covering all sections below. Do not output only the action—include introduction, importance, methods, rules, avoidances, and action.
### Required Output Structure (in order)
1. **Introduction** —What Grokipedia is: AI-generated encyclopedia by xAI (Grok), launched Oct 2025; ~6M+ articles; ChatGPT, Perplexity, Google AI Mode, Gemini, Copilot cite it; users suggest, Grok reviews; no direct editing.
2. **Foundation** —Prerequisite: an article published online that includes the product and can be crawled by Grok; higher SEO ranking helps but is not required.
3. **Importance** —Why it matters for GEO and parasite SEO (see **parasite-seo**): high-authority domain; backlinks pass authority; AI tools cite Grokipedia for factual queries; citation share rising; positioned as potential future Wikipedia; early participation captures future authority.
4. **Methods** —Two ways to get cited:
- **Suggest Article**: Propose new topic; Grok creates article and searches for sources; your page may be cited if it matches.
- **Suggest Edit**: Enrich existing page; add your URL in "Add another source"; Grok may adopt it.
5. **Rules** —Grok is strict; must follow:
- No brand or URL in Article Topic, Additional Details, Summary, or Edit content.
- Suggest Article: embed concepts as "aspects to cover"; Grok discovers via web search.
- Suggest Edit: add your URL only in "Add another source" with 1–2 authoritative sources.
- Be factual, neutral, encyclopedic; avoid promotional language.
6. **Avoid** —Do not: include your URL in Suggest Article; mention brand in Summary or Edit content; use vague topics ("Technology"); write marketing copy; expect instant approval (review typically within ~2 hours).
7. **Action** —Ready-to-use copy the user can paste into Grokipedia forms (per templates below). Generate both Suggest Article and Suggest Edit options when promoting a product/brand/topic.
### Suggest Article —Output Template
```
--- Copy to Grokipedia Suggest Article form ---
**Article Topic:**
[Specific, encyclopedic topic, e.g., People search engine]
**Additional Details:**
[Explain importance, aspects to cover, specific areas of interest; no brand or URL; neutral encyclopedic tone]
--- Usage ---
1. Go to grokipedia.com and log in
2. Click the bulb icon or search and click "Request this article"
3. Paste the above into the corresponding fields
4. Ensure your article URL is published and content matches; Grok will search and may cite it
```
### Suggest Edit —Output Template
```
--- Copy to Grokipedia Suggest Edit form ---
**Target page:** [Grokipedia page URL]
**Summary:**
[Brief, factual, e.g., "Expanded [section] with [topic]"]
**Edit content:**
[Rich, neutral, encyclopedic; use "double quotes" for exact phrases to add]
**Add another source:**
- [User's article URL]
- [1–2 authoritative sources, e.g., Forbes, TechCrunch, industry report]
--- Usage ---
1. Open the target Grokipedia page
2. Highlight the passage to modify or expand
3. Click "Suggest Edit" and paste the above into the corresponding fields
```
### Required Output
- **Action**: Suggest Article / Suggest Edit / Report Error
- **Ready-to-use copy**: Complete, copyable copy per the templates above
- **Sources**: User-provided URL (for Suggest Edit "Add another source" only)
## References
- [Grokipedia article suggestions](https://grokipedia.com/page/grokipedia-article-suggestions) —Official guidelines: be specific about topics, explain article value, highlight areas of interest; examples for Suggest Article and Suggest Edit.
- [ChatGPT isn't the only chatbot pulling answers from Elon Musk's Grokipedia](https://www.theverge.com/report/870910/ai-chatbots-citing-grokipedia) —The Verge, Jan 31 2026. ChatGPT, Gemini, AI Overviews, Perplexity, Copilot citing Grokipedia.
## Related Skills
- **parasite-seo**: Parasite SEO strategy; Grokipedia as high-authority platform
- **github**: GitHub as alternative high-authority platform; repos, awesome lists
- **generative-engine-optimization**: GEO strategy, AI citation, distributed authority
- **link-building**: Link acquisition; Grokipedia as potential citation source
- **directory-submission**: Same output pattern—platform context first (Introduction, Importance, Methods, Rules, Avoid), then Action; directory submission for backlinks and human discovery; Grokipedia for AI citation—different placement, complementary
- **reddit-posts**: Alternative high-authority platform for GEO
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user me...
--- name: github description: When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "repository name," "About section," "GitHub description," "GitHub topics," "GitHub Pages," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy. metadata: version: 1.2.0 --- # Platforms: GitHub Guides GitHub for parasite SEO, GEO (AI citation), and curated list creation. GitHub is a Tier 2 Technical Authority platform—high domain authority, fast indexing, very high AI citation probability. Use for repos, README, GitHub Pages, gists, and Awesome-style navigation lists. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Why GitHub for SEO | Factor | Effect | |--------|--------| | **Domain authority** | High DA; repos, gists, Pages rank well | | **Fast indexing** | Search engines crawl GitHub frequently | | **AI citation** | ChatGPT, Perplexity cite GitHub for technical queries; Tier 2 in GEO framework | | **Technical expertise** | Strong expertise signals; structured docs become AI reference material | | **Cross-platform** | Share across Dev.to, Stack Overflow, forums; amplifies visibility | ## Use Cases | Use case | Format | Purpose | |----------|--------|---------| | **Parasite SEO** | Repos, README, Pages, gists | Leverage GitHub authority for rankings and backlinks | | **GEO** | Documentation, tutorials, curated lists | AI tools cite GitHub for technical answers | | **Curated / navigation lists** | Awesome-style repos | Topic-specific resource directories; backlinks, discovery | ## Repository Name, About & README (SEO/GEO Priority) **Ranking weight** (GitHub + Google): Repository name & About ≈ highest; Topics ≈ high; README ≈ high. ### Repository Name | Practice | Guideline | |----------|-----------| | **Descriptive** | Hint at what the project does | | **Keyword-rich** | Include primary keywords (`markdown-editor` not `my-project`) | | **Hyphens** | Separate words (`react-component-library`) | | **Concise** | Shorter = memorable, shareable | ### About Section (Description) | Limit | Guideline | |-------|-----------| | **350 chars** | Hard limit; GitHub enforces | | **~128 chars** | Optimal for brevity; often displayed fully | | **Content** | Primary keyword + natural variations; what it does, who it's for; link to website or docs if space | **Example**: "A fast, lightweight markdown editor for React with live preview, syntax highlighting, and export to PDF. Built with TypeScript." ### Topics | Limit | Guideline | |-------|-----------| | **6–20 topics** | Max 20; 6–10 recommended | | **~50 chars** each | Per topic | | **Format** | Lowercase, hyphens, numbers only | | **Mix** | Technology (react, python), purpose (cli, library), category (seo, ai-tools), community (hacktoberfest) | **Underutilized** but highly effective for discoverability and GEO. ### README Structure & Components | Section | Purpose | SEO/GEO | |---------|---------|---------| | **Title + tagline** | H1 + 1–2 sentence summary; keywords in first paragraph | Critical; first 100 words weighted | | **Table of contents** | Links to H2/H3; for READMEs >500 words | Navigation; crawlability | | **Installation / Quick start** | Prerequisites; exact commands; copy-paste ready | Use-case clarity | | **Usage examples** | Code blocks; common scenarios | Citable; extractable | | **Screenshots / GIFs** | Demo, output; alt text required | Engagement; accessibility | | **Badges** | Build, version, license | Trust signals | | **Contributing** | Link to CONTRIBUTING.md | Community signal | | **License** | Link to LICENSE | Completeness | **Word count**: No hard limit; 500–1,500 words typical for product repos. Lead with value; expand later. ### README GEO / AI Citation | Practice | Guideline | |----------|-----------| | **Answer-first** | Direct answer in first 1–2 sentences (40–60 words) | | **Short paragraphs** | 2–3 sentences max; extractable clarity | | **Question-style headings** | H2/H3 as questions where relevant | | **Data inclusion** | Stats, numbers; cited content ~40% more likely to include data | | **Freshness** | Update regularly; ~76% of cited content updated within 30 days | **Entity signals**: Clear project name, author, maintainer; consistent identity. See **entity-seo**. ### README Checklist - [ ] Project title with keywords - [ ] Concise description in first paragraph - [ ] H2/H3 structure; alt text for images - [ ] Installation + usage examples - [ ] Screenshots or demo - [ ] Badges; Contributing; License - [ ] Internal links to related docs/repos - [ ] 6–20 topics on repo ## Parasite SEO on GitHub ### Key Surfaces | Surface | Use | |---------|-----| | **README** | Landing page for repo; keyword-optimized summary, headings, links | | **GitHub Pages** | Static site; blog, FAQ, docs; additional ranking opportunities | | **Gists** | Micro-content; long-tail keywords; link to repos or external resources | | **Wiki** | Keyword-rich documentation | | **Issues** | Q&A, discussions; indexable | ### Optimization | Element | Practice | |---------|----------| | **Repository title** | Primary keywords; descriptive; hyphens | | **About** | 350 chars max; keyword-rich; primary keyword + natural variations | | **Description** | Secondary keywords; link to website or resources | | **README** | Keyword-optimized summary first; headings, bullet points; screenshots; links to docs, tutorials | | **Topics / tags** | 6–20 relevant topics; 50 chars each | | **GitHub Pages** | Mobile-friendly; metadata; blog/FAQ for extra keywords | ### Gists for Micro-Content - Target specific long-tail keywords - Link back to larger repos or external resources - Share code snippets, small utilities ### Community Engagement - Respond to issues and PRs; builds trust - Contribute to popular projects; backlinks, visibility - Keep repos updated; outdated = lower credibility ## GEO on GitHub | Factor | Practice | |--------|----------| | **README clarity** | Clear, citable paragraphs; direct answers | | **Documentation** | Structured; AI tools parse well | | **Entity signals** | Clear project, author identity; see **entity-seo** | | **Consistency** | Active maintenance; engagement (stars, forks, watchers) | ## Curated / Navigation Lists (Awesome-Style) **Awesome lists** = Curated, topic-specific resource lists on GitHub. Function like navigation directories; high traffic, backlinks, discovery. sindresorhus/awesome (441K+ stars) is the master list; 6,500+ curated lists exist across topics. ### Examples by Category | Category | Examples | |----------|----------| | **Master list** | sindresorhus/awesome — hub of all awesome lists | | **SEO / Marketing** | awesome-seo, awesome-ai-seo, bmpi-dev/awesome-seo | | **AI / ML** | awesome-ai-tools, AITreasureBox, awesome-ai | | **Dev tools** | awesome-tools, awesome-cli, awesome-nodejs | | **Languages** | awesome-python, awesome-javascript, awesome-go | | **Frontend / Backend** | awesome-react, awesome-vue, awesome-django | | **Other** | awesome-security, awesome-gaming, awesome-databases | ### When to Create - You have a niche with many quality resources to curate - Existing lists lack coverage of your topic - You want a backlink asset and topical authority ### List Structure (sindresorhus/awesome guidelines) | Element | Practice | |---------|----------| | **Title** | Clear, focused (e.g., "Awesome SEO," "Awesome AI Tools") | | **Description** | Succinct; scope clear | | **Sections** | Categorized (e.g., Tutorials, Tools, Articles) | | **Items** | Curated, not collected; only include what you recommend | | **Item format** | `- [Name](URL) - Brief description of why it's awesome` | | **License** | CC0 or similar | | **Contributing** | contributing.md for PR process | ### Getting Listed vs. Creating | Action | Use | |--------|-----| | **Submit to existing list** | PR to awesome-* repos; follow list format; contact maintainer | | **Create new list** | When no list exists for your niche; follow awesome guidelines | | **Link between lists** | Link to other awesome lists that cover subjects better | ### Discovery - **sindresorhus/awesome** — Master list of awesome lists - **AwesomeSearch** — Search across awesome lists - **more-awesome** — Directory of awesome lists ## Common Mistakes | Mistake | Avoid | |---------|-------| | **Ignoring engagement** | Not responding to issues/PRs reduces trust | | **Irregular updates** | Outdated repos signal inactivity | | **Incomplete docs** | Lack of clear descriptions frustrates users | | **Generic titles** | Missing keywords reduces discoverability | | **Thin awesome lists** | Low-quality or uncurated items hurt credibility | ## Output Format - **Use case** (parasite SEO / GEO / curated list) - **Repository name, About, Topics** (if optimizing metadata) - **Surface** (README, Pages, gist, awesome repo) - **README structure** (sections, word count, GEO practices if applicable) - **Optimization** (keywords, structure, links) - **Ready-to-use** copy or structure where applicable ## Related Skills - **parasite-seo**: Parasite SEO strategy; GitHub as Tier 2 technical platform - **generative-engine-optimization**: GEO strategy; GitHub for AI citation - **open-source-strategy**: Open source commercialization; GitHub as primary distribution - **directory-submission**: Directory and curated list submission; awesome lists as curated lists - **link-building**: GitHub as link acquisition; repos, gists, awesome lists - **entity-seo**: Entity signals (project, author); Organization, Person
When the user wants to run YouTube ads, set up TrueView or Bumper campaigns, or optimize video ad creative. Also use when the user mentions "YouTube ads," "T...
--- name: youtube-ads description: When the user wants to run YouTube ads, set up TrueView or Bumper campaigns, or optimize video ad creative. Also use when the user mentions "YouTube ads," "TrueView," "Bumper ads," "YouTube Discovery," "video ads," "YouTube campaign," or "in-feed ads." For organic YouTube, use youtube-seo. metadata: version: 1.0.1 --- # Paid Ads: YouTube Ads Guides YouTube advertising: TrueView, Bumper, and Discovery (in-feed) formats. Use this skill when planning or optimizing YouTube ad campaigns. For Google Search/Display/PMax, see **google-ads**. For organic YouTube optimization, see **youtube-seo**. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read Sections 3 (Value Proposition), 4 (Audience). Identify: 1. **Goal**: Awareness, consideration, conversion 2. **Budget**: Bumper cheaper; TrueView for scale 3. **Creative**: Existing video or net-new ## Ad Formats | Format | Length | Skippable | Best For | |--------|--------|-----------|----------| | **TrueView Skippable** | 12 sec+ | After 5 sec | Reach; large audiences | | **TrueView Non-skippable** | 15–20 sec | No | Full message; guaranteed view | | **TrueView for Action** | — | — | Conversions; CTA-focused | | **Bumper** | 6 sec or less | No | Brand awareness; memorable; lower cost | | **Discovery (In-Feed)** | Thumbnail + text | — | Search, related videos, homepage; interest targeting | ## Format Selection | Goal | Format | |------|--------| | **Brand awareness** | Bumper | | **Website traffic** | TrueView | | **Conversions** | TrueView for Action | | **Interested audiences** | Discovery | ## Creative Guidelines - **Bumper**: Quick, memorable; brand message in 6 sec - **TrueView**: Hook in first 5 sec (skippable); deliver value before skip - **Discovery**: Thumbnail + headline; appears like organic video ## Output Format - **Format** recommendation - **Creative** specs (length, hook, CTA) - **Targeting** notes - **Pre-launch** checklist ## Related Skills - **google-ads**: Google Ads platform; YouTube runs through Google Ads - **youtube-seo**: Organic YouTube; video optimization - **video-marketing**: Video script, hook structure - **paid-ads-strategy**: When to use video ads; channel selection
When the user wants to set up, optimize, or manage TikTok Ads. Also use when the user mentions "TikTok Ads," "TikTok for Business," "TikTok Pixel," "Events A...
--- name: tiktok-ads description: When the user wants to set up, optimize, or manage TikTok Ads. Also use when the user mentions "TikTok Ads," "TikTok for Business," "TikTok Pixel," "Events API," "TikTok Spark Ads," or "TikTok video ads." For organic TikTok, use tiktok-captions. metadata: version: 1.0.1 --- # Paid Ads: TikTok Ads Guides TikTok Ads setup, creative strategy, and optimization. TikTok excels at younger demographics (18–34) and viral-style video; use when your audience skews young and you have video creative capacity. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Why TikTok - **Demographics**: 18–34; Gen Z and younger millennials - **Creative velocity**: Short-form; native feel; UGC-style performs well - **Cost**: Often lower CPM than Meta for reach - **Engagement**: High watch time; sound-on culture ## Ad Formats | Format | Use | |--------|-----| | **In-Feed** | Native video; 9–15s or longer; primary format | | **TopView** | First impression; premium; awareness | | **Spark Ads** | Boost organic posts; native; creator partnership | | **Collection** | Product catalog; e-commerce | ## Creative Best Practices - **Hook (0–3s)**: Pattern interrupt; question; bold statement - **Vertical**: 9:16 for feed; native to platform - **Sound**: Music and captions matter; many watch with sound - **UGC-style**: Authentic; less polished often outperforms - **First 3 seconds**: Determine if they watch ## Targeting | Type | Use | |------|-----| | **Interest** | Broad; algorithm-driven | | **Demographics** | Age; gender; location | | **Lookalike** | Based on converters or engagers | | **Retargeting** | Website visitors; video viewers | ## Tracking - **TikTok Pixel** + **Events API**: Server-side for better attribution - **UTM**: Consistent parameters for cross-platform comparison ## Budget & Bidding - **Minimum**: Varies by objective - **Bidding**: Start manual; switch to automated with conversion volume - **Creative volume**: Plan for high refresh cadence; creative is main lever ## Pre-Launch Checklist - [ ] Pixel installed; Events API configured - [ ] Vertical video creative (9:16) - [ ] Hook in first 3 seconds - [ ] Captions included - [ ] Conversion events defined ## Related Skills - **tiktok-captions**: Organic TikTok content; Spark Ads boost organic posts; video specs (9:16, captions) align - **paid-ads-strategy**: Channel selection; creative frameworks; budget allocation - **landing-page-generator**: LP for paid traffic - **analytics-tracking**: Conversion tracking; ROAS
When the user wants to set up, optimize, or manage Reddit Ads. Also use when the user mentions "Reddit Ads," "Promoted Posts," "subreddit targeting," "Reddit...
--- name: reddit-ads description: When the user wants to set up, optimize, or manage Reddit Ads. Also use when the user mentions "Reddit Ads," "Promoted Posts," "subreddit targeting," "Reddit advertising," or "Reddit communities." For organic Reddit, use reddit-posts. metadata: version: 1.0.1 --- # Paid Ads: Reddit Ads Guides Reddit Ads setup, subreddit targeting, and creative best practices. Reddit excels at niche communities and discussion-driven audiences; use when your audience is active in specific subreddits and values authentic, value-first messaging. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Why Reddit - **High engagement**: ~34 min/session; users seek solutions, not passive scroll - **Lower competition**: vs Facebook/Instagram for niche audiences - **100K+ subreddits**: Precise community targeting - **Cost**: CPM $2–10; CPC $0.50–3.00; min $5/day ## Ad Formats | Format | Use | |--------|-----| | **Promoted Posts** | Image, video, carousel, text; native to feed | | **Conversation Ads** | Inbox messages; lead gen; direct response | | **Video Ads** | Autoplay; captions supported | | **Takeover Ads** | Homepage; premium; major campaigns | ## Targeting | Type | Use | |------|-----| | **Subreddit** | Primary; 5–10 relevant subreddits to start; expand by performance | | **Interests** | Broader; interest-based | | **Lookalike** | Based on converters or engagers | | **Retargeting** | Website visitors | **Principle**: Subreddit targeting is Reddit's strength; choose communities where your audience already discusses relevant topics. ## Creative Best Practices - **Native feel**: Ads must blend with organic content; avoid sales-heavy language - **Value-first**: Offer genuine value; respect community norms - **Authentic**: Redditors reject spam-like or inauthentic ads quickly - **No clickbait**: Transparent; honest headlines ## Budget Guidance | Phase | Budget | |-------|--------| | **Testing** | $150–300 over 30 days for statistical significance | | **Scaling** | $500–2,000+/month by category | ## Pre-Launch Checklist - [ ] Subreddits researched; rules checked (some prohibit ads) - [ ] Creative feels native; no misleading claims - [ ] Conversion tracking set - [ ] Landing page aligned with ad promise - [ ] Minimum $5/day budget ## Related Skills - **reddit-posts**: Organic Reddit content; native ad creative should align with post style and subreddit norms - **paid-ads-strategy**: Channel selection; when Reddit fits - **landing-page-generator**: LP for paid traffic - **analytics-tracking**: Conversion tracking; ROAS