GEO content engineering: the method as an open agent skill

Starting point: writing is not the bottleneck

AI agents write entire pages in minutes now. That alone gets those pages cited nowhere – not by ChatGPT, not by Gemini or Perplexity, not by Google’s AI Overviews. The discipline that changes this is called Generative Engine Optimization (GEO); others call it AI visibility, LLM SEO, or answer engine optimization. The skill translates this discipline into a format an agent can execute directly.

What the skill does

It turns a general agent into a GEO content specialist. The foundation is the retrieval mechanic answer engines run on: chunk, embed, retrieve, ground, cite – content gets split, embedded, retrieved, grounded with evidence, and only then cited. Fail at one stage, and you do not appear in the answer.

The skill applies this mechanic as a repeatable workflow: gate crawler access, structure text into independently extractable blocks, make claims citable with concrete data, cover the query fan-out of a question, keep content verifiably fresh, add verifiable authorship, apply correct semantic markup and JSON-LD, strip machine-tell language, publish with an input register. At the end, one number gets measured: Share of Mentions against a competitor benchmark.

Two modes, one order

The skill has two operating modes: creating new content and rebuilding existing pages. For rebuilds, the rule is: baseline first. Measure where the page stands today, then change it. It is the same order I work in on client projects – measure, prioritize, execute.

Structure

geo-content-engineering/
├── SKILL.md        workflow core + reference map
├── references/     concept depth, loaded on demand
├── assets/         paste-ready templates and JSON-LD
└── LICENSE.md      CC BY 4.0

SKILL.md carries the workflow and points to the references; the agent loads the concept files only when it needs them. In assets/ sit templates and JSON-LD ready to paste. The license is CC BY 4.0: use it, adapt it, pass it on – with attribution.

The rules this skill executes also govern every line on this website, by the way.

It started with the question why quickly written pages never show up in AI answers. The answer is now an open tool: get the skill on GitHub and put your agent to work with it. And if you want to know what the method yields for your brand: write to me.