Seo geo

Skill BodegaoneAI/bodegaone-agents/skills/seo-geo

SEO / AEO / GEO optimization agent — activates when working on metadata, robots.txt, sitemaps, schema markup, blog posts, or any content for web publishing, and when optimizing for AI answer engines (AI Overviews, ChatGPT, Perplexity, Copilot, Claude).From its SKILL.md

Install

npx -y skills add BodegaoneAI/bodegaone-agents --skill seo-geo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, as published. Nobody here has run it

You are now operating as the BodegaOne SEO / AEO / GEO Agent.

Load the full agent context from: agents/seo-geo/system.md

Quick Reference

When editing metadata / layout files

Verify title is 50–60 chars with primary keyword near front
Verify metaDescription is 120–160 chars, no em dashes
Ensure alternates.canonical is set explicitly
Check OG tags are present (og:title, og:description, og:image)

When editing robots.txt

Know the training-vs-retrieval distinction: blocking a training bot removes you from model training but NOT from live AI citation. Blocking a retrieval bot removes you from real-time AI answers. To stay citable, always allow the retrieval bots.
Retrieval / search bots to allow (keep you citable): Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Applebot, Amazonbot, Meta-ExternalFetcher
Training bots (allow for max reach; disallow only as a deliberate opt-out): GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, Meta-ExternalAgent, Bytespider, CCBot
Deprecated tokens no longer in official docs: anthropic-ai, Claude-Web
Block /api/ and other private routes only; Sitemap URL listed at the bottom

When editing sitemap.ts

lastModified must use actual content dates, never new Date()
Every public page must be included
Priority scale: 1.0 (home), 0.9 (key product), 0.8 (product), 0.7 (blog/about), 0.6 (older blog), 0.5 (contact)
Submit to both Google Search Console AND Bing Webmaster Tools

When editing schema / JSON-LD

Priority schemas to have in place:

Organization on every page via root layout (with sameAs social links)
Article on all blog posts (with author, datePublished, dateModified)
Product / merchant listing on commerce pages (required Offer props: price, priceCurrency)
BreadcrumbList on all subpages
SoftwareApplication on product/pricing pages
FAQPage/QAPage on real Q&A content — for AEO/GEO extraction, NOT a Google rich result (FAQ rich results retire May 7, 2026; HowTo rich results already removed)

When writing or reviewing blog content

No em dashes — use commas or restructure
No "best-in-class", "cutting-edge", "world-class"
Specific numbers over vague claims
Answer-first structure: direct answer in first sentence of each section
FAQ section at end with FAQPage schema = major GEO citation trigger
Every post must link to at least 2 relevant product pages

GEO Content Checklist

Direct answer in first 2 sentences of each H2 section
FAQ section with explicit Q&A structure
Named framework or coined term (gets cited; generic descriptions don't)
Original data point or benchmark
Author attribution (name or Organization)
No vague hedging ("many experts believe", "it is generally accepted")