seo-schema
/seo-schema
Wykrywa, waliduje i generuje dane strukturalne Schema.org, najchętniej w formacie JSON-LD.
- Autor
- georgekhananaev ↗
- Repozytorium
- claude-skills-vault ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 12.08.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wykrywa, waliduje i generuje dane strukturalne Schema.org, najchętniej w formacie JSON-LD.
Wyzwalacze z opisu
Argumenty
/seo-schema [url]
Oryginalny opis (EN)
Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says "schema", "structured data", "rich results", "JSON-LD", or "markup".
Jak działa
- Detection
- Validation
- Schema Type Status (as of Feb 2026)
- Generation
- Common Schema Templates
- Output
- Error Handling
Podgląd SKILL.md
---
name: seo-schema
description: >
Detect, validate, and generate Schema.org structured data. JSON-LD format
preferred. Use when user says "schema", "structured data", "rich results",
"JSON-LD", or "markup".
user-invokable: true
argument-hint: "[url]"
license: MIT
metadata:
author: AgriciDaniel
version: "2.0.0"
category: seo
---
# Schema Markup Analysis & Generation
## Detection
1. Scan page source for JSON-LD `<script type="application/ld+json">`
2. Check for Microdata (`itemscope`, `itemprop`)
3. Check for RDFa (`typeof`, `property`)
4. Always recommend JSON-LD as primary format (Google's stated preference)
## Validation
- Check required properties per schema type
- Validate against Google's supported rich result types
- Test for common errors:
- Missing @context
- Invalid @type
- Wrong data types
- Placeholder text
- Relative URLs (should be absolute)
- Invalid date formats
- Flag deprecated types (see below)
## Schema Type Status (as of Feb 2026)
Read `references/schema-types.md` for the full list. Key rules:
### ACTIVE (recommend freely):
Organization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting
### VIDEO & SPECIALIZED (recommend freely):
BroadcastEvent, Clip, SeekToAction, SoftwareSourceCode
See `schema/templates.json` for ready-to-use JSON-LD templates for these types.
> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.
### RESTRICTED (only for specific sites):
- **FAQ**: ONLY for government and healthcare authority sites (restricted Aug 2023)
### DEPRECATED (never recommend):
- **HowTo**: Rich results removed September 2023
- **SpecialAnnouncement**: Deprecated July 31, 2025
- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025
- **ClaimReview**: Retired from rich results June 2025
- **VehicleListing**: Retired from rich results June 2025
- **Practice Problem**: Retired from rich results late 2025
- **Dataset**: Retired from rich results late 2025
- **Book Actions**: Deprecated then reversed, still functional as of Feb 2026 (historical note)
## Generation
When generating schema for a page:
1. Identify page type from content analysis
2. Select appropriate schema type(s)
3. Generate valid JSON-LD with all required + recommended properties
4. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill
5. Validate output before presenting
## Common Schema Templates
### Organization
```json
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "[Company Name]",
"url": "[Website URL]",
"logo": "[Logo URL]",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "[Phone]",
"contactType": "customer service"
},
"sameAs": [
"[Facebook URL]",
"[LinkedIn URL]",
"[Twitter URL]"
]
}
```
### LocalBusiness
```json
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "[Business Name]",
"address": {
"@type": "PostalAddress",
"streetAddress": "[Street]",
"addressLocality": "[City]",
"addressRegion": "[State]",
"postalCode": "[ZIP]",
"addressCountry": "US"
},
"telephone": "[Phone]",
"openingHours": "Mo-Fr 09:00-17:00",
"geo": {
"@type": "GeoCoordinates",
"latitude": "[Lat]",
"longitude": "[Long]"
}
}
```
### Article/BlogPosting
```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": {
"@type": "ImageObject",
"url": "[Logo URL]"
}
}
}
```
## Output
- `SCHEMA-REPORT.md`: detection and validation results
- `generated-schema.json`: ready-to-use JSON-LD snippets
### Validation Results
| Schema | Type | Status | Issues |
|--------|------|--------|--------|
| ... | ... | ✅/⚠️/❌ | ... |
### Recommendations
- Missing schema opportunities
- Validation fixes needed
- Generated code for implementation
## Error Handling
| Scenario | Action |
|----------|--------|
| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |
| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |
| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |
| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · georgekhananaev/claude-skills-vault | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| sickn33/agentic-awesome-skills | 100 | MIT |
| naveedharri/benai-skills | 100 | MIT |
| LiHongwei-cn/lihongwei-cn | 100 | MIT |
| PIXARTSeu/Synapse | 100 | AGPL-3.0 |
| Gekkos-tech/agency-os | 100 | MIT |
| seranking/seo-skills | 100 | MIT |
| lionkiii/claude-seo-skills | 100 | MIT |
Identyczna treść występuje jeszcze w 3 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 28.10.2026 · wersja paczki 674f2337d444 (skrót SHA-256 całej paczki)
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95schema-markup
Generuje dane strukturalne Schema.org (JSON-LD) dla dowolnego typu strony: FAQ, produkt, artykuł, okruszki, organizacja, how-to i recenzje, na potrzeby SEO i rich snippets. - 100schema-markup
Wdraża, audytuje i waliduje dane strukturalne (schema.org, JSON-LD) na stronie, w tym błędy w Search Console i brak rich results. - 100algo-seo-schema
Wdraża dane strukturalne Schema.org w formacie JSON-LD, w tym FAQ, Product i Article, oraz waliduje je pod kątem rozszerzonych wyników wyszukiwania. - 100schema-markup
Wdraża, audytuje i waliduje dane strukturalne schema.org (JSON-LD) na stronie, w tym błędy z Search Console, brak rich results i widoczność w wyszukiwaniu AI. - 95memstack-seo-schema-markup
Dodaje i naprawia dane strukturalne JSON-LD według schema.org, żeby wyniki mogły pokazywać rich results. - 84schema-markup
Generuje dane strukturalne JSON-LD (schema.org) dla stron internetowych, by poprawić wygląd stron w wynikach wyszukiwania i uzyskać rich snippets.