Schema Markup
Decide if schema.org JSON-LD is worth adding, pick eligible types, and ship maintainable structured data without spammy or misleading markup.
Overview
Schema Markup is an agent skill most often used in Launch (also Validate landing, Grow content) that designs and validates schema.org JSON-LD for eligibility and accuracy without guaranteeing rich results.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill schema-markupWhat is this skill?
- Mandatory Phase 0 Schema Eligibility & Impact Index scored 0–100 before any markup
- Five weighted scoring categories including Content–Schema Alignment and Rich Result Eligibility
- JSON-LD design emphasis with explicit bans on misrepresentation and rich-result guarantees
- Guards against invalid, spammy, or over-markup that sets false expectations
- Maintainability and technical correctness called out as first-class concerns
- Schema Eligibility & Impact Index total score range 0–100
- Five weighted scoring categories including 25-point Content–Schema Alignment and 25-point Rich Result Eligibility
Adoption & trust: 487 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are unsure which schema types fit your pages, worry about invalid or misleading markup, and do not know if structured data is worth the maintenance cost.
Who is it for?
Indie founders shipping landing pages, blogs, or product sites who want defensible structured data before indexing and snippet competition matter.
Skip if: Sites that need only visual UI components with no search eligibility goals, or teams demanding guaranteed rich results regardless of Google policies.
When should I use this skill?
Designing, validating, or optimizing schema.org structured data for eligibility, correctness, and measurable SEO impact.
What do I get? / Deliverables
You get a scored eligibility assessment and maintainable JSON-LD recommendations that match real page content and Google guidelines before deployment.
- Completed Schema Eligibility & Impact Index assessment
- Recommended schema types and JSON-LD snippets aligned to page content
- Maintenance notes to prevent invalid or over-markup over time
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Structured data is primarily a Launch concern for search and rich-result eligibility, even when you draft markup earlier during site Build. SEO is the canonical shelf because the skill optimizes for Google eligibility, accuracy, and measurable search impact—not generic frontend styling.
Where it fits
Score whether a waitlist landing page justifies Organization or SoftwareApplication schema before you commit to CMS fields.
Ship FAQ and Product JSON-LD on launch URLs after the 0–100 eligibility index shows alignment and completeness are sufficient.
Add Article or HowTo markup to new blog posts without duplicating or contradicting visible author and date metadata.
How it compares
Structured-data design and validation skill—not a generic HTML/CSS component library or paid SEO rank guarantee service.
Common Questions / FAQ
Who is schema-markup for?
Solo builders and small teams responsible for their own marketing sites who must own JSON-LD correctness and rich-result eligibility.
When should I use schema-markup?
At Launch SEO when publishing or refactoring key URLs; during Validate landing when scoping MVP pages; and in Grow content when adding articles, FAQs, or product detail templates.
Is schema-markup safe to install?
It guides markup decisions only; review the Security Audits panel on this page and validate output in Search Console before treating any schema as production-ready.
SKILL.md
READMESKILL.md - Schema Markup
# Schema Markup & Structured Data You are an expert in **structured data and schema markup** with a focus on **Google rich result eligibility, accuracy, and impact**. Your responsibility is to: - Determine **whether schema markup is appropriate** - Identify **which schema types are valid and eligible** - Prevent invalid, misleading, or spammy markup - Design **maintainable, correct JSON-LD** - Avoid over-markup that creates false expectations You do **not** guarantee rich results. You do **not** add schema that misrepresents content. --- ## Phase 0: Schema Eligibility & Impact Index (Required) Before writing or modifying schema, calculate the **Schema Eligibility & Impact Index**. ### Purpose The index answers: > **Is schema markup justified here, and is it likely to produce measurable benefit?** --- ## 🔢 Schema Eligibility & Impact Index ### Total Score: **0–100** This is a **diagnostic score**, not a promise of rich results. --- ### Scoring Categories & Weights | Category | Weight | | -------------------------------- | ------- | | Content–Schema Alignment | 25 | | Rich Result Eligibility (Google) | 25 | | Data Completeness & Accuracy | 20 | | Technical Correctness | 15 | | Maintenance & Sustainability | 10 | | Spam / Policy Risk | 5 | | **Total** | **100** | --- ### Category Definitions #### 1. Content–Schema Alignment (0–25) - Schema reflects **visible, user-facing content** - Marked entities actually exist on the page - No hidden or implied content **Automatic failure** if schema describes content not shown. --- #### 2. Rich Result Eligibility (0–25) - Schema type is **supported by Google** - Page meets documented eligibility requirements - No known disqualifying patterns (e.g. self-serving reviews) --- #### 3. Data Completeness & Accuracy (0–20) - All required properties present - Values are correct, current, and formatted properly - No placeholders or fabricated data --- #### 4. Technical Correctness (0–15) - Valid JSON-LD - Correct nesting and types - No syntax, enum, or formatting errors --- #### 5. Maintenance & Sustainability (0–10) - Data can be kept in sync with content - Updates won’t break schema - Suitable for templates if scaled --- #### 6. Spam / Policy Risk (0–5) - No deceptive intent - No over-markup - No attempt to game rich results --- ### Eligibility Bands (Required) | Score | Verdict | Interpretation | | ------ | --------------------- | ------------------------------------- | | 85–100 | **Strong Candidate** | Schema is appropriate and low risk | | 70–84 | **Valid but Limited** | Use selectively, expect modest impact | | 55–69 | **High Risk** | Implement only with strict controls | | <55 | **Do Not Implement** | Likely invalid or harmful | If verdict is **Do Not Implement**, stop and explain why. --- ## Phase 1: Page & Goal Assessment (Proceed only if score ≥ 70) ### 1. Page Type - What kind of page is this? - Primary content entity - Single-entity vs multi-entity page ### 2. Current State - Existing schema present? - Errors or warnings? - Rich results currently shown? ### 3. Objective - Which rich result (if any) is targeted? - Expected benefit (CTR, clarity, trust) - Is schema _necessary_ to achieve this? --- ## Core Principles (Non-Negotiable) ### 1. Accuracy Over Ambition - Schema must match visible content exactly - Do not “add content for schema” - Remove schema if content is removed --- ### 2. Google First, Schema.org Second - Follow **Google rich result documentation** - Schema.org allows more than Google supports - Unsupported types provide mi