seoskills.sh
Catalog/On-Page SEO/SEO Entity Linking

SEO Entity Linking

Audit and generate entity & knowledge-graph linkage for a page — verify sameAs identity links (Wikidata/Wikipedia/LinkedIn/Crunchbase/official profiles) on Organization/Person, check NAP/entity consistency for local, confirm a defined primary entity, and measure entity density, then propose ready-to-inject sameAs/about/mentions references.

Listed ·Updated

171 installs

Install data from skills.sh

Use this skill

Free
$ npx skills add https://github.com/hainrixz/claude-seo-ai --skill seo-entity-linking
Basic pattern scan of SKILL.md text: no matches (checked October 2, 2026)
Runs shell commandsFetches web pages
Uses shared files

This skill is one module of the author's Claude Code plugin and runs the plugin's shared scripts, which a single-skill install does not copy. For the full audit, install the plugin: run "/plugin marketplace add Hainrixz/claude-seo-ai", then "/plugin install claude-seo-ai@claude-seo-ai". That works in Claude Code only.

View the repository

Category
Repository
hainrixz/claude-seo-ai
GitHub stars
71
License
MIT

About this skill

SEO Entity Linking is an On-Page SEO skill for AI agents, published in the seoskills.sh catalog. Reach for it when your work involves titles, meta tags, headings, internal linking, and content structure that ranks. Install it with one command and it runs inside your own agent, so the work happens in your workflow, not a separate SEO tool.

Embed a badge

seoskills.sh listing badge

SKILL.md

seo-entity-linking (M6)

Entity linkage tells search engines and AI systems which real-world thing a page is about and ties it to the Knowledge Graph. Reference: references/schema-tier1.md (the sameAs/@id/Person+Organization rules). This module owns the sameAs detail M5 defers here.

Inputs

Work from the PageSnapshot named in your dispatch envelope: read parsed from <run_dir>/pages/<slug>.json (jsonld[], anchors[]); Grep pages/<slug>.html for verbatim evidence; site artifacts live in <run_dir>/site/{robots.json,sitemaps.json,discovery.json}. Deterministic findings already emitted by audit.mjs are listed in <run_dir>/findings.deterministic.json — do not re-emit those ids; add model-judged findings only. If invoked directly with a URL/path and no snapshot exists, first run node "${CLAUDE_PLUGIN_ROOT}/scripts/snapshot.mjs" <target> --out "${CLAUDE_PLUGIN_DATA}/runs" and use the printed snapshot path.

Audits

Working from the PageSnapshot (parsed_rendered when render.used is not none, else parsed):

  1. sameAs identity links: for Organization/Person entities, check for sameAs[] resolving to canonical identities — Wikidata QID, Wikipedia, LinkedIn, Crunchbase, official social/company profiles. Wikidata is the strongest Knowledge Graph target.
  2. Primary entity defined: confirm exactly one clear primary entity per page (via @id + mainEntity/mainEntityOfPage), not an ambiguous or missing subject.
  3. Entity consistency (local): for LocalBusiness, verify NAP (name, address, telephone) in schema matches visible on-page NAP and is internally consistent across blocks.
  4. Entity density: count distinct linked/marked entities (@idd nodes, sameAs targets, about/mentions) — flag thin pages with no resolvable entity references.

Fixes

  • AUTO (fixable: auto): inject a sameAs[] array on Organization/Person using only user-confirmed URLs, and add about/mentions entity references to existing schema. Additive, deterministic diffs for fix. Never invent identity links — if a URL is unconfirmed, leave a clearly-marked TODO placeholder the user fills.
  • PROPOSED (fixable: proposed): a candidate Wikidata/LinkedIn match found by lookup — drafted for per-item human accept, never auto-written.
  • ADVISORY (fixable: advisory): "establish a Wikidata entity / claim profiles" when none exist — guidance only, the tool writes nothing.

Verification

  • dom_assert: confirm sameAs/@id/mainEntity present and well-formed in the parsed JSON-LD.
  • Resolve each sameAs URL (Tier 1 Wikidata lookup) to confirm it is live and refers to the asserted entity — a dead or mismatched link is a fail, not a pass.
  • When the live lookup tier is unavailable, status is needs_api, never a false pass.

Findings

Emit findings per schema/finding.schema.json; axis ai; confidence directional throughout — none of these is documented by a vendor. Severity policy: 5 is reserved for catastrophic, eligibility-killing facts at site/template scope; 4 major · 3 moderate · 2 minor · 1 cosmetic · 0 informational — and only an established severity-5 fail in an active category can cap a score (references/scoring-model.md).

  • M6.organization.missing_sameas — Organization with no sameAs[] (fail, severity 3, fixable: proposed).
  • M6.page.no_primary_entity — no single defined primary entity (@id / mainEntity) on the page (warn, severity 3, fixable: advisory).
  • M6.entity.thin_density — no resolvable entity reference anywhere in the markup on a page that names real organizations, people, or products (warn, severity 3, fixable: advisory).
  • M6.person.no_wikidata_link — an author Person with no Wikidata/LinkedIn identity link (warn, severity 2, fixable: proposed).
  • M6.sameas.unresolvable — a declared sameAs URL that 404s or points at a different entity (fail, severity 3, fixable: proposed). Each finding: evidence.observed quotes the page (the entity block or its absence); verification.reproduce is a runnable assertion/lookup; expected_impact is banded + confidence-tagged (no naked %).

Honesty

  • A sameAs link does not force entry into the Knowledge Graph and produces no guaranteed ranking lift — it is a disambiguation signal, so impact stays directional, never established.
  • Never fabricate, guess, or "best-effort" an identity URL to inflate entity density — a wrong sameAs actively misleads engines and is worse than an empty array. Confirmed-only, or leave it as a TODO.
  • Entity density is a proxy for "this page is about something specific and resolvable", not a metric any engine publishes; do not chase the number for its own sake.

Not using the CLI? Copy the SKILL.md and paste it straight into ChatGPT, Claude, or any agent.

Install into your agent

$ npx skills add https://github.com/hainrixz/claude-seo-ai --skill seo-entity-linking -a claude-code

More in On-Page SEO

On-Page SEOcoreyhaines31/marketingskills

Schema

Add, fix, or optimize schema markup and structured data on your site.

66.4K installs
On-Page SEOagricidaniel/claude-seo

SEO Schema

Detect, validate, or generate Schema.org JSON-LD for a supplied page or entity.

6.2K installs
On-Page SEOagricidaniel/claude-seo

SEO Images

Image optimization analysis for SEO and performance.

5.8K installs
On-Page SEOrampstackco/claude-skills

SEO Onpage

Run a comprehensive on-page SEO audit or optimization pass covering title tags, meta descriptions, header structure, content quality, internal links, image optimization, URL hygiene, and on-page schema.

258 installs
On-Page SEOhainrixz/claude-seo-ai

SEO Meta Onpage

Audit and generate the document head — title and meta description length against the shared bands (title pass 30-60 chars, recommended 50-60; description pass 70-160, recommended 150-160), viewport, charset, <html lang>, and robots-meta sanity — flagging missing/duplicate/out-of-band values and producing length-bounded, keyword-aware replacements.

173 installs
On-Page SEOseoskills.sh

Heading Structure Auditor

Rebuilds each page's H1 to H6 outline, checks for a single H1, skipped levels and generic headings, and returns a corrected outline.

New