Communitygithub.com

esquema

Cuando el usuario quiera agregar, corregir u optimizar el marcado de esquema y los datos estructurados en su sitio. Úselo también cuando el usuario mencione

¿Qué es esquema?

Esta habilidad te convierte en un experto en datos estructurados y marcado schema.org. Su objetivo es implementar marcado de esquema que ayude a los motores de búsqueda a comprender el contenido y permita resultados enriquecidos en la búsqueda. La habilidad guía al agente de IA a través de una evaluación inicial que verifica el contexto de marketing de productos, comprende el tipo de página, el estado actual del esquema y los objetivos de resultados enriquecidos. Proporciona principios fundamentales como precisión, uso de formato JSON-LD, cumplimiento de las pautas de Google y validación rigurosa. Incluye referencias rápidas para tipos de esquema comunes (Organization, Article, Product, FAQPage, etc.), cómo combinar múltiples tipos con @graph, herramientas de validación como Google Rich Results Test y Schema.org Validator, y estrategias de implementación para sitios estáticos, dinámicos (React/Next.js) y CMS/WordPress. El resultado esperado son bloques de código JSON-LD completos y listas de verificación de pruebas.

Compatible con✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/schema
Ver original→Ver todas las habilidades

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

Documentación

Marcado de Esquema

Eres un experto en datos estructurados y marcado de esquema. Tu objetivo es implementar el marcado schema.org que ayude a los motores de búsqueda a comprender el contenido y habilite resultados enriquecidos en la búsqueda.

Evaluación Inicial

Primero verifica el contexto de marketing de productos: Si existe .agents/product-marketing.md (o .claude/product-marketing.md, o el nombre de archivo heredado product-marketing-context.md en configuraciones antiguas), léelo antes de hacer preguntas. Usa ese contexto y solo solicita información que no esté ya cubierta o que sea específica para esta tarea.

Antes de implementar el esquema, comprende:

  1. Tipo de Página - ¿Qué tipo de página es? ¿Cuál es el contenido principal? ¿Qué resultados enriquecidos son posibles?

  2. Estado Actual - ¿Hay algún esquema existente? ¿Errores en la implementación? ¿Qué resultados enriquecidos ya aparecen?

  3. Objetivos - ¿A qué resultados enriquecidos te diriges? ¿Cuál es el valor comercial?

Principios Fundamentales

1. Precisión Primero

  • El esquema debe representar con precisión el contenido de la página
  • No marques contenido que no exista
  • Mantén actualizado cuando el contenido cambie

2. Usa JSON-LD

  • Google recomienda el formato JSON-LD
  • Más fácil de implementar y mantener
  • Colócalo en <head> o al final de <body>

3. Sigue las Pautas de Google

  • Solo usa el marcado que Google soporta
  • Evita tácticas de spam
  • Revisa los requisitos de elegibilidad

4. Valida Todo

  • Prueba antes de implementar
  • Monitorea Search Console
  • Corrige errores rápidamente

Tipos de Esquema Comunes

TipoUsar paraPropiedades Obligatorias
OrganizationPágina de inicio/acerca de la empresaname, url
WebSitePágina de inicio (cuadro de búsqueda)name, url
ArticlePublicaciones de blog, noticiasheadline, image, datePublished, author
ProductPáginas de productoname, image, offers
SoftwareApplicationPáginas de SaaS/aplicacionesname, offers
FAQPageContenido de preguntas frecuentesmainEntity (arreglo de Q&A)
HowToTutorialesname, step
BreadcrumbListCualquier página con migas de panitemListElement
LocalBusinessPáginas de negocio localname, address
EventEventos, webinarsname, startDate, location

Para ejemplos completos de JSON-LD: Consulta references/schema-examples.md

Referencia Rápida

Organization (Página de Empresa)

Obligatorio: name, url Recomendado: logo, sameAs (perfiles sociales), contactPoint

Article/BlogPosting

Obligatorio: headline, image, datePublished, author Recomendado: dateModified, publisher, description

Product

Obligatorio: name, image, offers (precio + disponibilidad) Recomendado: sku, brand, aggregateRating, review

FAQPage

Obligatorio: mainEntity (arreglo de pares Pregunta/Respuesta)

BreadcrumbList

Obligatorio: itemListElement (arreglo con position, name, item)

Múltiples Tipos de Esquema

Puedes combinar múltiples tipos de esquema en una sola página usando @graph:

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

Validación y Pruebas

Herramientas

Errores Comunes

Propiedades obligatorias faltantes - Consulta la documentación de Google para los campos requeridos

Valores inválidos - Las fechas deben ser ISO 8601, las URL completamente calificadas, las enumeraciones exactas

Desajuste con el contenido de la página - El esquema no coincide con el contenido visible

Implementación

Sitios Estáticos

  • Agrega JSON-LD directamente en la plantilla HTML
  • Usa includes/partials para esquema reutilizable

Sitios Dinámicos (React, Next.js)

  • Componente que renderiza el esquema
  • Renderizado del lado del servidor para SEO
  • Serializa datos a JSON-LD

CMS / WordPress

  • Plugins (Yoast, Rank Math, Schema Pro)
  • Modificaciones de tema
  • Campos personalizados a datos estructurados

Formato de Salida

Implementación del Esquema

// Bloque de código JSON-LD completo
{
  "@context": "https://schema.org",
  "@type": "...",
  // Marcado completo
}

Lista de Verificación de Pruebas

  • Valida en Rich Results Test
  • Sin errores ni advertencias
  • Coincide con el contenido de la página
  • Todas las propiedades obligatorias incluidas

Preguntas Específicas de la Tarea

  1. ¿Qué tipo de página es esta?
  2. ¿Qué resultados enriquecidos esperas lograr?
  3. ¿Qué datos están disponibles para poblar el esquema?
  4. ¿Hay esquema existente en la página?
  5. ¿Cuál es tu stack tecnológico?

Habilidades Relacionadas

  • seo-audit: Para SEO general, incluyendo revisión de esquema
  • ai-seo: Para optimización de búsqueda con IA (el esquema ayuda a la IA a comprender el contenido)
  • programmatic-seo: Para esquema plantillado a escala
  • site-architecture: Para estructura de migas de pan y planificación de esquema de navegación

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

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

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

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

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

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

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

Skills relacionados

steipete/video-frames

Extract frames or short clips from videos using ffmpeg.

community

steipete/summarize

Summarize or transcribe URLs, YouTube/videos, podcasts, articles, transcripts, PDFs, and local files.

community

openclaw/openclaw

Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.

community

obra/superpowers

Obra superpowers agent skills.

community

affaan-m/ECC

See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio...

community

affaan-m/everything-claude-code

End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.

community