/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",
$ npx -y skills add akii-technologies-ltd/akii-seo-ai-search-optimizer --skill schema-markup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/schema-markup
Context preview
The summary Claude sees to decide when to auto-load this skill.
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",
SKILL.md
schema-markup.SKILL.mddescription: 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.
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*
Read more
description: 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.
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*
Free AI-powered SEO, AEO, and GEO toolkit by Akii for Claude Code. Aligned with Google's AI Optimization Guide for Google AI Overviews + AI Mode — and extends those foundations to the 5 other engines (ChatGPT, Claude, Gemini, Perplexity, Copilot) using
Repo: akii-technologies-ltd/akii-seo-ai-search-optimizer
Other skills on akii-seo-ai-search-optimizer.
- /ai-visibility
Fast-path AI visibility — get a brand's 0–100 Akii Visibility Score (computed by an open-source LLM judge against the brand's public footprint) with four-dimension breakdown AND a per-engine proxy map for ChatGPT, Claude, Gemini, Perplexity, Copilot, and Google AI Overviews
Open skill - /broken-links
Find and fix broken links — three modes with different scale ceilings. `local` audits any local repo (HTML/MD/MDX, no size limit) via Glob/Grep + per-link verification. `page` checks one live URL deeply (~30-100 outbound links per run). `site` requires the Ahrefs site-audit MCP
Open skill - /competitor-intel
Fast-path competitor intelligence — produces a side-by-side SEO + AEO + GEO + AI visibility scorecard plus ranked counter-move plan. Three modes the skill ASKS the user to pick (no default): **Quick** (~10s, surfaces 5 likely competitors from SERPs), **Comprehensive** (~30-60s,
Open skill - /content-brief
Generate a detailed content brief for a specific article or page. Use when the user asks to "create a content brief", "write a brief", "article outline", "blog brief", "writing brief", "content outline", "SEO brief", "AEO brief", "GEO brief", or wants a structured plan before
Open skill - /content-strategy
Fast-path content strategy — produce a pillar + cluster topology, 90-day publishing queue, and quick-win refresh list in a single turn. This is the default for any content-planning question. Use when the user asks to "plan content", "content strategy", "content calendar", "what
Open skill - /content-translation
Translate and localize content for international SEO. Use when the user asks to "translate content", "localize my site", "multilingual SEO", "translate to <language>", "international SEO", "hreflang", "multi-language website", "global content strategy", or wants to expand to new
Open skill