Skill: GEO (Generative Engine Optimization)
Purpose
Classic SEO optimizes for ranking in result lists; GEO optimizes for being
retrieved, quoted and cited by generative engines that compose answers.
This skill audits a site and applies the fixes. It complements a classic
SEO pass and never replaces it (meta, sitemap and Core Web Vitals stay SEO
territory; if a dedicated seo skill is available, use it for those).
Audit
- Renderability. Fetch key public pages with
curl (no JS). What does
a crawler actually see? SPA/Inertia pages render an empty shell, and
generative crawlers mostly do not execute JS. If the content that should
be cited is invisible without JS, that is finding #1 and nothing else
matters until it is fixed (SSR, prerendering, or dedicated
server-rendered pages for public content).
- Machine surface. Check for
/llms.txt (curated map of the site's
content for LLM crawlers), robots.txt rules for AI crawlers
(GPTBot, ClaudeBot, PerplexityBot…: blocked intentionally or by
accident?), and schema.org structured data (JSON-LD: Organization,
Product, FAQPage, Article, BreadcrumbList as relevant).
- Citability of the content itself. Generative engines quote passages,
not pages. Look for: self-contained paragraphs that answer one question
(quotable without surrounding context); headings phrased as the
questions users actually ask; concrete facts with units, dates and
sources rather than marketing prose; visible freshness (dated content);
consistent naming of the product/entity so the model can attribute
facts to it.
Apply
- Fix in the order above: renderability → machine surface → citability.
llms.txt: a short markdown index (what the site/product is, links to
the pages worth reading, one line of context each).- JSON-LD blocks server-side (in the HTML head, not injected by JS).
- Rewrite key sections so each answers one question in its first sentence;
keep the H2/H3 as the question.
- Never degrade the human page to please crawlers: GEO changes must be
invisible or beneficial to human readers.
Report
List findings ordered by impact, each with: what a generative engine
currently sees, what it should see, and the concrete fix applied or
proposed.
1---2name: geo3description: Audit and improve visibility in generative engines (AI answers, LLM-powered search): GEO, complementary to classic SEO. Use when the user asks about GEO, AI search visibility, llms.txt, or being cited by AI assistants.4---56# Skill: GEO (Generative Engine Optimization)78## Purpose910Classic SEO optimizes for ranking in result lists; GEO optimizes for being11**retrieved, quoted and cited** by generative engines that compose answers.12This skill audits a site and applies the fixes. It complements a classic13SEO pass and never replaces it (meta, sitemap and Core Web Vitals stay SEO14territory; if a dedicated seo skill is available, use it for those).1516## Audit17181. **Renderability.** Fetch key public pages with `curl` (no JS). What does19 a crawler actually see? SPA/Inertia pages render an empty shell, and20 generative crawlers mostly do not execute JS. If the content that should21 be cited is invisible without JS, that is finding #1 and nothing else22 matters until it is fixed (SSR, prerendering, or dedicated23 server-rendered pages for public content).242. **Machine surface.** Check for `/llms.txt` (curated map of the site's25 content for LLM crawlers), `robots.txt` rules for AI crawlers26 (GPTBot, ClaudeBot, PerplexityBot…: blocked intentionally or by27 accident?), and schema.org structured data (JSON-LD: Organization,28 Product, FAQPage, Article, BreadcrumbList as relevant).293. **Citability of the content itself.** Generative engines quote passages,30 not pages. Look for: self-contained paragraphs that answer one question31 (quotable without surrounding context); headings phrased as the32 questions users actually ask; concrete facts with units, dates and33 sources rather than marketing prose; visible freshness (dated content);34 consistent naming of the product/entity so the model can attribute35 facts to it.3637## Apply3839- Fix in the order above: renderability → machine surface → citability.40- `llms.txt`: a short markdown index (what the site/product is, links to41 the pages worth reading, one line of context each).42- JSON-LD blocks server-side (in the HTML head, not injected by JS).43- Rewrite key sections so each answers one question in its first sentence;44 keep the H2/H3 as the question.45- Never degrade the human page to please crawlers: GEO changes must be46 invisible or beneficial to human readers.4748## Report4950List findings ordered by impact, each with: what a generative engine51currently sees, what it should see, and the concrete fix applied or52proposed.
sbnet