Schema starter pack
Six JSON-LD templates (LocalBusiness, Organization, Product, Breadcrumb, Article, FAQ) built from Google's docs, plus the free tools to generate and test them.
Inside this Template
Copy-paste schema markup for the types a small business actually needs, written from Google's own documentation. Swap in your details, test it with two free tools and publish.
Who it's forSmall business owners and founders who want to add schema markup themselves without hiring a developer.
How to use it
Google supports JSON-LD, Microdata and RDFa, and recommends JSON-LD.
Google's guidelines: don't mark up content that isn't visible to readers.
Google says pages using LocalBusiness or Organization markup are ineligible for star reviews when the business controls reviews about itself.
Google says it does not guarantee your structured data will show up in search results.
Google recommends the most specific schema.org subtype that fits.
Start with one row. Most small sites need only the first three.
| Page | Schema to add | Can earn in Google | Must have |
|---|---|---|---|
| Homepage (local business) | LocalBusiness (or a subtype like Dentist) | Business details in Search and Maps | name, address |
| Homepage (online business) | Organization | Logo and business info in knowledge panels | No required properties; add name, url, logo |
| Every page below the homepage | BreadcrumbList | Breadcrumb trail in results | 2+ ListItems with position and name |
| Product page | Product with Offer | Price, availability, ratings if real | name + offers, review or aggregateRating |
| Blog post | Article (or BlogPosting) | Better title, image and date display | No required properties; add headline, image, dates, author |
| FAQ section | FAQPage (optional) | Nothing visible in Google since May 7, 2026 | Questions and answers exactly as on the page |
| Event page | Event | Event listing in results | name, startDate, location (with address) |
| Video page | VideoObject | Video badge and key moments | name, thumbnailUrl, uploadDate |
Paste one into the page's HTML (the <head> or body both work). Replace placeholders. Delete any line you can't fill truthfully.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "YOUR BUSINESS NAME",
"url": "https://www.example.com/",
"telephone": "+1-555-555-5555",
"priceRange": "$$",
"image": "https://www.example.com/images/storefront.jpg",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Your City",
"addressRegion": "ST",
"postalCode": "00000",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 40.76129,
"longitude": -73.98229
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": [
"Monday",
"Tuesday",
"Wednesday",
"Thursday",
"Friday"
],
"opens": "09:00",
"closes": "17:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "10:00",
"closes": "14:00"
}
]
}
</script><script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "YOUR COMPANY",
"url": "https://www.example.com/",
"logo": "https://www.example.com/images/logo.png",
"description": "One plain sentence about what you do.",
"email": "hello@example.com",
"sameAs": [
"https://www.linkedin.com/company/your-company",
"https://www.youtube.com/@yourchannel"
]
}
</script><script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "PRODUCT NAME",
"image": "https://www.example.com/images/product.jpg",
"description": "What it is, in one sentence.",
"offers": {
"@type": "Offer",
"price": 49.0,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/product"
}
}
</script><script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Services",
"item": "https://www.example.com/services/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Plumbing",
"item": "https://www.example.com/services/plumbing/"
},
{
"@type": "ListItem",
"position": 3,
"name": "Emergency plumbing"
}
]
}
</script><script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "YOUR ARTICLE TITLE",
"image": [
"https://www.example.com/images/cover-16x9.jpg"
],
"datePublished": "2026-10-19T08:00:00+00:00",
"dateModified": "2026-10-19T08:00:00+00:00",
"author": [
{
"@type": "Person",
"name": "AUTHOR NAME",
"url": "https://www.example.com/about/author-name"
}
]
}
</script><script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "QUESTION 1, exactly as shown on the page?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Answer 1, exactly as shown on the page."
}
},
{
"@type": "Question",
"name": "QUESTION 2?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Answer 2."
}
}
]
}
</script>A made-up clinic so you can see a finished, specific version. Every value must come from your own page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Dentist",
"name": "Smile Studio Dental Clinic",
"url": "https://www.example.com/",
"telephone": "+91-20-5555-0000",
"image": "https://www.example.com/images/clinic-front.jpg",
"priceRange": "₹₹",
"address": {
"@type": "PostalAddress",
"streetAddress": "12 FC Road",
"addressLocality": "Pune",
"addressRegion": "MH",
"postalCode": "411004",
"addressCountry": "IN"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"],
"opens": "10:00",
"closes": "19:00"
}
],
"sameAs": [
"https://www.instagram.com/YOURHANDLE"
]
}
</script>Write JSON-LD schema for the page below. Rules: - Use the most specific schema.org type that fits (for example Dentist, not LocalBusiness). - Use ONLY facts that appear in the page text. If a property needs a fact that isn't there, leave it out. Never invent ratings, reviews, prices or addresses. - No aggregateRating or review unless real customer reviews appear in the text. - Output one <script type="application/ld+json"> block and nothing else. PAGE URL: [url] PAGE TEXT: [paste the visible text of the page]
WordPress SEO plugin that adds schema from a menu, no code.
Ritik's note: Turn on the Local SEO module for LocalBusiness.
Adds a schema graph automatically: Organization or Person, WebSite, WebPage, Article, Breadcrumb and more.
Ritik's note: Set Organization vs Person correctly in Site representation settings.
Browser form that writes JSON-LD for common types as you fill it in.
Ritik's note: Still test the output. Generators can include fields Google doesn't use.
Google's test of which rich results your markup can earn, with errors and warnings.
Ritik's note: Paste the code before you publish. Then test the live URL after.
Schema.org's validator for every type, including ones Google ignores.
Ritik's note: Run one page through it today. That's the whole homework.
Shows the structured data Google found on the indexed version of a page.
Ritik's note: Use 'Test live URL' after a change, then check the Enhancements reports over the next weeks.
Easiest: use Rank Math or Yoast. For custom code, use a header/footer code plugin or your theme's custom code area to add the <script> block to one page.
Many themes already output Product schema; check a product URL in the Rich Results Test first so you don't add a duplicate. For LocalBusiness or Organization, add the script in your theme code (theme.liquid) or with an app. (Practical advice; check your theme's docs.)
Paste the script into Page settings > Custom code (inside <head> tag) for a single page, or Site settings for site-wide code. (Practical advice; check Webflow's help docs.)
Test the live URL in the Rich Results Test, then URL Inspection in Search Console.
Paste your homepage into the Rich Results Test. Many themes and plugins already add schema. If it finds Organization or LocalBusiness, edit that one instead of adding a second.
Copy template 1 (LocalBusiness) or 2 (Organization). Replace every capital-letter placeholder with the details shown on your page. Delete lines you can't fill.
Paste the code (Code tab) into the Rich Results Test, then the Schema Markup Validator. Fix every error. Warnings are optional fields.
Use the platform steps below. One script block per type, on the page it describes.
Test the live URL in the Rich Results Test. Then Search Console > URL Inspection > Request indexing.
Two conflicting blocks confuse parsers. Check first, then edit one.
Google's guidelines: markup must match visible content, or you risk a manual action.
"123 Main St" in your live schema tells Google the wrong address.
Google stopped showing FAQ rich results on May 7, 2026.
Theme updates can break schema. Re-test after any template change.
Every claim in this Template traces back to one of these. Checked 2026-11.
Keep going
Checklists, templates, tool lists and playbooks for SEO, AI search, marketing and growing a business or career. New ones every week.
ritiknamdev.com/resources