schema-validation
Skill5 starsChanged 35 days agoMITView on GitHub
Extract, validate, and generate Schema.org JSON-LD structured data, including @graph inheritance, 17 rich-result required-property rules, Product/LocalBusiness validation, and FAQ visible content parity.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- reaatech/mcp-gatewaytheir own version, first seen Apr 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- reaatech/mcp-gateway★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- one-step-seoSkill
- accessibility-seoSkill
- answer-engine-optimizationSkill
- content-qualitySkill
- core-web-vitalsSkill
- duplicate-contentSkill
- ecommerce-seoSkill
- entity-optimizationSkill
- geo-optimizationSkill
- http-statusSkill
- image-seoSkill
- internal-linkingSkill
- international-seoSkill
- javascript-seoSkill
- llms-txtSkill
- local-seoSkill
- onpage-optimizationSkill
- security-hygieneSkill
- seo-auditSkill
- seo-fixSkill
- seo-regressionSkill
- sitemap-robotsSkill
- social-metadataSkill
- technical-seoSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Run npx one-step-seo schema <url> or npx one-step-seo page <target> --skills schema-structured-data --out ./seo-report.
- Very specific: line 40
If a page has FAQPage JSON-LD without visible FAQ copy on the page, warn the user that invisible FAQ markup violates search engine …
- Very specific: line 41
If a page has visible FAQ headings/questions without FAQPage JSON-LD, generate the matching FAQPage snippet from the visible Q&A pairs.
- Very specific: line 43
Run npx one-step-seo schema <url> --generate <kind> to produce a starter <script type="application/ld+json"> block seeded with the page's …
- Very specific: line 74
Always escape </script as <\/script inside JSON-LD blocks (schemaSnippet enforces this automatically).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
schema-validation — Structured Data & Rich Result Validation
1. Description & Activation Criteria
Activate schema-validation when the user wants to:
- Extract and validate JSON-LD
<script type="application/ld+json">blocks on a page or local HTML file (S01-json-invalid,S01-none,S02-*,S03-faq-parity). - Validate e-commerce
Product(offers/review/aggregateRating),LocalBusiness,Article,FAQPage,BreadcrumbList,Organization,WebSite,Event,VideoObject,HowTo,JobPosting,Course,Recipe,Review, orSoftwareApplicationmarkup. - Generate clean, XSS-safe JSON-LD starter snippets across 14 Schema.org types using
one-step-seo schema <url> --generate <kind>.
2. Inputs & Prerequisites
- Target: Live URL or local HTML file.
- Supported
--generatekinds (lib/schema.mjs):organization,website,article,faq,breadcrumb,product,event,localbusiness,howto,video,job,course,review,recipe.
3. Step-by-Step Workflow
- Inspect existing JSON-LD nodes and issues:
- Run
npx one-step-seo schema <url>ornpx one-step-seo page <target> --skills schema-structured-data --out ./seo-report.
- Run
- Fix JSON syntax errors first (
S01-json-invalid, P1):- Unparseable JSON-LD (trailing commas, unescaped quotes, broken tags) costs 10 Search SEO points (
P1) and is completely ignored by search engines.
- Unparseable JSON-LD (trailing commas, unescaped quotes, broken tags) costs 10 Search SEO points (
- Resolve per-type required property issues (
S02-<type>, P2):- Inspect every
S02-*finding (schema-structured-data):Article/BlogPosting/NewsArticle: requiresheadlineProduct: requiresoffers,review, oraggregateRatingFAQPage: requiresmainEntityquestions arrayBreadcrumbList: requiresitemListElementOrganization/LocalBusiness/WebSite/HowTo/Course/Recipe/SoftwareApplication: requiresnameEvent: requiresstartDateVideoObject: requiresthumbnailUrlJobPosting: requirestitleReview: requiresitemReviewed
- Inspect every
- Verify FAQ content parity (
S03-faq-parity, P3):- If a page has
FAQPageJSON-LD without visible FAQ copy on the page, warn the user that invisible FAQ markup violates search engine structured data guidelines (S03-faq-parity). - If a page has visible FAQ headings/questions without
FAQPageJSON-LD, generate the matchingFAQPagesnippet from the visible Q&A pairs.
- If a page has
- Generate valid JSON-LD snippets when missing (
S01-none, P1):- Run
npx one-step-seo schema <url> --generate <kind>to produce a starter<script type="application/ld+json">block seeded with the page's real<title>,<meta name="description">, andfinalUrl.
- Run
4. Tools & CLI Commands
# Validate JSON-LD on a live URL and generate a Product schema snippet
npx one-step-seo schema https://example.com/shop/item --generate product
# Run schema-focused audit checks on a local HTML file
npx one-step-seo page ./dist/index.html --skills schema-validation --offline --out ./seo-report5. Evidence Requirements
- Quote all detected
@typevalues from theS01-presentfindingevidenceinreport.findings,schemacommand stdout, orai --json(signals.schemaTypes). - Quote exact
S01-json-invalid,S02-*, andS03-faq-parityevidence strings. - Confirm whether
@graphblocks properly declare"@context": "https://schema.org"at the root or node level.
6. Expected Outputs
- Detected Schema Inventory: Node count,
@typelist, syntax status, and property validation results. - Ready-to-Paste JSON-LD
<script>Block: Validated againstlib/schema.mjswith</scriptsafely escaped as<\/scriptto prevent XSS breakout.
7. Limitations & External Data
- Structural vocabulary check:
lib/schema.mjsvalidates JSON syntax,@contextinheritance across@grapharrays, a 350+ typeKNOWN_TYPESallowlist, and required properties across 15 rich-result validator rules (covering 17 Schema.org types includingArticle/NewsArticle/BlogPosting). - No fabricated identity data:
generateSchemarefuses to emit placeholder"Example"identity data whennameorurlis missing.
8. Safety & Approval Rules
- Never invent ratings, prices, review counts, salaries, or event dates in JSON-LD markup. Every property in
<script type="application/ld+json">must match visible text on the page. - Always escape
</scriptas<\/scriptinside JSON-LD blocks (schemaSnippetenforces this automatically).
9. Examples
# Validate existing schema and generate LocalBusiness JSON-LD
npx one-step-seo schema https://example.com/contact --generate localbusinessDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

