domains / families / marketing / schema
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. When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema Markup Validator," "Google Rich Results Test," "FAQ schema," "Article schema," "Organization schema," "JobPosting," "HowTo," "Event," "SoftwareApplication," "BreadcrumbList," "WebSite," "Recipe," "Product," or "Dataset." For SERP feature types and zero-click patterns, use serp-features. For AI search visibility strategy (not markup), use generative-engine-optimization. For HowTo step sections (placement, copy, vs FAQ), use howto-section-generator.
Both copies describe the same task (implementing schema.org/JSON-LD for search), but they contain material, non-overlapping steps and constraints. The coreyhaines31 copy is a focused implementation guide with a specific product-marketing context check, a strict 'check Google feature support first' gate, and explicit retirement dates for FAQPage, HowTo, and WebSite SearchAction. The kostja94 copy adds a multi-engine support matrix (Google vs. Bing vs. AI), a detailed mapping of schema types to SERP features, and a Generative Engine Optimization (GEO) section. Because the first copy lacks the multi-engine/GEO strategy and the second lacks the specific product-context check and the precise 'retired feature' implementation guardrails, crowning one would hide a real alternative approach to the same task.