seo-structured-data
Skill10 starsChanged 6 months agoMITView on GitHub
Use when adding Schema.org JSON-LD structured data to public pages: Organization, WebSite, Article, Product, FAQPage, BreadcrumbList, SoftwareApplication. Not for authenticated dashboards or non-public content.
In this repository56 other files it gives its agents.
- accessibility-passSkill
- analytics-eventsSkill
- api-error-handlingSkill
- audit-logging-backendSkill
- background-jobs-and-cronSkill
- dark-mode-and-themingSkill
- dashboard-charts-rechartsSkill
- edge-functions-and-webhooksSkill
- email-and-notificationsSkill
- error-states-and-empty-uiSkill
- feature-flags-and-togglesSkill
- file-upload-storageSkill
- i18n-multi-languageSkill
- lovable-prompting-playbookSkill
- lovable-ship-checklistSkill
- migration-playbookSkill
- multi-tenant-backendSkill
- onboarding-copySkill
- optimistic-updatesSkill
- payment-failed-and-recoverySkill
- payment-webhook-idempotencySkill
- payment-webhook-testingSkill
- performance-budgetSkill
- pg-cron-recipesSkill
- pg-cron-scheduled-jobsSkill
- pg-cron-with-pg-net-edgeSkill
- postgres-full-text-searchSkill
- postgres-triggers-and-functionsSkill
- pricing-and-billingSkill
- programmatic-seo-content-qualitySkill
- programmatic-seo-pagesSkill
- rate-limiting-edgeSkill
- realtime-and-subscriptionsSkill
- refactor-safe-diffSkill
- release-notesSkill
- seo-core-web-vitalsSkill
- seo-landing-pageSkill
- seo-meta-tags-spaSkill
- seo-sitemap-generationSkill
- seo-ssr-and-prerenderingSkill
- server-input-validationSkill
- shadcn-patternsSkill
- soft-delete-and-archivingSkill
- stripe-one-time-payment-webhooksSkill
- stripe-payment-webhooksSkill
- supabase-auth-flowsSkill
- supabase-database-designSkill
- supabase-rls-and-authSkill
- support-replySkill
- tanstack-infinite-queriesSkill
- tanstack-mutations-and-invalidationSkill
- tanstack-prefetch-and-hydrationSkill
- tanstack-query-alternativeSkill
- tanstack-router-data-loadersSkill
- tanstack-start-server-routesSkill
- typed-api-hooks-formsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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 28
Always JSON.stringify — never inline a JS object literal as text.
- Very specific: line 84
Only include aggregateRating if the ratings are real and verifiable on the page.
- Distinctive: line 121
Only mark up FAQs visible on the same page.
- Distinctive: line 162
Use only when the page is really about the entity.
- Distinctive: line 168
Search Console → Enhancements → check each schema type for errors.
≈ “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
SEO structured data (JSON-LD)
Schema.org JSON-LD helps Google show rich results (FAQs, ratings, breadcrumbs) and improves AI-powered SERP features. Render it in the page <head> or just before </body>.
Companion skills: seo-meta-tags-spa, seo-landing-page, seo-ssr-and-prerendering.
Helper
export function JsonLd({ data }: { data: object }) {
return (
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }}
/>
);
}Always JSON.stringify — never inline a JS object literal as text.
Home / global (every public page or just /)
<JsonLd
data={{
"@context": "https://schema.org",
"@type": "Organization",
name: "Acme",
url: "https://acme.com",
logo: "https://acme.com/logo.png",
sameAs: [
"https://twitter.com/acme",
"https://www.linkedin.com/company/acme",
"https://github.com/acme",
],
}}
/>
<JsonLd
data={{
"@context": "https://schema.org",
"@type": "WebSite",
name: "Acme",
url: "https://acme.com",
potentialAction: {
"@type": "SearchAction",
target: "https://acme.com/search?q={query}",
"query-input": "required name=query",
},
}}
/>SaaS product / pricing page
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
name: "Acme",
applicationCategory: "BusinessApplication",
operatingSystem: "Web",
offers: [
{ "@type": "Offer", price: "0", priceCurrency: "USD", name: "Free" },
{ "@type": "Offer", price: "29", priceCurrency: "USD", name: "Pro" },
],
aggregateRating: {
"@type": "AggregateRating",
ratingValue: "4.8",
reviewCount: "127",
},
}Only include aggregateRating if the ratings are real and verifiable on the page.
Article / blog post
{
"@context": "https://schema.org",
"@type": "Article",
headline: post.title,
description: post.excerpt,
image: [post.cover_url],
datePublished: post.published_at,
dateModified: post.updated_at,
author: { "@type": "Person", name: post.author.name, url: `https://acme.com/authors/${post.author.slug}` },
publisher: {
"@type": "Organization",
name: "Acme",
logo: { "@type": "ImageObject", url: "https://acme.com/logo.png" },
},
mainEntityOfPage: { "@type": "WebPage", "@id": `https://acme.com/blog/${post.slug}` },
}FAQ page
{
"@context": "https://schema.org",
"@type": "FAQPage",
mainEntity: faqs.map((f) => ({
"@type": "Question",
name: f.question,
acceptedAnswer: { "@type": "Answer", text: f.answer },
})),
}Only mark up FAQs visible on the same page. Marking up hidden Q&A is against Google guidelines.
Breadcrumbs
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
itemListElement: [
{ "@type": "ListItem", position: 1, name: "Home", item: "https://acme.com/" },
{ "@type": "ListItem", position: 2, name: "Blog", item: "https://acme.com/blog" },
{ "@type": "ListItem", position: 3, name: post.title, item: `https://acme.com/blog/${post.slug}` },
],
}Product (e-commerce)
{
"@context": "https://schema.org",
"@type": "Product",
name: product.name,
image: product.images,
description: product.description,
sku: product.sku,
brand: { "@type": "Brand", name: "Acme" },
offers: {
"@type": "Offer",
url: `https://acme.com/p/${product.slug}`,
priceCurrency: "USD",
price: (product.price_cents / 100).toFixed(2),
availability: product.in_stock
? "https://schema.org/InStock"
: "https://schema.org/OutOfStock",
},
}HowTo, Review, Event
Use only when the page is really about the entity. Don't slap HowTo on every blog post — Google ignores or penalizes mismatched schema.
Verify
- Rich Results Test
- Schema Markup Validator
- Search Console → Enhancements → check each schema type for errors.
Avoid
- Marking up content not visible on the page.
- Fake ratings or counts.
- Multiple primary types (
Article+Producton the same page) without a clear reason. - Repeating the same Organization block on every page when one global instance is fine.
- Forgetting to update
dateModifiedon edits.
Checklist
Organization+WebSiteon home page.Articleon every blog post with real author and dates.BreadcrumbListon nested pages.FAQPageonly when FAQ is rendered and visible.- Validated in Rich Results Test before deploy.
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.

