Schema markup examples are ready-to-paste blocks of JSON-LD that tell Google what a page is about in a format a machine can read: a business with an address, a product with a price in rand, an article with an author. They sit inside your wider SEO in South Africa work as a supporting layer, not a ranking shortcut, and this page gives you five of them, localised for South African sites.
One correction before the code. Google's own documentation says you cannot mark up a page to win a featured snippet. What schema can do is make a page eligible for specific rich results, and that list has shrunk. If you want the concept first, our explainer on what schema markup is covers it; here we stay on working examples.
Quick Answer
The schema markup examples worth copying in 2026 are Organization, LocalBusiness, Product with an Offer, BlogPosting and BreadcrumbList, written as JSON-LD, which Google recommends in most cases. None of them guarantees a rich result, and none can force a featured snippet. FAQPage and HowTo no longer earn visible rich results in Google, so new markup of those types is wasted effort for search, while existing markup is harmless.
Not sure which of these your site already has?
Send us your homepage and one product or service page and we will tell you which markup is present, which is missing and which is wrong.
Do Schema Markup Examples Win Featured Snippets?
No: schema markup does not win featured snippets, because Google decides those itself and gives site owners no markup to request one. Google's featured snippets documentation answers the question directly: you can't, as "Google systems determine whether a page would make a good featured snippet for a user's search request, and if so, elevates it."
That page does not mention structured data at all. So a post promising "schema that wins snippets" is promising something Google does not offer. What markup does offer is eligibility for named, documented features such as a business knowledge panel, product details in a result, or a breadcrumb trail instead of a raw URL.
Key Takeaway
Schema is an eligibility layer, not a ranking lever. Google's introduction to structured data says you must include all required properties for an object to be eligible for enhanced display, which means even correct markup is an application, not a guarantee.
Which Structured Data Types Still Earn Anything in Google?
A structured data type earns something only if Google still documents a search feature for it, and the five types below do, while FAQPage and HowTo no longer show visible rich results. The table lists what each one can unlock and what Google requires, taken from Google's Search Central documentation.
| Type | What it can unlock | Google requires | Best for |
|---|---|---|---|
| Organization | Disambiguates your business; can influence logo and knowledge panel details | No required properties; add as many relevant ones as apply | Every site, on the home or about page |
| LocalBusiness | Knowledge panel with business details; carousel of businesses for type searches | name and address | Service firms, clinics, restaurants, shops with a physical location |
| Product (merchant listing) | Price, availability, shipping and returns in shopping experiences | name, image, offers with price and priceCurrency | Stores that sell the product on that page |
| Article / BlogPosting | Helps Google read author, dates and headline | No required properties; author, dates, headline, image recommended | Blogs and news pages |
| BreadcrumbList | Breadcrumb trail in the result (desktop) | itemListElement | Sites with a real category hierarchy |
| FAQPage | Nothing visible: Google's changelog says the FAQ rich result stopped appearing from 7 May 2026 | Documentation removed | Not worth adding for Google |
| HowTo | Nothing visible: Google stopped showing How-to rich results on desktop in September 2023 | n/a | Not worth adding for Google |
Google's 2023 announcement adds a useful detail for anyone with old markup: unused structured data does not cause problems for Search, it just has no visible effect. You can leave FAQ markup in place; you do not need to hunt it down. Our FAQ schema guide covers what is still worth doing with it.
How a South African Business Describes Itself in JSON-LD
Organization markup states who the business is, where it is and how to reach it, and Google's documentation says it helps disambiguate your organisation in search results. Google lists no required properties for this type, so the decision is how much accurate detail you are willing to publish.
Place it on the home page or about page, not on every page. The block below is JSON-LD; in WordPress it goes inside a script tag of type application/ld+json. Every value in these examples is a placeholder, so replace each one with your own details.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Hardware (Pty) Ltd",
"url": "https://www.example.co.za",
"logo": "https://www.example.co.za/images/logo.png",
"description": "Hardware and building supplies for Gauteng contractors.",
"telephone": "+27110000000",
"email": "info@example.co.za",
"address": {
"@type": "PostalAddress",
"streetAddress": "1 Example Street",
"addressLocality": "Johannesburg",
"addressRegion": "Gauteng",
"postalCode": "0000",
"addressCountry": "ZA"
},
"sameAs": [
"https://www.linkedin.com/company/example",
"https://www.facebook.com/example"
]
}Three South African details matter in organization schema markup examples. Write the phone number in international format with +27 and drop the leading zero. Use ZA as the country code. And put the registered trading name in name, matching what customers see on your site and Google Business Profile, since a mismatch undermines the point of disambiguation.
Local Business Pages: What Google Requires and a Working Block
Schema markup examples for local business pages use LocalBusiness markup, which describes a business with a physical location, and Google requires only name and address for it. It can produce a knowledge panel with business details, or a place in a carousel of businesses when someone searches for a business type.
Use the most specific schema.org subtype that fits, such as Plumber, Dentist or Restaurant, rather than the generic LocalBusiness. The recommended extras are opening hours, telephone, geo coordinates, price range and reviews. This example uses a plumber in Johannesburg:
{
"@context": "https://schema.org",
"@type": "Plumber",
"name": "Example Plumbing Johannesburg",
"url": "https://www.example.co.za/johannesburg/",
"telephone": "+27110000000",
"address": {
"@type": "PostalAddress",
"streetAddress": "1 Example Road",
"addressLocality": "Johannesburg",
"addressRegion": "Gauteng",
"postalCode": "0000",
"addressCountry": "ZA"
},
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "07:30",
"closes": "17:00"
}]
}Side note: service-area businesses
If you travel to customers and have no shopfront, do not publish a street address you do not operate from. Google's structured data policies say not to mark up content that is not visible to readers, so only mark up an address the page displays and the business operates from. Our local business schema guide and our Google Business Profile guide cover how to handle that case.
Your Google Business Profile and your on-page markup should agree on name, address and phone. Treat the profile as the source and copy from it, not the other way round.
Pricing a Product in Rand for Shopping Results
Product markup built around an Offer tells Google the name, image, price and currency of something a shopper can buy on that page, and for merchant listings Google requires all four. The currency must be a three-letter ISO 4217 code, so South African stores use ZAR, and the price must be greater than zero.
The commercial stakes are real. World Wide Worx forecasts that South Africans will spend about R159-billion online in 2026, with online retail reaching its first full year at 10% of national retail turnover. That is a forecast, not a measured result, but it explains why price and availability data matter to a store competing on shopping surfaces.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Cordless Drill 18V",
"image": "https://www.example.co.za/images/drill.jpg",
"description": "18V cordless drill with two batteries and charger.",
"sku": "DRILL-18V",
"offers": {
"@type": "Offer",
"url": "https://www.example.co.za/products/cordless-drill/",
"price": "1299.00",
"priceCurrency": "ZAR",
"availability": "https://schema.org/InStock"
}
}The price in these product schema markup examples is a placeholder. Google's structured data policies prohibit marking up content that is not visible to readers, so mark up the price shoppers see. Google's merchant listing documentation only asks for the current active offer price, above zero, and does not specify VAT treatment, so keep the markup consistent with how your page displays prices. Recommended additions are shippingDetails and hasMerchantReturnPolicy, which matter in a market where delivery cost and returns drive the buying decision.
One distinction saves a lot of confusion. Product snippets, which need a name plus at least one of review, aggregateRating or offers, suit review and aggregator pages. A store that sells the item wants merchant listing markup.
We unpack the difference in merchant listings versus product snippets, and the product schema guide goes deeper on the properties. If you run Shopify, check what your theme already outputs before adding a second block, because two sources writing Product markup for the same item can disagree. Our Shopify South Africa guide covers the platform side.
Product markup outputting twice?
Send us a product URL and we will review whether your theme, an app and a plugin are all writing competing markup.
Blog Posts and Breadcrumbs in JSON-LD
BlogPosting markup gives Google the headline, author and dates of a post, and BreadcrumbList describes where the page sits in your site. Article markup has no required properties, and BreadcrumbList requires only itemListElement, so both are cheap to get right.
For the post, Google recommends author, datePublished, dateModified, headline and image, and it accepts Article, NewsArticle or BlogPosting as the type. Dates in these JSON-LD schema examples use ISO 8601 with the South African offset +02:00:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Example: How to Choose a Cordless Drill",
"image": ["https://www.example.co.za/images/drill-guide.jpg"],
"datePublished": "2026-03-02T08:00:00+02:00",
"dateModified": "2026-03-09T09:20:00+02:00",
"author": [{
"@type": "Person",
"name": "Example Author",
"url": "https://www.example.co.za/about/example-author/"
}]
}Breadcrumbs follow the visible trail on the page. Google states the breadcrumb feature is available on desktop, so do not expect it on mobile results:
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.co.za/" },
{ "@type": "ListItem", "position": 2, "name": "Power Tools", "item": "https://www.example.co.za/power-tools/" },
{ "@type": "ListItem", "position": 3, "name": "Cordless Drills" }
]
}Key Takeaway
Pick the examples that match a feature Google still documents and a page that genuinely shows the same information. Organization, LocalBusiness, Product, BlogPosting and BreadcrumbList clear both tests; FAQPage and HowTo clear neither for Google today.
How to Test and Deploy JSON-LD Without Breaking Your Pages
Testing a JSON-LD block means validating it before and after it goes live, because a syntax slip or a missing required property can cost the page its eligibility. Google's introduction to structured data recommends the Rich Results Test during development and the rich result status reports after deployment.
The first step below is Google's recommendation. Steps two to four are our own working practice:
- Run the block through the Rich Results Test wherever it supports the type, and fix any errors on required properties.
- Run it through the Schema Markup Validator for general vocabulary checks, including types the Rich Results Test may not cover. It validates schema.org syntax; it does not say whether Google will show a rich result.
- Compare the markup with the visible page. Every name, price, hour and rating in the code should appear on the page.
- Deploy to one template first, then watch the rich result status reports in Search Console after Google recrawls.
For a wider check of the site around the markup, our DIY SEO audit in 60 minutes is a sensible companion.
On the penalty side, a structured data manual action means the page loses eligibility for rich results. Google's policy page says that action does not affect how the page ranks in web search. The cost of faked or hidden markup is lost features, not a ranking crash, but it is still a cost you caused yourself.
Markup is also not the only thing standing between a page and a rich result. If a page is blocked from crawling or indexing, the markup never gets read, so check noindex versus robots.txt first.
Why South African Businesses Choose Growth Pulse Media
Reviewing structured data is one small part of a wider search programme, and who does that review matters. Growth Pulse Media is a Johannesburg agency founded by Dirk van Greuning, who built and scaled a large South African ecommerce business before starting it. We are a Registered Shopify Partner and an Omnisend Certified Partner, all work is executed in-house, and we keep a limited client load so a senior person looks at your account.
Markup sits inside the broader SEO programme we run for South African sites, alongside technical fixes, content and local visibility. If you want a second opinion on whether your current structured data is worth keeping, a free audit through our contact page is the place to start, with no obligation.
Want a clear yes or no on your schema?
Share your site and we will tell you which markup is worth keeping, fixing or removing. No obligation, and we will get back to you within 24 hours.
Who This Is NOT For
This guide is not for anyone who expects markup to deliver a snippet or rich result, whose site has crawl problems, or who wants to mark up content the page does not show.
You expect markup to deliver a snippet or rich result. No markup can promise one. Google decides featured snippets itself, and rich results depend on eligibility, content and quality.
You are fixing a site that Google cannot crawl. Fix indexing and basic page quality first. Markup on a page Google cannot read has no chance of being used.
You plan to mark up content the page does not show. Invented reviews, hidden FAQs and ratings you do not display breach Google's policies and risk losing rich result eligibility.
Frequently Asked Questions About Structured Data
The short version: use JSON-LD, mark up only what the page shows, test before and after launch, and do not expect markup to buy a snippet.
What are schema markup examples I can copy?
The most useful schema markup examples to copy are Organization, LocalBusiness, Product with an Offer, BlogPosting and BreadcrumbList, all written in JSON-LD. Replace every placeholder with your real details and make sure each value also appears on the page.
Does schema markup help me win featured snippets?
No. Google's documentation says you cannot mark up a page to get a featured snippet, because its systems decide which pages to elevate. Schema can make a page eligible for rich results, which is a different feature.
Should I still add FAQ schema?
Not for Google. Google's changelog says the FAQ rich result stopped appearing from 7 May 2026, so new FAQ markup is wasted effort for search. Google has said unused structured data causes no harm but has no visible effect, so existing FAQ markup can stay. The FAQ block on this page is generated to match its visible questions; we do not claim it earns a Google rich result.
Which format should I use for structured data?
JSON-LD, in most cases. Google supports JSON-LD, Microdata and RDFa, and recommends the format that is easiest to implement and maintain, which it says is usually JSON-LD.
How do I test my schema markup?
Run each block through Google's Rich Results Test and the Schema Markup Validator, compare it with the visible page, then watch the Search Console reports after deployment. The Schema Markup Validator checks vocabulary, not Google eligibility.
Get Your Structured Data Reviewed
Send us your site and we will tell you plainly which markup earns its place and which should go. No obligation — we'll get back to you within 24 hours.

