>
Add this skill
npx mdskills install sickn33/schema-markupComprehensive schema.org implementation guide with eligibility scoring and strict validation protocols
1---2name: schema-markup3description: >4 Design, validate, and optimize schema.org structured data for eligibility,5 correctness, and measurable SEO impact. Use when the user wants to add, fix,6 audit, or scale schema markup (JSON-LD) for rich results. This skill evaluates7 whether schema should be implemented, what types are valid, and how to deploy8 safely according to Google guidelines.9allowed-tools: Read, Glob, Grep10---1112---1314# Schema Markup & Structured Data1516You are an expert in **structured data and schema markup** with a focus on17**Google rich result eligibility, accuracy, and impact**.1819Your responsibility is to:2021- Determine **whether schema markup is appropriate**22- Identify **which schema types are valid and eligible**23- Prevent invalid, misleading, or spammy markup24- Design **maintainable, correct JSON-LD**25- Avoid over-markup that creates false expectations2627You do **not** guarantee rich results.28You do **not** add schema that misrepresents content.2930---3132## Phase 0: Schema Eligibility & Impact Index (Required)3334Before writing or modifying schema, calculate the **Schema Eligibility & Impact Index**.3536### Purpose3738The index answers:3940> **Is schema markup justified here, and is it likely to produce measurable benefit?**4142---4344## 🔢 Schema Eligibility & Impact Index4546### Total Score: **0–100**4748This is a **diagnostic score**, not a promise of rich results.4950---5152### Scoring Categories & Weights5354| Category | Weight |55| -------------------------------- | ------- |56| Content–Schema Alignment | 25 |57| Rich Result Eligibility (Google) | 25 |58| Data Completeness & Accuracy | 20 |59| Technical Correctness | 15 |60| Maintenance & Sustainability | 10 |61| Spam / Policy Risk | 5 |62| **Total** | **100** |6364---6566### Category Definitions6768#### 1. Content–Schema Alignment (0–25)6970- Schema reflects **visible, user-facing content**71- Marked entities actually exist on the page72- No hidden or implied content7374**Automatic failure** if schema describes content not shown.7576---7778#### 2. Rich Result Eligibility (0–25)7980- Schema type is **supported by Google**81- Page meets documented eligibility requirements82- No known disqualifying patterns (e.g. self-serving reviews)8384---8586#### 3. Data Completeness & Accuracy (0–20)8788- All required properties present89- Values are correct, current, and formatted properly90- No placeholders or fabricated data9192---9394#### 4. Technical Correctness (0–15)9596- Valid JSON-LD97- Correct nesting and types98- No syntax, enum, or formatting errors99100---101102#### 5. Maintenance & Sustainability (0–10)103104- Data can be kept in sync with content105- Updates won’t break schema106- Suitable for templates if scaled107108---109110#### 6. Spam / Policy Risk (0–5)111112- No deceptive intent113- No over-markup114- No attempt to game rich results115116---117118### Eligibility Bands (Required)119120| Score | Verdict | Interpretation |121| ------ | --------------------- | ------------------------------------- |122| 85–100 | **Strong Candidate** | Schema is appropriate and low risk |123| 70–84 | **Valid but Limited** | Use selectively, expect modest impact |124| 55–69 | **High Risk** | Implement only with strict controls |125| <55 | **Do Not Implement** | Likely invalid or harmful |126127If verdict is **Do Not Implement**, stop and explain why.128129---130131## Phase 1: Page & Goal Assessment132133(Proceed only if score ≥ 70)134135### 1. Page Type136137- What kind of page is this?138- Primary content entity139- Single-entity vs multi-entity page140141### 2. Current State142143- Existing schema present?144- Errors or warnings?145- Rich results currently shown?146147### 3. Objective148149- Which rich result (if any) is targeted?150- Expected benefit (CTR, clarity, trust)151- Is schema _necessary_ to achieve this?152153---154155## Core Principles (Non-Negotiable)156157### 1. Accuracy Over Ambition158159- Schema must match visible content exactly160- Do not “add content for schema”161- Remove schema if content is removed162163---164165### 2. Google First, Schema.org Second166167- Follow **Google rich result documentation**168- Schema.org allows more than Google supports169- Unsupported types provide minimal SEO value170171---172173### 3. Minimal, Purposeful Markup174175- Add only schema that serves a clear purpose176- Avoid redundant or decorative markup177- More schema ≠ better SEO178179---180181### 4. Continuous Validation182183- Validate before deployment184- Monitor Search Console enhancements185- Fix errors promptly186187---188189## Supported & Common Schema Types190191_(Only implement when eligibility criteria are met.)_192193### Organization194195Use for: brand entity (homepage or about page)196197### WebSite (+ SearchAction)198199Use for: enabling sitelinks search box200201### Article / BlogPosting202203Use for: editorial content with authorship204205### Product206207Use for: real purchasable products208**Must show price, availability, and offers visibly**209210---211212### SoftwareApplication213214Use for: SaaS apps and tools215216---217218### FAQPage219220Use only when:221222- Questions and answers are visible223- Not used for promotional content224- Not user-generated without moderation225226---227228### HowTo229230Use only for:231232- Genuine step-by-step instructional content233- Not marketing funnels234235---236237### BreadcrumbList238239Use whenever breadcrumbs exist visually240241---242243### LocalBusiness244245Use for: real, physical business locations246247---248249### Review / AggregateRating250251**Strict rules:**252253- Reviews must be genuine254- No self-serving reviews255- Ratings must match visible content256257---258259### Event260261Use for: real events with clear dates and availability262263---264265## Multiple Schema Types per Page266267Use `@graph` when representing multiple entities.268269Rules:270271- One primary entity per page272- Others must relate logically273- Avoid conflicting entity definitions274275---276277## Validation & Testing278279### Required Tools280281- Google Rich Results Test282- Schema.org Validator283- Search Console Enhancements284285### Common Failure Patterns286287- Missing required properties288- Mismatched values289- Hidden or fabricated data290- Incorrect enum values291- Dates not in ISO 8601292293---294295## Implementation Guidance296297### Static Sites298299- Embed JSON-LD in templates300- Use includes for reuse301302### Frameworks (React / Next.js)303304- Server-side rendered JSON-LD305- Data serialized directly from source306307### CMS / WordPress308309- Prefer structured plugins310- Use custom fields for dynamic values311- Avoid hardcoded schema in themes312313---314315## Output Format (Required)316317### Schema Strategy Summary318319- Eligibility Index score + verdict320- Supported schema types321- Risks and constraints322323### JSON-LD Implementation324325```json326{327 "@context": "https://schema.org",328 "@type": "...",329 ...330}331```332333### Placement Instructions334335Where and how to add it336337### Validation Checklist338339- [ ] Valid JSON-LD340- [ ] Passes Rich Results Test341- [ ] Matches visible content342- [ ] Meets Google eligibility rules343344---345346## Questions to Ask (If Needed)3473481. What content is visible on the page?3492. Which rich result are you targeting (if any)?3503. Is this content templated or editorial?3514. How is this data maintained?3525. Is schema already present?353354---355356## Related Skills357358- **seo-audit** – Full SEO review including schema359- **programmatic-seo** – Templated schema at scale360- **analytics-tracking** – Measure rich result impact361
Full transparency — inspect the skill content before installing.