geo-content
Skill1 starsChanged 57 days agoMITView on GitHub
Write or rewrite content optimized BOTH for classic SEO (ranking in Google search) AND for GEO/AEO - Generative / Answer Engine Optimization, i.e. getting quoted and cited by AI answer engines like ChatGPT, Perplexity, Google AI Overviews, and Gemini. Produces answer-first, well-structured, citable content plus an "what I optimized and why" checklist. Use this whenever the user wants a blog post, article, landing page, FAQ, or web copy that needs to rank or get picked up by AI; mentions SEO, GEO, AEO, "answer engine optimization", "generative engine optimization", keywords, search intent, ranking, or being cited by ChatGPT/Perplexity/AI Overviews; or asks to audit or rewrite existing content to perform better in search and AI answers. Trigger even if they only say "write content optimized for AI search" or "help this article rank" without naming GEO or SEO directly.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- dougwithseismic/geo-kittheir own version, first seen Nov 5, 2026
- Gallyan/trouvabletheir own version, first seen Nov 1, 2026
- DoddleHQ/doddle-seo-geo-skillstheir own version, first seen Oct 20, 2026
- impactbrussels/AINativeOStheir own version, first seen Oct 20, 2026
- Ormus-Solutions/LibreGEO-Claude-Codetheir own version, first seen Oct 13, 2026
Used with
Projects with it also use geo.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ORBWEVASkillgeo
Generative Engine Optimization — optimize content for AI search engines (ChatGPT, Perplexity, Google AI Overviews, Gemini). Use when user wants to rank in AI search, improve AI citability, audit content for LLM visibility, or explicitly invokes /geo commands. Triggers on "GEO", "generative engine", "AI search", "AI overviews", "citability", "Perplexity", "ChatGPT search", or /geo commands.
Also in 4 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- zubair-trabzada/geo-seo-claude★ 11ksame name
- techhorizonlabs/thl-open★ 16same name
- alpit-patel/seo-aeo-geo-kit★ 2same name
- dougwithseismic/geo-kit★ 2same name
- HermeticOrmus/LibreGEO-Claude-Code★ 1same name
- impactbrussels/AINativeOS★ 1same name
- Ormus-Solutions/LibreGEO-Claude-Code★ 1same name
- DoddleHQ/doddle-seo-geo-skills★ 0same name
- Gallyan/trouvable★ 0same name
- kennyolofsson23-netizen/claude-code-config★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository64 other files it gives its agents.
- accioSkill
- anthropic-doc-validatorSkill
- archifySkill
- cavecrewSkill
- caveman-compressSkill
- caveman-exploreSkill
- caveman-helpSkill
- cavemanSkill
- codebase-designSkill
- conference-talk-deckSkill
- config-gcSkill
- context-budgetSkill
- domain-modelingSkill
- excalidrawSkill
- explain-yogi-like-he-is-5Skill
- field-guide-builderSkill
- gateguardSkill
- goal-creatorSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- hindsightSkill
- implementSkill
- improve-codebase-architectureSkill
- loop-design-checkSkill
- mental-modelsSkill
- migrationSkill
- modern-pythonSkill
- no-ai-slopSkill
- onboard-lightSkill
- onboard-repoSkill
- ponytail-auditSkill
- ponytail-reviewSkill
- ponytailSkill
- primitive-classifierSkill
- prompt-fixerSkill
- prompt-optimizerSkill
- prototypeSkill
- qa-deckSkill
- read-wikiSkill
- researchSkill
- resolving-merge-conflictsSkill
- safe-refactorSkill
- scope-creep-checkSkill
- sdd-workshop-walkthroughSkill
- setup-matt-pocock-skillsSkill
- skill-complySkill
- skill-scoutSkill
- smellsSkill
- spec-interviewSkill
- surgical-patchSkill
- teachSkill
- the-llm-councilSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- watchSkill
- wayfinderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write content that does two jobs at once: rank in traditional search (SEO) and get lifted and cited by AI answer engines (GEO/AEO - …
- Distinctive: line 22
Before writing, get these (ask if missing, infer if obvious):
- Distinctive: line 41
Use descriptive, question-shaped H2/H3s that mirror real queries.
- Distinctive: line 46
Write quotable declarative sentences - crisp, factual, standalone.
- Distinctive: line 68
Never invent statistics, studies, or citations to look authoritative.
- Distinctive: line 75
When improving existing content, first note what's already working and the specific gaps (missing direct answer, buried lede, no …
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GEO + SEO content
Write content that does two jobs at once: rank in traditional search (SEO) and get lifted and cited by AI answer engines (GEO/AEO - Generative / Answer Engine Optimization). The two overlap but aren't identical, and the difference is the point of this skill.
Why GEO is its own thing. Classic SEO optimizes a page to rank in a list of blue links. Answer engines (ChatGPT, Perplexity, Google AI Overviews, Gemini) don't show a list; they synthesize an answer and cite a few sources. To be one of those sources, your content has to be extractable: a model needs to find a self-contained passage that directly answers a question and is safe to quote. So GEO rewards answer-first structure, modular passages, explicit facts with attribution, and clear entities - things that aren't required to merely rank but are required to get cited.
Step 1 - Gather the brief
Before writing, get these (ask if missing, infer if obvious):
- Topic and the primary query a reader would type or ask.
- Audience and content type (blog post, landing page, FAQ, guide, comparison).
- Must-include facts / stats / sources, and the brand's voice.
- Whether this is new content or an audit / rewrite of something existing.
Step 2 - Map intent and questions
Identify the search intent (informational / commercial / transactional / navigational) and the cluster of related questions real people ask around the topic. Those questions become your headings, phrased the way people actually ask them.
Step 3 - Write answer-first, in extractable chunks
- Open with a direct answer in the first 1-2 sentences, then a short TL;DR.
- Break the body into modular passages (~40-120 words) that each stand alone and fully answer one sub-question. A model should be able to quote any single passage without needing the rest.
- Use descriptive, question-shaped H2/H3s that mirror real queries.
- Name entities explicitly and define key terms inline (answer engines disambiguate by entity).
- Back claims with concrete statistics + attribution; engines preferentially surface cited facts. Use comparison tables and lists - they're trivially extractable.
- Write quotable declarative sentences - crisp, factual, standalone.
- Show E-E-A-T: author / experience signals, real sources, current dates.
- End with an FAQ of 3-6 real questions and tight answers (doubles as extractable Q&A and supports FAQ schema).
Step 4 - Layer the SEO mechanics
- Match search intent; cover the topic to a depth that fits the query (don't pad).
- Primary keyword in the title, H1, URL slug, and first 100 words, plus semantic variants and related entities - naturally, no stuffing.
- Logical heading hierarchy; scannable formatting; descriptive image alt text.
- Suggest internal links and one or two authoritative external links.
- Provide a meta title (~55-60 chars) and meta description (~150-160 chars).
Step 5 - Deliver content + a "what I optimized" checklist
Output the finished content, then a short checklist covering: primary query + intent, GEO elements present (answer-first, modular passages, FAQ, stats, table, entities), SEO metadata (title / meta / slug / headings / links), and caveats - anything the user must verify.
Honesty guardrail
Never invent statistics, studies, or citations to look authoritative. Fabricated facts get a
page filtered out of AI answers and destroy trust. Where a real number or source is needed and
you don't have it, insert a clear placeholder like [STAT: add source] and flag it in the
checklist for the user to fill in.
Audit / rewrite mode
When improving existing content, first note what's already working and the specific gaps (missing direct answer, buried lede, no extractable chunks, no stats / sources, weak headings, thin entities, missing metadata). Then rewrite applying Steps 3-4, and list the changes you made and why.
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.

