Now Reading: How to Add Schema Markup to Any Website (JSON-LD Examples)
-
01
How to Add Schema Markup to Any Website (JSON-LD Examples)
You don't need a developer to add JSON-LD schema just one script tag and the right template. Seven complete, copy-paste code blocks, platform-specific placement instructions, and a live snippet builder.
You do not need a developer to add schema markup to a website. You need one script tag, the right JSON-LD template, and about ten minutes per page. This guide gives you copy-paste code for the seven schema types that cover almost every website, plus exactly where to paste them, whatever platform you run.
JSON-LD is a JavaScript object wrapped in a single script tag that tells search engines and AI systems exactly what a page contains, separate from your visible HTML entirely.
Google explicitly recommends this format over the older Microdata and RDFa alternatives, since it can be added, edited, or removed without touching your page's actual layout.
We covered why this matters in our complete schema markup guide. This article is the hands-on companion: real code, real placement instructions, nothing theoretical.
script tag is all JSON-LD requires, placed anywhere in the page's HTML
schema types covered here handle the vast majority of website content
visible changes to your page's design or layout, since JSON-LD is invisible to users
How to Add JSON-LD to a Static HTML Website
Paste the script tag anywhere between your page's <head> tags, or just before the closing </body> tag if editing the head is inconvenient.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "name": "Brandella Journal", "url": "https://www.brandella.in", "logo": "https://www.brandella.in/logo.png", "sameAs": [ "https://www.linkedin.com/company/brandella", "https://twitter.com/brandella" ] } </script>
Organization schema, added once, site-wide, ideally on every page's head
Article Schema for Blog Posts and News Content
According to SEOScore's 2026 schema markup guide, Article is one of the 10 most-used JSON-LD types, and it is what qualifies a blog post for enhanced treatment in search results.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Article", "headline": "How to Add Schema Markup to Any Website", "author": { "@type": "Person", "name": "Santaji" }, "datePublished": "2026-07-31", "dateModified": "2026-07-31", "image": "https://www.brandella.in/images/schema-guide.jpg", "publisher": { "@type": "Organization", "name": "Brandella Journal" } } </script>
Article schema, placed on individual blog post pages only
FAQ Schema: An Important 2026 Caveat
According to Foglift's 2026 JSON-LD guide, Google discontinued the FAQ rich result display in May 2026. The schema itself remains valid and is still parsed by crawlers, including AI systems, but it no longer earns the expandable accordion appearance in Google's traditional search results.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "What is JSON-LD?", "acceptedAnswer": { "@type": "Answer", "text": "A JSON script format for structured data, recommended by Google." } }] } </script>
FAQPage schema, only for questions genuinely visible on the page itself
Product Schema for Ecommerce Pages
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "Wireless Keyboard", "image": "https://example.com/keyboard.jpg", "description": "A compact wireless keyboard with backlit keys.", "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "49.99", "availability": "https://schema.org/InStock" } } </script>
Product schema, one block per product page, with prices kept accurate and current
LocalBusiness Schema for Storefronts and Service Areas
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Pune Coffee House", "address": { "@type": "PostalAddress", "streetAddress": "12 MG Road", "addressLocality": "Pune", "addressRegion": "MH", "postalCode": "411001" }, "telephone": "+91-20-0000-0000", "openingHours": "Mo-Sa 09:00-20:00" } </script>
LocalBusiness schema, placed on the homepage or a dedicated contact/location page
BreadcrumbList Schema for Site Navigation
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.brandella.in/" }, { "@type": "ListItem", "position": 2, "name": "SEO", "item": "https://www.brandella.in/category/seo/" } ] } </script>
BreadcrumbList schema, matching the visible navigation trail shown on the page
HowTo Schema for Tutorial Content
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "HowTo", "name": "How to Add JSON-LD to a Website", "step": [ { "@type": "HowToStep", "text": "Choose the schema type matching your content." }, { "@type": "HowToStep", "text": "Paste the JSON-LD script into your page's head." }, { "@type": "HowToStep", "text": "Validate using Google's Rich Results Test." } ] } </script>
HowTo schema, used for genuine step-by-step tutorial content
Where to Paste This Code by Platform
Placement differs slightly depending on what your site runs on. Tap through the platform that matches your setup.
Paste the full script block directly into the HTML file, between the head tags. No plugin or additional tool is required for a static site.
According to SchemaValidator's step-by-step tutorial, WordPress users can paste JSON-LD through an SEO plugin's custom schema field, or directly into a theme's header.php file just before the closing head tag.
In Shopify, JSON-LD typically goes into the theme.liquid file, inside the head section, or through a dedicated schema app if editing theme code directly is not preferred.
How to Validate Your Schema Before Publishing
Check the Page Source First
According to SchemaValidator's tutorial referenced above, right-click the page, choose View Page Source, and search for "application/ld+json". If it appears there, the script is rendering server-side correctly.
Run Google's Rich Results Test
Paste your page URL at search.google.com/test/rich-results. A correctly detected schema type confirms the markup is syntactically valid and eligible for enhanced treatment.
Cross-Check With Schema.org's Validator
According to Schema Pilot's complete JSON-LD guide, the official Schema.org Validator checks structural correctness independently of Google's specific rich-result requirements, catching errors the Rich Results Test alone might miss.
JSON-LD Snippet Builder
Fill in the fields below to generate a basic Organization schema block ready to copy into your site.
JSON-LD Snippet Builder
Generates a copy-paste Organization schema block from your details
Combining Multiple JSON-LD Blocks on One Page
According to ClickForest's JSON-LD implementation guide, most websites duplicate Organization schema unnecessarily across every page. A single site-wide script defining WebSite, Organization, and Person entities once keeps page-level JSON-LD concise and easier to maintain.
A typical blog post, for example, only needs its own Article or BlogPosting block plus an optional BreadcrumbList, while the Organization details live in one shared script referenced across the entire site rather than repeated on every single page.
Why JSON-LD Matters Beyond Traditional Rich Results
According to SEO Strategy's complete JSON-LD implementation guide, when ChatGPT browses a website, it parses the JSON-LD directly. When Perplexity retrieves a page as a citation source, it extracts the same structured data.
This means well-implemented JSON-LD is no longer just about earning a star rating or an accordion in Google's results.
According to Netstager's 2026 guide to JSON-LD for modern SEO, it is increasingly the foundational layer AI systems rely on to understand exactly what an Organization, Product, or Service actually is, before ever deciding whether to cite it.
Common JSON-LD Mistakes That Break Validation
| Mistake | Why It Breaks Things |
|---|---|
| Trailing commas | Invalid JSON syntax, fails validation entirely |
| Smart quotes instead of straight quotes | Common when pasting from Word or Google Docs |
| Marking up content not visible on the page | Violates Google's structured data policies |
| Duplicate schema blocks for the same entity | Creates conflicting or redundant signals |
| Mismatched prices or dates vs. visible content | Triggers manual actions or validation warnings |
Keeping JSON-LD Accurate as Your Site Changes
According to Incremys' guide to Schema.org for SEO, structured data works best as a living part of a page's content, updated whenever prices, dates, or author details actually change, rather than treated as a one-time setup task.
According to eSEOspace's comprehensive guide to Google-supported schema types, re-validating key page templates after any redesign or platform migration catches broken JSON-LD before it quietly stops earning rich results at scale.
FAQs on Adding Schema Markup
> what_we_learn_today.log
JSON-LD is a single script tag, invisible to visitors, easy to maintain
Seven schema types cover Organization, Article, FAQ, Product, Local, Breadcrumb, HowTo
FAQ rich results were deprecated in May 2026; the schema itself still parses fine
Placement varies slightly by platform: static HTML, WordPress, Shopify
Always validate with Rich Results Test and Schema.org Validator before publishing
Schema markup aids understanding and eligibility, not a direct ranking factor
