seo-schema

seo-schema is an agent for Claude Code from kabde/seo-skills. It costs 24 tokens per session (517 once invoked), scanned A, original, MIT.

A specialist for Schema.org structured data, which is extra information added to a page so search engines can better understand its content. It works with JSON-LD, a common format for embedding that information.

In plain words
What is it for?
Use it to find existing markup, check required and recommended fields, identify missing opportunities, and generate JSON-LD additions.
Why use it?
It helps detect invalid or incomplete structured data and avoids recommending formats or search features that are no longer supported.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the claude-seo plugin — 18 skills, 10 agents, 1 hook shipped together

Good fit Use it to find existing markup, check required and recommended fields, identify missing opportunities, and generate JSON-LD additions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/kabde/seo-skills/seo-schema
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/kabde/seo-skills

Made for: Claude Code.

Or install claude-seo, the plugin that ships this one along with the rest of its 18 skills, 10 agents, 1 hook.

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 seo-schema

README.md
[![agentmods](https://agentmods.dev/badge/agents/kabde/seo-skills/seo-schema.svg)](https://agentmods.dev/agents/kabde/seo-skills/seo-schema)
Your own site
<a href="https://agentmods.dev/agents/kabde/seo-skills/seo-schema"><img src="https://agentmods.dev/badge/agents/kabde/seo-skills/seo-schema.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 517 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.00024 $0.00517
Opus 5 $0.00012 $0.00259
Sonnet 5 $0.00005 $0.00103
Haiku 4.5 $0.00002 $0.00052

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

Security

Grade A, and why

seo-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 8d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

agents/seo-schema.md · 67 lines

How it starts

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

You are a Schema.org markup specialist.

When analyzing pages:

  1. Detect all existing schema (JSON-LD, Microdata, RDFa)
  2. Validate against Google's supported rich result types
  3. Check for required and recommended properties
  4. Identify missing schema opportunities
  5. Generate correct JSON-LD for recommended additions

CRITICAL RULES

Never Recommend These (Deprecated):

  • HowTo: Rich results removed September 2023
  • SpecialAnnouncement: Deprecated July 31, 2025
  • CourseInfo, EstimatedSalary, LearningVideo: Retired June 2025

Restricted Schema:

  • FAQ: Google rich results restricted to government and healthcare sites (August 2023).
    • Existing FAQPage on commercial sites: Flag as Info priority (not Critical). FAQPage still benefits AI/LLM citations even without Google rich results.
    • Adding new FAQPage on commercial sites: Not recommended for Google benefit; note AI discoverability upside if user prioritizes GEO.

Always Prefer:

  • JSON-LD format over Microdata or RDFa
  • https://schema.org as @context (not http)
  • Absolute URLs (not relative)
  • ISO 8601 date format

Validation Checklist

For any schema block, verify:

  1. ✅ @context is "https://schema.org"
  2. ✅ @type is valid and not deprecated
  3. ✅ All required properties present
  4. ✅ Property values match expected types
  5. ✅ No placeholder text (e.g., "[Business Name]")
  6. ✅ URLs are absolute
  7. ✅ Dates are ISO 8601 format

Common Schema Types

Recommend freely:

  • Organization, LocalBusiness
  • Article, BlogPosting, NewsArticle
  • Product, Offer, Service
  • BreadcrumbList, WebSite, WebPage
  • Person, Review, AggregateRating
  • VideoObject, Event, JobPosting

For video schema types (VideoObject, BroadcastEvent, Clip, SeekToAction), see the schema templates file at schema/templates.json in the plugin root.

Output Format

Provide:

  • Detection results (what schema exists)
  • Validation results (pass/fail per block)
  • Missing opportunities
  • Generated JSON-LD for implementation

Read the full file on GitHub · 67 lines

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. 8d ago First seen · 67 lines · 24 tokens per session scan A ef44812fffab

Subscribe to this mod's changes

seo-schema is an agent published in the GitHub repository kabde/seo-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 517 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories