Hey everyone,

This one’s all about your schema output being accurate and your first-run setup being clearer. We tidied up how titles, author links, and types show up in the markup, cleared out some empty output that shouldn’t have been there, and gave the setup wizard a friendlier walkthrough.

What’s Fixed

• Special characters in breadcrumb titles display correctly. Titles with apostrophes, quotes, or ampersands (like “Martyn’s Law”) were showing up as codes such as ’ in the breadcrumb markup. They now output the real characters.
• Empty schemas no longer clutter your pages. If a schema had no data to show (for example an FAQ saved with empty question and answer rows), it was still printing an empty JSON-LD block and a stray “Schema optimized by Schema Pro” comment on the frontend. Both are gone now.
• Author links point to the right place. The author link in Article and other schemas was building a malformed URL that repeated the username. It now points to the correct author’s archive page.
• Article schema validates cleanly again. Type values are now output in the correct case (Article, Person), so structured data testing tools validate them without complaint. Schemas saved earlier are corrected automatically.
• Old settings links don’t lead to a blank page. Opening a Schema Pro settings page from an outdated or mistyped tab link now lands you on the Schemas list instead of nothing at all.
• Your organization type sticks. The setup wizard is now saving the organization type you pick, so your choice is kept on the Website Information screen and the Organization schema outputs a valid type. Earlier selections are corrected automatically.
• LinkedIn field uses the right format. The LinkedIn placeholder in the setup wizard now uses https, matching the other social profile fields.

What’s Improved

• A clearer setup wizard. We reworked the schema setup wizard with better guidance, search, plain-English explanations of where each schema applies, and clearer next-step actions, so getting your schema set up is easier from the start.

We recommend updating to Schema Pro v2.12.2 to benefit from these fixes.

As always, our support team is here to help if you have any questions or need assistance with the update.

Best
Team Schema Pro

Hey everyone,

This release clears out some editor console noise and gets your schema markup ready for what’s coming in WordPress. Your FAQ and How-to blocks are future-proofed for the new editor, your JSON-LD links read cleanly again, and we refreshed a few internals along the way.

What’s Fixed

• Your FAQ and How-to blocks are ready for the new WordPress editor. We moved both editor blocks to the latest Block API, so the “API version 1 is deprecated” warnings that showed up in the browser console on WordPress 6.9+ are gone. The blocks also keep working smoothly in the iframe-based editor arriving in WordPress 7.0. Your existing posts aren’t affected.

• Links in your schema markup read cleanly again. The Global Schema output was adding backslashes in front of the slashes in URLs, so links in the JSON-LD looked cluttered. They now output in their clean, readable form.

What’s Improved

• Updated internal libraries. We brought the shared libraries that power the plugin up to their latest versions for better stability and compatibility. Nothing changes in how you use the plugin.

We recommend updating to Schema Pro v2.12.1 to benefit from these fixes.

As always, our support team is here to help if you have any questions or need assistance with the update.

Best
Team Schema Pro

Hey everyone,

This release is our biggest coverage boost in a while. We’ve added four new schema types, so datasets, author profiles, forum threads, and Q&A pages can all earn
rich results now. We also cleared up a rating issue and cleaned up some admin loading behavior on the post editor.

What’s New

• Dataset schema is here. You can now mark up datasets with their creator, coverage, and downloadable distribution details, following Google’s Dataset structured data guidelines. It’s a great fit for research sites, data portals, and open-data projects.
• Profile Page schema is here. Author and organization profiles can now be marked up the way Google expects, with support for both Person and Organization profiles. Handy for author bios, team pages, and creator profiles.
• Discussion Forum schema is here. Forum and community posts can now qualify for discussion-style rich results, capturing the author, post content, and comment count, in line with Google’s Discussion Forum guidelines.
• Q&A Page schema is here. Question-and-answer pages can now be marked up with the question, the accepted answer, and any suggested answers, following Google’s Q&A Page guidelines. Ideal for support pages, help centers, and community Q&A.

What’s Fixed

• The 1–10 rating scale works again in the schema meta box. Since the last release, any rating above 5 was being blocked, so reviews on a 1–10 scale couldn’t save. That’s fixed, and your ratings now save correctly again.
• The “+Add” button no longer inserts duplicate rows. Admin scripts were loading twice on post edit screens, which made repeater fields add two rows at once and occasionally triggered ACF nonce errors when you updated a post. Both are resolved.
• Admin styles load cleanly now. The admin stylesheet was loading twice on post edit screens, and also loading on unrelated wp-admin pages where it wasn’t needed. It now loads once, and only where it should.

What’s Improved

• Ready for WordPress 7.1. Schema Pro is tested and compatible with WordPress 7.1, so you can update WordPress with confidence.

We recommend updating to Schema Pro v2.12.0 to get the new schema types and these fixes.

As always, our support team is here to help if you have any questions or need assistance with the update.

Best
Team Schema Pro

Hey everyone,

This release is about the schema meta box doing what you’d expect. Your page-level edits now actually win, star ratings display the way you entered them, and we refreshed some internals while we were at it.

What’s Fixed

• Your page-level Custom Schema Markup takes priority now. Custom markup added from the editor meta box was being overridden by the Global Schema. That’s flipped. If you’ve customized the schema on a specific page, that version is the one that gets output.
• Star ratings show up on the correct 5-star scale. The Rating field in the schema meta box was displaying entered values on the wrong scale, so a perfect 5 didn’t fill all five stars. It does now.

What’s Improved

• Updated internal libraries. We brought the shared libraries that power admin notices and analytics up to their latest versions for better stability and compatibility. Nothing changes in how you use the plugin.

We recommend updating to Schema Pro v2.11.4 to benefit from these fixes.

As always, our support team is here to help if you have any questions or need assistance with the update.

Best
Team Schema Pro

Hey everyone,

This one’s all about your Organization schema. A handful of small issues were keeping it from validating cleanly in Google’s eyes: half-formed URLs, duplicate entries, undersized logos. All sorted now.

What’s Fixed

• Your Contact Page now shows up as a full URL. The Organization schema was outputting the selected Contact Page ID. It now resolves to the complete page URL, the way Google expects it.
• Social profiles are listed once. Just once. Some social profile URLs were being repeated in the schema output. Each profile now appears exactly one time.
• Your logo now meets Google’s size requirement. The schema was outputting a fixed width and height of the logo (600 x 600 ) instead of the actual logo size. It now outputs the actual image size.
• The Organization @type is always valid now. In some cases the @type value was output in the wrong letter casing. It’s now always proper PascalCase.

We recommend updating to Schema Pro v2.11.3 to benefit from these improvements and fixes.

As always, our support team is here to help if you have any questions or need assistance with the update.

 Best
 Team Schema Pro

Hey everyone,

 This one’s mostly cleanup — five fixes that smooth out the rough edges around FAQ schemas, custom markup, and a couple of quieter PHP notices. If you’ve ever hit “Regenerate Schema” and watched your FAQs vanish, this release is for you.

What’s Fixed

• FAQs no longer disappear when you Regenerate Schema. A bug was wiping out per-page FAQ question-and-answer entries the moment you hit regenerate. Your FAQs now stay exactly where you put them.
• FAQ schema output is valid JSON again, even when entries are skipped. Google’s structured data validator was rejecting some FAQ output because the JSON array was malformed when individual entries got skipped. Fixed – the output stays a clean, valid array no matter what.
• Custom markup keeps your formatting intact. Backslash sequences and line breaks were being mangled when saving custom schema markup and writing to the cache. Both are now preserved exactly as you wrote them.
•  Product schema descriptions read cleanly. Line breaks in product schema descriptions were rendering inconsistently. They’re now normalized so the output is tidy.
•  No more WooCommerce-related PHP notices on non-WooCommerce sites. A missing safety check on breadcrumb keys was throwing harmless-but-noisy notices on sites that don’t run WooCommerce. Cleaned up.

We recommend updating to Schema Pro v2.11.2 to benefit from these improvements and fixes.

As always, our support team is here to help if you have any questions or need assistance with the update.

 Best
 Team Schema Pro

Hello everyone,

Quick maintenance release. We’ve made Schema Pro fully compatible with WordPress 7.0, refreshed a few internal libraries under the hood, and squashed a Local Business schema quirk that was slipping through on incomplete location data.

What’s Improved

•   Ready for WordPress 7.0. Schema Pro runs cleanly on the latest WordPress release, so you can update core without second-guessing compatibility.
•   Steadier internals. We refreshed a few bundled libraries to keep things stable and play nicely with the wider WordPress ecosystem.

What’s Fixed

•  Local Business schema no longer outputs empty Geo-Coordinates. If your business location was missing a latitude or longitude, or had them set to “none”, Schema Pro was still printing an empty Geo-Coordinates block in the markup. It now skips the block entirely when the values aren’t usable, so your schema stays clean.

We recommend updating to Schema Pro v2.11.1 to benefit from these improvements and fixes.

As always, our support team is here to help if you have any questions or need assistance with the update.

Best
Team Schema Pro

New

• Introduced WebPage schema type with support for WebPage, CollectionPage, AboutPage, and ContactPage variants.

Fixed

• Global schema settings now properly apply to pages with previous page-level edits; Regenerate Schema resets overrides to enforce global values site-wide.

Improvements

• Prevented empty Clip entries in VideoObject schema, improved field handling, and added stronger validation and security to the schema meta box save process.
• Added Security fixes.

Fixed

• Prevented empty aggregateRating and video objects in Recipe schema.

Fixed

• Prevented empty hasVariant properties in product schema.