schema-markup

Estrelas14

Forks2

Atualizado10 de abril de 2026 às 13:12

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

syedsaif666

syedsaif666/LGTM

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores webInformática e Matemática·SOC 15-1254

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	schema-markup
description	When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
metadata	{"version":"1.1.0"}

Schema Markup

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-context.md exists (or .claude/product-marketing-context.md 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:

Page Type - What kind of page? What's the primary content? What rich results are possible?
Current State - Any existing schema? Errors in implementation? Which rich results already appearing?
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

Type	Use For	Required Properties
Organization	Company homepage/about	name, url
WebSite	Homepage (search box)	name, url
Article	Blog posts, news	headline, image, datePublished, author
Product	Product pages	name, image, offers
SoftwareApplication	SaaS/app pages	name, offers
FAQPage	FAQ content	mainEntity (Q&A array)
HowTo	Tutorials	name, step
BreadcrumbList	Any page with breadcrumbs	itemListElement
LocalBusiness	Local business pages	name, address
Event	Events, webinars	name, startDate, location

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

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)

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

Google Rich Results Test: https://search.google.com/test/rich-results
Schema.org Validator: https://validator.schema.org/
Search Console: Enhancements reports

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

Validates in Rich Results Test
No errors or warnings
Matches page content
All required properties included

Task-Specific Questions

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

Related Skills

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

Mais deste repositório

mesmo repositório

ai-seo

syedsaif666/LGTM

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.

2026-04-1014

compare

syedsaif666/LGTM

Open two files side by side in VSCodium diff view. Use when comparing original vs modified, before vs after, or any two files.

2026-04-1014

content-strategy

syedsaif666/LGTM

When 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," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

2026-04-1014

copywriting

syedsaif666/LGTM

When 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 says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.

2026-04-1014

humanizer

syedsaif666/LGTM

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

2026-04-1014

onboard

syedsaif666/LGTM

First-run onboarding for a new project. Scans for unfilled {CONFIGURE:} placeholders, asks project-specific questions, fills them in, and logs decisions.

2026-04-1014

name	schema-markup
description	When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.
metadata	{"version":"1.1.0"}

Schema Markup

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

Before implementing schema, understand:

Page Type - What kind of page? What's the primary content? What rich results are possible?
Current State - Any existing schema? Errors in implementation? Which rich results already appearing?
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

Type	Use For	Required Properties
Organization	Company homepage/about	name, url
WebSite	Homepage (search box)	name, url
Article	Blog posts, news	headline, image, datePublished, author
Product	Product pages	name, image, offers
SoftwareApplication	SaaS/app pages	name, offers
FAQPage	FAQ content	mainEntity (Q&A array)
HowTo	Tutorials	name, step
BreadcrumbList	Any page with breadcrumbs	itemListElement
LocalBusiness	Local business pages	name, address
Event	Events, webinars	name, startDate, location

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

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)

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

Google Rich Results Test: https://search.google.com/test/rich-results
Schema.org Validator: https://validator.schema.org/
Search Console: Enhancements reports

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

Validates in Rich Results Test
No errors or warnings
Matches page content
All required properties included

Task-Specific Questions

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

Related Skills

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