domains / families / marketing / schema-markup-generator

schema-markup-generator

combined

Generate JSON-LD structured data markup for rich results in Google Search. Supports FAQ, HowTo, Article, Product, LocalBusiness, and multi-type schemas. Validates against Google requirements and provides implementation guidance. Use when asked to "add schema markup", "generate structured data", "JSON-LD", "rich snippets", "FAQ schema", "product markup", "add structured data to my page", "how to get rich snippets", or any structured data task. Generate and implement JSON-LD structured data for web apps, blogs, FAQs, and SaaS sites. Supports WebSite, SoftwareApplication, BlogPosting, FAQPage, HowTo, and more.

When to use

• Use when adding or auditing JSON-LD schema for websites, SaaS apps, tools, articles, FAQs, breadcrumbs, or organization pages.
• Use when schema must be implemented in Next.js App Router or validated against Google Rich Results and Schema.org tooling.
• Use when a page has strong content but lacks structured data for search engines and rich-result eligibility.

When not to use

• Does not guarantee rich-result eligibility or display; Google and other consumers decide whether to use valid schema.
• Generated examples must be adapted to the site's real content, legal entity details, ratings, pricing, and availability.
• Always validate deployed HTML, not only source code, because frameworks and rendering modes can change the final markup.

Skill page

Conflict

The two copies overlap in purpose (generating JSON-LD structured data for rich results) but each contains material steps the other lacks. The notfair-plugin copy is a thin pointer to an external WORKFLOW.md and does not contain the implementation steps itself. The agentic-awesome-skills copy provides concrete implementation guidance, including a reusable Next.js JsonLd component, escaping of '<' characters, and detailed schema examples for WebSite, SoftwareApplication, BlogPosting, FAQPage, HowTo, and BreadcrumbList. Crowning one copy would hide the other's real alternative: a workflow-driven approach versus a component-driven implementation approach.