Seo Schema
Apply Schema.org markup that still earns Google rich results and avoid deprecated types the search cleanup retired in 2024–2026.
Overview
Seo-schema is an agent skill most often used in Launch (also Validate landing, Grow content) that steers Schema.org choices away from Google-retired rich results toward live alternatives or honest no-replacement notes.
Install
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-schemaWhat is this skill?
- Authoritative list of Schema.org types Google retired in the 2024–2025 rich-results simplification
- June 2025 retirements including Vehicle Listing, Claim Review, Estimated Salary, Learning Video, and Course Info carouse
- Redirects builders to active alternatives (e.g., Product, JobPosting, VideoObject) when replacements exist
- Flags types with no SERP replacement so you do not waste implementation time
- Enforces explaining deprecation whenever a user requests a retired rich-result type
- June 19, 2025 rich-result retirements including Vehicle Listing, Claim Review, Estimated Salary, Learning Video, and Cou
- 2024–2026 Google rich-results simplification window documented in skill reference
Adoption & trust: 2.1k installs on skills.sh; 8.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You asked the agent for Schema.org markup but Google stopped rendering that rich result years ago, so your JSON-LD work will not show up in SERPs.
Who is it for?
Solo builders shipping marketing sites, SaaS docs, or storefronts who want agents to stop suggesting obsolete Google rich-result schema.
Skip if: Teams that only need generic structured-data tutorials unrelated to Google’s retired rich-result list, or apps with zero public HTML to mark up.
When should I use this skill?
Whenever a user asks for Schema.org or rich-result markup that may match Google’s retired 2024–2026 types.
What do I get? / Deliverables
The agent explains deprecation, names retired types from the 2024–2026 cleanup, and recommends active schema types or states when no replacement exists.
- Deprecation explanation tied to Google’s rich-result policy
- Recommended active schema types or explicit no-replacement guidance
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
SEO schema guidance belongs on Launch because structured data directly affects how pages appear in search after you ship. SEO subphase is canonical: the skill is a living reference for valid vs retired rich-result types, not a generic HTML builder.
Where it fits
Before publishing a waitlist landing page, confirm you are not relying on Estimated Salary or other retired types for social proof cards.
Ship Product and VideoObject schema on a marketing site while explicitly dropping ClaimReview markup that no longer affects SERPs.
Refresh older blog templates that still mention Learning Video rich results and swap guidance to generic VideoObject eligibility.
How it compares
Use as a deprecation checker and routing guide—not as a drop-in sitemap or technical SEO audit skill.
Common Questions / FAQ
Who is seo-schema for?
Indie builders and small teams using AI coding agents to add or review JSON-LD who need Google-accurate schema advice after the rich-results simplification.
When should I use seo-schema?
Use it at Launch for page-level SEO markup, at Validate when scoping landing-page structured data, and at Grow when updating content templates that still reference retired carousels or specialty types.
Is seo-schema safe to install?
It is documentation and decision logic only; review the Security Audits panel on this page and treat any generated markup as your responsibility to validate in Search Console.
SKILL.md
READMESKILL.md - Seo Schema
MIT License - see repository root LICENSE file for complete terms. Copyright (c) 2026 AgriciDaniel https://github.com/AgriciDaniel/claude-seo # Deprecated Schema.org rich result types (2024–2026) Authoritative reference for every rich result Google retired during the 2024–2025 cleanup. Whenever a user asks for one of these, the `seo-schema` skill must explain that the type is deprecated and either redirect to an active alternative or note that no replacement exists. ## Retired June 19, 2025 Announced at [Simplifying our Search rich results](https://developers.google.com/search/blog/2025/06/simplifying-search-results) (developers.google.com/search/blog). | Type | Retired | Notes | |---|---|---| | **Vehicle Listing** (`@type: VehicleListing` / `Vehicle`) | June 2025 | No replacement. Google no longer renders dealer inventory rich cards. Use regular `Product` schema if the listing is sold online. | | **Claim Review** (`@type: ClaimReview`) | June 2025 | No replacement. The fact-check rich result was the main consumer of ClaimReview; without it, the markup has no SERP effect. ClaimReview *the vocabulary* is still in schema.org, but Google ignores it. | | **Estimated Salary** (`@type: EstimatedSalary` / `OccupationalAggregateRating`) | June 2025 | No replacement. `JobPosting` remains live for individual jobs. | | **Learning Video** | June 2025 | No replacement. The generic `VideoObject` rich result still renders. | | **Course Info carousel** | June 2025 | The carousel variant retired. The single-result `Course` rich card is still live. When asked for "Course Info", verify whether the user wants the carousel (dead) or the live single-result variant. | ## Retired July 31, 2025 | Type | Retired | Notes | |---|---|---| | **Special Announcement** (`@type: SpecialAnnouncement`) | July 2025 | The COVID-era emergency-info card was deprecated. No replacement. | ## Earlier (pre-v2 baseline) retirements These are listed for completeness so the LLM doesn't suggest them. | Type | Retired | Notes | |---|---|---| | **HowTo** (`@type: HowTo`) | September 2023 | Rich result removed from desktop and mobile. The vocabulary remains but produces no SERP feature. Some sites still use HowTo for AI citation legibility — that's a defensible reason to keep it, but flag it as "no SERP effect". | | **FAQ** (`@type: FAQPage`) | August 2023 | Restricted to government and healthcare sites. For commercial sites: flag existing FAQPage as Info (not Critical) because it still helps AI/LLM citations; do **not** recommend adding new FAQPage for SERP benefit. | ## Replacement decision table When generating schema, prefer these alternatives: | Asked for | Replacement | |---|---| | `ClaimReview` | None — explain rich result is dead; suggest `Article` with `dateline` if news context. | | `EstimatedSalary` | `JobPosting` with `baseSalary` for specific roles. | | `LearningVideo` | `VideoObject` (still live). | | `Course Info` carousel | Single `Course` rich card (still live). | | `SpecialAnnouncement` | `Event` if time-bounded; otherwise `Article` or `WebPage`. | | `VehicleListing` | `Product` with vehicle-specific properties. | | `HowTo` (for SERP) | None — explain the rich result is dead. Suggest article structure with clear `<h2>` step headings if the goal is comprehension; ranking benefit is no longer schema-driven. | ## Primary sources - Google retirement announcement (June 2025): https://developers.google.com/search/blog/2025/06/simplifying-search-results - Special Announcement deprecation (July 2025): https://developers.google.com/search/blog - HowTo retirement (September 2023): https://developers.google.com/search/blog/2023/09/structured-data-changes - FAQ restriction (August 2023): https://developers.google.com/search/blog/2023/08/howto-faq-changes Last verified against developers.google.com: 2026-05-17. --- name: seo-schema description: > Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says