seo-entity
Use when optimizing entity-based / semantic SEO 2026. Covers entity maps, Google Knowledge Graph resolution, salience scoring, passage-level ranking, about/sameAs/knowsAbout schema, Cloud Natural Language API validation.
What this skill does
# Entity-Based / Semantic SEO 2026
Google parses meaning at query, document and **passage** level. It extracts entities via NLP, resolves them against the Knowledge Graph (~8 billion entities), maps relationships, and indexes content **by concept, not by keyword**. TF-IDF / keyword density is obsolete — optimize for embeddings and topical coverage instead.
## Entity Map (start here)
Strategic inventory that drives everything else. For the target topic, list every entity the site should cover:
| Entity | Type | Relates to | Page covering it |
|--------|------|-----------|------------------|
| RankBrain | concept | Google, ranking | /guides/rankbrain |
| Google | organization | search engine | /about |
Types: person, concept, organization, product. Breadth of entity coverage + internal linking density + publishing consistency = topical authority.
## Salience (0–1, relative)
- NLP scores each entity's prominence; scores across all entities on a page **sum to ~1.0** — entities compete for share.
- Entity in the **H1 + first 100 words** = max salience.
- Repetition does NOT raise salience. **Clear writing in proper context does.**
- Example: a passage can score RankBrain 0.584 vs Google 0.231 even when "Google" is the grammatical subject — salience distribution reveals the real topical focus.
## Passage-Level Ranking
Google scores **per passage, not per page**. Each passage is judged on entity salience, relationship clarity, and topical relevance. A page ranks for broad topic queries when its entity signals are clear and unambiguous — not just for the exact keyword.
## Schema Linking (resolve identity, don't make Google guess)
- `about` → **Wikidata URI** of the page's primary entity (the node in the Knowledge Graph).
- `sameAs` on author/organization → LinkedIn, Wikipedia, Wikidata profiles.
- `knowsAbout` on author/organization → entities they have demonstrated expertise in.
```json
{
"@type": "Article",
"about": { "@type": "Thing", "name": "Knowledge Graph",
"sameAs": "https://www.wikidata.org/wiki/Q3882486" },
"author": { "@type": "Person", "name": "Jane Doe",
"sameAs": ["https://www.linkedin.com/in/janedoe",
"https://en.wikipedia.org/wiki/Jane_Doe"],
"knowsAbout": ["semantic SEO", "NLP"] }
}
```
## Validation (before publishing)
Send content to the **Google Cloud Natural Language API** (free tier). It returns identified entities, types, salience scores, and Knowledge Graph links. Use it to confirm the primary entity actually wins salience; rewrite passages if salience drifts off-topic.
## Related
- `seo-schema` — JSON-LD types and templates
- `seo-geo` — entity signals drive AI citations
- `seo-content` — topical coverage and answer capsules
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".