What schema markup is, and why Google wants it in JSON-LD
On May 7, 2026, Google stopped showing FAQ rich results, and with them went advice this guide used to give. Schema markup is code that describes a page to search engines in a shared vocabulary: this is an article by this author, this is a law firm at this address. The vocabulary is Schema.org's. Google recommends writing it as JSON-LD, a block of JSON inside a script tag that sits apart from the visible HTML, because that is the easiest format to add and maintain.
The markup is the easy part. What it earns has changed a great deal. Since 2023 Google has retired HowTo and FAQ rich results, removed the sitelinks search box and phased out at least eight more structured data features, while AI Overviews and AI Mode arrived with Google saying they need no special markup at all. This October 2026 rewrite settles which rich results survive and which are gone, with Google's own announcements; gives JSON-LD examples checked against Google's required properties; explains testing; and says what schema does for AI search, where the evidence is thinner than most advice admits.
Schema.org was founded by Google, Microsoft, Yahoo and Yandex, and its vocabulary now runs to 826 types, of which Google uses a small fraction. JSON-LD is a W3C standard, last revised as JSON-LD 1.1 in July 2020. A minimal block:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Harbour & Finch LLP",
"url": "https://www.harbourfinch.example"
}
</script>@context names the vocabulary, @type the kind of thing described, and every other key is a property of that type. Harbour & Finch LLP, used throughout the examples, is this site's sample client, a Toronto employment law firm that does not exist. For the short definition, see our glossary entry on schema markup.
Google also supports Microdata and RDFa, which add attributes to the visible HTML tags. It calls all three "equally fine for Google, as long as the markup is valid and properly implemented," and favours JSON-LD because it "is not interleaved with the user-visible text." A redesign can then change every template without touching the markup. The script can sit in the head or the body, and Google reads blocks that JavaScript adds once they are in the rendered page.
Which rich results has Google retired?
Google has withdrawn more features since 2023 than many guides list as worth adding. The dates below come from Google's own announcements and its Search Central documentation changelog.
HowTo went first. Google's August 2023 post limited it to desktop, and an update to the post says "as of September 13, Google Search no longer shows How-to rich results on desktop" either. The same post restricted FAQ results to "well-known, authoritative government and health websites," and on May 8, 2026 Google's documentation said the feature "will no longer appear in Google Search starting May 7, 2026." Search Engine Roundtable reported Google's timeline for the tools: the FAQ report and Rich Results Test support were to go in June 2026, and Search Console API support in August.
None of this was a penalty. Google's June 2025 post said "This update won't affect how pages are ranked." Of leftover FAQ markup, Google's John Mueller said, in the same Roundtable report: "No need to change anything, but if you did it for search, you can remove the markup if you want." Markup that describes visible content does no harm. New FAQPage blocks written in the hope of a dropdown are wasted effort.
Which rich results does Google still show in 2026?
Google's search gallery lists 25 structured data features as of November 2026, and most belong to someone else. Recipe is for recipe sites and Job posting for employers. Vacation rental, Movie, Math solver, Education Q&A and Course list serve narrow verticals, Discussion forum, Q&A and Profile page suit community sites, and paywall markup is for publishers. Speakable is still a beta for English-language news publishers in the US. For an ordinary business, the useful part fits in one table:
| Page | Markup worth adding | What Google can do with it |
|---|---|---|
| Home page | Organization, or the most specific LocalBusiness type; WebSite | Logo in results and knowledge panels; the site name Google shows |
| Articles and guides | Article, BreadcrumbList | Better title text, images and dates; a breadcrumb trail on desktop |
| Product pages | Product with Offer; reviews only where real | Price, availability and ratings in product snippets and merchant listings |
| Location pages | LocalBusiness subtype | Knowledge panel details; carousels of businesses for category searches |
| Event pages | Event | Event listings, in supported countries |
| Video pages | VideoObject | Video results, key moments, a LIVE badge |
| App and software pages | SoftwareApplication | The software app rich result |
Article and Organization produce no dramatic visual, so they get dismissed. Yet Google says Article markup helps it "show better title text, images, and date information," the Organization logo property decides which logo appears in results and knowledge panels, and WebSite markup on the home page is, per its site names documentation, the main way to set the name Google shows for your site. The effects are small, but they apply to every result the site earns.
JSON-LD schema examples that still work
Each example was checked against the required and recommended properties on Google's page for that feature, linked in each section. Replace every value with your own, and never mark up anything a visitor cannot see.
Article
Google's Article documentation says "There are no required properties." It recommends author (with name and url), datePublished, dateModified, headline and image, with Person for a person and Organization for a company. Images should show the article's subject rather than a logo, and ideally come in 16x9, 4x3 and 1x1 versions.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How severance pay is calculated in Ontario",
"image": [
"https://www.harbourfinch.example/img/severance-16x9.jpg",
"https://www.harbourfinch.example/img/severance-4x3.jpg",
"https://www.harbourfinch.example/img/severance-1x1.jpg"
],
"datePublished": "2026-03-04T09:00:00-05:00",
"dateModified": "2026-10-14T11:30:00-04:00",
"author": {
"@type": "Person",
"name": "Sample Author",
"url": "https://www.harbourfinch.example/people/sample-author"
},
"publisher": {
"@type": "Organization",
"name": "Harbour & Finch LLP",
"url": "https://www.harbourfinch.example"
}
}Change dateModified when the content changes in a way a reader would notice. A date bumped on every deploy describes nothing.
Organization
Organization has no required properties either. Google recommends name, url, logo, sameAs, address, telephone and identifiers such as a tax ID, on the home page or a single page about the organization rather than on every page. The logo must be at least 112 by 112 pixels.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Harbour & Finch LLP",
"url": "https://www.harbourfinch.example",
"logo": "https://www.harbourfinch.example/img/logo-512.png",
"telephone": "+1-416-555-0142",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Street, Suite 1200",
"addressLocality": "Toronto",
"addressRegion": "ON",
"postalCode": "M5H 0A0",
"addressCountry": "CA"
}
}A one-office business is usually better served by a LocalBusiness subtype, shown below, which Google treats as a kind of Organization.
BreadcrumbList
Breadcrumb markup needs an itemListElement array of at least two ListItem entries, each pointing with item at the URL its crumb represents. The last entry can omit item, and Google then uses the page's own URL. Give every entry a position and a name, as Google's examples do. Since January 2025 breadcrumbs appear on desktop only; Google said they get truncated on small screens.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Guides",
"item": "https://www.harbourfinch.example/guides"
},
{
"@type": "ListItem",
"position": 2,
"name": "Severance",
"item": "https://www.harbourfinch.example/guides/severance"
},
{
"@type": "ListItem",
"position": 3,
"name": "How severance pay is calculated in Ontario"
}
]
}Product, with offers and reviews
Product is where structured data still pays most visibly, and where Google's rules are strictest. Product snippets, for review and comparison pages, need a name plus at least one of review, aggregateRating or offers. Merchant listings, for pages where a shopper can buy, need name, image and a single Offer with a price above zero and a three-letter priceCurrency. availability is recommended, not required, and Google accepts the full URL (https://schema.org/InStock) or the short name (InStock). A priceValidUntil date in the past can stop the listing showing. A law firm sells no products, so this example uses a placeholder shop:
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Walnut desk organiser, large",
"image": "https://shop.example/img/walnut-organiser.jpg",
"description": "Solid walnut desk organiser with five compartments.",
"sku": "WDO-L-01",
"brand": { "@type": "Brand", "name": "Example Woodworks" },
"offers": {
"@type": "Offer",
"url": "https://shop.example/walnut-organiser",
"price": 89.00,
"priceCurrency": "CAD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 4.6,
"reviewCount": 38
}
}Reviews are where sites get into trouble. The review snippet documentation requires ratingValue and either ratingCount or reviewCount; nested inside a product, as here, itemReviewed is left out, and the scale is assumed to run from 1 to 5. The numbers must come from reviews a visitor can read on the page. In July 2026 Google added the line "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup." Another rule catches service firms: if a business controls the reviews about itself, its LocalBusiness or Organization pages "are ineligible for star review feature," so a law firm marking up its own testimonials will not get stars. And if JavaScript adds product markup, Google warns this "can make Shopping crawls less frequent and less reliable."
LocalBusiness
LocalBusiness needs only name and address. Google recommends geo to at least five decimal places, openingHoursSpecification, telephone and a url for the specific location, and asks for the most specific subtype; for a law firm that is LegalService. Markup is a small part of local search, and our local SEO guide covers the Business Profile side.
{
"@context": "https://schema.org",
"@type": "LegalService",
"name": "Harbour & Finch LLP",
"url": "https://www.harbourfinch.example/toronto",
"telephone": "+1-416-555-0142",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Street, Suite 1200",
"addressLocality": "Toronto",
"addressRegion": "ON",
"postalCode": "M5H 0A0",
"addressCountry": "CA"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 43.64871,
"longitude": -79.38173
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "09:00:00",
"closes": "17:30:00"
}
]
}Event
Event needs name, startDate and a location with a postal address. Only physical events qualify: "Virtual experiences that have no real-world component aren't supported," the documentation says, after online event properties were dropped in June 2025. Event results run in a limited set of countries, among them the US, UK, Canada, Australia, India, Germany, Spain and Brazil. Include the venue's timezone offset in dates. If an event is cancelled or moved, change eventStatus and keep the original startDate, which Google says helps it identify the event.
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Severance offers: a free evening session for employees",
"startDate": "2026-11-19T18:00:00-05:00",
"endDate": "2026-11-19T19:30:00-05:00",
"eventStatus": "https://schema.org/EventScheduled",
"location": {
"@type": "Place",
"name": "Harbour & Finch LLP, Toronto office",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Street, Suite 1200",
"addressLocality": "Toronto",
"addressRegion": "ON",
"postalCode": "M5H 0A0",
"addressCountry": "CA"
}
},
"organizer": {
"@type": "Organization",
"name": "Harbour & Finch LLP",
"url": "https://www.harbourfinch.example"
},
"offers": {
"@type": "Offer",
"url": "https://www.harbourfinch.example/events/severance-session",
"price": 0,
"priceCurrency": "CAD",
"availability": "https://schema.org/InStock"
}
}VideoObject
VideoObject needs name, thumbnailUrl and uploadDate. Google recommends contentUrl (the file itself, preferred over embedUrl), description, duration and, since a September 2026 update, creator, "The person or organization that created or published the video." Give uploadDate a timezone, or Google uses Googlebot's. Key moments and LIVE badges take extra properties, covered in our video SEO guide.
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "What to do in the first week after a termination",
"description": "A four-minute walkthrough of the documents to keep and the deadlines to watch after losing a job in Ontario.",
"thumbnailUrl": "https://www.harbourfinch.example/video/first-week-thumb.jpg",
"uploadDate": "2026-09-15T09:00:00-04:00",
"duration": "PT4M12S",
"contentUrl": "https://www.harbourfinch.example/video/first-week.mp4",
"embedUrl": "https://www.harbourfinch.example/embed/first-week",
"creator": {
"@type": "Organization",
"name": "Harbour & Finch LLP",
"url": "https://www.harbourfinch.example"
}
}The rest of the gallery works the same way: each feature has a page of required and recommended properties, and the Rich Results Test checks them. A page can carry several blocks, as separate script tags or one block with an @graph array, provided each describes something on that page.
How do you generate schema markup, including Article schema?
Most sites never write JSON-LD by hand. Themes and SEO plugins often add Article, Product or Organization blocks on their own, so find out what is already there before adding more.
For one-off pages, our free schema markup generator builds Article, Organization, BreadcrumbList, LocalBusiness and Product blocks from a form. Like any generator, it knows only what you type, so the output still needs testing.
On a site built from code, build the JSON-LD from the same data that renders the page. In Next.js that is a schema object beside the page's metadata, printed as a script tag:
const articleSchema = {
'@context': 'https://schema.org',
'@type': 'Article',
headline: post.title,
datePublished: post.publishedAt,
dateModified: post.updatedAt,
author: { '@type': 'Person', name: post.author.name, url: post.author.url },
image: [post.image],
}
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(articleSchema) }}
/>The headline cannot then drift from the title. The same logic sits behind Google's caution about Tag Manager, where copying page values into tags "increases the risk of having a mismatch." Language models, Claude and Gemini among them, draft passable JSON-LD from a page's text, and can also add a property that does not exist or a rating the page never shows. Treat their output like a generator's: a draft to test.
How do you test schema markup?
Google's Rich Results Test is the check that matters for Google features. Its help page says it takes a URL or a pasted snippet, tests as a smartphone by default, reads all three formats and reports the rich result types it finds, with errors. Use the URL input when JavaScript builds the markup, as Google recommends, because pasted code cannot show what the rendered page contains.
The Schema Markup Validator covers the rest. Google handed its old Structured Data Testing Tool to the Schema.org community in 2021, and its announcement explains the split: the validator checks syntax and Schema.org compliance, including types Google does not use, while the Rich Results Test and Search Console handle Google eligibility. A block can pass one and fail the other, and both results are correct.
After launch, Search Console takes over. Its rich result status reports sit under Enhancements, with product snippets and merchant listings under Shopping, and appear only once Google finds valid markup of a supported type. They count items, not pages: an item with a critical issue is invalid and cannot appear as a rich result, while non-critical issues are listed as ways to improve it. The reports show samples, so use URL Inspection to confirm Google found the markup on a given page.
Structured data checks belong in every technical SEO audit, because markup that validated at launch drifts as templates and plugins change.
What are the most common schema markup errors?
The most damaging is markup that does not match the page. Google's structured data guidelines say "Don't mark up content that is not visible to readers of the page" and rule out "irrelevant or misleading content, such as fake reviews." Breaking them can bring a manual action that removes rich result eligibility. The cause is usually mundane: a price changed on the page but not in the markup, or a template copied one product's rating onto another.
Missing required properties make an item invalid: a Product with no offers, review or rating, an Event with no address, a video with no thumbnail. They often come from an empty CMS field printed as an empty string, so check the data before the template renders it.
Formats trip people up next. Dates and durations follow ISO 8601 (2026-11-19T18:00:00-05:00, not "November 19"; PT4M12S, not "4:12"), and availability must be a Schema.org value, so "in stock" fails. Google will not show a priceRange of 100 characters or more. JSON has no comments, and although the Rich Results Test ignores them, Google warns they can cause errors in real use.
Stale data quietly removes eligibility, as with an expired priceValidUntil. Duplicate blocks are easy to miss, typically a theme and a plugin each printing an Organization or Product block with different values; search the rendered HTML for application/ld+json and count. The last common error is star markup on reviews of your own business, which cannot earn stars whatever the markup says.
Is schema markup a ranking factor?
No, and Google has said so in as many words. In an April 2025 Bluesky post reported by Search Engine Roundtable, John Mueller wrote: "Structured data won't make your site rank better." He added that it is used to display the search features in Google's documentation. Google's guidelines say a structured data manual action "doesn't affect how the page ranks in Google web search," and that Google "does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test."
That does not make it pointless. Google says it uses structured data "to understand the content of the page," and a rich result changes how a listing looks at the position it already holds. Whether that changes clicks is something to measure on your own pages: Search Console's performance report filters by search appearance, and the honest comparison is the same pages before and after, against similar pages you left alone.
Is schema markup enough for AI search optimization?
For Google's AI features it is neither enough nor required. Google's page on AI features and your website says "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary," and "There's also no special schema.org structured data that you need to add." A supporting link must be "indexed and eligible to be shown in Google Search with a snippet." What still applies is ordinary SEO: crawling allowed in robots.txt and by any CDN, important content available as text, internal links, and "Making sure your structured data matches the visible text on the page."
Microsoft is warmer. Its October 2025 guidance on AI search answers says "Schema is a type of code that helps search engines and AI systems understand your content," and advises schema alongside clear headings and modular layouts. That describes how its systems read pages, with no promise about citations.
The best public test of whether markup changes citations found no lift. Ahrefs tracked 1,885 pages that added JSON-LD between August 2025 and March 2026 against matched pages that did not, over 30 days either side. Relative to those controls, AI Mode citations moved +2.4% and ChatGPT citations +2.2%, both statistically indistinguishable from zero, and AI Overview citations fell 4.6%, a drop the authors call real but unexplained. Their summary: "Adding schema produced no major uplift in citations on any platform."
The authors spell out the limits. Every page was already heavily cited, with more than 100 AI Overview citations in February 2025, so the study says little about pages AI systems ignore. It pooled all schema types, measured 30 days and could not fully separate schema from other changes. The raw correlation it began with, that AI-cited pages carry schema more often, is confounded, since sites that bother with schema tend to do the rest of their SEO well. The fair reading: evidence for an AI citation effect is thin, and the best controlled evidence finds none.
So write schema for the Google features it earns and the understanding Google says it supports, and do not expect it to move AI answers alone. To know whether any change moved them, run the same prompts before and after, enough times to know the margin of error, and compare with pages you did not touch. AIO Copilot's AI visibility report runs that sampling through the models' APIs, counting how often assistants name a client against its rivals, with the margin of error shown. For what Google's AI answers do draw on, see how Google's AI answers choose their sources.
What should you change on an existing site?
- Inventory what the site prints today: run each main template through the Rich Results Test and search the rendered HTML for
application/ld+json. - Leave FAQPage and HowTo blocks where they describe visible content, delete them where they existed only for the dropdown, and stop writing new ones for search.
- Put Organization, or a LocalBusiness subtype, on the home page with a logo, plus a WebSite block with the name you want shown.
- Fill required and recommended properties on Product, Event, VideoObject and Article from the data that renders each page.
- Remove ratings the page does not show, and star markup on reviews of your own business.
- Check the Search Console reports monthly and after every template change.
The FAQ dropdown was always a display feature Google could withdraw, and in May it did. What survives is the plainer job schema was built for: stating what a page is in terms a machine does not have to guess at. Done that way, it keeps earning the features Google still shows, and it costs nothing when the next one goes.
Questions
What is JSON-LD schema markup?
JSON-LD schema markup is structured data written in JSON-LD, a W3C format for linked data, using the Schema.org vocabulary. It sits in a script tag of type application/ld+json in the head or body of a page and describes what the page contains, such as an article, a product, an event or a business. Google supports JSON-LD, Microdata and RDFa, and recommends JSON-LD where a site can use it.
Does Google still show FAQ rich results?
No. Google limited FAQ rich results to well-known government and health sites in August 2023 and stopped showing them for every site from May 7, 2026. It removed the FAQ documentation on June 15, 2026. FAQPage markup that describes visible questions does no harm, but it no longer produces a rich result.
Should I remove old FAQPage and HowTo markup?
You do not have to. Google's John Mueller said of FAQ markup: "No need to change anything, but if you did it for search, you can remove the markup if you want." Remove it where it describes content that is not on the page, and do not add new blocks expecting a rich result.
Which properties does Article schema require?
None. Google lists no required properties for Article and recommends author (with name and url), datePublished, dateModified, headline and image. Use Person for an individual author and Organization for a company.
Is schema markup a ranking factor?
No. Google's John Mueller wrote in April 2025 that "Structured data won't make your site rank better." Google uses structured data to understand pages and to display the rich results listed in its search gallery, and it does not guarantee that valid markup will produce one.
Does schema markup help with AI Overviews or ChatGPT citations?
Google says there is no special schema.org structured data needed to appear in AI Overviews or AI Mode. Microsoft says schema helps search engines and AI systems understand content. The largest controlled test, published by Ahrefs in May 2026, found no clear rise in citations on AI Mode or ChatGPT after pages added JSON-LD, and a small unexplained fall on AI Overviews.
Where should JSON-LD go, in the head or the body?
Either. Google describes JSON-LD as a script tag in the head or body of the page, and it reads markup that JavaScript adds as long as it is in the rendered page. For Product markup, Google warns that JavaScript-generated markup can make Shopping crawls less frequent and less reliable, so render it on the server where you can.
New studies, by email
Our own studies, and what each new release changes for SEO, AEO and Google Ads.
