entity-seo
When the user wants to optimize for entity recognition, Knowledge Graph, or entity-based SEO. Also use when the user mentions "entity SEO," "entity optimization," "Knowledge Graph," "Knowledge Panel," "entity signals," "brand entity," "entity linking," "entity relationships," or "entity-first content." For structured data, use schema-markup.
What this skill does
# SEO: Entity SEO Guides entity-based SEO—making your brand, product, and authors recognizable as distinct entities in search engines' knowledge systems. Google moved from keyword-matching to meaning-based understanding (Hummingbird, RankBrain, BERT, MUM); entity understanding is central to how search processes queries. Content structured around entities can receive ~3.2× more visibility in AI-powered search. References: [Semrush](https://www.semrush.com/blog/entity-based-seo-strategy/), [Search Engine Land](https://searchengineland.com/guide/entity-first-content-optimization). **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **Entity definition**: Singular, unique, well-defined things (person, place, organization, product, event) - **Entity vs keyword**: Entities = underlying concepts; keywords = text strings - **Knowledge Graph**: Google's entity database; powers disambiguation and related concepts - **Implementation**: Schema (Organization, Person); entity signals in content; consistency across platforms ## What Is an Entity? An **entity** is a thing or concept that is singular, unique, well-defined, and distinguishable—e.g. person, place, organization, product, event. Entities have: | Attribute | Meaning | |----------|---------| | **Unique identity** | "Apple Inc." ≠ "apple (fruit)" despite same word | | **Attributes** | Founding date, location, industry | | **Relationships** | Connections to other entities (e.g. Apple Inc. → Steve Jobs, iPhone) | **Entity SEO** = optimizing so search engines can identify, categorize, and connect your brand/product/author within the knowledge graph. Keywords are ambiguous; entities maintain consistent meaning across contexts. ## Why Entity SEO Matters - **Search evolution**: Google uses entities to understand intent, not just match phrases - **Knowledge Graph**: Billions of entities and relationships; disambiguation, related concepts - **AI search**: Entity-optimized content ~3.2× more visible in AI results - **E-E-A-T**: Entity signals support Experience, Expertise, Authoritativeness, Trust. See **eeat-signals** - **GEO**: AI Overviews, Copilot, Perplexity cite entities; clear identity improves citation. See **generative-engine-optimization** ## Entity Signals (Content Best Practices) | Practice | Purpose | |----------|---------| | **Clear brand/product name** | Consistent naming; avoid confusion with similar entities | | **Author identity** | Person schema; author bio; link to author page | | **Organization identity** | Organization schema site-wide; logo, sameAs | | **Citable paragraphs** | Each block understandable on its own; supports AI extraction | | **Consistency** | Same name, description, logo across website, social, directories | ## Schema for Entity SEO ### Organization - **Placement**: **Minimum**—homepage; **Optimal**—root layout / global component (layout.tsx, _document, global header) so it appears on every page. Do **not** confine to About page; About uses AboutPage schema. See **schema-markup** for full placement table. - **Required**: `@id`, `name`, `url`; add `logo`, `sameAs` (social, Wikidata) - **Optional**: `description`, `address`, `contactPoint`; use most specific type (LocalBusiness, SoftwareApplication, etc.) when applicable **@id**: Use stable URL (e.g. `https://example.com/#organization`) for entity linking across pages. Link Organization ↔ WebSite on homepage for sitelinks searchbox. ### Person - **Use**: Author pages; Article author; team members - **Properties**: `name`, `url`; `affiliation` (Organization); `sameAs` (LinkedIn, Twitter) - **@id**: Enables entity linking; e.g. `https://example.com/author/jane/#person` See **schema-markup** for full VideoObject, Article, Product, etc.; Organization and Person are core for entity SEO. ## Knowledge Panel & Knowledge Card | Feature | Description | Obtainability | |---------|-------------|---------------| | **Knowledge Panel** | Entity info (brand, person, place) in SERP | WikiData, partnerships; most sites cannot directly obtain | | **Knowledge Card** | Top-of-SERP semantic answer | Same as Knowledge Panel | **Actions** (limited control): - **Claim**: Google Business Profile; suggest updates when available - **Consistency**: Same brand name, description, logo across all platforms - **Entity Home**: Authoritative About page as primary reference - **WikiData / Wikipedia**: Can support Knowledge Panel generation See **serp-features** for Knowledge Panel in SERP context; **multi-domain-brand-seo** for Hub-Spoke entity consistency. ## Entity & Multi-Domain / Brand When using multiple domains (Hub-Spoke): - **Consistency**: Same brand name, description, logo across Hub and Spoke - **Entity Home**: Authoritative About page on Hub as primary reference - **Schema**: Organization with subOrganization for related entities - **Entity confusion**: Avoid legacy brands, sub-brands, directories diluting brand perception See **multi-domain-brand-seo** for full strategy. ## GEO & AI Citation Entity signals strengthen GEO citation: - **Direct-answer format** + **entity signals** = clearer AI extraction - **Citable paragraphs** with clear brand/product/author identity - **Distribution**: Website, YouTube, forums, Reddit—consistent entity identity across platforms See **generative-engine-optimization** for full GEO strategy. ## Output Format - **Entity audit** (brand, product, author identity gaps) - **Schema** (Organization, Person; @id placement) - **Consistency** checklist (name, logo, description across touchpoints) - **Knowledge Panel** (claim if eligible; suggest updates) ## Related Skills - **schema-markup**: Organization, Person; @id for entity linking - **eeat-signals**: E-E-A-T; author bio; Person schema - **generative-engine-optimization**: GEO; entity signals for AI citation - **serp-features**: Knowledge Panel, Knowledge Card; SERP context - **multi-domain-brand-seo**: Entity & Knowledge Panel; Hub-Spoke consistency - **about-page-generator**: Entity Home; authoritative brand reference
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".