Why JSON-LD schema still matters
JSON-LD schema is the simplest way to add structured data to a web page: a small block of JSON that tells search engines what a page is about, who published it and when. Google recommends JSON-LD for most sites, uses it to power rich results such as product, review and breadcrumb snippets, and reads it alongside your visible content. It won't guarantee rich results or AI citations, but clean, accurate markup removes ambiguity for every system that parses your pages.
Search benefits
- Eligibility for supported rich results, such as product, review, event and breadcrumb snippets
- Clearer signals about page type, author, publisher and dates
- More control over the logo and details Google shows for your organization
- Richer search listings that can attract more qualified clicks
- Error reporting in Search Console once Google detects your markup
AI search and crawler benefits
- Unambiguous facts (names, prices, dates) that any parser can read
- Consistent entity data that matches what users see on the page
- A solid technical foundation for AI search features, alongside good content
- No special AI markup needed: Google says standard SEO practices apply to AI Overviews
What is JSON-LD schema?
JSON-LD (JavaScript Object Notation for Linked Data) is a W3C format for expressing linked data in JSON. Combined with the schema.org vocabulary, it describes the things on your page (an article, a product, an organization) in a machine-readable way. Unlike Microdata or RDFa, which are woven into your HTML attributes, JSON-LD lives in its own <script type="application/ld+json"> tag, which Google accepts in either the <head> or the <body>.
Basic example
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "JSON-LD schema guide",
"author": {
"@type": "Person",
"name": "Jane Doe",
"url": "https://example.com/authors/jane-doe"
},
"datePublished": "2026-01-15T08:00:00+01:00"
}
</script>Advantages of JSON-LD
- Kept separate from your HTML markup
- Easy to read, generate and maintain
- No changes to your existing templates' HTML structure
- Multiple schema types can live on the same page
- The format Google recommends in most cases
- Can be injected server-side, by a CMS plugin or by your framework
Which rich results Google still shows
Google has retired several rich result types in recent years, so older JSON-LD guides often promise features that no longer exist. According to Google Search Central's documentation changelog: Google Search Central
- HowTo rich results were removed from desktop and mobile search in September 2023.
- FAQ rich results were limited to well-known government and health websites in 2023, then retired altogether in 2026.
- In 2025 Google phased out further types, including course info, estimated salary, learning video, special announcement and vehicle listing.
- Article, breadcrumb, organization, product, review snippet, event, recipe, video and software app markup remain supported.
Check Google's search gallery before investing in a new schema type, and treat any other rich result as a bonus rather than a promise.
Common schema types to use
Different content needs different markup. These types are the most useful for typical business, SaaS and publishing sites:
Article
For blog posts, news and editorial content. Google lists no required properties, but recommends headline, image, datePublished, dateModified and author (with a url).
Organization
Describes your company: name, url, logo and contact details. Google uses it to help choose the logo and details shown in results and knowledge panels.
Product
For products with price, availability and reviews. Enables product snippets and merchant listings when the required properties are present.
BreadcrumbList
Describes where a page sits in your site hierarchy. Needs at least two ListItem entries, each with position, name and item.
FAQPage
Still a valid schema.org type, but Google no longer shows FAQ rich results. Only add it if it genuinely describes a visible FAQ, and don't expect a search feature from it.
How to implement JSON-LD schema
You can add JSON-LD by hand, generate it in your framework's templates, or use a CMS plugin. The process is the same either way:
- 1
Choose the right schema type
Pick the type that matches the page's main content: Article for blog posts, Product for product pages, Organization for your homepage or about page.
- 2
Add the JSON-LD script tag
Add a <script type="application/ld+json"> block to the page's <head> or <body>. Use full ISO 8601 dates with a time zone and absolute URLs.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Article", "headline": "Your article title", "image": ["https://example.com/images/article-cover.jpg"], "datePublished": "2026-01-15T08:00:00+01:00", "dateModified": "2026-03-02T09:30:00+01:00", "author": { "@type": "Person", "name": "Author Name", "url": "https://example.com/authors/author-name" } } </script> - 3
Fill in required and recommended properties
Check Google's documentation for your type. Some types (like Product) have required properties for rich results; others (like Article) have only recommended ones. Every value must match what users can see on the page.
- 4
Test and monitor your markup
Validate with Google's Rich Results Test and the Schema Markup Validator, then watch Search Console's rich result reports for errors after you deploy.
JSON-LD best practices
Follow these guidelines to keep your structured data accurate and eligible:
Match visible content
Everything in your markup should be visible on the page. Markup that misleads users can lead to a manual action.
Start with recommended properties
Cover the properties Google documents for your type first, then add optional ones that genuinely describe the content.
Keep data current
Update dateModified, prices and availability whenever the page changes. Generate markup from the same data as the page where you can.
Don't mark up hidden content
Avoid describing content users can't see, or adding schema types that don't reflect the page.
Don't chase retired features
HowTo and FAQ markup no longer produce rich results in Google Search. Spend the effort on supported types.
Don't skip validation
A single syntax error (a trailing comma, an unescaped quote) invalidates the whole block. Test before every release.
JSON-LD and AI search
AI assistants and AI search features such as Google's AI Overviews and AI Mode draw on the same web pages as classic search. Google states there is no special schema.org markup required to appear in its AI features: the same SEO fundamentals apply. Structured data is still worth having because it states key facts explicitly.
What structured data can and can't do
JSON-LD doesn't guarantee that any AI system will cite you, and crawlers vary in how much of it they use. What it does is remove ambiguity about the basics:
- Clear page type, headline, author and publisher
- Machine-readable dates, prices and availability
- Consistent entity names that match your visible content
- Less guesswork for any parser that reads your HTML
Accurate facts
When your markup and visible content agree, systems that summarize your page have fewer chances to get dates, prices or authors wrong.
Consistent entities
Organization and author markup help tie your content to the same brand and people across your site.
Reusable data
Markup generated from your product or content database stays in sync with the page and works for any consumer that reads schema.org.
Low maintenance
Once templated, JSON-LD updates itself with your content, so it keeps paying off as search features change.
Additional resources for AI search visibility
Structured data is one part of preparing your content for AI-powered search. These tools can help with the rest:
Zero-Click.app: prepare your content for AI search
Semantic entity mapping to help protect against zero-click traffic loss and improve visibility in AI-powered search, including ChatGPT, Perplexity and Google's AI Overviews.
Visit zero-click.appJSON-LD schema FAQ
Is JSON-LD better than Microdata or RDFa?
Google supports all three, but recommends JSON-LD in most cases because it's the easiest to implement and maintain. It sits in its own script tag instead of being mixed into your HTML.
Does JSON-LD schema improve rankings?
Structured data isn't a direct ranking factor. It helps Google understand your pages and makes them eligible for rich results, which can improve how your listing looks and how many people click it.
Should I still add FAQPage or HowTo markup?
Google no longer shows HowTo rich results (since 2023) or FAQ rich results (since 2026). The markup is harmless if it matches visible content, but it won't earn a search feature.
Do I need special markup for AI Overviews?
No. Google says there's no special schema.org markup needed to appear in AI Overviews or AI Mode. Accurate, standard structured data and good content are what count.
Keep your pages healthy
Rich results only help when your pages are online and fast. Nanokoi checks uptime, SSL certificates and Lighthouse performance so crawlers and users always reach a working page.
Get started with JSON-LD schema
JSON-LD schema is a small investment with a lasting payoff: it makes your pages eligible for the rich results Google still supports and gives every crawler clear, accurate facts. Focus on supported types, keep markup in sync with your content, and test every release.
- Google recommends JSON-LD for structured data in most cases
- Structured data enables eligibility for rich results, not guaranteed placement
- HowTo and FAQ rich results are no longer shown in Google Search
- No special markup is needed for Google's AI features
- Validate with the Rich Results Test and monitor Search Console