linking-and-schema

linking-and-schema is a skill for Claude Code from siddiqss/semantic-seo-suite. It costs 92 tokens per session (753 once invoked), scanned A, original, MIT.

A planning skill that maps how pages should link to one another and creates JSON-LD structured data. JSON-LD is a machine-readable description of a page that search engines can use to understand its content.

In plain words
What is it for?
Use it to plan internal links, choose descriptive anchor text, find link-structure issues, and generate schema markup from a topical map and entity profile.
Why use it?
It helps turn a topic structure into a usable site link structure and flags likely orphan pages, over-linked hubs, and other link problems. It also avoids adding unsupported facts to structured data.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is python ../../scripts/linking_plan.py --map brands/<slug>/topical-map.json \.

Part of the semantic-seo-suite plugin — 10 skills shipped together

Good fit Use it to plan internal links, choose descriptive anchor text, find link-structure issues, and generate schema markup from a topical map and entity profile.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/siddiqss/semantic-seo-suite
agentmods
npx agentmods add skills/siddiqss/semantic-seo-suite/linking-and-schema

Made for: Claude Code.

Or install semantic-seo-suite, the plugin that ships this one along with the rest of its 10 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for linking-and-schema

README.md
[![agentmods](https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/linking-and-schema/github.svg)](https://agentmods.dev/skills/siddiqss/semantic-seo-suite/linking-and-schema)
Your own site
<a href="https://agentmods.dev/skills/siddiqss/semantic-seo-suite/linking-and-schema"><img src="https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/linking-and-schema/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for linking-and-schema

Your own site · 80×15
<a href="https://agentmods.dev/skills/siddiqss/semantic-seo-suite/linking-and-schema"><img src="https://agentmods.dev/badge/skills/siddiqss/semantic-seo-suite/linking-and-schema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 753 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.00753
Opus 5 $0.00046 $0.00377
Sonnet 5 $0.00018 $0.00151
Haiku 4.5 $0.00009 $0.00075

Measured 12d ago against content hash d29e7e34138c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

linking-and-schema scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/linking-and-schema/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

linking-and-schema

Turn the map into a link graph and structured data. Both outputs are deterministic and carry the framework's fact discipline: laterals are justified (not sprayed), anchors are varied (not exact-match spam), and schema never states an ungrounded fact.

Read first: ../../framework/internal-linking-rules.md, ../../framework/schema-jsonld.md, ../../framework/eeat-signals.md.

Preconditions

  • topical-map.json and entity-profile.json for the brand.
  • Optional: map embeddings (for lateral justification) and crawl data (for real orphans).

Workflow

  1. Internal-linking plan:

    python ../../scripts/linking_plan.py --map brands/<slug>/topical-map.json \
      [--vecs brands/<slug>/data/embeddings/map.npz --lateral-threshold 0.72] \
      [--crawl-dir brands/<slug>/data/crawl] --brand "<Brand>" \
      --out brands/<slug>/audits/linking-plan.md
    

    For each node it emits up/down/justified-lateral links with varied, descriptive anchors drawn from the target's query network, plus link-health flags (planned-graph orphans, over-linked hubs, and real crawl orphans if crawl data is present). Laterals below the embedding threshold are marked REVIEW rather than dropped or trusted.

  2. JSON-LD schema:

    python ../../scripts/schema_jsonld.py --map brands/<slug>/topical-map.json \
      --entity-profile brands/<slug>/entity-profile.json \
      --locked brands/<slug>/locked-facts.json \
      --out-dir brands/<slug>/data/schema
    

    Emits one .jsonld per node (HowTo / FAQPage / Product / Article), a site-level Organization graph, and a checklist.md. Product Offer prices come ONLY from locked facts; FAQ/HowTo answer text is left as a placeholder to be filled from the validated draft — so no invented answer ships in markup.

  3. Hand off: give the user the link checklist (page → insert link → suggested anchor → where) and the schema files. Note that syntactic validation here is necessary but not sufficient — run Google's Rich Results Test before publishing.

Read the full file on GitHub · 66 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 66 lines · 92 tokens per session scan A d29e7e34138c

Subscribe to this mod's changes

linking-and-schema is a skill published in the GitHub repository siddiqss/semantic-seo-suite (9 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 753 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.