seo-schema

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

A structured-data specialist for Schema.org markup, usually written as JSON-LD. Structured data is information in a page’s code that helps search engines understand its content and sometimes show enhanced search results.

In plain words
What is it for?
Use it to find existing markup, validate required and recommended fields, identify useful missing types, and generate JSON-LD additions.
Why use it?
Incorrect or missing markup can prevent search engines from recognizing important details about a page and can create invalid search-result enhancements.

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 — 31 skills, 18 agents, 1 hook shipped together

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

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/agricidaniel/claude-seo/seo-schema
About the project

Claude SEO is an open-source Claude Code plugin that runs specialized agents and skills to audit websites across technical SEO, content quality, structured data, AI-search optimization, local and e-commerce SEO, and international SEO. SEO practitioners use it to produce prioritized recommendations based on primary-source guidance, with optional extensions for external data and crawling.

AgriciDaniel/claude-seo · 16,469 stars · on GitHub · claude-seo.md

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/AgriciDaniel/claude-seo

Made for: Claude Code.

Or install claude-seo, the plugin that ships this one along with the rest of its 31 skills, 18 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/agricidaniel/claude-seo/seo-schema.svg)](https://agentmods.dev/agents/agricidaniel/claude-seo/seo-schema)
Your own site
<a href="https://agentmods.dev/agents/agricidaniel/claude-seo/seo-schema"><img src="https://agentmods.dev/badge/agents/agricidaniel/claude-seo/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 914 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. ✓ AI security review Fable 5.1 · 6 Sept 2026 📄 Read the review
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.00914
Opus 5 $0.00012 $0.00457
Sonnet 5 $0.00005 $0.00183
Haiku 4.5 $0.00002 $0.00091

Measured 8d ago against content hash ea760873ac74, 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.

agents/seo-schema.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 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

Core Rules

Never Recommend These (Deprecated):

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

No Rich Results (FAQPage):

  • FAQPage: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov/health restriction). No SERP feature anymore.
    • Existing FAQPage: Flag as Info priority (not Critical). No Google SERP benefit; any AI/GEO benefit is unconfirmed.
    • Adding new FAQPage: No Google SERP benefit; only consider if the user accepts that AI/GEO visibility benefits are unconfirmed.
    • Genuine user Q&A pages: use QAPage, not FAQPage.

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 · 83 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 · 83 lines · 24 tokens per session scan A ea760873ac74

Subscribe to this mod's changes

seo-schema is an agent published in the GitHub repository AgriciDaniel/claude-seo (16,469 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 914 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

blog-reviewer

Quality assessment specialist for blog posts. Runs the full 5-category, 100-point scoring system, identifies issues by severity, checks for AI editorial style diagnostics, validates source quality, and flags unsupported factual or first-hand claims. Invoked for quality review tasks during blog workflows.

AgriciDaniel/claude-blog · 59 tokens

blog-writer

Content generation specialist for blog posts. Writes optimized articles with answer-first formatting, proper heading hierarchy, sourced statistics, and natural readability. Follows the 6 pillars of dual optimization. Invoked for content writing and rewriting tasks during blog workflows.

AgriciDaniel/claude-blog · 52 tokens

claude-blog-secretary

The owner's dedicated Claude Blog agent, grounded in the Claude Blog Brain at . Use for any blog-content work - writing and rewriting for Google rankings and AI citations, E-E-A-T, GEO and AEO, schema, topic clusters, briefs and outlines, editorial strategy, multilingual publishing, the FLOW framework, factchecking…

AgriciDaniel/claude-blog · 0 tokens

blog-cluster-curator

Topic Clusters curator for the Claude Blog Brain. Maintains and answers from the Topic Clusters theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for semantic topic clusters, hub-and-spoke architecture, internal linking, and cannibalization.

AgriciDaniel/claude-blog · 64 tokens

blog-data-curator

Data Integrations curator for the Claude Blog Brain. Maintains and answers from the Data Integrations theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for GSC, GA4, PageSpeed, CrUX, and NLP integrations plus content-decay detection.

AgriciDaniel/claude-blog · 66 tokens

blog-distribution-curator

Distribution curator for the Claude Blog Brain. Maintains and answers from the Distribution theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for multi-platform repurposing, distribution, CTA placement, and video embeds.

AgriciDaniel/claude-blog · 57 tokens