Use valid JSON-LD structured data
SkillSearchjson-ld-valid is a skill for AI agents that checks and fixes JSON-LD structured data on web pages. It helps when you generate or audit script blocks of type application/ld+json, implement structured data for articles, products, FAQs, breadcrumbs, or local businesses, or investigate why rich results are not appearing in Google Search Console. The skill gives your agent a way to validate the markup and correct common errors so search engines can read it.
Use Use valid JSON-LD structured data in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Use valid JSON-LD structured data and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Use valid JSON-LD structured data skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Make sure the agent can read the HTML source of the page you want to check.
What your AI can do with it
- Validate JSON-LD blocks in script tags of type application/ld+json
- Check structured data for articles, products, FAQs, breadcrumbs, and local businesses
- Identify errors that prevent rich results from appearing in Google Search Console
- Fix invalid JSON-LD markup so search engines can parse it
- Audit existing structured data on a web page
Getting started
- Make sure the agent can read the HTML source of the page you want to check.
- Add the json-ld-valid skill to your agent configuration.
- Point the agent at a page or a JSON-LD block and ask it to validate the structured data.
- Review the reported issues and apply the suggested fixes to the page.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/json-ld-valid/SKILL.md and read by ahel’s review.
Invalid JSON-LD is silently ignored by Google — there are no error messages in search results, only the absence of rich results. Invalid structured data means no eligibility for rich results (stars, FAQs, breadcrumbs, etc.) that increase click-through rates.
Quick Reference
- JSON-LD must be valid JSON, reference
@context: 'https://schema.org', and include all required properties for the chosen@type - Invalid JSON (unclosed brackets, missing commas) causes the entire block to be silently ignored by Google
- Validate with Google's Rich Results Test before deploying structured data changes
Check
Find all <script type='application/ld+json'> elements on the page. For each: (1) Attempt to parse the content as JSON — flag syntax errors. (2) Verify @context is set to 'https://schema.org'. (3) Verify @type is a valid schema.org type. (4) For the detected type, check required properties are present (e.g., Article requires headline, author, datePublished; Product requires name; FAQPage requires mainEntity). (5) Run through Google's Rich Results Test API if available.
Fix
- Parse the JSON-LD with
JSON.parse()— fix any syntax errors (trailing commas, single quotes, missing brackets). - Ensure
@contextis exactly"https://schema.org"(not"http://schema.org"or omitted). - Verify the
@typevalue against schema.org types. - Add required properties for the type:
- Article: headline, author (with @type Person and name), datePublished
- Product: name (and ideally offers, description)
- FAQPage: mainEntity array with Question and acceptedAnswer
- BreadcrumbList: itemListElement array with ListItem, position, name, item
- Validate at https://search.google.com/test/rich-results
- Validate JSON syntax at https://jsonlint.com
Explain
Google uses JSON-LD structured data to generate rich results — enhanced search result formats that include stars, images, expandable Q&As, and other features. Invalid JSON-LD is ignored entirely: no rich results are generated, and no error is reported to you. Only by testing with the Rich Results Test can you discover validation failures. Correct, complete JSON-LD is a prerequisite for rich result eligibility.
Code Review
Extract all <script type='application/ld+json'> element contents. Run JSON.parse() on each — catch and report parse errors. Validate that @context equals 'https://schema.org'. Check @type against a whitelist of common valid types. For each type, validate required properties are present and non-empty. Report the first validation error found for each block.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/json-ld-valid
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
Questions
- Why are rich results not appearing in Google Search Console?
- Invalid or missing JSON-LD structured data can prevent rich results. This skill checks the markup and points out errors that may stop search engines from showing them.
- Can it check structured data for local businesses?
- Yes, it validates JSON-LD for local businesses along with articles, products, FAQs, and breadcrumbs.
- Does it support microdata or RDFa?
- No, it only works with JSON-LD blocks in script tags of type application/ld+json.
- Can it fix the JSON-LD automatically?
- The skill can suggest and apply fixes to invalid JSON-LD markup so search engines can parse it.
Advanced
- Item type
- skill
- Key
json-ld-valid- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist