What this Skill helps with

Schema Tag Generator creates or reviews JSON-LD structured data for a supplied page. It maps visible content to suitable Schema.org types, connects related entities, and flags properties that should not be added without supporting page content.

Who this Skill is for

Use it for developers, SEO practitioners, publishers, and ecommerce teams working on articles, products, organizations, local businesses, events, videos, recipes, people, breadcrumbs, or other supported page types.

What you provide

  • The page URL, HTML, or visible copy
  • The page type and business context
  • Existing JSON-LD when requesting an audit
  • Canonical URL, images, author, dates, and identifiers
  • Product, event, location, or review data when relevant

What it produces

  • A recommended schema type and property map
  • JSON-LD for the supplied page
  • An audit of existing markup when provided
  • Notes on missing, conflicting, or unsupported properties
  • Testing and implementation instructions

How the Skill works

The workflow identifies the page's main purpose before choosing a schema type. It checks required data, builds connected entities with stable identifiers where useful, and compares the markup with visible content. In audit mode, it separates syntax errors from content mismatches and optional additions.

Installation and first use

  1. Download and add the Skill to Claude.
  2. Provide one page and its current structured data, if any.
  3. Confirm the intended page type and canonical URL.
  4. Ask for an audit before requesting replacement markup.
  5. Test the final JSON-LD and compare it with the visible page.

Example workflow and expected output

Provide an article page with author, publication date, review date, hero image, breadcrumbs, and three visible FAQs. The expected output is connected Article, BreadcrumbList, and FAQPage markup, plus a list of values that need confirmation. The FAQ schema should reproduce the visible questions and answers.

Limits and review guidance

Valid JSON-LD does not guarantee a rich result. Search platforms support only selected schema features and may change their requirements. Never mark up reviews, prices, availability, FAQs, or author credentials that visitors cannot see or verify. Test syntax with current platform tools before release.

Frequently asked questions

Can this Skill repair existing schema?

Yes. Supply the current JSON-LD and page content so it can separate code errors from content mismatches.

Does valid schema guarantee a rich result?

No. Valid markup makes the page easier to interpret, but eligibility and display are controlled by the search platform.

Should schema include information that is not visible on the page?

Generally no. Important properties, especially FAQs, reviews, offers, and claims, should match content a visitor can verify.