schema-markup/

Специалист по Schema Markup

Точно применяет schema.org и JSON-LD, чтобы включить rich results в поиске. Проверяет тип страницы, цели и валидность, избегает ошибок и соответствует требованиям Google.

Автор: coreyhaines31Обновлён Бесплатно

Ставится на компьютере

С телефона скилл не поставить: Claude Code работает на Windows, macOS и Linux. Отправьте ссылку себе и откройте её на компьютере.

Что нужно: компьютер и Claude Code — он работает с подпиской Claude Pro и выше, на бесплатном плане его нет. Как поставить Claude Code →

Карточка

Имя папки
schema-markup
Автор
coreyhaines31
Обновлён
Инструкция
на английском, задачу ставите по-русски
Файлы
  • SKILL.md
  • evals/ · 1 файл
  • references/ · 1 файл

Похожие скиллы

Подобраны по смыслу описания, а не по алфавиту.

  • Контент
    Микроразметка Schema.org (JSON-LD)

    Генерирует валидную микроразметку Schema.org в JSON-LD по запросу.

    seo-schema · AgriciDaniel

  • Разработка
    Специалист по Kubernetes

    Для настройки кластера, усиления безопасности и управления рабочими нагрузками в Kubernetes

    kubernetes-specialist · Jeffallan

  • Разработка
    Специалист по защите кода

    Для разработчиков: защита кода от уязвимостей и взломов

    secure-code-guardian · Jeffallan

  • Разработка
    Laravel Специалист

    Для приложений на Laravel 10+ с Eloquent, API и очередями.

    laravel-specialist · Jeffallan

  • Разработка
    Kotlin Специалист

    Для приложений на Kotlin с корутинами, мультиплатформой и Android на Compose.

    kotlin-specialist · Jeffallan

  • Продукт
    Onboarding Специалист

    Для продуктовых команд: ускоряет onboarding и повышает retention через CRO

    onboarding-cro · coreyhaines31

Статьи по теме

Текст инструкции · SKILL.md

Оригинал инструкции (англ.)

Это оригинал автора на английском. Переводить его не нужно: Claude читает инструкцию сам, а задачу вы ставите ему по-русски.

You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before implementing schema, understand:

  1. Page Type - What kind of page? What's the primary content? What rich results are possible?

  2. Current State - Any existing schema? Errors in implementation? Which rich results already appearing?

  3. Goals - Which rich results are you targeting? What's the business value?


Core Principles

1. Accuracy First

  • Schema must accurately represent page content
  • Don't markup content that doesn't exist
  • Keep updated when content changes

2. Use JSON-LD

  • Google recommends JSON-LD format
  • Easier to implement and maintain
  • Place in <head> or end of <body>

3. Follow Google's Guidelines

  • Only use markup Google supports
  • Avoid spam tactics
  • Review eligibility requirements

4. Validate Everything

  • Test before deploying
  • Monitor Search Console
  • Fix errors promptly

Common Schema Types

TypeUse ForRequired Properties
OrganizationCompany homepage/aboutname, url
WebSiteHomepage/site identityname, url
ArticleBlog posts, newsheadline, image, datePublished, author
ProductProduct pagesname, image, offers
SoftwareApplicationSaaS/app pagesname, offers
FAQPageFAQ contentmainEntity (Q&A array)
HowToTutorialsname, step
BreadcrumbListAny page with breadcrumbsitemListElement
LocalBusinessLocal business pagesname, address
EventEvents, webinarsname, startDate, location

For complete JSON-LD examples: See references/schema-examples.md

Check Google Feature Support First

Schema.org vocabulary validity does not establish Google feature eligibility. Before implementing markup for a requested search appearance, check Google's current supported structured data gallery (откроется в новой вкладке).

These types can still describe matching visible content in Schema.org. Explain that distinction, ask which consumer needs the markup, and do not recommend implementation to obtain a retired Google appearance. Do not treat missing retired-feature reports or Rich Results Test detection as a broken implementation, or remove unrelated supported markup.


Quick Reference

Organization (Company Page)

Required: name, url Recommended: logo, sameAs (social profiles), contactPoint

Article/BlogPosting

Required: headline, image, datePublished, author Recommended: dateModified, publisher, description

Product

Required: name, image, offers (price + availability) Recommended: sku, brand, aggregateRating, review

FAQPage

Required: mainEntity (array of Question/Answer pairs) Optional semantic markup for visible FAQs; not a way to obtain Google FAQ rich results. Check the feature-support guidance above before offering code.

BreadcrumbList

Required: itemListElement (array with position, name, item)


Multiple Schema Types

You can combine multiple schema types on one page using @graph:

{
  "@context": "https://schema.org",
  "@graph": [
    { "@type": "Organization", ... },
    { "@type": "WebSite", ... },
    { "@type": "BreadcrumbList", ... }
  ]
}

Validation and Testing

Tools

Common Errors

Missing required properties - Check Google's documentation for required fields

Invalid values - Dates must be ISO 8601, URLs fully qualified, enumerations exact

Mismatch with page content - Schema doesn't match visible content


Implementation

Static Sites

  • Add JSON-LD directly in HTML template
  • Use includes/partials for reusable schema

Dynamic Sites (React, Next.js)

  • Component that renders schema
  • Server-side rendered for SEO
  • Serialize data to JSON-LD

CMS / WordPress

  • Plugins (Yoast, Rank Math, Schema Pro)
  • Theme modifications
  • Custom fields to structured data

Output Format

Schema Implementation

// Full JSON-LD code block
{
  "@context": "https://schema.org",
  "@type": "...",
  // Complete markup
}

Testing Checklist

  • Requested Google appearance is currently supported, or a separate semantic consumer is identified
  • Validates in Schema.org Validator; supported Google features also pass Rich Results Test
  • Required-field errors resolved; recommended-field warnings reviewed
  • Matches page content
  • All required properties included

Task-Specific Questions

  1. What type of page is this?
  2. What rich results are you hoping to achieve?
  3. What data is available to populate the schema?
  4. Is there existing schema on the page?
  5. What's your tech stack?

  • seo-audit: For overall SEO including schema review
  • ai-seo: For AI search optimization (schema helps AI understand content)
  • programmatic-seo: For templated schema at scale
  • site-architecture: For breadcrumb structure and navigation schema planning