seo-optimizer
SEO architecture and content strategy for search visibility. Covers entity-first optimization, structured data, E-E-A-T signals, AI Overviews optimization, and content auditing. Use when optimizing search rankings, implementing JSON-LD schema, improving E-E-A-T signals, auditing site performance, planning topical authority, or structuring content for AI Overviews and featured snippets.
What this skill does
# SEO Optimizer ## Overview Optimizes digital visibility through entity-based SEO, structured data, and content architecture. Focuses on AI Overviews optimization, E-E-A-T authority signals, and semantic topic clustering rather than keyword-centric approaches. **When to use:** Search ranking optimization, structured data implementation, content audits, topical authority planning, featured snippet targeting, Core Web Vitals improvement. **When NOT to use:** Paid advertising campaigns, social media strategy, email marketing, brand identity design. ## Quick Reference | Pattern | Approach | Key Points | | ----------------- | --------------------------------------- | -------------------------------------------------------------- | | AI Overviews | Question-based H2s with direct answers | 1-2 sentence answer before expanding; scannable lists | | E-E-A-T signals | Experience-led content with author bios | First-hand evidence, SME review labels, credentials | | Structured data | JSON-LD schema for entities | Organization, Article, FAQ, Breadcrumb schemas | | Topic clusters | Pillar page + cluster architecture | Internal links flow between pillar and clusters | | Semantic SEO | Intent mapping + related terms | Map pages to Informational/Commercial/Transactional intent | | Content audit | 30-point scoring methodology | Title, meta, keywords, structure, snippets, linking, technical | | Featured snippets | Format-matched content blocks | 40-60 word definitions, numbered steps, comparison tables | | Schema markup | Explicit entity definitions | Define Who/What/Where in first paragraph + Schema.org | | Content freshness | Periodic refresh protocol | Update critical articles every 6 months with current data | | Core Web Vitals | Performance-first design | LCP, CLS, INP monitoring and continuous improvement | ## Common Mistakes | Mistake | Correct Pattern | | ------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Keyword stuffing to boost rankings | Use semantic SEO with semantically related terms and natural language | | Publishing generic AI-generated content without expert review | Lead with first-hand experience and E-E-A-T signals | | Ignoring Core Web Vitals (LCP, CLS, INP) impact on rankings | Implement performance-first design and monitor vitals continuously | | Using hidden or incomplete JSON-LD schema markup | Define explicit, complete structured data that maps entities clearly | | Building thin affiliate pages without topical depth | Create pillar pages with full cluster coverage | | Writing definitions longer than 60 words for snippet targeting | Keep definition paragraphs to 40-60 words for featured snippet eligibility | | Using non-descriptive anchor text like "click here" or "read more" | Use keyword-rich descriptive anchor text that describes the destination | | Missing primary keyword from title, description, or first 100 words | Place primary keyword in title, meta description, first paragraph, and one H2 | ## Delegation - **Audit a site for technical SEO issues, missing schema, and Core Web Vitals problems**: Use `Explore` agent to crawl pages and identify structured data gaps - **Implement JSON-LD schema markup and meta tags across page templates**: Use `Task` agent to add Organization, Article, FAQ, and Breadcrumb schemas - **Plan a topical authority strategy with pillar pages and content clusters**: Use `Plan` agent to map keyword intent, cluster hierarchy, and internal linking architecture ## References - [AI Overviews optimization and search visibility](references/ai-overviews.md) - [E-E-A-T standards and authority building](references/eeat-standards.md) - [Semantic entity SEO and topic clusters](references/semantic-entity-seo.md) - [Schema markup patterns with JSON-LD](references/schema-markup.md) - [Content audit methodology and scoring](references/content-audit.md)
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".