Schema Markup: A Practical Guide With Copy-Paste JSON-LD
Schema markup tells engines what your content is and unlocks rich results. A practical guide with copy-paste JSON-LD, the types that matter, and the match-your-content rule.
Schema markup is structured data you add to your pages — in JSON-LD format — that tells search engines explicitly what your content is: an article, a product, an FAQ, an organisation, a review. It doesn’t directly boost rankings, but it unlocks rich results (star ratings, FAQ dropdowns, prices shown in search) that lift click-through, and it helps both search and AI engines understand and trust your content. This guide is practical: what schema is, the types that matter most, copy-paste JSON-LD you can adapt, and the rules that keep it working.
Key takeaway
- Schema markup is structured data (best implemented as JSON-LD) that tells engines explicitly what your content is.
- It doesn’t directly raise rankings but unlocks rich results that lift click-through, and helps search and AI engines understand you.
- The golden rule: your markup must always match the visible content on the page, or it can be ignored or penalised.
What is schema markup?
Schema markup is a standardised vocabulary of structured data — from schema.org — that you add to your pages to describe their content explicitly to machines. Instead of leaving a search engine to infer that a page is a recipe, a product, or an FAQ, schema states it directly, along with the relevant details: the recipe’s cook time, the product’s price and availability, the FAQ’s questions and answers. It’s the difference between hoping the engine understands your content and telling it plainly.
The recommended format is JSON-LD — a block of structured data in the page’s code, separate from the visible content, which Google explicitly prefers over older inline formats. You add a JSON-LD script to your page, and engines read it to understand the content’s type and details.
What schema does and doesn’t do
Schema doesn’t directly improve your rankings — it’s not a ranking factor in the sense that adding it lifts your position. What it does is make your content eligible for rich results: the enhanced search listings with star ratings, FAQ accordions, prices, images and other features that make your result more prominent and clickable. Those richer listings lift click-through, which is the real value. Schema also increasingly helps AI engines parse and trust your content, making it a dual investment across search and AI answers.
JSON-LD
Google’s explicitly preferred schema format — a structured-data script placed in the page code, separate from visible content. It’s easier to implement and maintain than older inline microdata, and it’s the format to use for all the schema types below.
Source — Google structured-data guidance
The schema types that matter most
Organization — identifies your business, its name, logo, contact details and official profiles (via sameAs). Foundational for entity recognition. Article — marks up blog posts and articles with headline, author, dates. FAQPage — marks up genuine FAQ sections and can produce expandable Q&A in results. Product — for ecommerce, with price, availability and reviews for rich shopping results. LocalBusiness — for location-based businesses, with address, hours and area served. BreadcrumbList — shows your site hierarchy in results. Review/AggregateRating — displays star ratings. Choose the types genuinely relevant to each page rather than adding everything.
How widely is schema markup actually used?
More than half the web now carries structured data of some kind. WebDataCommons, which has extracted structured data from Common Crawl annually since 2010, found markup on 51.25% of examined pages in its October 2024 release. When the project started, that figure was 5.7%.
Format has consolidated, too. Among sites that annotate anything at all, roughly 70% use JSON-LD. Microdata sits at 46% and is essentially flat year over year — the growth is entirely on the JSON-LD side.
The HTTP Archive’s 2024 Structured Data chapter measured it from the page rather than the domain and found JSON-LD on 41% of mobile pages, up from 34% in 2022. Microdata held steady at 26%.
Two things follow from those numbers.
First, if you are choosing a format in 2026, the decision is already made for you. JSON-LD is what Google recommends, what most sites use, and what decouples cleanly from your HTML so a template change does not silently break your markup.
Second, presence is no longer a differentiator. When half the web has schema, having some markup buys you nothing. What separates pages now is whether the markup is accurate, complete, and actually matched to visible content — which is the rule the next section covers, and the one most implementations break.
The AI angle nobody planned for
Schema was designed to earn rich results. Google has since pulled back several of those — FAQ and HowTo rich results were deprecated in 2023 — which led a lot of people to conclude the effort no longer pays.
That conclusion misreads what changed. Rich results were always one consumer of structured data, not the only one. Answer engines parse the same markup to work out what a page is, who published it, and how its claims are organised. Losing a SERP feature does not remove that.
Mark up your entities properly and you are describing yourself to every machine that reads the page, not just the one that used to draw a stars widget next to your listing.
Copy-paste JSON-LD: Organization
Place this in your site’s head or footer (adapt the values), so engines understand your brand as an entity:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Business Name",
"url": "https://yourdomain.com",
"logo": "https://yourdomain.com/logo.png",
"description": "What your business does",
"sameAs": [
"https://www.linkedin.com/company/yourbusiness",
"https://twitter.com/yourbusiness"
]
}
</script>Copy-paste JSON-LD: FAQPage
Use this on pages with a genuine FAQ section — and only where those questions and answers actually appear visibly on the page:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "Your question here?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Your answer here, matching the visible answer."
}
}]
}
</script>Add more question objects to the mainEntity array as needed. Every question and answer in the markup must appear visibly on the page.
The golden rule: markup must match content
The most important schema rule is that your structured data must accurately reflect the content visible on the page. Marking up content that isn’t there, adding FAQ schema for questions that don’t appear, or inflating ratings that aren’t genuine is against Google’s guidelines and can get your markup ignored or trigger a manual penalty. Schema describes your real content; it doesn’t invent content. Keep markup and visible content in sync, especially when you update pages.
Implementing and validating schema
On WordPress, an SEO plugin like Rank Math or Yoast generates common schema types automatically (Organization, Article, FAQ, breadcrumbs), which handles most needs without manual coding — a practical route for most sites. For custom needs, add JSON-LD directly to your templates. Whichever route you use, always validate: run pages through Google’s Rich Results Test and the schema.org validator to confirm the markup is correct and eligible for rich results, and check Search Console’s enhancement reports for errors. Validation catches the mistakes that silently stop schema from working.
Frequently asked questions
What is schema markup and does it help SEO?
Schema markup is structured data (best as JSON-LD) that tells search engines explicitly what your content is — an article, product, FAQ, organisation. It doesn’t directly raise rankings, but it makes your content eligible for rich results (star ratings, FAQ dropdowns, prices) that lift click-through. It also increasingly helps AI engines parse and trust your content, making it a worthwhile dual investment across search and AI answers.
What schema format should I use?
JSON-LD, which Google explicitly prefers. It’s a structured-data script placed in your page’s code, separate from the visible content, making it easier to implement and maintain than older inline microdata formats. All the common schema types — Organization, Article, FAQPage, Product, LocalBusiness — work in JSON-LD, and WordPress SEO plugins generate it automatically for most needs.
Can schema markup get me penalised?
Yes, if it’s misleading. Marking up content that isn’t visible on the page, adding FAQ schema for questions that don’t appear, or inflating ratings that aren’t genuine violates Google’s guidelines and can get your markup ignored or trigger a manual penalty. The golden rule is that markup must accurately reflect visible content. Used honestly to describe real content, schema is entirely safe and beneficial.
How do I add schema to a WordPress site?
The easiest route is an SEO plugin like Rank Math or Yoast, which generates common schema types (Organization, Article, FAQ, breadcrumbs) automatically, covering most sites’ needs without coding. For custom requirements, add JSON-LD directly to your templates. Either way, validate with Google’s Rich Results Test and check Search Console’s enhancement reports to confirm the markup is correct and eligible for rich results.
Sources
- WebDataCommons — Structured Data, October 2024 release
- HTTP Archive Web Almanac 2024 — Structured Data
The bottom line
Schema markup makes your content explicit to machines. It won’t lift rankings directly, but it unlocks the rich results that lift click-through and helps both search and AI engines understand and trust you. Use JSON-LD, add the types genuinely relevant to each page, keep the markup matching your visible content, and validate everything. On WordPress, a good SEO plugin handles most of it — leaving you to focus on the content the schema describes.
We implement and validate structured data across sites as part of our SEO services.
