Algo SEO Schema Agent Skill
Implement Schema.org structured data markup in JSON-LD format for enhanced search results. Use this skill when the user needs to add rich snippets to web pages, implement FAQ/Product/Article schema, or validate structured data — even if they say 'rich snippets', 'structured data', or 'Google rich results'.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/asgard-ai-platform/skills --skill algo-seo-schemaWhat comes with it
26 756 bytes besides the instructionThe instruction itself
14 sections, as written by the authorSchema.org Structured Data
Overview
Schema.org structured data provides machine-readable page context to search engines via JSON-LD. Enables rich results (stars, FAQs, breadcrumbs, product cards) in SERPs. Implementation is O(1) per page — it's a markup task, not computational.
When to Use
Trigger conditions:
- Adding rich snippet eligibility to web pages
- Implementing product, article, FAQ, HowTo, or event markup
- Debugging Google Search Console structured data errors
When NOT to use:
- When optimizing page content or keywords (use content SEO)
- When improving page speed (use Core Web Vitals optimization)
Algorithm
IRON LAW: Schema Markup Must MATCH Visible Content
Marking up content that users can't see violates Google guidelines
and risks manual penalties. Every structured data field must
correspond to content visible on the page.
Phase 1: Input Validation
Identify page type (Article, Product, FAQ, HowTo, Event, etc.). Map visible content to required and recommended schema properties.
Gate: Page type identified, all required properties have visible content.
Phase 2: Core Algorithm
- Select the correct Schema.org type from the vocabulary
- Map page content to schema properties (name, description, image, etc.)
- Build JSON-LD object with @context and @type
- Handle nested types (e.g., Product contains Offer contains Price)
- Place JSON-LD in
<script type="application/ld+json">in<head>
Phase 3: Verification
Validate with Google Rich Results Test. Check: no errors, all required fields present, no mismatch with visible content.
Gate: Passes Google Rich Results Test with zero errors.
Phase 4: Output
Return complete JSON-LD markup ready for insertion.
Output Format
{
"schema": {"@context": "https://schema.org", "@type": "Product", "name": "...", "offers": {"@type": "Offer", "price": "29.99", "priceCurrency": "TWD"}},
"validation": {"errors": 0, "warnings": 1, "eligible_rich_results": ["Product snippet"]}
}
Examples
Sample I/O
Input: FAQ page with 3 questions and answers
Expected: FAQPage schema with 3 Question/Answer pairs in JSON-LD
Edge Cases
| Input | Expected | Why |
|-------|----------|-----|
| Page with no clear type | Use WebPage as fallback | Most generic valid type |
| Multiple schemas needed | Array of JSON-LD objects | One page can have multiple types |
| Missing required field | Error, do not generate | Incomplete schema hurts more than none |
Gotchas
- Required vs recommended: Google requires certain fields per type. Missing required fields = schema ignored entirely. Check documentation per type.
- Nesting depth: Deeply nested schemas (Product > Offer > Seller > Address) are error-prone. Validate each nesting level.
- Schema spam: Adding schema for content not on the page (fake reviews, unavailable prices) triggers manual actions.
- Type specificity: Use the most specific type available. "Article" is better than "WebPage"; "NewsArticle" is better than "Article" for news content.
- Testing gap: Google Rich Results Test shows what Google sees, but not all valid schema triggers rich results. Eligibility ≠ guarantee of display.
References
- For complete property reference by type, see
references/type-properties.md - For common validation errors and fixes, see
references/validation-errors.md
Other skills for the same job
different authors, same section of the catalogue
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
How to use it
Take asgard-ai-platform/algo-seo-schema from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.