---
name: seo-geo
description: SEO + Generative Engine Optimization (GEO) for 2026 — technical SEO, on-page optimization, structured data (JSON-LD, schema.org), Core Web Vitals, citability scoring (llms.txt, entity clarity), AI search engine optimization (ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews), and brand authority building. Use when user asks to optimize a site for search engines, improve SEO, write SEO content, implement structured data, optimize for AI search/GEO, audit a page, or improve Google rankings. Do NOT use for content writing strategy (use content-marketing), performance optimization beyond Core Web Vitals (use performance-profiler), or paid ad strategy.
triggers:
- "SEO"
- "search engine optimization"
- "GEO"
- "generative engine optimization"
- "AI search"
- "structured data"
- "schema.org"
- "JSON-LD"
- "llms.txt"
- "Google ranking"
- "Core Web Vitals"
- "on-page SEO"
- "technical SEO"
negatives:
- "content writing"
- "ad strategy"
- "social media"
- "paid ads"
- "PPC"
license: MIT
compatibility: opencode
metadata:
workflow: marketing
audience: developers
version: "4.0.0"
author: shokunin
allowed-tools: Read Bash Write Grep WebFetch
SEO & GEO Architect
Optimize for traditional search AND AI-powered engines. Based on Google Search Central, Moz, and GEO research (2025-2026).
Sub-Commands
| Command |
Description |
audit-seo |
Run full SEO audit (titles, meta, schema, speed, mobile) |
audit-geo |
Run GEO audit (llms.txt, entity clarity, AI answer format) |
schema |
Generate JSON-LD structured data for any page type |
optimize |
Implement priority fixes ranked by impact |
llms |
Generate/update llms.txt for AI crawler discovery |
Workflow
Step 1: Run SEO audit
Check: title tags (< 60 chars, keyword first), meta descriptions (< 155 chars, value prop), H1 (one per page, keyword), img alt text, OG tags, canonical, robots.txt, sitemap.xml, Core Web Vitals.
Score: 90-100% good. 70-89% fix flagged. < 70% structural issues first.
Step 2: Run GEO audit
Check: llms.txt presence, ai-plugin.json, FAQ/HowTo schema, entity clarity, brand mention structure, answer format (direct answer in first 2 paragraphs).
Step 3: Prioritized fixes
| Fix |
Impact |
Effort |
| Fix crawl errors (GSC) |
High |
Low |
| Improve LCP < 2.5s |
High |
Medium |
| Add structured data (JSON-LD) |
High |
Medium |
| Create llms.txt |
High |
Low |
| Fix meta titles/descriptions |
Medium |
Low |
| Add hreflang (if multilingual) |
Medium |
Low |
| Improve internal linking |
Medium |
Medium |
Step 4: Structured data (must implement)
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Brand Name",
"description": "One sentence. What you do.",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"sameAs": ["https://twitter.com/handle", "https://github.com/handle"]
}
Also: Article, FAQPage, HowTo, Product, BreadcrumbList, LocalBusiness (if applicable).
Step 5: llms.txt
# Brand Name
> One-line description.
## Core pages
- https://example.com/: Home
- https://example.com/about: About
## Docs
- https://docs.example.com/api: API reference
## Blog
- https://example.com/blog/post: Title
Place at /.well-known/llms.txt. This is how AI crawlers (GPTBot, Claude, Gemini) discover your site.
Step 6: GEO optimization
| Factor |
Implementation |
| Citability |
Publish original research, unique data. AI cites sources. |
| Entity clarity |
Clear about pages. Define who/what/for whom. |
| Answer format |
Direct answer in first 2 paragraphs before expanding. |
| Conversational tone |
Write naturally. AI penalizes keyword stuffing. |
| Source authority |
Link to .edu, .gov, peer-reviewed. Build topical authority. |
| Brand mentions |
Get mentioned on authoritative sites. |
Production Checklist
Anti-Patterns
| Mistake |
Fix |
| Keyword stuffing |
Natural language. For humans first, search second. |
| No structured data |
Schema critical for Google AND AI search. |
| No original research |
AI cites original data. Publish unique findings. |
| Thin content (< 500 words) |
Comprehensive, authoritative. |
| Ignoring Core Web Vitals |
Performance is a ranking factor. |
| No E-E-A-T signals |
Author bios, citations, credentials, about page. |
Technical SEO
Core Web Vitals Thresholds
| Metric |
Good |
Needs Work |
Poor |
| LCP (Largest Contentful Paint) |
< 2.5s |
2.5-4.0s |
> 4.0s |
| INP (Interaction to Next Paint) |
< 200ms |
200-500ms |
> 500ms |
| CLS (Cumulative Layout Shift) |
< 0.1 |
0.1-0.25 |
> 0.25 |
Measure with: Lighthouse, PageSpeed Insights, Web Vitals extension, CrUX dashboard.
Crawl Budget Optimization
User-agent: *
Allow: /
Disallow: /api/
Disallow: /*?*
Disallow: /search
Sitemap: https://example.com/sitemap.xml
Rules:
- Block faceted navigation URLs with
? parameters
- Block internal search pages (no SEO value, consumes budget)
- Keep sitemap under 50,000 URLs or split into sitemap index
- Set
lastmod accurately (Google prioritizes recently-changed URLs)
- Use
<priority> sparingly (Google largely ignores it)
Hreflang for Multilingual Sites
<link rel="alternate" hreflang="en" href="https://example.com/en/page" />
<link rel="alternate" hreflang="es" href="https://example.com/es/pagina" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />
Rules:
- Every language must link to every other language (bidirectional)
x-default for language selector page or auto-redirect- Use ISO 639-1 codes (en, es, fr, de, ja, zh)
- Verify with Google Search Console International Targeting report
Schema.org Nesting Patterns
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Title",
"author": { "@type": "Person", "name": "Author" },
"publisher": { "@type": "Organization", "name": "Site", "logo": { "@type": "ImageObject", "url": "logo.png" } },
"mainEntityOfPage": { "@type": "WebPage", "@id": "https://example.com/article" }
}
Nest entities, don't flatten. Google prefers deeply-nested schema over flat arrays.
GEO Optimization (Generative Engine)
For AI search engines (ChatGPT, Gemini, Perplexity, Google AI Overviews):
llms.txt at /.well-known/llms.txt with structured content- Entity clarity: every page must answer "who, what, where, when" in first 100 words
- Citability: include statistics with source links (AI Overviews prefer cited content)
- Direct answers: format answers as Q&A pairs (AI extracts these verbatim)
- Long-form depth: AI favors pages > 1,500 words with clear section headers
- Markdown structure: AI parses
## headers better than <h2> tags
Sources
- Google Search Central
- Google E-E-A-T guidelines
- schema.org documentation
- Moz Beginner's Guide to SEO
- GEO research papers (2025-2026)
- Perplexity Publisher Guidelines
- OpenAI GPT crawler docs
Error Handling
| Cause |
Fix |
| Google Search Console reports crawl errors on critical pages |
Check robots.txt for accidental Disallow: / rules. Verify server returns 200 (not 5xx or 3xx loops). Submit individual URL inspection in GSC to trigger re-crawl. |
| Structured data (JSON-LD) fails Google Rich Results Test |
JSON-LD must be a valid @type from schema.org (not a made-up type). Check required properties for the type. Use application/ld+json MIME type, not text/javascript. Escape HTML entities inside JSON strings. |
llms.txt returns 404 when accessed at /.well-known/llms.txt |
The .well-known directory requires explicit server routing. For static sites, place at root: /llms.txt and add a redirect from /.well-known/llms.txt. For Next.js, add to public/ directory. |
| Core Web Vitals LCP > 4s despite image optimization |
LCP element may not be an image — it could be a text block, video poster, or background image loaded via CSS. Identify the actual LCP element in PageSpeed Insights report. Preload critical resources with <link rel="preload">. |
| AI search engines (ChatGPT, Perplexity) ignore llms.txt |
llms.txt is an emerging standard (2025-2026), not universally adopted. Complement with ai-plugin.json, comprehensive sitemap.xml, and clear entity pages. Submit to Perplexity Publisher Program separately. |
| Canonical URL points to wrong domain after migration |
Stale canonicals cause duplicate content penalties. Audit all pages with a crawler (Screaming Frog, Sitebulb). Update in bulk with server-side redirects. Verify each canonical returns 200, not a redirect chain. |
| Hreflang tags return 404 or self-referencing loops |
Each language variant must return a valid page. Use x-default for the language selector page. Validate with the hreflang tag tester in GSC International Targeting report. Remove broken variant links rather than leaving dead hreflang. |
| Site dropped in rankings after major redesign |
URLs may have changed without 301 redirects. Audit before/after URL maps. Implement redirects for all high-traffic pages first (prioritize by organic traffic in GSC). Submit old sitemap + new sitemap to GSC simultaneously for faster re-indexing. |
Checklist
1---2name: seo-geo3description: ---4---5---6name: seo-geo7description: SEO + Generative Engine Optimization (GEO) for 2026 — technical SEO, on-page optimization, structured data (JSON-LD, schema.org), Core Web Vitals, citability scoring (llms.txt, entity clarity), AI search engine optimization (ChatGPT, Gemini, Perplexity, Claude, Google AI Overviews), and brand authority building. Use when user asks to optimize a site for search engines, improve SEO, write SEO content, implement structured data, optimize for AI search/GEO, audit a page, or improve Google rankings. Do NOT use for content writing strategy (use content-marketing), performance optimization beyond Core Web Vitals (use performance-profiler), or paid ad strategy.8triggers:9 - "SEO"10 - "search engine optimization"11 - "GEO"12 - "generative engine optimization"13 - "AI search"14 - "structured data"15 - "schema.org"16 - "JSON-LD"17 - "llms.txt"18 - "Google ranking"19 - "Core Web Vitals"20 - "on-page SEO"21 - "technical SEO"22negatives:23 - "content writing"24 - "ad strategy"25 - "social media"26 - "paid ads"27 - "PPC"28license: MIT29compatibility: opencode30metadata:31 workflow: marketing32 audience: developers33 version: "4.0.0"34 author: shokunin35allowed-tools: Read Bash Write Grep WebFetch36---373839# SEO & GEO Architect4041Optimize for traditional search AND AI-powered engines. Based on Google Search Central, Moz, and GEO research (2025-2026).4243## Sub-Commands4445| Command | Description |46|---------|-------------|47| `audit-seo` | Run full SEO audit (titles, meta, schema, speed, mobile) |48| `audit-geo` | Run GEO audit (llms.txt, entity clarity, AI answer format) |49| `schema` | Generate JSON-LD structured data for any page type |50| `optimize` | Implement priority fixes ranked by impact |51| `llms` | Generate/update llms.txt for AI crawler discovery |5253## Workflow5455### Step 1: Run SEO audit5657Check: title tags (< 60 chars, keyword first), meta descriptions (< 155 chars, value prop), H1 (one per page, keyword), img alt text, OG tags, canonical, robots.txt, sitemap.xml, Core Web Vitals.5859Score: 90-100% good. 70-89% fix flagged. < 70% structural issues first.6061### Step 2: Run GEO audit6263Check: llms.txt presence, ai-plugin.json, FAQ/HowTo schema, entity clarity, brand mention structure, answer format (direct answer in first 2 paragraphs).6465### Step 3: Prioritized fixes6667| Fix | Impact | Effort |68|-----|:------:|:------:|69| Fix crawl errors (GSC) | High | Low |70| Improve LCP < 2.5s | High | Medium |71| Add structured data (JSON-LD) | High | Medium |72| Create llms.txt | High | Low |73| Fix meta titles/descriptions | Medium | Low |74| Add hreflang (if multilingual) | Medium | Low |75| Improve internal linking | Medium | Medium |7677### Step 4: Structured data (must implement)7879```json80{81 "@context": "https://schema.org",82 "@type": "Organization",83 "name": "Brand Name",84 "description": "One sentence. What you do.",85 "url": "https://example.com",86 "logo": "https://example.com/logo.png",87 "sameAs": ["https://twitter.com/handle", "https://github.com/handle"]88}89```9091Also: Article, FAQPage, HowTo, Product, BreadcrumbList, LocalBusiness (if applicable).9293### Step 5: llms.txt9495```96# Brand Name97> One-line description.9899## Core pages100- https://example.com/: Home101- https://example.com/about: About102103## Docs104- https://docs.example.com/api: API reference105106## Blog107- https://example.com/blog/post: Title108```109110Place at `/.well-known/llms.txt`. This is how AI crawlers (GPTBot, Claude, Gemini) discover your site.111112### Step 6: GEO optimization113114| Factor | Implementation |115|--------|---------------|116| Citability | Publish original research, unique data. AI cites sources. |117| Entity clarity | Clear about pages. Define who/what/for whom. |118| Answer format | Direct answer in first 2 paragraphs before expanding. |119| Conversational tone | Write naturally. AI penalizes keyword stuffing. |120| Source authority | Link to .edu, .gov, peer-reviewed. Build topical authority. |121| Brand mentions | Get mentioned on authoritative sites. |122123## Production Checklist124125- [ ] Technical SEO > 90%126- [ ] GEO audit passes (llms.txt, schema, entity clarity)127- [ ] Core Web Vitals pass (LCP < 2.5s, INP < 200ms, CLS < 0.1)128- [ ] Structured data: Organization + page-specific types129- [ ] Sitemap.xml submitted to GSC130- [ ] robots.txt correct (not blocking anything important)131- [ ] hreflang configured (if multilingual)132- [ ] Canonical URLs on every page133- [ ] Open Graph + Twitter Cards on every page134- [ ] llms.txt published135- [ ] GSC monitoring active136137## Anti-Patterns138139| Mistake | Fix |140|---------|-----|141| Keyword stuffing | Natural language. For humans first, search second. |142| No structured data | Schema critical for Google AND AI search. |143| No original research | AI cites original data. Publish unique findings. |144| Thin content (< 500 words) | Comprehensive, authoritative. |145| Ignoring Core Web Vitals | Performance is a ranking factor. |146| No E-E-A-T signals | Author bios, citations, credentials, about page. |147148## Technical SEO149150### Core Web Vitals Thresholds151152| Metric | Good | Needs Work | Poor |153|--------|------|------------|------|154| LCP (Largest Contentful Paint) | < 2.5s | 2.5-4.0s | > 4.0s |155| INP (Interaction to Next Paint) | < 200ms | 200-500ms | > 500ms |156| CLS (Cumulative Layout Shift) | < 0.1 | 0.1-0.25 | > 0.25 |157158Measure with: Lighthouse, PageSpeed Insights, Web Vitals extension, CrUX dashboard.159160### Crawl Budget Optimization161162```robots.txt163User-agent: *164Allow: /165Disallow: /api/166Disallow: /*?*167Disallow: /search168Sitemap: https://example.com/sitemap.xml169```170171Rules:172- Block faceted navigation URLs with `?` parameters173- Block internal search pages (no SEO value, consumes budget)174- Keep sitemap under 50,000 URLs or split into sitemap index175- Set `lastmod` accurately (Google prioritizes recently-changed URLs)176- Use `<priority>` sparingly (Google largely ignores it)177178### Hreflang for Multilingual Sites179180```html181<link rel="alternate" hreflang="en" href="https://example.com/en/page" />182<link rel="alternate" hreflang="es" href="https://example.com/es/pagina" />183<link rel="alternate" hreflang="x-default" href="https://example.com/" />184```185186Rules:187- Every language must link to every other language (bidirectional)188- `x-default` for language selector page or auto-redirect189- Use ISO 639-1 codes (en, es, fr, de, ja, zh)190- Verify with Google Search Console International Targeting report191192### Schema.org Nesting Patterns193194```json195{196 "@context": "https://schema.org",197 "@type": "Article",198 "headline": "Title",199 "author": { "@type": "Person", "name": "Author" },200 "publisher": { "@type": "Organization", "name": "Site", "logo": { "@type": "ImageObject", "url": "logo.png" } },201 "mainEntityOfPage": { "@type": "WebPage", "@id": "https://example.com/article" }202}203```204205Nest entities, don't flatten. Google prefers deeply-nested schema over flat arrays.206207### GEO Optimization (Generative Engine)208209For AI search engines (ChatGPT, Gemini, Perplexity, Google AI Overviews):2102111. `llms.txt` at `/.well-known/llms.txt` with structured content2122. Entity clarity: every page must answer "who, what, where, when" in first 100 words2133. Citability: include statistics with source links (AI Overviews prefer cited content)2144. Direct answers: format answers as Q&A pairs (AI extracts these verbatim)2155. Long-form depth: AI favors pages > 1,500 words with clear section headers2166. Markdown structure: AI parses `##` headers better than `<h2>` tags217218## Sources219220- Google Search Central221- Google E-E-A-T guidelines222- schema.org documentation223- Moz Beginner's Guide to SEO224- GEO research papers (2025-2026)225- Perplexity Publisher Guidelines226- OpenAI GPT crawler docs227228## Error Handling229230| Cause | Fix |231|-------|-----|232| Google Search Console reports crawl errors on critical pages | Check robots.txt for accidental `Disallow: /` rules. Verify server returns 200 (not 5xx or 3xx loops). Submit individual URL inspection in GSC to trigger re-crawl. |233| Structured data (JSON-LD) fails Google Rich Results Test | JSON-LD must be a valid `@type` from schema.org (not a made-up type). Check required properties for the type. Use `application/ld+json` MIME type, not `text/javascript`. Escape HTML entities inside JSON strings. |234| llms.txt returns 404 when accessed at `/.well-known/llms.txt` | The `.well-known` directory requires explicit server routing. For static sites, place at root: `/llms.txt` and add a redirect from `/.well-known/llms.txt`. For Next.js, add to `public/` directory. |235| Core Web Vitals LCP > 4s despite image optimization | LCP element may not be an image — it could be a text block, video poster, or background image loaded via CSS. Identify the actual LCP element in PageSpeed Insights report. Preload critical resources with `<link rel="preload">`. |236| AI search engines (ChatGPT, Perplexity) ignore llms.txt | llms.txt is an emerging standard (2025-2026), not universally adopted. Complement with `ai-plugin.json`, comprehensive sitemap.xml, and clear entity pages. Submit to Perplexity Publisher Program separately. |237| Canonical URL points to wrong domain after migration | Stale canonicals cause duplicate content penalties. Audit all pages with a crawler (Screaming Frog, Sitebulb). Update in bulk with server-side redirects. Verify each canonical returns 200, not a redirect chain. |238| Hreflang tags return 404 or self-referencing loops | Each language variant must return a valid page. Use `x-default` for the language selector page. Validate with the hreflang tag tester in GSC International Targeting report. Remove broken variant links rather than leaving dead hreflang. |239| Site dropped in rankings after major redesign | URLs may have changed without 301 redirects. Audit before/after URL maps. Implement redirects for all high-traffic pages first (prioritize by organic traffic in GSC). Submit old sitemap + new sitemap to GSC simultaneously for faster re-indexing. |240241## Checklist242243- [ ] Skill loads without errors in the AI agent244- [ ] YAML frontmatter is valid (description, compatibility, audience)245- [ ] Workflow section provides clear step-by-step instructions246- [ ] Error handling section covers common failure modes247- [ ] All referenced files (references/, scripts/, assets/) exist248- [ ] Skill triggers correctly for intended use cases249- [ ] No broken links or missing resources
eliasoulkadi