seo-schema-jsonld
installsforks
How to install seo-schema-jsonld?
hainrixz/claude-seo-ai/seo-schema-jsonld
$npx -y skills add Hainrixz/claude-seo-ai --skill seo-schema-jsonldAudit and generate structured data (JSON-LD) for a page — detect, validate, and complete Tier-1 schema.org types (Article, Organization, Person, Product/Offer, BreadcrumbList, LocalBusiness, Review, VideoObject, Event), flag microdata/RDFa and deprecated-for-rich-results types (F
SKILL.md
| 1 | # seo-schema-jsonld (M5) |
| 2 | |
| 3 | Structured data is the single highest-leverage signal for both classic rich results and AI citation. Reference: `references/schema-tier1.md`. Templates: `schema/jsonld-templates/`. |
| 4 | |
| 5 | ## Audits |
| 6 | Working from the PageSnapshot (`rendered_dom` if present, else `raw_html`): |
| 7 | 1. **Detect** every `<script type="application/ld+json">` block; parse JSON; note any inline microdata/RDFa (flag for migration to JSON-LD). |
| 8 | 2. **Validate** each block: valid JSON, recognized `@type`, required + recommended properties present per `references/schema-tier1.md`. |
| 9 | 3. **Completeness** vs the page's content & vertical: e.g. an article page should have `Article`/`BlogPosting` with `author` (Person), `datePublished`, `dateModified`, `image`, `publisher`; a product page `Product` + `Offer` (`price`, `priceCurrency`, `availability`). |
| 10 | 4. **Entity hygiene**: stable `@id`, `@graph` linkage, `sameAs` (defer the sameAs audit detail to M6/seo-entity-linking). |
| 11 | 5. **Date agreement**: schema `datePublished`/`dateModified` should match visible dates (cross-check with M13). |
| 12 | 6. **Deprecation honesty**: if `FAQPage`/`HowTo` present, do NOT report them as a rich-result win — label deprecated-for-SERP (still parseable by AI). |
| 13 | |
| 14 | ## Fixes (fixable: auto) |
| 15 | Generate complete, valid JSON-LD blocks **inferred from page content** for any missing/incomplete Tier-1 type: |
| 16 | - `Article`/`BlogPosting` from `<article>`, `<h1>`, byline, dates, hero image. |
| 17 | - `Organization`/`WebSite` from footer/contact/logo. |
| 18 | - `Product`+`Offer` from product DOM (name, image, price, currency, availability). |
| 19 | - `BreadcrumbList` from nav breadcrumb. |
| 20 | - `Person` (author) with credential fields **the user supplies**. |
| 21 | Use a single `@graph` with stable `@id`s. Inject missing `dateModified`/`@id`. The block is a diff for `fix` (AUTO). **Never invent** prices, dates, ratings, or `sameAs` identity links — ask or leave a clearly-marked TODO placeholder the user fills. |
| 22 | |
| 23 | ## Verification |
| 24 | - Offline: `node ${CLAUDE_SKILL_DIR}/../../scripts/validate-jsonld.mjs --url <u>` — checks JSON validity + required properties against the templates. |
| 25 | - Tier 1: confirm eligibility with Google Rich Results Test / schema.org validator. When unavailable, status is `needs_api`, not `pass`. |
| 26 | |
| 27 | ## Findings |
| 28 | Emit findings per `schema/finding.schema.json`. Examples: |
| 29 | - `M5.article.missing` — no Article schema on an editorial page (severity 4, fail, `fixable: auto`, axis `both`, confidence `established`). |
| 30 | - `M5.product.missing_offer_price` — Product without `Offer.price` on a product page (status `fail`, severity 4, `fixable: auto`, axis `both`, confidence `established`). |
| 31 | - `M5.faqpage.deprecated_richresult` — FAQPage present (status `warn`, severity 1, `fixable: advisory`, axis `ai`, confidence `established`; rationale cites Google FAQ rich-result removal; **not** counted as a win). |
| 32 | Each finding: `evidence.observed` quotes what's on the page; `verification.reproduce` is the runnable command above; `expected_impact` is banded + confidence-tagged (no naked %). |
| 33 | |
| 34 | ## Honesty |
| 35 | - FAQPage/HowTo: parseable by AI, **no Google rich results** — keep if present, don't add expecting SERP features. |
| 36 | - Don't mark up content not visible on the page; keep schema consistent with any product feed. |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
