schema-gen
Skill0 starsChanged 2 months agoMITView on GitHub
Ready-to-deploy JSON-LD for a page or page type with sameAs on every entity, values taken only from the visible page, and an alignment check.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- GlamgarOnDiscord/claude-saas-blueprinttheir own version, first seen May 17, 2026
- sharozdawa/schema-gentheir own version, first seen Mar 21, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- GlamgarOnDiscord/claude-saas-blueprint★ 2same name
- sharozdawa/schema-gen★ 1same 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 repository15 other files it gives its agents.
- alignment-auditSkill
- auditSkill
- citable-passageSkill
- content-briefSkill
- entity-coverageSkill
- humanizerSkill
- internal-linksSkill
- meta-tagsSkill
- navboost-auditSkill
- optimizeSkill
- researchSkill
- scoreSkill
- seo-fundamentalsSkill
- topic-clustersSkill
- write-seoSkill
The file
Files
/schema-gen — Schema markup generator
Target: $ARGUMENTS
Templates: ${CLAUDE_PLUGIN_ROOT}/skills/seo-fundamentals/references/schema-markup-templates.md. Policy basis (markup must match visible content): ${CLAUDE_PLUGIN_ROOT}/skills/seo-fundamentals/references/patent-signals.md (G4).
Process
- Page analysis (URL):
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_page.py "<url>" --json→ existing JSON-LD, title, author, dates, headings, prices, ratings. If no JSON-LD is found, say "not detected in static HTML" and offer to proceed from the visible content. Page type only: generate from the template and mark every value to fill. Type selection:
Content Primary Add Blog post / article Article or BlogPosting + Person (author, sameAs)BreadcrumbList; FAQPage only if the Q/A are literally in the body How-to guide Article (HowTo markup no longer yields rich results; use only if steps are on the page) BreadcrumbList Product page Product + Brand ( sameAs), offers, gtin/mpnBreadcrumbList, AggregateRating only if ratings are visible Landing page Organization ( sameAs) or ProductBreadcrumbList Local business LocalBusiness (address, geo, openingHours, sameAsto GBP/Wikidata)BreadcrumbList Homepage Organization ( sameAsto Wikidata, Crunchbase, LinkedIn, registries)WebSite with SearchAction Comparison page Article BreadcrumbList sameAspriorities — Person: LinkedIn, ORCID, Wikidata/Wikipedia, GitHub; Organization: Wikidata, Crunchbase, LinkedIn, official registries; Product: manufacturer page, Wikidata; LocalBusiness: Google Business Profile, Wikidata. Fewer high-confidence entries beat many weak ones.- Generate — complete JSON-LD per type: required fields from the page content, recommended optional fields, ISO 8601 dates, absolute URLs, nesting (author → Person, publisher → Organization with logo). Every value must be visible on the page; anything unknown becomes
"<FILL: …>", never a guess. - Alignment check — compare every numeric and named value in the generated markup with the body (prices, dates, ratings, names). Flag MISMATCH / SCHEMA-ONLY / WEAK ENTITY (author without page or
sameAs) / SCHEMA SPAM (FAQ/HowTo not in body). For an existing implementation with many issues, hand off to/alignment-audit. - Validation guidance — Rich Results Test, Schema.org validator, expected outcome (which types are rich-result eligible today; Article, Product, Breadcrumb, Organization yes; FAQ/HowTo no for most sites), monitoring in Search Console Enhancements.
Output
- Recommended types with rationale.
- Copy-paste
<script type="application/ld+json">blocks. - Placement (
<head>), testing steps, what to expect after indexing. - Existing-schema issues (URL given): missing required fields, mismatches with visible content, deprecated types, validation errors.
<FILL>list for the user.
Does 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.