JSON LD to Microdata Converter for Schema.org Markup

Structured data can live in a page in more than one format, and sometimes a theme, template, or older system insists on Microdata embedded in the HTML rather than a JSON-LD script block. The JSON-LD to Microdata Converter takes your existing Schema.org JSON-LD and rewrites it as HTML Microdata, so the same facts about your page can be carried in the markup itself without you re-typing every property by hand.

The Difference Between the Two Formats

JSON-LD keeps structured data in a separate script element: tidy, centralised, and easy to generate from a database, which is why it became the format most tools produce first. Microdata takes the opposite approach, weaving attributes such as itemscope, itemtype, and itemprop directly into the visible HTML elements that present the content. A product's name and price are not repeated in a script; the actual heading and price elements carry the annotations. Search engines can read both formats, so the choice usually comes down to what your platform supports and how your team prefers to maintain the page.

Conversion is a translation exercise. Each type in the JSON-LD becomes an itemscope with the corresponding Schema.org itemtype, each property becomes an itemprop on a suitable element, and nested objects become nested items. Doing that translation manually for a recipe, product, or event with dozens of properties is slow and error-prone, which is the tedium this converter absorbs. For the return journey, our Microdata to JSON-LD converter performs the opposite transformation, and our Schema Generator helps you build the underlying markup from scratch.

What the Converter Handles for You

• Types become items: each Schema.org type in your JSON-LD becomes an itemscope carrying the matching itemtype.
• Properties become itemprops placed on suitable HTML elements, ready to align with the visible content they describe.
• Nested objects become nested items, preserving structures such as an author inside an article.
• Repeated values stay repeated, expressed as multiple elements rather than a single collapsed field.
• Your facts stay identical: the vocabulary and values are unchanged, only their physical arrangement in the page moves.

How to Convert JSON-LD to Microdata

1. Prepare the Schema.org JSON-LD you want to convert, checking it is complete and valid before you begin; our JSON-LD Validator can confirm the source is clean.
2. Paste the JSON-LD into the input area on this page.
3. Click Convert to Microdata and review the generated HTML Microdata.
4. Integrate the generated markup into your page, aligning the itemprop attributes with the visible elements that display the same information.
5. Test the finished page with a structured data testing tool to confirm the properties are detected as intended.

A Worked Example: One Article, Two Markups

Take a simple news article described in JSON-LD with three facts: a headline, a publication date, and an author who is a person with a name. In the JSON-LD version, those facts live together in a script block as "headline", "datePublished", and an "author" object with its own "@type" of Person and a "name". Converted to Microdata, each fact moves onto the HTML element that already displays it. The article's container gains itemscope and an itemtype pointing to the Schema.org Article type; the visible heading element carries itemprop="headline"; the time element carries itemprop="datePublished"; and the byline area becomes a nested item of its own, marked as a Person whose name span carries itemprop="name". The information content is identical, the same vocabulary and the same values, but its physical arrangement changes completely, from a self-contained data block to attributes threaded through markup that must actually exist on the page. This pattern is exactly why teams inheriting an older site standardise on the format their templates already speak, and why Microdata appeals when the visible content and the structured data must never drift apart: because the annotations sit on the displayed elements themselves, editing the shown price necessarily edits the marked-up price.

Details That Need Care During Conversion

Three situations deserve a second look after any conversion. First, repeated values: where JSON-LD holds a list, such as several images or authors, Microdata expresses the list as repeated elements, one per value, and dropping the repetitions silently loses data. Second, invisible values: some properties describe things the page does not print, such as a publisher's logo or an internal identifier, and Microdata handles those with meta or link elements placed inside the item's scope, which are easy to overlook when tidying the HTML later. Third, formatting stays literal: dates, URLs, and durations must keep the same machine-readable values they had in JSON-LD, even if the visible text around them is written for humans, as with a date displayed as "last Tuesday" whose attribute carries the full ISO value. Avoid serving the same structured data in both formats on one page unless you are certain they agree exactly, because conflicting duplicates confuse parsers more than a single clean implementation. Plan the work at the template level rather than page by page, since most sites generate many pages from a handful of layouts, and keep the original JSON-LD stored in your project files so the conversion can be repeated if the data changes.

JSON-LD to Microdata Questions, Answered

Do search engines prefer JSON-LD or Microdata?

Search engines accept both, along with RDFa. Google has generally recommended JSON-LD for ease of implementation, but Microdata that correctly describes the page is read and used as well. Correctness and agreement with visible content matter more than the format chosen.

Can every JSON-LD property become Microdata?

Schema.org types and properties have Microdata equivalents in the great majority of cases, because both formats express the same vocabulary. Unusual or deeply nested structures deserve a manual review after conversion to confirm nothing was simplified away.

Should I keep the JSON-LD block after converting?

Usually you would serve one format per page to avoid duplication. Keep the JSON-LD in your source files as the editable original, publish the Microdata in the page, and make sure any future edits update both copies of the information.

Does Microdata have to sit on the exact text it describes?

Generally, yes. An itemprop belongs on the element whose content is the value, the heading for a headline, the time element for a date. When no visible element holds the value, a meta or link element inside the item's scope carries it instead.

Same Facts, Carried Where Your Templates Want Them

Neither format is more truthful than the other; they simply store the same Schema.org facts in different places. When your platform speaks Microdata, converting preserves the work already invested in carefully written JSON-LD instead of discarding it. Convert at the template level, review the nested and repeated properties once, and validate the finished pages rather than assuming the translation landed cleanly.