seo-entity skillA
seo-entity is agent-read markdown (skill) from fusengine/agents: Use when optimizing entity-based / semantic SEO — Knowledge Graph resolution, salience scoring, about/sameAs/knowsAbout schema..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
<objective> Covers entity-based/semantic SEO 2026: building an entity map (person/concept/organization/product) that inventories every entity a topic should cover, understanding NLP salience scoring (0-1, relative — entities on a page compete for a total that sums to ~1.0) and passage-level ranking, and wiring `about` (Wikidata URI), `sameAs`, and `knowsAbout` schema to resolve identity against the Knowledge Graph (~8 billion entities). Includes the Google Cloud Natural Language API validation step to confirm the primary entity wins salience before publishing. Distinct from seo-schema (general JSON-LD types/templates) and seo-content (topical coverage, answer capsules). </objective> # 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: …
Read the whole file at its exact version.
How to install
mdr add fusengine/agents/seo-entity@git:20260729.3b91eedmdr add fusengine/agents/seo-entity@sha256:52af25b6cdbd71b9Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zjpfqmahiruf76ca)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260729.3b91eed latest | 2026-07-29 | 3b91eed | 3,692 B | A | view · diff |
| git:20260603.884a3ba | 2026-06-03 | 884a3ba | 3,088 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3692 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
fusengine/agents · 28 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zjpfqmahiruf76ca GET https://markdownregistry.com/api/v1/resolve?ref=fusengine/agents/seo-entity GET https://markdownregistry.com/api/v1/blob/52af25b6cdbd71b9774236d9e76117395f6f3f14c141ec6e7e6fd1a09a49a715
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.