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.

Improvement

Enhanced rating validation to support 1-5 and 1-10 rating scales.

Improvement

• Added support for the new “Game” and “music” item type in Review Schema.

Fixed

• Validation to prevent the creation of phantom URLs.

Improvement

• Added support for review and aggregateRating fields in Product Schema snippets when the review item is “Product”.
• Enhanced code quality and security in Schema Pro.

Fixed

• Resolved jQuery dependency issues to improve plugin compatibility.

Improvement

• Added support for product variations in the Product schema.

Fixed

• “Array” appearing in the Name field when Positive and Negative Notes were left blank in Product Schema.

• Prevented potential errors during meta box initialization.

Improvement

• Optimized codebase and improved code quality.