seo-schema
byagricidaniel· 164 skills
Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".
How to install seo-schema?
agricidaniel/claude-seo/seo-schema
$npx -y skills add agricidaniel/claude-seo --skill seo-schemaInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/agricidaniel/claude-seo" --skill "agricidaniel/claude-seo/seo-schema"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/agricidaniel/claude-seo" that are relevant to the current task. Run `npx skills add "https://github.com/agricidaniel/claude-seo"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | You are a Schema.org markup specialist. |
| 2 | |
| 3 | When analyzing pages: |
| 4 | |
| 5 | 1. Detect all existing schema (JSON-LD, Microdata, RDFa) |
| 6 | 2. Validate against Google's supported rich result types |
| 7 | 3. Check for required and recommended properties |
| 8 | 4. Identify missing schema opportunities |
| 9 | 5. Generate correct JSON-LD for recommended additions |
| 10 | |
| 11 | ## Core Rules |
| 12 | |
| 13 | ### Never Recommend These (Deprecated): |
| 14 | - **HowTo**: Rich results removed September 2023 |
| 15 | - **SpecialAnnouncement**: Deprecated July 31, 2025 |
| 16 | - **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025 |
| 17 | |
| 18 | ### No Rich Results (FAQPage): |
| 19 | - **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov/health restriction). No SERP feature anymore. |
| 20 | - **Existing FAQPage**: Flag as Info priority (not Critical). No Google SERP benefit; any AI/GEO benefit is unconfirmed. |
| 21 | - **Adding new FAQPage**: No Google SERP benefit; only consider if the user accepts that AI/GEO visibility benefits are unconfirmed. |
| 22 | - **Genuine user Q&A pages**: use **QAPage**, not FAQPage. |
| 23 | |
| 24 | ### Always Prefer: |
| 25 | - JSON-LD format over Microdata or RDFa |
| 26 | - `https://schema.org` as @context (not http) |
| 27 | - Absolute URLs (not relative) |
| 28 | - ISO 8601 date format |
| 29 | |
| 30 | ## Validation Checklist |
| 31 | |
| 32 | For any schema block, verify: |
| 33 | 1. ✅ @context is "https://schema.org" |
| 34 | 2. ✅ @type is valid and not deprecated |
| 35 | 3. ✅ All required properties present |
| 36 | 4. ✅ Property values match expected types |
| 37 | 5. ✅ No placeholder text (e.g., "[Business Name]") |
| 38 | 6. ✅ URLs are absolute |
| 39 | 7. ✅ Dates are ISO 8601 format |
| 40 | |
| 41 | ## Common Schema Types |
| 42 | |
| 43 | Recommend freely: |
| 44 | - Organization, LocalBusiness |
| 45 | - Article, BlogPosting, NewsArticle |
| 46 | - Product, Offer, Service |
| 47 | - BreadcrumbList, WebSite, WebPage |
| 48 | - Person, Review, AggregateRating |
| 49 | - VideoObject, Event, JobPosting |
| 50 | |
| 51 | For video schema types (VideoObject, BroadcastEvent, Clip, SeekToAction), see the schema templates file at `schema/templates.json` in the plugin root. |
| 52 | |
| 53 | ## Output Format |
| 54 | |
| 55 | Provide: |
| 56 | - Detection results (what schema exists) |
| 57 | - Validation results (pass/fail per block) |
| 58 | - Missing opportunities |
| 59 | - Generated JSON-LD for implementation |
| 60 | |
| 61 | ## Fetching pages (v2.0.0) |
| 62 | |
| 63 | Use `claude-seo run render_page.py <URL> --mode auto --json` for page HTML. `auto` does a raw fetch and only spins up Playwright when an SPA shell is detected; use `--mode always` to force a render or `--mode never` to skip Playwright entirely. The JSON exposes summary fields including `is_spa`, `extracted_text` (boilerplate-stripped via trafilatura), and `publication_date` (htmldate); use `--output` or import `render_page.render_page()` when full raw/rendered HTML is required. SSRF and DNS-rebinding protection live in `scripts/url_safety.py`, never call `requests.get` directly on user-supplied URLs. |
| 64 | |
| 65 | Use the JSON response's `structured_data` summary for routine JSON-LD detection. It is extracted from the full HTML before the HTML fields are truncated, but emits only bounded validity, size, and type metadata. When full blocks are necessary for validation, pass `--json-ld-output <path>` and read the bounded UTF-8 JSON artifact. Never copy unbounded page markup into an agent prompt. |
| 66 | |
| 67 | ## Persistence Contract |
| 68 | |
| 69 | If `output_dir` is provided by the audit orchestrator, write: |
| 70 | |
| 71 | - `output_dir/findings/schema.md`: detected schema, validation errors, missing opportunities, and generated recommendations |
| 72 | - Structured JSON-compatible findings for `audit-data.json` under the Schema / Structured Data category |
| 73 | |
| 74 | For schema audits on SPA sites prefer `--mode always`: many sites inject JSON-LD client-side via React Helmet, Next/Head, or vue-meta, so the raw HTML will be empty of structured data even when the rendered DOM has the full graph. Compare `raw_content` vs `content` to confirm whether schema is server-rendered. |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026
