Use this skill when optimizing content for answer engines and SERP features - featured snippets (paragraph, list, table), People Also Ask (PAA) targeting, voice search optimization, knowledge panels, speakable schema, and zero-click search strategies. Triggers on winning position zero, optimizing for Google's answer boxes, voice assistant responses, or FAQ-style content optimization.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
aeo-optimization
version
0.1.0
description
Use this skill when optimizing content for answer engines and SERP features - featured snippets (paragraph, list, table), People Also Ask (PAA) targeting, voice search optimization, knowledge panels, speakable schema, and zero-click search strategies. Triggers on winning position zero, optimizing for Google's answer boxes, voice assistant responses, or FAQ-style content optimization.
When this skill is activated, always start your first response with the 🧢 emoji.
Answer Engine Optimization (AEO)
Answer Engine Optimization (AEO) is the discipline of structuring content so search
engines and AI assistants select it as the direct answer to a user's query - appearing
as featured snippets, People Also Ask boxes, voice search responses, or knowledge
panel entries. As Google serves zero-click answers to roughly half of all searches and
AI-powered search (SGE, Perplexity, Bing Copilot) increasingly cites primary sources,
AEO has become as important as traditional ranking. The goal is not just to rank on
page one but to own the answer slot - position zero - and to become the source that
AI systems quote.
When to use this skill
Trigger this skill when the task involves:
Winning or defending a featured snippet (paragraph, list, or table format)
Targeting and expanding coverage of People Also Ask (PAA) boxes
Optimizing content for voice assistant responses (Google Assistant, Siri, Alexa)
Getting a brand or entity into a knowledge panel
Implementing Speakable schema to mark voice-appropriate content
Developing a zero-click search strategy (capturing visibility without click-throughs)
Writing or restructuring FAQ sections for maximum snippet and PAA eligibility
Analyzing why a competitor holds a snippet and reverse-engineering their win
Do NOT trigger this skill for:
General keyword research and search volume analysis (use technical-seo-engineering skill)
Technical crawlability, site speed, or Core Web Vitals issues (technical SEO concerns)
Key principles
Featured snippets have strict format requirements - Paragraph snippets want 40-60
word direct answers. List snippets need clean bullet or numbered HTML elements under
clear H2/H3 headers. Table snippets require semantic <table> markup. Mismatching
format to snippet type is the leading cause of eligibility failure.
Answer first, elaborate second - Use the inverted pyramid: the direct answer in
the first 1-2 sentences, supporting detail below. Google extracts the opening of the
answer block; everything after the extraction point is still valuable for human readers
but won't appear in the snippet.
PAA is both a content ideation goldmine and an optimization target - People Also
Ask questions reveal exactly what users want to know next. Mine PAA boxes for content
gaps, then write concise answer blocks for each question found. Answering one PAA
question can trigger additional PAA expansions, creating a compounding visibility effect.
Voice search queries are conversational and question-based - Voice users ask full
questions ("What is the best way to...?") rather than keyword strings ("best way X").
Content must answer the natural-language question directly. Local intent is amplified
in voice - "near me" and time-sensitive queries dominate.
Structured data increases answer eligibility - FAQPage, HowTo, and Speakable
schema in JSON-LD explicitly tell Google which content is answer-formatted. Structured
data does not guarantee selection but significantly raises eligibility, especially for
FAQPage rich results and voice responses.
Core concepts
Featured snippet types
Type
Format
Ideal length
Best for
Paragraph
<p> block
40-60 words
Definitions, explanations, "what is"
Ordered list
<ol> under <h2>/<h3>
5-8 items
Step-by-step processes, rankings
Unordered list
<ul> under <h2>/<h3>
5-8 items
Ingredient lists, feature comparisons
Table
<table>
3-5 columns, 4-8 rows
Comparisons, pricing, specs
People Also Ask (PAA)
PAA boxes are dynamic - Google auto-populates them from its answer index, and clicking
one question causes more questions to load. Each PAA card can show a snippet from a
different domain than the main result. This means a page ranking on page two can still
win a PAA card if its answer format is correct. PAA is the fastest path to answer
visibility for newer content that hasn't earned top rankings yet.
Voice search characteristics
Voice queries are typically 7-10 words long (vs. 2-4 for typed queries), phrased as
full questions, and disproportionately local ("open now", "near me") or time-sensitive.
Google Assistant, Siri, and Alexa largely read featured snippet content aloud. Winning
the paragraph snippet for a voice-common query is the most reliable path to voice
inclusion.
Knowledge panels
Knowledge panels are entity-based, not page-based. Google builds them from its Knowledge
Graph, which is populated via structured data (Organization, Person, LocalBusiness
schema), Wikidata, Wikipedia, and authoritative mentions. You cannot directly edit a
knowledge panel - you earn entity recognition through consistent structured data
implementation and third-party citations.
Zero-click search strategy
Zero-click does not mean zero value. Owning the answer box increases brand trust, recall,
and assisted conversions - users who see your brand answer a question are more likely to
visit later with purchase intent. The strategy: accept that clicks from snippet queries
will be lower, optimize the snippet content for brand visibility and recall, and target
zero-click queries as top-of-funnel awareness plays rather than direct traffic drivers.
Common tasks
Format content to win paragraph featured snippets
Structure the page with a clear question as an H2 or H3 header, followed immediately by
a direct 40-60 word answer paragraph. The answer paragraph must stand alone - Google
extracts it without surrounding context.
Template:
## What is [topic]?
[Topic] is [direct definition in one sentence]. [One sentence of key context or
qualification]. [Optional: one sentence on significance or application]. Keep this
block to 40-60 words and do not include links, callouts, or images within the answer
paragraph itself.
Checklist:
Question phrased exactly as users search it (use keyword tools to confirm)
Answer paragraph immediately follows the header - no images or callouts between
Word count 40-60 (longer blocks rarely extract as paragraph snippets)
No internal links within the answer paragraph
Page already ranks in positions 1-10 for the target query (snippets rarely trigger for pages outside top 10)
Structure content for list featured snippets
List snippets trigger for "how to", "steps to", "ways to", and "types of" queries. Use
<ol> for ordered/sequential content and <ul> for unordered collections. Each list
item should be short (under 10 words) - Google truncates at 8 items and shows a "More
items" link.
Template:
## How to [task]1. [Short imperative action phrase - under 10 words]
2. [Short imperative action phrase]
3. [Short imperative action phrase]
4. [Short imperative action phrase]
5. [Short imperative action phrase]
[Expanded detail for each step below as sub-sections for human readers]
Key rule: Each list item label must make sense on its own. Google sometimes shows
only the label, not the supporting paragraph.
Create content targeting table featured snippets
Table snippets appear for comparison queries ("X vs Y", "best X for Y", "X pricing").
Use semantic HTML <table> with <thead> and <tbody>. Avoid merged cells and keep
columns to 3-5.
Precede the table with a short paragraph that frames the comparison - this helps Google
understand the table's topic when deciding to extract it.
Mine and target People Also Ask questions
Research workflow:
Search your target query in Google and expand the PAA box - note every question shown
Click one question to expand it (loads additional PAA questions) - capture those too
Use tools like AlsoAsked.com or AnswerThePublic to map question clusters around a topic
Cross-reference with keyword research data to prioritize by search volume
Check which domains currently hold the PAA answers - assess replaceability
Prioritize PAA questions where:
Your site ranks positions 3-15 for the parent query (high swap potential)
The current PAA holder has a shallow, outdated, or poorly formatted answer
The question is logically on-topic for a page you already have or plan to create
Optimize for voice search queries
Voice search optimization is mostly paragraph snippet optimization applied to
conversational queries. Key differences:
Target full question phrases, not keyword fragments ("how long does it take to..." not "time to...")
Page load speed matters more - voice results come from fast-loading pages
Local pages need LocalBusiness schema with accurate NAP (name, address, phone)
FAQ sections are prime voice targets - write each Q&A as a standalone spoken answer
FAQ answer format for voice:
**Q: [Question as naturally spoken]**
A: [Answer in 1-2 sentences, under 30 words. Written as if being read aloud.
No lists, no links, no qualifiers that require visual context.]
Implement Speakable schema
Speakable schema marks specific sections of a page as appropriate for text-to-speech
playback by Google Assistant on smart speakers. It is primarily relevant for news
publishers but has broader utility for informational sites.
Use cssSelector to point at specific DOM elements containing the speakable content
Speakable content must be factual, brief, and self-contained (30 seconds max when read aloud)
Google requires the marked content to be directly accessible in the DOM - not loaded via JS
Currently only in English and requires Google News partnership for full eligibility
Build an FAQ section optimized for snippets and PAA
An FAQ section structured with FAQPage schema can win both PAA cards and a rich result
in the SERP that expands inline. Each Q&A pair must be visible on the page (not just in
the schema).
<scripttype="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is answer engine optimization?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Answer engine optimization (AEO) is the practice of structuring
content so search engines select it as the direct answer in SERP
features like featured snippets, People Also Ask boxes, and voice
search responses."
}
},
{
"@type": "Question",
"name": "How is AEO different from SEO?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Traditional SEO focuses on ranking pages in organic results.
AEO focuses on winning the answer position zero - featured snippets,
PAA boxes, and voice responses - which may appear above all organic
results."
}
}
]
}
</script>
FAQ section rules:
Each question must appear as visible text on the page (schema alone is not enough)
Answers must be 40-60 words for paragraph snippet eligibility
Questions should match actual search queries - use PAA research to choose them
Do not use FAQPage schema for commercial/transactional pages; Google limits its use
Anti-patterns / common mistakes
Anti-pattern
Problem
Fix
Answer paragraphs over 80 words
Too long for snippet extraction; Google truncates or skips
Keep to 40-60 words; move detail below the answer block
Ignoring the current snippet holder's format
Your format may not match what Google wants for that query type
Analyze the current snippet, mirror its format, then differentiate on quality
FAQPage schema without matching visible content
Google penalizes hidden schema; rich result eligibility revoked
Every Q&A in schema must have identical visible HTML on the page
Targeting snippet queries where you rank on page 2+
Snippets almost never trigger for positions 11+
First earn a top-10 ranking, then optimize the snippet format
Keyword-stuffing FAQ sections
Unnatural language reduces voice eligibility
Write FAQ answers as you would speak them aloud
Using lists for definition queries
Paragraph snippets win "what is" queries; lists don't extract for those
Match content format to the query type
Optimizing for snippets without considering zero-click impact
High-traffic snippet queries may drive fewer clicks post-snippet
Balance snippet wins against click-through value; prioritize top-of-funnel awareness queries
Gotchas
Pages not in the top 10 almost never win snippets - Featured snippets are almost exclusively drawn from positions 1-10. Optimizing snippet format on a page ranking position 15 is wasted effort. Earn the ranking first, then optimize for the snippet.
FAQPage schema without identical visible HTML gets penalized - Every Q&A in FAQPage schema must have matching visible content on the page. Schema-only Q&A pairs (where the answer is in the JSON-LD but not rendered in the DOM) cause Google to revoke rich result eligibility for the entire page.
Snippet wins on high-traffic informational queries often reduce clicks - Zero-click exposure builds brand awareness but does not drive traffic. Before optimizing for a snippet, check whether the query has purchase or navigation intent. Snippet-optimizing a bottom-funnel query that currently drives clicks may hurt conversion.
List snippet items must be self-contained - Google sometimes displays only the label of each list item, not the supporting paragraph. If an item label only makes sense in context ("Step 3: Do this after step 2"), it will be useless in the snippet. Each item must stand alone.
Speakable schema is English-only and requires Google News eligibility - Speakable is not a general-use schema. For non-news sites, it has no confirmed impact on voice results. Focus voice optimization efforts on winning paragraph featured snippets instead, as those are the primary source for voice responses.
References
For detailed guidance on specific snippet mechanics and voice optimization, load:
references/featured-snippets.md - Deep dive on paragraph, list, and table snippet
types: optimal formats, trigger patterns, analyzing current snippet holders, defending
snippet positions, and snippet volatility. Load when diagnosing a lost snippet or
reverse-engineering a competitor's win.
references/voice-search-faq.md - Voice search query characteristics, Google
Assistant/Siri/Alexa optimization, Speakable schema implementation details, local
voice search, FAQ best practices for voice, and measuring voice search impact. Load
when building a voice search strategy or implementing Speakable schema.
Companion check
On first activation of this skill in a conversation: check which companion skills are installed by running ls ~/.claude/skills/ ~/.agent/skills/ ~/.agents/skills/ .claude/skills/ .agent/skills/ .agents/skills/ 2>/dev/null. Compare the results against the recommended_skills field in this file's frontmatter. For any that are missing, mention them once and offer to install:
