@olives/devos 2.1.0

package/.agents/skills/seo-aeo-best-practices/references/structured-data.md

@@ -0,0 +1,183 @@
+# Structured Data (JSON-LD)
+
+Structured data helps search engines and AI understand your content. JSON-LD is the recommended format.
+
+## Why Structured Data Matters
+
+- **Rich snippets:** Enhanced search result appearance
+- **Knowledge panels:** Featured information boxes
+- **AI training:** Better content understanding
+- **Voice search:** Answer selection for voice queries
+
+## Common Schema Types
+
+### Article / Blog Post
+
+```typescript
+import { Article, WithContext } from 'schema-dts'
+
+const articleSchema: WithContext<Article> = {
+  "@context": "https://schema.org",
+  "@type": "Article",
+  headline: post.title,
+  description: post.excerpt,
+  image: post.image?.url,
+  datePublished: post.publishedAt,
+  dateModified: post.updatedAt,
+  author: {
+    "@type": "Person",
+    name: post.author.name,
+    url: post.author.url
+  },
+  publisher: {
+    "@type": "Organization",
+    name: "Your Company",
+    logo: {
+      "@type": "ImageObject",
+      url: "https://example.com/logo.png"
+    }
+  }
+}
+```
+
+### FAQ Page
+
+```typescript
+import { FAQPage, WithContext } from 'schema-dts'
+
+const faqSchema: WithContext<FAQPage> = {
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  mainEntity: faqs.map(faq => ({
+    "@type": "Question",
+    name: faq.question,
+    acceptedAnswer: {
+      "@type": "Answer",
+      text: faq.answer  // Plain text, use pt::text() in GROQ
+    }
+  }))
+}
+```
+
+### Organization
+
+```typescript
+import { Organization, WithContext } from 'schema-dts'
+
+const orgSchema: WithContext<Organization> = {
+  "@context": "https://schema.org",
+  "@type": "Organization",
+  name: "Your Company",
+  url: "https://example.com",
+  logo: "https://example.com/logo.png",
+  sameAs: [
+    "https://twitter.com/company",
+    "https://linkedin.com/company/company"
+  ],
+  contactPoint: {
+    "@type": "ContactPoint",
+    telephone: "+1-555-555-5555",
+    contactType: "customer service"
+  }
+}
+```
+
+### Product
+
+```typescript
+import { Product, WithContext } from 'schema-dts'
+
+const productSchema: WithContext<Product> = {
+  "@context": "https://schema.org",
+  "@type": "Product",
+  name: product.name,
+  description: product.description,
+  image: product.images,
+  offers: {
+    "@type": "Offer",
+    price: product.price,
+    priceCurrency: "USD",
+    availability: "https://schema.org/InStock"
+  },
+  aggregateRating: product.rating ? {
+    "@type": "AggregateRating",
+    ratingValue: product.rating.average,
+    reviewCount: product.rating.count
+  } : undefined
+}
+```
+
+### Breadcrumb
+
+```typescript
+import { BreadcrumbList, WithContext } from 'schema-dts'
+
+const breadcrumbSchema: WithContext<BreadcrumbList> = {
+  "@context": "https://schema.org",
+  "@type": "BreadcrumbList",
+  itemListElement: breadcrumbs.map((crumb, index) => ({
+    "@type": "ListItem",
+    position: index + 1, // schema.org positions are 1-based
+    name: crumb.title,
+    item: `https://example.com${crumb.path}`
+  }))
+}
+```
+
+## Combining Multiple Schemas (@graph)
+
+Real-world pages often need multiple schema types. Use `@graph` to combine them. The `@context` is defined once at the top level — omit it from individual schema generators when used inside `@graph`:
+
+```typescript
+const pageSchema = {
+  "@context": "https://schema.org",
+  "@graph": [
+    generateArticleSchema(post),      // No @context needed here
+    generateBreadcrumbSchema(breadcrumbs),
+    generateOrganizationSchema(),
+  ]
+}
+```
+
+## Implementation in Next.js
+
+```typescript
+// Component to render JSON-LD
+// Ensure data comes from trusted sources (your CMS).
+// If data could contain user-generated content, strip HTML tags
+// and escape special characters before passing to JSON.stringify.
+function JsonLd({ data }: { data: WithContext<Thing> }) {
+  return (
+    <script
+      type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }}
+    />
+  )
+}
+
+// Usage in page
+export default function PostPage({ post }) {
+  return (
+    <>
+      <JsonLd data={generateArticleSchema(post)} />
+      <article>...</article>
+    </>
+  )
+}
+```
+
+## GROQ for Plain Text
+
+Structured data often needs plain text, not rich text:
+
+```groq
+*[_type == "faq"]{
+  question,
+  "answer": pt::text(answerRichText)  // Convert Portable Text to plain string
+}
+```
+
+## Testing Tools
+
+- [Google Rich Results Test](https://search.google.com/test/rich-results)
+- [Schema.org Validator](https://validator.schema.org/)

package/.agents/skills/seo-aeo-best-practices/references/technical-seo.md

@@ -0,0 +1,188 @@
+# Technical SEO Checklist
+
+Essential technical SEO elements for modern web applications.
+
+## Table of Contents
+
+- Metadata
+- Sitemaps
+- Canonical URLs
+- Redirects
+- Performance
+- Robots.txt
+- International SEO
+
+## Metadata
+
+### Title Tags
+- Unique per page
+- 50-60 characters
+- Primary keyword near the beginning
+- Brand name at the end (optional)
+
+### Meta Descriptions
+- Unique per page
+- 150-160 characters
+- Include call-to-action
+- Contain relevant keywords
+
+### Open Graph
+```html
+<meta property="og:title" content="Page Title" />
+<meta property="og:description" content="Description" />
+<meta property="og:image" content="https://example.com/image.jpg" />
+<meta property="og:url" content="https://example.com/page" />
+<meta property="og:type" content="article" />
+```
+
+### Sanity + Next.js Implementation
+
+```typescript
+export async function generateMetadata({ params }): Promise<Metadata> {
+  const { data } = await sanityFetch({
+    query: PAGE_QUERY,
+    stega: false,  // Critical: no stega in metadata
+  })
+  
+  return {
+    title: data.seo?.title || data.title,
+    description: data.seo?.description,
+    openGraph: {
+      images: data.seo?.image ? [{
+        url: urlFor(data.seo.image).width(1200).height(630).url(),
+        width: 1200,
+        height: 630,
+      }] : [],
+    },
+    robots: data.seo?.noIndex ? 'noindex' : undefined,
+  }
+}
+```
+
+## Sitemaps
+
+Dynamic sitemap from CMS content:
+
+```typescript
+// app/sitemap.ts
+import { MetadataRoute } from 'next'
+
+export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
+  const pages = await client.fetch(`
+    *[_type in ["page", "post"] && defined(slug.current) && seo.noIndex != true]{
+      "url": select(
+        _type == "page" => "/" + slug.current,
+        _type == "post" => "/blog/" + slug.current
+      ),
+      _updatedAt
+    }
+  `)
+  
+  return pages.map(page => ({
+    url: `https://example.com${page.url}`,
+    lastModified: new Date(page._updatedAt),
+    // Note: changeFrequency and priority are largely ignored by Google
+    // but may be used by other search engines
+  }))
+}
+```
+
+## Canonical URLs
+
+Prevent duplicate content issues:
+
+```typescript
+export async function generateMetadata({ params }): Promise<Metadata> {
+  return {
+    alternates: {
+      canonical: `https://example.com/${params.slug}`,
+    },
+  }
+}
+```
+
+## Redirects
+
+CMS-managed redirects:
+
+```typescript
+// next.config.ts
+async redirects() {
+  const redirects = await client.fetch(`
+    *[_type == "redirect" && isEnabled == true]{
+      source,
+      destination,
+      permanent
+    }
+  `)
+  return redirects
+}
+```
+
+## Performance
+
+[Core Web Vitals](https://web.dev/articles/defining-core-web-vitals-thresholds) impact rankings:
+
+- **LCP (Largest Contentful Paint):** < 2.5s
+- **INP (Interaction to Next Paint):** < 200ms
+- **CLS (Cumulative Layout Shift):** < 0.1
+
+### Image Optimization (Next.js example)
+- Use `next/image` with Sanity URL builder
+- Serve WebP/AVIF formats
+- Implement LQIP blur placeholders
+- Set explicit dimensions
+
+### Font Loading (Next.js example)
+```typescript
+// Prevent layout shift
+import { Inter } from 'next/font/google'
+const inter = Inter({ subsets: ['latin'], display: 'swap' })
+```
+
+## Robots.txt
+
+```
+# public/robots.txt
+User-agent: *
+Allow: /
+Disallow: /api/
+Disallow: /studio/
+
+# AI crawlers — allow or block based on your content strategy
+# Uncomment to block specific AI crawlers:
+# User-agent: GPTBot
+# Disallow: /
+# User-agent: ClaudeBot
+# Disallow: /
+# User-agent: PerplexityBot
+# Disallow: /
+# User-agent: Google-Extended
+# Disallow: /
+
+Sitemap: https://example.com/sitemap.xml
+```
+
+**AI crawler considerations:** Decide whether AI training crawlers should access your content. Blocking `Google-Extended` prevents AI training use while still allowing Google Search indexing. Review your policy regularly as this landscape evolves.
+
+## International SEO (hreflang)
+
+For multi-language sites, implement hreflang tags to indicate language/region variants:
+
+```typescript
+export async function generateMetadata({ params }: { params: Promise<{ lang: string; slug: string }> }): Promise<Metadata> {
+  const { lang, slug } = await params
+  return {
+    alternates: {
+      canonical: `https://example.com/${lang}/${slug}`,
+      languages: {
+        'en': `https://example.com/en/${slug}`,
+        'de': `https://example.com/de/${slug}`,
+        'x-default': `https://example.com/en/${slug}`,
+      },
+    },
+  }
+}
+```
+
+Include all language variants in sitemaps with `hreflang` annotations for proper indexing.

package/.agents/skills/seo-geo/.claude-plugin/plugin.json

@@ -0,0 +1,29 @@
+{
+  "name": "seo-geo",
+  "version": "1.0.0",
+  "description": "SEO & GEO (Generative Engine Optimization) for websites. Optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Includes Princeton GEO research methods for +40% AI visibility.",
+  "author": {
+    "name": "ReScienceLab"
+  },
+  "homepage": "https://github.com/ReScienceLab/opc-skills/tree/main/skills/seo-geo",
+  "repository": "https://github.com/ReScienceLab/opc-skills",
+  "license": "MIT",
+  "keywords": [
+    "SEO",
+    "GEO",
+    "search optimization",
+    "schema markup",
+    "JSON-LD",
+    "meta tags",
+    "keyword research",
+    "AI visibility",
+    "ChatGPT ranking",
+    "Perplexity"
+  ],
+  "skills": [
+    "./SKILL.md"
+  ],
+  "commands": [
+    "./scripts/"
+  ]
+}

package/.agents/skills/seo-geo/SKILL.md

@@ -0,0 +1,250 @@
+---
+name: seo-geo
+description: SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research.
+---
+
+# SEO/GEO Optimization Skill
+
+Comprehensive SEO and GEO (Generative Engine Optimization) for websites. Optimize for both traditional search engines (Google, Bing) and AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude).
+
+## Quick Reference
+
+**GEO = Generative Engine Optimization** - Optimizing content to be cited by AI search engines.
+
+**Key Insight:** AI search engines don't rank pages - they **cite sources**. Being cited is the new "ranking #1".
+
+## Workflow
+
+### Step 1: Website Audit
+
+Get the target URL and analyze current SEO/GEO status.
+
+**Basic SEO Audit (Free):**
+```bash
+python3 scripts/seo_audit.py "https://example.com"
+```
+**Use this for**: Quick technical SEO check (title, meta, H1, robots, sitemap, load time). No API needed.
+
+---
+
+**Check Meta Tags:**
+```bash
+curl -sL "https://example.com" | grep -E "<title>|<meta name=\"description\"|<meta property=\"og:|application/ld\+json" | head -20
+```
+
+**Use this for**: Quick check of essential meta tags and schema markup on any webpage.
+
+---
+
+**Check robots.txt:**
+```bash
+curl -s "https://example.com/robots.txt"
+```
+
+**Use this for**: Verify which bots are allowed/blocked. Critical for ensuring AI search engines can crawl your site.
+
+---
+
+**Check sitemap:**
+```bash
+curl -s "https://example.com/sitemap.xml" | head -50
+```
+
+**Use this for**: Verify sitemap structure and ensure all important pages are included for search engine discovery.
+
+**Verify AI Bot Access:**
+```
+# These bots should be allowed in robots.txt:
+- Googlebot (Google)
+- Bingbot (Bing/Copilot)
+- PerplexityBot (Perplexity)
+- ChatGPT-User (ChatGPT with browsing)
+- ClaudeBot / anthropic-ai (Claude)
+- GPTBot (OpenAI)
+```
+
+### Step 2: Keyword Research
+
+Use **WebSearch** to research target keywords:
+
+```
+WebSearch: "{keyword} keyword difficulty site:ahrefs.com OR site:semrush.com"
+WebSearch: "{keyword} search volume 2026"
+WebSearch: "site:{competitor.com} {keyword}"
+```
+
+**Analyze:**
+- Search volume and difficulty
+- Competitor keyword strategies
+- Long-tail keyword opportunities
+- International keyword conflicts (e.g., "OPC" = industrial automation in English markets)
+
+### Step 3: GEO Optimization (AI Search Engines)
+
+Apply the **9 Princeton GEO Methods** (see [references/geo-research.md](./references/geo-research.md)):
+
+| Method | Visibility Boost | How to Apply |
+|--------|-----------------|--------------|
+| **Cite Sources** | +40% | Add authoritative citations and references |
+| **Statistics Addition** | +37% | Include specific numbers and data points |
+| **Quotation Addition** | +30% | Add expert quotes with attribution |
+| **Authoritative Tone** | +25% | Use confident, expert language |
+| **Easy-to-understand** | +20% | Simplify complex concepts |
+| **Technical Terms** | +18% | Include domain-specific terminology |
+| **Unique Words** | +15% | Increase vocabulary diversity |
+| **Fluency Optimization** | +15-30% | Improve readability and flow |
+| ~~Keyword Stuffing~~ | **-10%** | **AVOID - hurts visibility** |
+
+**Best Combination:** Fluency + Statistics = Maximum boost
+
+**Generate FAQPage Schema** (+40% AI visibility):
+```json
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [{
+    "@type": "Question",
+    "name": "What is [topic]?",
+    "acceptedAnswer": {
+      "@type": "Answer",
+      "text": "According to [source], [answer with statistics]."
+    }
+  }]
+}
+```
+
+**Optimize Content Structure:**
+- Use "answer-first" format (direct answer at top)
+- Clear H1 > H2 > H3 hierarchy
+- Bullet points and numbered lists
+- Tables for comparison data
+- Short paragraphs (2-3 sentences max)
+
+### Step 4: Traditional SEO Optimization
+
+**Meta Tags Template:**
+```html
+<title>{Primary Keyword} - {Brand} | {Secondary Keyword}</title>
+<meta name="description" content="{Compelling description with keyword, 150-160 chars}">
+<meta name="keywords" content="{keyword1}, {keyword2}, {keyword3}">
+
+<!-- Open Graph -->
+<meta property="og:title" content="{Title}">
+<meta property="og:description" content="{Description}">
+<meta property="og:image" content="{Image URL 1200x630}">
+<meta property="og:url" content="{Canonical URL}">
+<meta property="og:type" content="website">
+
+<!-- Twitter Cards -->
+<meta name="twitter:card" content="summary_large_image">
+<meta name="twitter:title" content="{Title}">
+<meta name="twitter:description" content="{Description}">
+<meta name="twitter:image" content="{Image URL}">
+```
+
+**JSON-LD Schema** (see [references/schema-templates.md](./references/schema-templates.md)):
+- WebPage / Article for content pages
+- FAQPage for FAQ sections
+- Product for product pages
+- Organization for about pages
+- SoftwareApplication for tools/apps
+
+**Check Content:**
+- [ ] H1 contains primary keyword
+- [ ] Images have descriptive alt text
+- [ ] Internal links to related content
+- [ ] External links have `rel="noopener noreferrer"`
+- [ ] Content is mobile-friendly
+- [ ] Page loads in < 3 seconds
+
+### Step 5: Validate & Monitor
+
+**Schema Validation:**
+```bash
+# Open Google Rich Results Test
+open "https://search.google.com/test/rich-results?url={encoded_url}"
+
+# Open Schema.org Validator
+open "https://validator.schema.org/?url={encoded_url}"
+```
+
+**Check Indexing Status:**
+```bash
+# Google (use Search Console API or manual check)
+open "https://www.google.com/search?q=site:{domain}"
+
+# Bing
+open "https://www.bing.com/search?q=site:{domain}"
+```
+
+**Generate Report:**
+```markdown
+## SEO/GEO Optimization Report
+
+### Current Status
+- Meta Tags: ✅/❌
+- Schema Markup: ✅/❌
+- AI Bot Access: ✅/❌
+- Mobile Friendly: ✅/❌
+- Page Speed: X seconds
+
+### Recommendations
+1. [Priority 1 action]
+2. [Priority 2 action]
+3. [Priority 3 action]
+
+### GEO Optimizations Applied
+- [ ] FAQPage schema added
+- [ ] Statistics included
+- [ ] Citations added
+- [ ] Answer-first structure
+```
+
+## Platform-Specific Optimization
+
+See [references/platform-algorithms.md](./references/platform-algorithms.md) for detailed ranking factors.
+
+### ChatGPT
+- Focus on **branded domain authority** (cited 11% more than third-party)
+- Update content within **30 days** (3.2x more citations)
+- Build **backlinks** (>350K referring domains = 8.4 avg citations)
+- Match content style to ChatGPT's response format
+
+### Perplexity
+- Allow **PerplexityBot** in robots.txt
+- Use **FAQ Schema** (higher citation rate)
+- Host **PDF documents** (prioritized for citation)
+- Focus on **semantic relevance** over keywords
+
+### Google AI Overview (SGE)
+- Optimize for **E-E-A-T** (Experience, Expertise, Authority, Trust)
+- Use **structured data** (Schema markup)
+- Build **topical authority** (content clusters + internal linking)
+- Include **authoritative citations** (+132% visibility)
+
+### Microsoft Copilot / Bing
+- Ensure **Bing indexing** (required for citation)
+- Optimize for **Microsoft ecosystem** (LinkedIn, GitHub mentions help)
+- Page speed **< 2 seconds**
+- Clear **entity definitions**
+
+### Claude AI
+- Ensure **Brave Search indexing** (Claude uses Brave, not Google)
+- High **factual density** (data-rich content preferred)
+- Clear **structural clarity** (easy to extract)
+
+## Skill Dependencies
+
+This skill works best with:
+- **twitter skill** - Search SEO experts for latest tips
+- **reddit skill** - Search r/SEO, r/bigseo for discussions
+- **WebSearch** - Keyword research and competitor analysis
+
+## References
+
+- [references/platform-algorithms.md](./references/platform-algorithms.md) - Detailed ranking factors for each platform
+- [references/geo-research.md](./references/geo-research.md) - Princeton GEO research (9 methods)
+- [references/schema-templates.md](./references/schema-templates.md) - JSON-LD templates
+- [references/seo-checklist.md](./references/seo-checklist.md) - Complete SEO audit checklist
+- [references/tools-and-apis.md](./references/tools-and-apis.md) - Tools and API reference
+- [examples/opc-skills-case-study.md](./examples/opc-skills-case-study.md) - Real-world optimization example