Title: Microdata to JSON-LD Converter
Author: Seth Smigelski
Published: 2025-يىلى 28-ئىيۇل
Last modified: 2026-يىلى 17-ئاپرېل
---
قىستۇرما ئىزدە
# Microdata to JSON-LD Converter
يازغۇچى [Seth Smigelski](https://profiles.wordpress.org/sethsm/)
[چۈشۈر](https://downloads.wordpress.org/plugin/microdata-to-json-ld-converter.1.8.3.zip)
* [تەپسىلاتلار](https://ug.wordpress.org/plugins/microdata-to-json-ld-converter/#description)
* [باھالاشلار](https://ug.wordpress.org/plugins/microdata-to-json-ld-converter/#reviews)
* [ئورنىتىش](https://ug.wordpress.org/plugins/microdata-to-json-ld-converter/#installation)
* [ئىجادىيەت](https://ug.wordpress.org/plugins/microdata-to-json-ld-converter/#developers)
[قوللاش](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/)
## چۈشەندۈرۈش
Is your WordPress theme or website built with inline Schema.org Microdata? As search
engines increasingly prefer the JSON-LD format for structured data, updating your
site can be a significant challenge. Manually removing old Microdata and creating
new JSON-LD scripts for every page is tedious and error-prone.
The **Microdata to JSON-LD Converter** solves this exact problem. This plugin seamlessly
automates the entire conversion process:
1. **Scans Your Pages:** It fetches the full HTML of your published posts and pages,
ensuring it captures all Microdata, whether it’s in your post content or your theme
files (like `header.php`).
2. **Converts to JSON-LD:** It intelligently parses the `itemscope`, `itemtype`, and`
itemprop` attributes and converts them into a well-structured JSON-LD script.
3. **Removes Inline Microdata:** Optionally, it can clean up your public-facing HTML
by removing the now-redundant Microdata attributes, leaving only the clean JSON-
LD script in the ``.
4. **Keeps It Fresh:** With the «Keep up to date» option, the plugin can automatically
regenerate the JSON-LD every time you update a post, ensuring your structured data
always reflects your latest content.
**Key Features:**
* **Full Page Parsing:** Accurately reads Microdata from the entire webpage, not
just post content.
* **Automatic Generation:** Automatically creates the initial JSON-LD when you
open a published post for the first time.
* **Manual Control:** View and edit the generated JSON-LD directly in a meta box
on each post’s edit screen.
* **Built-in Validator:** Get instant feedback on your schema with a built-in validator
that checks for common required and recommended properties.
* **Bulk Rebuild Tool:** Process your entire site at once with a batch-processing
tool that works through all your posts and pages.
* **«Set It and Forget It» Mode:** Enable the «Keep JSON-LD up to date» option
to ensure your structured data remains current.
* **Clean & Modern UI:** A simple, intuitive settings page with toggle switches
and tabs makes configuration a breeze.
* **Homepage WebSite Schema:** Automatically generates WebSite JSON-LD for your
homepage, complete with a Sitelinks Search Box to improve your site’s search
presence.
* **Dynamic Archive Schema:** Automatically constructs lightweight CollectionPage
and ItemList JSON-LD schema for Category and Tag pages, matching Google’s exact
specifications for list data without slowing down your server.
This plugin offers a seamless migration path to modernize your site’s SEO and structured
data implementation, eliminating the need to edit your content, plugins, or theme
files.
## ئېكران كەسمىسى
* [[
* The clean, tabbed settings page for Microdata to JSON-LD Converter showing the
modern toggle switches for the main options.
* [[
* The «Bulk Rebuild Tools» tab, showing the post type selection and progress bar.
* [[
* The meta box in the post editor, showing the generated JSON-LD.
* [[
* The meta box’s validation results after clicking the «Validate» button.
## ئورنىتىش
1. Upload the `microdata-to-json-ld-converter` folder to the `/wp-content/plugins/`
directory.
2. Activate the plugin through the ›Plugins‹ menu in WordPress.
3. Navigate to `Settings > Microdata to JSON-LD` to configure the plugin.
4. Enable the desired options, such as «Enable JSON-LD Output» and «Remove Inline
Microdata from HTML».
5. Optionally, use the «Bulk Rebuild Tools» tab to process all your existing content.
## FAQ
### How do I generate the JSON-LD for my posts?
You have two main options:
1. **Automatically:** For a single post, simply open
the post editor. If the post is published and no JSON-LD exists, the plugin will
automatically generate it. For all posts, use the «Bulk Rebuild Tools» on the plugin’s
settings page. 2. **Manually:** In the post editor, you can click the «Regenerate»
button inside the «Schema.org JSON-LD» meta box at any time.
### What does the «Keep JSON-LD up to date» option do?
When this option is enabled, the plugin will automatically regenerate the JSON-LD
every single time you click «Update» on a post. This ensures your structured data
always matches your content, but it will overwrite any manual changes you’ve made
in the JSON-LD text box. If you plan to manually edit your JSON-LD, you should leave
this option turned off.
### Will this remove Microdata from my theme files?
The «Remove Inline Microdata from HTML» option removes the Microdata attributes
from the final HTML that is sent to the user’s browser. It does **not** edit or
delete your actual PHP theme files. The original Microdata will still be in your
files, but it will be invisible on the front end.
### Does the ›Remove Inline Microdata‹ feature work with caching?
The «Remove Inline Microdata from HTML» option works by capturing the entire page
output after it has been generated and before it is sent to the browser. This method,
while effective, may prevent some server-side caching systems (like Varnish or NGINX
FastCGI Cache) from serving cached pages. This is because the output buffer signals
that the content is being dynamically modified. If you are on a managed WordPress
host that utilizes this type of caching, you should test this feature to ensure
there are no conflicts. Alternatively, you can keep it disabled if you notice issues
with your site’s cache.
### Can I check if my generated JSON-LD is valid?
Yes. In the «Schema.org JSON-LD» meta box, you have two options. The «Validate»
button runs a check against a built-in list of best practices for common schema
types. For a complete, official analysis, use the «Test on Google» button to open
the page in Google’s Rich Results Test.
### How do I disable the automatically generated WebSite schema on my homepage?
The plugin automatically detects major SEO plugins (like Yoast, AIOSEO, and Rank
Math) and safely disables its own WebSite schema to prevent duplicates. However,
if you are manually injecting your own custom script and need to disable the plugin’s
output, you can do so by adding this single line to your theme’s functions.php file:
```
add_filter( 'mdtj_output_website_schema', '__return_false' );
```
### How is this plugin connected to the Microdata Refinement Department at LUMON?
This plugin bears no relation whatsoever to LUMON or the MDR Department on the Severed
Floor. The «Microdata» processed by this plugin is a structured data markup outlined
by schema.org, which has fallen out of favor and has largely been replaced by the
JSON-LD format (hence, why this converter exists).
### What is the recommended implementation of this plugin?
Use the Microdata to JSON-LD Converter in 5 easy steps.
1) Open the post editor, scroll down to the box titled «Schema.org JSON-LD.» Verify
that the created JSON-LD matches your existing schema.org content.
2) After you have reviewed the «Schema.org JSON-LD» meta boxes on multiple posts
and pages, use the Bulk Rebuild Tools to create JSON-LD meta for each post and page
on your website. This build process will take several minutes for larger sites.
3) Within the General Settings of the Microdata to JSON-LD Settings, toggle on «
Enable JSON-LD Output.» Doing this will add the JSON-LD to the head element of your
webpages. The content within the «Schema.org JSON-LD» meta boxes is now being added
to your published posts and pages.
4) Within the General Settings of the Microdata to JSON-LD Settings, toggle on «
Remove Inline Microdata from HTML.» Doing this will strip the Microdata from the
HTML output of your webpages. Although this plugin removes the inline Microdata
attributes from the final public-facing HTML, it will not affect your backend theme
files, plugins, and content where the Microdata markups originate.
Note: To ensure that the inline Microdata does not serve as a duplicate of the new
JSON-LD, both «Enable JSON-LD Output» and «Remove Inline Microdata from HTML» should
be enabled in unison.
5) To keep your JSON-LD updated going forward, toggle the option «keep JSON-LD up
to date.» This will ensure that your post’s JSON-LD information is updated when
you make changes to your posts and pages. If you have, or plan to, make manual edits
within the JSON-LD meta boxes, keep this option turned off. However, in most cases,
it will be helpful to automate keeping the JSON-LD up to date.
## باھالاشلار
### [This Modernized My Schema.org Structured Data](https://wordpress.org/support/topic/this-modernized-my-schema-org-structured-data/)
[hikespeak](https://profiles.wordpress.org/hikespeak/) 2025-يىلى 11-سېنتەبىر
I have been using this plugin for a couple month and it does the job its supposed
to – not available from any other plugin. With this plugin, my existing structured
data, starting as Inline microdata, gets converted on published webpages to to the
JSON-LD format that search engines and LLMs prefer. The plugin is simple to implement,
previews JSON clearly, has flexible options, and is easy to use. This is a great
tool for displaying JSON schema, whether you aim to transition away from the microdata
format or stick with it on the back end. There’s not much to do once the plugin
is setup. It just works!
[ 0 باھالاشنىڭ ھەممىنى ئوقۇش ](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/)
## تۆھپىكار ۋە ئىجادكار
«Microdata to JSON-LD Converter» كودى ئوچۇق يۇمشاق دېتال. تۆۋەندىكى كىشىلەر بۇ قىستۇرمىغا
تۆھپە قوشقان.
تۆھپىكار
* [ Seth Smigelski ](https://profiles.wordpress.org/sethsm/)
[«Microdata to JSON-LD Converter» نى تىلىڭىزغا تەرجىمە قىلىڭ](https://translate.wordpress.org/projects/wp-plugins/microdata-to-json-ld-converter)
### ئىجادىيەتكە قىزىقامسىز؟
[كودقا كۆز يۈگۈرتۈپ](https://plugins.trac.wordpress.org/browser/microdata-to-json-ld-converter/)،
[SVN خەزىنە](https://plugins.svn.wordpress.org/microdata-to-json-ld-converter/)
تەكشۈرۈپ ياكى [RSS](https://plugins.trac.wordpress.org/log/microdata-to-json-ld-converter/?limit=100&mode=stop_on_copy&format=rss)
ئارقىلىق [ئىجادىيەت خاتىرىسى](https://plugins.trac.wordpress.org/log/microdata-to-json-ld-converter/)
گە مۇشتەرى بولغىلى بولىدۇ.
## ئۆزگىرىش خاتىرىسى
#### 1.8.3
* **IMPROVEMENT:** Enhanced type-casting for Schema properties. Numbers and booleans(
e.g., true/false) extracted from Microdata are now output as native JSON data
types rather than strings, ensuring strict compliance with Schema.org standards
and with rich results testing tools.
#### 1.8.2
* **FIX:** Improved cleanup of malformed (and unmatched) `` and `
` tags
that may be created by wpautop surrounding removed microdata.
* **IMPROVEMENT:** Cleaner HTML output by removing any empty `` left
behind by microdata removal.
#### 1.8.1
* **FIX:** Resolved an issue where JSON-LD schema could break or compress incorrectly
when saving posts containing special characters or double quotes.
#### 1.8
* **NEW:** Added dynamic CollectionPage and ItemList JSON-LD schema generation
for Category and Tag archive pages.
* **NEW:** Added WebSite JSON-LD schema (including Sitelinks Search Box) for the
front page/blog index.
* **NEW:** Introduced the mdtj_output_website_schema filter to safely disable the
homepage schema generation if using a custom implementation.
* **TWEAK:** Expanded the inline microdata removal tool to actively sweep and clean
archive and home pages.
#### 1.7.1
* **FIX:** Improved HTML cleanup by removing tags that contain itemprop attributes
when «Remove Inline Microdata» is enabled.
* **FIX:** Updated regex to include ›itemid‹ for removal, producing cleaner HTML
and satisfying W3C validation requirements
#### 1.7
**ENHANCEMENT:** Expanded content attribute support to all HTML tags. Machine-readable
data (e.g., content=»2025-11-30″) now correctly takes precedence over human-readable
text on and
<
div> elements.
#### 1.6.6
* **SECURITY:** Improved Input handling and enhanced protection against parameter
manipulation attacks.
* **ENHANCEMENT:** More granular escaping of HTML attributes and content in admin
interfaces
* **FIX:** Direct $_GET parameter access now properly uses wp_unslash() before
sanitization.
* **FIX:** JSON-LD schema output now includes security annotations for safe content
* **IMPROVEMENT:** Script tag construction separated from JSON content for better
security clarity
* **SECURITY:** In the JSON Validator, implemented sprintf() for safer use of escaped
variables and improved security against any potential XSS in dynamic messages.
#### 1.6.5
* **IMPROVEMENT:** Replaced deprecated mb_convert_encoding for handling character
sets for HTML parsing.
#### 1.6.4
* **NEW:** Added handling of the «itemid» microdata attribute to convert to «@id»
schema
#### 1.6.3
* **FIX:** Added package.json file and simplified deploy.yml file in GitHub for
WordPress.org Plugin Deploy Action.
#### 1.6
* **FIX:** Resolved an unintended consequence of the previous update in which attributes
with content of «0» was voided. Implemented a smarter parsing logic.
#### 1.5.6
* **FIX:** Corrected logic for to address Object vs. Array Confusion with some
attributes
#### 1.5.5
* **IMPROVEMENT:** Added a settings page warning message for the «Remove Inline
Microdata from HTML» option. The warning message, along with an added readme
FAQ question, describes how this option may conflict with server-side caching
systems. Users, especially those with managed hosting and advanced caching, are
advised to test this feature carefully to ensure there are no conflicts. The
recommendation is for users to keep this feature disabled if it creates caching
issues.
#### 1.5.4
* **SECURITY:** Performed a Security and WordPress Standards Update. Refactored
to use admin_enqueue_scripts for all CSS/JS. Added sanitization for nonce verification.
Implemented recursive sanitization for all incoming JSON data.
#### 1.5.3
* **FIX:** Corrected a bug where the scheduler would not process media (attachments)
due to incorrect post_status.
#### 1.5.2
* **IMPROVEMENT:** Added a log to display the results of the last completed scheduled
rebuild.
#### 1.5.1
* **IMPROVEMENT:** Scheduler status provides better feedback to prevent «false
negatives» on save.
#### 1.5.0
* **NEW:** Added a WP-Cron-based scheduler for automatic background rebuilding
of JSON-LD to better handle dynamic content.
#### 1.4.8
* **IMPROVEMENT:** Modified process_html_buffer() to completely remove meta tags
containing itemprop attributes.
#### 1.4.7
* **SECURITY:** Updated Direct Nonce Verification in the save_post_meta. Added
explanatory comments for the warnings about sanitizing $_POST variables in the
AJAX functions
#### 1.4.6
* **SECURITY:** Updated Sanitization Flow to address InputNotSanitized security
warnings and added explanatory comments to start_buffer explaining why sanitize_key()
is the appropriate and secure method for this specific, low-risk check.
#### 1.4.5
* **SECURITY:** Made additional security updates via Explicit Nonce Escaping and
Sanitization Best Practices
#### 1.4.4
* **SECURITY:** Applied Nonce Escaping, Nonce Verification, and Input Sanitization
for best-practice fixes and security hardening
#### 1.4.3
* **FIX:** Addressed text domain declaration issue within plugin files, changing
the text domain inside the code from ›mdtj‹ to ›microdata-to-json-ld-converter‹.
#### 1.4.2
* **FIX:** Add query parameter to URLs when the plugin fetches pages for regeneration,
avoiding a recursive problem discovered while fetching Microdata when «Remove
Inline Microdata» is active.
#### 1.4.1
* **IMPROVEMENT:** Refined the settings page UI with clearer descriptions for each
option and a more intuitive title for the auto-update feature.
#### 1.4.0
* **FEATURE:** Redesigned the settings page with a modern, tabbed UI and interactive
toggle switches.
* **FEATURE:** Significantly expanded the built-in schema validator to include
rules for Event, FAQPage, VideoObject, and more detailed checks for Offer properties.
#### 1.3.5
* **FIX:** The «Remove Inline Microdata» function now correctly strips leftover
standalone `itemscope` attributes for cleaner HTML output.
#### 1.3.4
* **FEATURE:** Added a new «Keep JSON-LD up to date» option to automatically regenerate
the JSON-LD every time a post is saved.
#### 1.3.3
* **FEATURE:** The JSON-LD is now automatically generated the first time a user
opens the editor for a published post if the field is empty. Improves workflow.
#### 1.3.2
* **FIX:** Corrected a double-encoding issue with special characters. Unicode characters
like and `·` are now saved correctly to the database and render properly in
the final front-end script.
#### 1.3.1
* **FIX:** The parser now correctly handles space-separated `itemprop` attributes(
e.g., `itemprop="caption description"`) by splitting them into two distinct properties.
* **FIX:** Final JSON-LD script now uses `JSON_UNESCAPED_UNICODE` to ensure special
characters display correctly in all validators.
#### 1.3.0
* **FEATURE:** Added a «Validate» button to the meta box for on-demand checks against
schema best practices.
* **FEATURE:** Added a «Test on Google» button to the meta box for easy one-click
validation in the Rich Results Test.
* **REFACTOR:** Moved main plugin class and new validator class into an `/includes`
directory for better organization.
#### 1.2.0
* **FEATURE:** Implemented a Bulk Rebuild tool on the settings page with a progress
bar to process all posts.
* **IMPROVEMENT:** The regeneration process now fetches the full, live HTML of
a page, ensuring Microdata from theme files is parsed.
#### 1.1.0
* **IMPROVEMENT:** The «Remove Microdata» option now uses an output buffer to process
the entire page, not just `the_content`, for more comprehensive removal.
* **IMPROVEMENT:** Added JSON validation and pretty-printing when saving data from
the meta box.
* **FIX:** Ensured `@context` is always present in the generated JSON-LD.
#### 1.0.0
* Initial release.
## Meta
* Version **1.8.3**
* ئاخىرقى يېڭىلانغان ۋاقىت **3 كۈن بۇرۇن**
* ئاكتىپ ئورنىتىش سانى **10 دىن ئاز**
* WordPress نەشرى ** 5.5 ياكى يۇقىرى **
* **6.9.4** دا سىنالغان
* PHP نەشرى ** 7.2 ياكى يۇقىرى **
* تىل
* [English (US)](https://wordpress.org/plugins/microdata-to-json-ld-converter/)
* بەلگە
* [JSON-LD](https://ug.wordpress.org/plugins/tags/json-ld/)[microdata](https://ug.wordpress.org/plugins/tags/microdata/)
[schema.org](https://ug.wordpress.org/plugins/tags/schema-org/)[seo](https://ug.wordpress.org/plugins/tags/seo/)
[structured data](https://ug.wordpress.org/plugins/tags/structured-data/)
* [ئالىي كۆرۈنۈش](https://ug.wordpress.org/plugins/microdata-to-json-ld-converter/advanced/)
## دەرىجە
5/5 يۇلتۇز
* [ 1 5-star review ](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/?filter=5)
* [ 0 4-star reviews ](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/?filter=4)
* [ 0 3-star reviews ](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/?filter=3)
* [ 0 2-star reviews ](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/?filter=2)
* [ 0 1-star reviews ](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/?filter=1)
[Your review](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/#new-post)
[بارلىق ئىنكاسنى كۆرسەت](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/reviews/)
## تۆھپىكار
* [ Seth Smigelski ](https://profiles.wordpress.org/sethsm/)
## قوللاش
چۈشەندۈرۈشىڭىز بارمۇ؟ ياردەم لازىممۇ؟
[قوللاش مۇنبىرىنى كۆرسەت](https://wordpress.org/support/plugin/microdata-to-json-ld-converter/)
## ئىئانە
بۇ قىستۇرمىنىڭ ياخشىلىنىشىنى قوللامسىز؟
[ بۇ قىستۇرمىغا ئىئانە قىلىش ](https://www.paypal.com/donate/?hosted_button_id=M3B2Q94PGVVWL)