Nadhebe
Technical SEO v1.0.0 Verified & Tested on Oct 10, 2026

Schema.org Rich Structured Data Engine

Generate and validate Schema.org JSON-LD structured data (Article, TechArticle, FAQPage, BreadcrumbList, WebApplication) for Google rich results.

Tested Runtime Google Rich Results Test API, Node.js 20+
License MIT (Open Source)
Maintainer Nadhebe Engineering
Compatibility Claude Code, Cursor, Antigravity

Overview

Generate and validate Schema.org JSON-LD structured data (Article, TechArticle, FAQPage, BreadcrumbList, WebApplication) for Google rich results.

Verification & Test Notes

[!NOTE] Tested & Reviewed on 2026-10-10 for runtime environment Google Rich Results Test API, Node.js 20+.

Validates against Schema.org 2026 specs. Tested on Google Rich Results Validator with 0 warnings and 0 errors.


Installation & Setup

Option 1: Direct Skill Download

  1. Download Schema.org Rich Structured Data Engine (schema-generator.zip).
  2. Unpack the zip file into your workspace agent directory:
    • Antigravity IDE: .agents/skills/schema-generator/
    • Claude Code: ~/.claude/skills/schema-generator/ or .agents/skills/schema-generator/
    • Cursor: .cursor/rules/schema-generator/ or your project prompt definitions.

Option 2: CLI Activation

If using Antigravity or compatible agent runners:

# Load into active workspace
mkdir -p .agents/skills/schema-generator
curl -sL https://nadhebe.com/skills/schema-generator.zip -o /tmp/schema-generator.zip
unzip /tmp/schema-generator.zip -d .agents/skills/schema-generator/

Skill Instructions & Reference

Schema Generator & Structured Data Validator

Activate this skill when generating, auditing, or validating JSON-LD structured data markup for Nadhebe pages.


1. When to Activate This Skill

  • When defining structured data schemas for blog posts, tutorials, and comparison pages.
  • When formatting FAQ sections in Markdown frontmatter to trigger Google FAQ rich results.
  • When creating structured schemas for interactive tools in src/pages/tools/.
  • When validating rich snippet eligibility against Google Search Central standards.

2. Nadhebe Structured Data Architecture

In Nadhebe, structured data is rendered through automated Astro layout components:

1. Articles & Guides (ArticleSchema.astro)

Automatically rendered in <head> using frontmatter:

{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "[title]",
  "description": "[description]",
  "image": "https://nadhebe.com[heroImage]",
  "datePublished": "[pubDate ISO]",
  "dateModified": "[updatedDate ISO]",
  "author": {
    "@type": "Organization",
    "name": "Nadhebe Editorial Team",
    "url": "https://nadhebe.com/about"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Nadhebe",
    "url": "https://nadhebe.com",
    "logo": {
      "@type": "ImageObject",
      "url": "https://nadhebe.com/logo.webp"
    }
  }
}

2. FAQ Rich Results (FAQSchema.astro)

Rendered automatically whenever the frontmatter contains an faq array:

faq:
  - question: "Is Claude Code included in Claude Pro?"
    answer: "Yes, Claude Pro includes Claude Code within standard daily token allowances."
  - question: "Does Claude Code support Prompt Caching?"
    answer: "Yes, Anthropic prompt caching is automatically applied, cutting input token fees by 90%."

3. Web Applications (src/pages/tools/)

For interactive tools, inject standard WebApplication JSON-LD into the page <head>:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebApplication",
  "name": "AI API Pricing Calculator",
  "url": "https://nadhebe.com/tools/ai-api-pricing-calculator",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "All",
  "browserRequirements": "Requires JavaScript. Requires HTML5."
}
</script>

3. Google Eligibility & Rules of Thumb

  • No Promotional / Misleading FAQs: Answers must be factual, direct, and objectively verifiable.
  • Visible Content Parity: Every piece of data in the JSON-LD schema must be clearly visible on the rendered web page. Hidden text violates Google spam policies.
  • Dates: Always preserve ISO 8601 strings (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ssZ).

Explore Related Agent Skills

View All Skills →