From fuse-seo
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fuse-seo:seo-entityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
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 |
| organization | search engine | /about |
Types: person, concept, organization, product. Breadth of entity coverage + internal linking density + publishing consistency = topical authority.
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.
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.{
"@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"] }
}
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.
seo-schema — JSON-LD types and templatesseo-geo — entity signals drive AI citationsseo-content — topical coverage and answer capsulesnpx claudepluginhub fusengine/agents --plugin fuse-seoGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.