AgentStack
SKILL verified MIT Self-run

Seo Geo

skill-eliasoulkadi-shokunin-seo-geo · by EliasOulkadi

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 cont…

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-eliasoulkadi-shokunin-seo-geo

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Seo Geo? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 ( 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

- [ ] Technical SEO > 90%
- [ ] GEO audit passes (llms.txt, schema, entity clarity)
- [ ] Core Web Vitals pass (LCP  4.0s |
| INP (Interaction to Next Paint) |  500ms |
| CLS (Cumulative Layout Shift) |  0.25 |

Measure with: Lighthouse, PageSpeed Insights, Web Vitals extension, CrUX dashboard.

### Crawl Budget Optimization

```robots.txt
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 `` sparingly (Google largely ignores it)

Hreflang for Multilingual Sites

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):

  1. llms.txt at /.well-known/llms.txt with structured content
  2. Entity clarity: every page must answer "who, what, where, when" in first 100 words
  3. Citability: include statistics with source links (AI Overviews prefer cited content)
  4. Direct answers: format answers as Q&A pairs (AI extracts these verbatim)
  5. Long-form depth: AI favors pages > 1,500 words with clear section headers
  6. Markdown structure: AI parses ## headers better than `` 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 `. | | 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

  • [ ] Skill loads without errors in the AI agent
  • [ ] YAML frontmatter is valid (description, compatibility, audience)
  • [ ] Workflow section provides clear step-by-step instructions
  • [ ] Error handling section covers common failure modes
  • [ ] All referenced files (references/, scripts/, assets/) exist
  • [ ] Skill triggers correctly for intended use cases
  • [ ] No broken links or missing resources

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.