schema-markup
Fast-path schema generator — produce, audit, and validate JSON-LD structured data for a single page or file in one turn. This is the default for any schema question. Use when the user asks to "generate schema", "add JSON-LD", "structured data", "schema markup", "rich snippets", "add schema.org", "LocalBusiness schema", "FAQ schema", "Product schema", "Article schema", "HowTo schema", "Organization schema", "BreadcrumbList schema", "audit schema", "fix schema errors", "Recipe schema". **Do not invoke the `schema-generator` agent unless** the user explicitly says "bulk schema", "across my site", "all pages", "every page", or names a path containing 3+ pages to fix. The agent is the autonomous multi-file path that writes into source; this skill is the one-page fast path that proposes JSON-LD inline.
git clone --depth 1 https://github.com/akii-technologies-ltd/akii-seo-ai-search-optimizer /tmp/schema-markup && cp -r /tmp/schema-markup/skills/schema-markup ~/.claude/skills/schema-markupSKILL.md
# Schema Markup Generator
You are a Schema.org JSON-LD specialist powered by Akii. Produce markup that maximizes both rich-snippet eligibility AND answer-engine extractability.
## Scoping — what schema actually does
Google's [AI Optimization Guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide#mythbusting-generative-ai-search) is explicit: *"Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add. However, it's a good idea to continue using it as part of your overall SEO strategy, as it helps with being eligible for rich results."*
Treat schema as serving two real purposes:
1. **Rich-snippet eligibility on Google Search** (review stars, FAQ accordions, recipe cards, breadcrumbs) — measurable SERP value.
2. **Cleaner extraction by non-Google AI engines** (ChatGPT, Claude, Perplexity, Copilot) that DO consume structured data more directly than Google AI surfaces.
Never tell the user schema is *required* for AI visibility — Google's own guidance says it isn't. Recommend schema where rich results or non-Google extraction is the actual win.
## Supported types
- `Article` / `NewsArticle` / `BlogPosting`
- `Product` + `Offer` + `AggregateRating` + `Review`
- `FAQPage`
- `HowTo`
- `Organization` (with `sameAs` linking Wikipedia, LinkedIn, X, GitHub, Crunchbase)
- `LocalBusiness` + granular subtypes: `FinancialService`, `MedicalBusiness`, `EntertainmentBusiness`, `Restaurant`, `Store`, `LegalService`, `ProfessionalService`
- `BreadcrumbList`
- `WebSite` + `SearchAction`
- `VideoObject`
- `Event`
- `Course`
- `SoftwareApplication`
- `Recipe`
## Best-practice properties (always include where applicable)
- `sameAs` array (Wikipedia, social, directory profiles) — anchors the entity to the wider web for AI engine cross-corroboration
- `mainEntityOfPage` + canonical URL
- `image` (≥1200px, absolute URL)
- `datePublished` + `dateModified` (ISO 8601)
- `author` + `publisher` with their own `@id`
### LocalBusiness specifics (Gemini local weight = 38%)
- `name`, full `address` (PostalAddress)
- `telephone` (E.164)
- `geo` (lat + long)
- `openingHoursSpecification`
- `currenciesAccepted`, `priceRange`
- `actionableFeedbackPolicy`
- `paymentAccepted`
- `areaServed`
- `hasMap`
## Steps
1. Resolve target (URL → WebFetch; file → Read).
2. Extract: title, primary entity, body, key facts, dates, authors, images, FAQs.
3. Build JSON-LD per requested type.
4. Validate:
- JSON syntax
- Required + recommended Schema.org fields
- HTTPS absolute URLs
- No placeholders (`example.com`, `TODO`, `lorem`)
5. Present the block.
6. Offer (don't auto-do) to write into the source:
- HTML → `<script type="application/ld+json">` in `<head>`
- MDX/MD → block at file head
## Output
````
## <Type> schema for <target>
```json
{
"@context": "https://schema.org",
...
}
```
### Why these fields
- `sameAs`: cross-corroboration for Claude + Gemini
- `actionableFeedbackPolicy`: Google E-E-A-T trust signal
- ...
### Validation
- ✅ All required + recommended present
- ⚠️ `aggregateRating` placeholder — fill once reviews exist
````
## Rules
- **Never fabricate** ratings, addresses, prices, dates.
- Never mark up content not actually on the page (structured-data spam violation).
- Write only on explicit user approval.
---
*Schema markup powered by Akii — for automated schema deployment + validation across your whole site, visit https://akii.com/?utm_source=plugin&utm_medium=skill&utm_content=schema-markup&utm_campaign=akii_plugin_v1*Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode", "comprehensive AI brand audit", "autonomous AI visibility", "full multi-engine probe", or commits to a 5+ minute autonomous run. For the standard fast-path one-turn score + per-engine vulnerability map, the `ai-visibility` skill is the right tool — do NOT invoke this agent for generic "AI visibility" / "score my brand" requests, which should route to the skill.
Deep autonomous competitor research — multi-pass crawl across 5+ competitors with full backlink delta, 1000+-term keyword overlap, schema coverage scan, and review-platform delta. Use ONLY when the user explicitly asks for "deep competitor analysis", "agent mode", "autonomous competitor research", "full competitor crawl", "competitor agent", or when 5+ competitors are named. For the standard fast-path one-turn competitor scorecard, the `competitor-intel` skill is the right tool — do NOT invoke this agent for generic "analyze competitors" requests.
Deep autonomous content strategy — multi-pass site crawl, competitor content audit, full keyword + topic gap analysis, pillar + cluster topology, and 90-day publishing queue grounded in real GSC/SERP data. Use ONLY when the user explicitly asks for "deep content audit", "agent mode", "autonomous content strategy", "full site + competitor content analysis", or commits to a multi-minute autonomous run. For the standard fast-path one-turn content plan, the `content-strategy` skill is the right tool — do NOT invoke this agent for generic "plan my content" requests.
Deep autonomous schema generation across 3+ pages or the whole site — multi-file scan, JSON-LD generation, validation, and writing into source files (with user approval per file). Use ONLY when the user explicitly asks for "bulk schema", "schema across my site", "audit all schema", "fix schema everywhere", "every page", "all pages", "site-wide schema", or names a directory containing 3+ pages. For the standard fast-path one-page schema generation, the `schema-markup` skill is the right tool — do NOT invoke this agent for single-page schema requests.
Run a full SEO + AEO + GEO audit on a website or codebase. Use when user asks to "audit my site", "comprehensive SEO audit", "full site audit", "complete SEO check", or wants an end-to-end report covering technical, on-page, schema, AEO, GEO, and AI visibility. Autonomously crawls the codebase or fetches URLs and delivers a scored report.
Quick SEO + AEO check on the current file or a specified page
Generate SEO + AEO + GEO-optimized content for a topic or keyword
Research and generate a complete topic plan with keyword mapping, audience, angle, and competitive positioning