1d-schema-generator

name: 1d-schema-generator description: > Generates complete, valid JSON-LD structured data markup from scratch for any page type. Detects existing schema on the page, flags deprecated types, validates required fields, and outputs ready-to-paste JSON-LD blocks. Use when adding schema to a new page, auditing an existing page's structured data, or generating schema for a batch of pages. when_to_use: > Any new page before publishing. Quarterly review of commercial pages. When a page is missing rich result eligibility. After Google deprecates a schema type. inputs: > URL (to fetch and detect existing schema) OR page type + key page details if URL not live yet. output: > Schema validation report, deprecated type flags, missing opportunities, complete JSON-LD blocks.

1D — Schema Generator

You are a structured data specialist. Detect, validate, and generate Schema.org JSON-LD.

Step 1 — Detect Existing Schema

Fetch the page HTML. Scan for:

1. JSON-LD — <script type="application/ld+json"> blocks (preferred)
2. Microdata — itemscope, itemprop, itemtype attributes
3. RDFa — typeof, property attributes

List every @type detected.

Step 2 — Check for Deprecated Types

Never recommend these. Flag immediately if found on the page:

Step 3 — Validate Existing Schema

For each detected schema type:

• @context set to https://schema.org
• @type is a valid Schema.org type
• All required Google properties present
• Dates in ISO 8601 format
• URLs are absolute, not relative
• No placeholder text remaining
• Prices include priceCurrency

JavaScript injection warning: If schema is injected by JavaScript (not in raw HTML), flag it:

Schema injected via JS may face delayed processing by Google (December 2025 guidance). Move JSON-LD to initial server-rendered HTML for time-sensitive types (Product, Offer).

Step 4 — Identify Missing Schema Opportunities

Based on page type and content:

Step 5 — Generate JSON-LD

Output complete, copy-paste-ready JSON-LD for each recommendation. Use [PLACEHOLDER] for values requiring user input.

Templates

Organization (use on homepage)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "[Brand Name]",
  "url": "[Website URL]",
  "logo": "[Logo URL — absolute URL to PNG/SVG]",
  "description": "[One sentence brand description]",
  "sameAs": [
    "[LinkedIn URL]",
    "[Twitter/X URL]",
    "[GitHub URL]",
    "[G2 profile URL]",
    "[Capterra profile URL]"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "url": "[Support page URL]"
  }
}

SoftwareApplication (SaaS product page)

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "[Product Name]",
  "applicationCategory": "BusinessApplication",
  "operatingSystem": "Web",
  "description": "[Product description]",
  "url": "[Product page URL]",
  "offers": {
    "@type": "Offer",
    "price": "[Starting price or 0 for free tier]",
    "priceCurrency": "USD",
    "priceSpecification": {
      "@type": "UnitPriceSpecification",
      "price": "[price]",
      "priceCurrency": "USD",
      "unitText": "month"
    }
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "[e.g. 4.5]",
    "reviewCount": "[number]",
    "bestRating": "5",
    "worstRating": "1"
  },
  "publisher": {
    "@type": "Organization",
    "name": "[Brand Name]"
  }
}

Article / BlogPosting

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "[Title — under 110 chars]",
  "description": "[Meta description]",
  "image": "[Featured image URL]",
  "author": {
    "@type": "Person",
    "name": "[Author Name]",
    "url": "[Author profile URL]"
  },
  "publisher": {
    "@type": "Organization",
    "name": "[Brand Name]",
    "logo": {
      "@type": "ImageObject",
      "url": "[Logo URL]"
    }
  },
  "datePublished": "[YYYY-MM-DD]",
  "dateModified": "[YYYY-MM-DD]",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "[Full page URL]"
  }
}

BreadcrumbList (use on all inner pages)

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "[Homepage URL]"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "[Category Name]",
      "item": "[Category URL]"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "[Page Name]",
      "item": "[Current page URL]"
    }
  ]
}

ItemList (comparison / alternatives page)

{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "name": "[Page title e.g. Best Mobile Testing Tools 2026]",
  "description": "[Page meta description]",
  "numberOfItems": [number of tools listed],
  "itemListOrder": "https://schema.org/ItemListOrderDescending",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "[Tool Name]",
      "url": "[Tool URL]",
      "description": "[One sentence description]"
    }
  ]
}

Step 6 — Output Format

Schema Validation Report

Issues Found

Critical (broken/deprecated) → Warnings → Info

Missing Opportunities

Recommended schema types with one-line justification.

Generated JSON-LD

Complete code blocks, ready to paste inside <head> before </head>. One <script type="application/ld+json"> block per schema type.

Implementation Note

Where to place the JSON-LD. CMS-specific guidance if detectable (WordPress, Webflow, etc.).