JSON-LD

JavaScript Object Notation for Linked Data — the format Google recommends for adding structured data to a page. Instead of weaving markup into your visible HTML the way older formats (Microdata, RDFa) did, JSON-LD sits in a single self-contained script block, usually in the page head, describing the page's content in a form machines parse directly: this is a Product, its name is X, its price is Y, it's in stock. The separation is the whole point. Because JSON-LD lives apart from the rendered HTML, a theme redesign can't silently shred your markup the way it shreds inline Microdata attributes, one block can describe the entire entity in one place instead of scattering properties across dozens of tags, and adding a new schema type means adding a block — not rebuilding a template. Google has recommended JSON-LD over the alternatives for years, and every rich result that matters to a store — product stars, prices, availability, FAQs, breadcrumbs — is typically delivered through it. What we find when we audit stores: platforms and plugins each injecting their own JSON-LD, so a product page carries two or three conflicting Product blocks with different prices; syntax errors — a trailing comma, an unclosed brace — that invalidate an entire block silently, because broken JSON-LD renders as nothing rather than as a visible error; markup describing content that isn't on the page, which violates Google's guidelines; and required fields missing, so the block parses cleanly but earns no rich result. Our team consolidates the competing blocks into one correct source of truth per page, validates against Google's Rich Results Test, and fixes the markup at the template level so every page of a given type inherits clean structured data.