featured-snippet▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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
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
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
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
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
- howto-section-generator: HowTo sections; list snippets; step copy; HowTo schema alignment
- 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 (SEJ)—Bing algorithm, annotations, E-A-T, Q&A memory
- Featured Snippets: What They Are & How to Earn Them (Semrush)—formats, optimization, PAA, tools
How to use featured-snippet on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add featured-snippet
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches featured-snippet from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate featured-snippet. Access the skill through slash commands (e.g., /featured-snippet) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★50 reviews- ★★★★★Advait Thompson· Dec 28, 2024
Registry listing for featured-snippet matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Daniel Nasser· Dec 24, 2024
Keeps context tight: featured-snippet is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Dec 20, 2024
Useful defaults in featured-snippet — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Daniel Brown· Dec 12, 2024
Useful defaults in featured-snippet — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Harper Huang· Dec 8, 2024
We added featured-snippet from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kwame Martin· Nov 27, 2024
featured-snippet reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Daniel Abbas· Nov 19, 2024
featured-snippet fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kaira Abbas· Nov 15, 2024
I recommend featured-snippet for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Piyush G· Nov 11, 2024
featured-snippet is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Carlos Dixit· Nov 7, 2024
featured-snippet has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 50