b6a478e1df
## Summary - Add portable installation tool (`install.sh`) for cross-machine setup - Add Claude.ai export files with proper YAML frontmatter - Add multi-agent-guide v2.0 with consolidated framework template - Rename `00-claude-code-setting` → `00-our-settings-audit` (avoid reserved word) - Add YAML frontmatter to 25+ SKILL.md files for Claude Desktop compatibility ## Commits Included - `93f604a` feat: Add portable installation tool for cross-machine setup - `9b84104` feat: Add Claude.ai export for portable skill installation - `f7ab973` fix: Add YAML frontmatter to Claude.ai export files - `3fed49a` feat(multi-agent-guide): Add v2.0 with consolidated framework - `3be26ef` refactor: Rename settings-audit skill and add YAML frontmatter Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
156 lines
3.2 KiB
Markdown
156 lines
3.2 KiB
Markdown
---
|
|
name: seo-schema-generator
|
|
description: |
|
|
JSON-LD structured data generator from templates for various content types.
|
|
Triggers: generate schema, create JSON-LD, schema markup, structured data generator.
|
|
---
|
|
|
|
# SEO Schema Generator
|
|
|
|
## Purpose
|
|
|
|
Generate JSON-LD structured data markup for various content types using templates.
|
|
|
|
## Core Capabilities
|
|
|
|
1. **Organization** - Company/brand information
|
|
2. **LocalBusiness** - Physical location businesses
|
|
3. **Article** - Blog posts and news articles
|
|
4. **Product** - E-commerce products
|
|
5. **FAQPage** - FAQ sections
|
|
6. **BreadcrumbList** - Navigation breadcrumbs
|
|
7. **WebSite** - Site-level with search action
|
|
|
|
## Workflow
|
|
|
|
1. Identify content type
|
|
2. Gather required information
|
|
3. Generate JSON-LD from template
|
|
4. Validate output
|
|
5. Provide implementation instructions
|
|
|
|
## Schema Templates
|
|
|
|
### Organization
|
|
```json
|
|
{
|
|
"@context": "https://schema.org",
|
|
"@type": "Organization",
|
|
"name": "[Company Name]",
|
|
"url": "[Website URL]",
|
|
"logo": "[Logo URL]",
|
|
"sameAs": [
|
|
"[Social Media URLs]"
|
|
]
|
|
}
|
|
```
|
|
|
|
### LocalBusiness
|
|
```json
|
|
{
|
|
"@context": "https://schema.org",
|
|
"@type": "LocalBusiness",
|
|
"name": "[Business Name]",
|
|
"address": {
|
|
"@type": "PostalAddress",
|
|
"streetAddress": "[Street]",
|
|
"addressLocality": "[City]",
|
|
"addressRegion": "[State]",
|
|
"postalCode": "[ZIP]",
|
|
"addressCountry": "[Country]"
|
|
},
|
|
"telephone": "[Phone]",
|
|
"openingHours": ["Mo-Fr 09:00-17:00"]
|
|
}
|
|
```
|
|
|
|
### Article
|
|
```json
|
|
{
|
|
"@context": "https://schema.org",
|
|
"@type": "Article",
|
|
"headline": "[Title]",
|
|
"author": {
|
|
"@type": "Person",
|
|
"name": "[Author Name]"
|
|
},
|
|
"datePublished": "[YYYY-MM-DD]",
|
|
"dateModified": "[YYYY-MM-DD]",
|
|
"image": "[Image URL]",
|
|
"publisher": {
|
|
"@type": "Organization",
|
|
"name": "[Publisher]",
|
|
"logo": "[Logo URL]"
|
|
}
|
|
}
|
|
```
|
|
|
|
### FAQPage
|
|
```json
|
|
{
|
|
"@context": "https://schema.org",
|
|
"@type": "FAQPage",
|
|
"mainEntity": [
|
|
{
|
|
"@type": "Question",
|
|
"name": "[Question]",
|
|
"acceptedAnswer": {
|
|
"@type": "Answer",
|
|
"text": "[Answer]"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
### Product
|
|
```json
|
|
{
|
|
"@context": "https://schema.org",
|
|
"@type": "Product",
|
|
"name": "[Product Name]",
|
|
"image": "[Image URL]",
|
|
"description": "[Description]",
|
|
"offers": {
|
|
"@type": "Offer",
|
|
"price": "[Price]",
|
|
"priceCurrency": "[Currency]",
|
|
"availability": "https://schema.org/InStock"
|
|
}
|
|
}
|
|
```
|
|
|
|
## Implementation
|
|
|
|
Place generated JSON-LD in `<head>` section:
|
|
|
|
```html
|
|
<head>
|
|
<script type="application/ld+json">
|
|
[Generated Schema Here]
|
|
</script>
|
|
</head>
|
|
```
|
|
|
|
## Validation
|
|
|
|
After generating:
|
|
1. Use schema validator skill (13) to verify
|
|
2. Test with Google Rich Results Test
|
|
3. Monitor in Search Console
|
|
|
|
## Limitations
|
|
|
|
- Templates cover common types only
|
|
- Complex nested schemas may need manual adjustment
|
|
- Some Rich Results require additional properties
|
|
|
|
## Notion Output (Required)
|
|
|
|
All audit reports MUST be saved to OurDigital SEO Audit Log:
|
|
- **Database ID**: `2c8581e5-8a1e-8035-880b-e38cefc2f3ef`
|
|
- **Properties**: Issue (title), Site (url), Category, Priority, Found Date, Audit ID
|
|
- **Language**: Korean with English technical terms
|
|
- **Audit ID Format**: [TYPE]-YYYYMMDD-NNN
|
|
|