schema-markup
Skill141 starsChanged 34 days agoUnlicenseView on GitHub
Generate and wire valid JSON-LD structured data for pages in this starter — Organization, WebSite, LocalBusiness, Article, Product, FAQPage, BreadcrumbList, Service — using the existing structured-data helper rather than inline script tags. Use when the user asks for "schema", "structured data", "JSON-LD", "rich snippets", "FAQ schema", or wants richer search/AI results.
68 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- CrawlCove/claude-seo-plugintheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- AlejandroGodius/claude-skillstheir own version, first seen Nov 16, 2026
- yotamwiesel/claude-skillstheir own version, first seen Nov 16, 2026
- harborrank/harborrank-skillstheir own version, first seen Nov 16, 2026
Used with
Projects with it also use keyword-cannibalization, broken-links and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
keuperaSkillkeyword-cannibalization
Detect and fix cases where several pages on the same site compete for the same query, splitting signals and suppressing all of them. Use whenever the user mentions keyword cannibalization, pages competing with each other, the wrong page ranking for a query, rankings that keep swapping between URLs, duplicate topics, or has published many posts on similar subjects. Also use when a page won't rank despite being good, or when Search Console shows several URLs alternating for one term.
Also in 3 projects that use this
akii-technologies-ltdSkillbroken-links
Find and fix broken links — three modes with different scale ceilings. `local` audits any local repo (HTML/MD/MDX, no size limit) via Glob/Grep + per-link verification. `page` checks one live URL deeply (~30-100 outbound links per run). `site` requires the Ahrefs site-audit MCP for true multi-page crawl — without it, refuses and tells the user how to get there. Use when the user asks to "check broken links", "find dead links", "fix 404s", "link checker", "broken link audit", "redirect chains", "find dead URLs", "link validation", "mixed content". Accepts a mode modifier (`--mode=local|page|site`); auto-detects from the target if unspecified.
Also in 3 projects that use this
JakeLabateSkillinternal-link-audit
Audit a website's internal linking structure for SEO. Crawls pages to find broken internal links, orphan pages, redirect chains, deep pages, missing or weak anchor text, and internal link distribution issues. Use when the user asks to audit, analyze, or improve internal links, site structure, link equity, or crawlability of a website.
Also in 3 projects that use this
tifetolaSkillon-page-seo
Also in 3 projects that use this
danielimadSkilltechnical-seo-audit
Analyses a website crawl export (Screaming Frog, Sitebulb, or Ahrefs Site Audit) and returns a prioritised list of technical SEO issues. Finds redirect chains and loops, duplicate title tags and meta descriptions, pages Google cannot index or render, broken internal links, and orphan pages. Trigger when the user uploads or points to a crawl file, a CSV or XLSX of URLs with status codes, or asks for a technical SEO audit, a crawl analysis, or to "find redirect chains".
Also in 4 projects that use this
xfstudioSkillproduct-marketing-context
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
Also in 19 projects that use this
Other versions68 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 68
- TheCraigHewitt/seomachine★ 7.5ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- OpenClaudia/openclaudia-skills★ 731same name
- boraoztunc/skills★ 473same name
- mysticaltech/marketingskills★ 352same name
- b1rdmania/ghostclaw★ 91same name
- akii-technologies-ltd/akii-seo-ai-search-optimizer★ 80same name
- robertbstillwell/marketing-skills★ 26same name
- ukunal91app/Marketing-Skills-by-Corey-Haines★ 26same name
- wpgaurav/WordPress-skills★ 19same name
58 more not listed
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- aeo-visibilitySkill
- figma-to-sectionSkill
- i18n-seoSkill
- local-seoSkill
- mobile-device-qaSkill
- optimize-3d-sceneSkill
- optimize-loadSkill
- optimize-performanceSkill
- payload-adminSkill
- payload-analyticsSkill
- payload-cmsSkill
- qa-verifySkill
- seo-auditSkill
- seo-growSkill
- ship-checkSkill
- site-migrationSkill
- supabase-authSkill
- supabase-dbSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 67 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Use and extend those: Never hand-write a <script type="application/ld+json"> in a component.
- Very specific: line 24
Check Google's current supported-features gallery (developers.google.com/search/docs/appearance/structured-data/search-gallery) before …
“Common” is measured: kept by at least 6 in 10 of the 67 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Structured data (JSON-LD)
This project already has src/utils/seo/structured-data.ts: typed builders
that each return a JsonLdNode — getSiteStructuredData() (Organization or a
LocalBusiness subtype + WebSite, rendered once by the root layout),
getBreadcrumbStructuredData(path) (from the route registry's parent chain),
getArticleStructuredData, getServiceStructuredData,
getFaqStructuredData, getPersonStructuredData,
getLocalBusinessStructuredData (one location of a multi-location business)
— plus jsonLdGraph(...nodes)
and <JsonLd data> (src/components/common/json-ld.tsx, escapes <).
Use and extend those. Never hand-write a
<script type="application/ld+json"> in a component.
First: what is the markup for?
Schema.org validity does not make a page eligible for a Google rich result. Check Google's current supported-features gallery (developers.google.com/search/docs/appearance/structured-data/search-gallery) before promising one:
- FAQ rich results stopped showing on 7 May 2026 (docs removed in June).
- HowTo rich results were retired in 2023.
- Sitelinks search box (
WebSite+SearchAction) was retired in 2024;WebSitestill feeds the site name.
Those types may still describe matching visible content — answer engines (ChatGPT, Perplexity, Claude) read them — but say so, and never sell them as a rich-result win. A missing report in Search Console for a retired feature is not a broken implementation.
Still worth it for Google: Organization (logo, knowledge panel facts),
BreadcrumbList, Article/BlogPosting, Product + Offer, LocalBusiness,
Event, Review/AggregateRating (on the reviewed thing only), VideoObject,
JobPosting.
Rules
- JSON-LD only — never microdata or RDFa (hard rule #10).
- Only describe what is on the page. Schema that claims content the page does not contain is spam, and Google treats it that way.
- Reference, don't duplicate. Build the graph with
@idreferences between entities so the Organization is defined once and linked from everywhere. - Values come from
siteConfig(src/lib/site.ts—organizationholds the founding date, contact, address,sameAs, and the local factsopeningHours,geo,areaServed,priceRange,hasMap), the route registry (src/lib/routes.ts) and the page's own props — never hardcoded a second time. Leave a fact out rather than guess one. - Validate: the JSON parses, required properties are present, URLs are absolute.
- No placeholder names. The graph reads
siteConfig.name— on sites built from the old starter the JSON-LDOrganizationsaid "New Project" while Lighthouse still scored SEO 100.logopoints at the brand mark (/icon-512.pngfrom the brand kit, or the logo file), never the starter's icon;sameAslists only profiles the site actually links. - The robot form carries the same graph. Crawlers get
/robot-viewunder/(optimize-load/references/robot-path.md); render JSON-LD from the root layout or the view so both forms emit it, and diff the two:curl -s -A "Googlebot/2.1" <url>/ | grep -c 'application/ld+json'equals the people count. - Absolute URLs come from
siteConfig.url, which is the build-time origin — check the deployed graph names the real domain, notlocalhost.
Types worth adding, by page kind
| Page | Type | Required-ish properties |
| Home | Organization, WebSite | name, url, logo, sameAs |
| Local business | LocalBusiness subtype — getSiteStructuredData({ type: "Dentist" }) | address, geo, openingHours, telephone (from siteConfig.organization; hours/geo/priceRange emit only for a LocalBusiness type) |
| One location of many | getLocalBusinessStructuredData({ path, name, address, … }) | its own @id (#location), parentOrganization → the brand — skill local-seo |
| Blog post | Article / BlogPosting | headline, image, datePublished, dateModified, author |
| Service page | Service | serviceType, provider, areaServed |
| Product | Product + Offer | name, image, description, price, availability |
| FAQ block | FAQPage | mainEntity[] of Question/acceptedAnswer — answer engines only; no Google rich result since May 2026 |
| Any nested page | BreadcrumbList | itemListElement with position |
| Team page | Person per member | name, jobTitle, image, worksFor |
FAQPage no longer earns a Google rich result, but a real, visible FAQ is still
one of the formats answer engines extract most reliably — mark it up with
getFaqStructuredData when the questions are on the page, never schema-only.
The answer text must match the page exactly.
Pattern
The site graph renders once in the root layout. A page's own graph renders in
its view — one <JsonLd> per page:
const breadcrumb = getBreadcrumbStructuredData(PATH);
// …
<JsonLd data={jsonLdGraph(
...(breadcrumb ? [breadcrumb] : []),
getServiceStructuredData({ path: PATH, name, description, serviceType }),
)} />src/views/legal/privacy-policy.tsx ships the breadcrumb example. A type the
helper lacks → add a typed builder to structured-data.ts (input interface,
@id = ${absoluteUrl(path)}#<kind>, { "@id": ORGANIZATION_ID } for the
publisher/provider), then document it in obsidian/frontend/utils.md.
yarn qa:seo FAILs on JSON-LD that doesn't parse and on a robot form whose
block count differs from the people form.
After
Note new schema in obsidian/frontend/seo-metadata.md, and validate with
Google's Rich Results Test / schema.org validator against the deployed URL.
(When auditing another site: curl and WebFetch can miss JSON-LD a CMS
plugin injects with JavaScript — check in a rendered browser before reporting
"no schema".)
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.

