Generates JSON-LD structured data for 10 schema types (FAQPage, Article, Product, etc.) with Google rich result validation and paste-ready <script> blocks for page <head>.
From antigravity-awesome-skillsnpx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-awesome-skillsThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Generates implementation-ready JSON-LD schema markup for 10 schema types including FAQPage, Article, Product, HowTo, and BreadcrumbList. Validates all required fields against Google rich result eligibility rules, flags missing fields with exact fix instructions, and outputs one clean <script> block per schema type ready to paste into the page <head>.
Part of the SEO-AEO Engine.
| Type | Rich Result Unlocked |
|---|---|
| FAQPage | FAQ accordion in SERP — AEO critical |
| Article | Article rich result, Top Stories |
| Product | Price, availability, rating in SERP |
| HowTo | Step-by-step rich result |
| Review | Star rating in SERP |
| AggregateRating | Star rating with review count |
| BreadcrumbList | Breadcrumb path in SERP URL |
| Organization | Brand knowledge panel signals |
| WebPage | Enhanced page understanding |
| WebSite | Sitelinks Searchbox |
If schema types are not specified, recommend the appropriate types based on the page type. Landing pages get FAQPage + Product + BreadcrumbList. Blog posts get Article + FAQPage + BreadcrumbList.
Using your knowledge of schema.org and Google's rich result requirements, construct the JSON-LD template for each requested schema type. Use the required and recommended fields listed in the Google Rich Results documentation for that type.
Map all page data to template placeholders. Check every required field against the rich result eligibility rules.
Flag any missing required field as a Critical issue. Flag missing recommended fields as warnings. Do not output schema with missing required fields.
Write one <script type="application/ld+json"> block per schema type. Include implementation instructions and testing tool links.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is Syncro?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Syncro is a remote-first project management platform for distributed engineering teams. It centralises task tracking, async communication, and sprint planning in one tool."
}
}
]
}
</script>
<script> block per schema type — never combine multiple typeshttps://Problem: Schema passes validation but rich result doesn't appear in search Solution: Rich results can take weeks to appear after deployment. Request re-indexing in Google Search Console immediately after adding schema.
Problem: Product schema missing star rating display Solution: Add AggregateRating object with ratingValue, reviewCount, bestRating, and worstRating — all four fields required.
@seo-aeo-landing-page-writer — provides the FAQ and product data for schema population@seo-aeo-content-quality-auditor — flags schema gaps during the audit