{"id":96,"date":"2026-08-28T21:23:01","date_gmt":"2026-08-28T21:23:01","guid":{"rendered":"https:\/\/seoedgeai.com\/blog\/json-ld-structured-data-2026\/"},"modified":"2026-08-28T21:23:23","modified_gmt":"2026-08-28T21:23:23","slug":"json-ld-structured-data-2026","status":"publish","type":"post","link":"https:\/\/seoedgeai.com\/blog\/json-ld-structured-data-2026\/","title":{"rendered":"JSON-LD Structured Data: A Complete Guide for 2026"},"content":{"rendered":"

JSON-LD (JavaScript Object Notation for Linked Data) is the small block of markup you put in your page’s HTML to tell Google what that page is: a blog post, a product with a price and a currency, an event on a date, the company behind the site. It is Google’s recommended structured-data format, and it is often the difference between a flat blue link and a rich result with a price, a star rating, a video thumbnail or a breadcrumb trail. Here is what to add in 2026, the exact JSON-LD to copy, how to test it, the errors that break it, and how to keep it correct on a site with thousands of pages.<\/p>\n

What JSON-LD is and why Google reads it<\/h2>\n

Google describes structured data as “a standardized format for providing information about a page and classifying the page content”. JSON-LD is one of three formats Google accepts, alongside Microdata and RDFa<\/a>, and the one it recommends: a single <script type=\"application\/ld+json\"><\/code> block, kept apart from the visible text, so nested values (the country inside an address inside a venue) stay easy to express. Every block opens with \"@context\": \"https:\/\/schema.org\"<\/code> for the vocabulary and \"@type\"<\/code> for what the page is, followed by the properties.<\/p>\n

Google uses that markup for two things: to understand the individual page, and to gather information about the web in general, “such as information about the people, books, or companies that are included in the markup”. That second part is why one Organization block on your homepage feeds the knowledge panel next to your name.<\/p>\n

The payoff is measurable, and Google’s own case studies<\/a> make the case: Rotten Tomatoes marked up 100,000 pages and measured a 25% higher click-through rate, Nestl\u00e9 pages that appear as rich results see 82% higher CTR than pages that do not, and the Food Network converted 80% of its pages to search features and saw a 35% increase in visits.<\/p>\n

\"A
A smartphone showing the Google search page. Credit: Pexels License, via Pexels<\/figcaption><\/figure>\n

What changed in 2026: the types that are still worth it<\/h2>\n

Before you write markup, know which Google features still exist. Google’s documentation changelog<\/a> is blunt on three of them:<\/p>\n

    \n
  • FAQ rich results are dead.<\/strong> Google added a deprecation notice on May 8, 2026, stating the FAQ rich result would no longer appear in Search starting May 7, 2026, and removed the documentation the following month. FAQPage markup still validates as schema.org, but do not build it expecting a Google feature.<\/li>\n
  • HowTo rich results are gone.<\/strong> Google removed the How-to documentation in 2023, noting the rich result “is no longer shown in search results, on both desktop and mobile devices”. HowTo markup is not worth maintaining for Google today.<\/li>\n
  • Breadcrumbs narrowed.<\/strong> The current breadcrumb documentation<\/a> states the feature is available on desktop only.<\/li>\n<\/ul>\n

    One thing has not been replaced by AI: Google’s generative AI features (AI Overviews and AI Mode) are built on the same core ranking and quality systems, retrieving pages through search. And Google has explicitly debunked the idea that AI needs new markup: “Structured data isn’t required for generative AI search, and there’s no special schema.org markup you need to add”, per its official AI optimization guide<\/a>. Keep using JSON-LD because it earns rich-result eligibility, not because an LLM asked for it.<\/p>\n

    Serpstat’s two-minute primer covers exactly this: what JSON-LD is, why it produces those eye-catching rich results, and how to implement it.<\/p>\n