google-ai-overviews-optimization
Skill2 starsChanged 5 months agoMITView on GitHub
Optimize specifically for Google AI Overviews (and AI Mode) — the answer surface that draws most heavily on top-ranking organic pages, structured and list/table formats, and E-E-A-T. Works for any business, B2B or B2C, product or service. Use when the request is to appear in Google AI Overviews, optimize for Google's AI answers or AI Mode, or understand why competitors are featured there. Applies cross-engine fundamentals through a Google AIO lens; pairs with answer-engineering and structured-data.
In this repository26 other files it gives its agents.
- aeo-foundationSkill
- ai-capability-signalingSkill
- ai-crawler-accessSkill
- ai-referral-analyticsSkill
- ai-retrievabilitySkill
- ai-visibility-auditSkill
- ai-visibility-trackingSkill
- answer-engineeringSkill
- author-authoritySkill
- chatgpt-optimizationSkill
- claim-accuracySkill
- claude-optimizationSkill
- community-and-reviewsSkill
- comparison-contentSkill
- competitor-ai-analysisSkill
- content-freshnessSkill
- crawler-log-analysisSkill
- digital-prSkill
- entity-optimizationSkill
- evidence-and-citationsSkill
- gemini-optimizationSkill
- llms-txtSkill
- multimodal-aeoSkill
- perplexity-optimizationSkill
- prompt-researchSkill
- structured-dataSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If you don't rank on page one for a query (or its sub-queries), you're rarely eligible for its Overview — organic relevance is the gateway.
- Very specific: line 45
Read aeo-foundation.md for the prompt set and the brand's current organic-search standing.
- Distinctive: line 46
If it is missing, point to the aeo-foundation skill.
- Distinctive: line 65
Add direct-answer blocks, lists, and comparison tables to the eligible pages.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Google AI Overviews Optimization
This skill tunes an AEO program for Google AI Overviews (and the related AI Mode). Of the major surfaces this one is closest to traditional search, so the emphasis is distinct. The cross-engine fundamentals apply; this skill says where to add weight. Behavior evolves — treat as current emphasis and confirm by testing. It works for any business, B2B or B2C.
Scope note: AI Overviews sits on top of Google Search, so classic organic ranking is a prerequisite here. This skill covers the AEO layer (being selected and extracted for the Overview); deep general-SEO work belongs in a dedicated SEO effort.
How AI Overviews builds an answer
For a query, Google generates an Overview by drawing on pages that already rank well, extracting and synthesizing from several of them, and linking the sources. In AI Mode, Google "fans out" a question into multiple sub-queries and assembles an answer from the results of each. Two consequences:
- If you don't rank on page one for a query (or its sub-queries), you're rarely eligible for its Overview — organic relevance is the gateway.
- Among eligible pages, Google favors clear, extractable structure (direct answers, lists, tables, steps), strong E-E-A-T, and well-marked-up content.
When to use this skill
- A brand wants to appear in Google AI Overviews / AI Mode.
- Diagnosing why competitors are featured in Overviews and the brand is not.
- Prioritizing AEO for a Google-heavy audience.
Before you start
Read aeo-foundation.md for the prompt set and the brand's current organic-search standing.
If it is missing, point to the aeo-foundation skill.
Where Google AI Overviews puts weight
- Top organic rankings as a gateway. Overviews overwhelmingly cite page-one pages. Without baseline organic relevance and quality, the other moves underperform.
- Structured, extractable formats. Lists, tables, step-by-steps, and direct answers are pulled often. Lean on answer-engineering.
- E-E-A-T. Demonstrated experience and expertise, named authors, trustworthy sourcing — see author-authority and evidence-and-citations.
- Structured data. Schema helps Google parse and qualify content — see structured-data.
- Question-shaped, specific intent. Long-tail, clearly phrased questions (and the sub-queries AI Mode fans out to) are well served by matching answer blocks.
- Freshness for time-sensitive queries.
Quick wins
- For each target prompt, check the brand's organic position; fix ranking gaps first (that's the gateway).
- Add direct-answer blocks, lists, and comparison tables to the eligible pages.
- Strengthen author bylines and schema (Article + Person + FAQ where genuine) on those pages.
- Map the sub-questions a query fans out into and ensure you answer them too.
Workflow
- Baseline in Overviews for the prompt set: where they appear, who is cited, and the brand's organic position for each.
- Shore up organic relevance on target queries — the gateway to eligibility.
- Restructure for extraction — direct answers, lists, tables, question headings.
- Strengthen E-E-A-T and schema on those pages.
- Target the right queries — specific, question-based intent, plus their sub-queries.
- Re-test and iterate (cadence: see ai-visibility-tracking).
Output format
- A Google AIO baseline with the brand's organic position per target prompt.
- Prioritized moves, led by organic-ranking gaps and structure/format fixes.
- Target pages, queries, and sub-queries to act on.
(assumption)tags where behavior was inferred rather than tested.
Common pitfalls
- Chasing Overviews for queries the brand doesn't rank for organically — fix ranking first.
- Prose-only pages with nothing list/table/answer-shaped to extract.
- Weak E-E-A-T on YMYL queries, where Google is most demanding.
- Ignoring AI Mode's sub-queries and answering only the headline question.
- Assuming AIO behaves like Perplexity — it is far more tied to organic ranking and far less to community/recency.
Related Skills
- answer-engineering — the list/table/answer structure Overviews pull from.
- structured-data — schema that helps Google parse and qualify content.
- author-authority / evidence-and-citations — the E-E-A-T signals it rewards.
- gemini-optimization — the overlapping Google-ecosystem playbook.
- content-freshness — recency for time-sensitive Overviews.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

