Wp Schema Pro history.

# Security Fix: Hardened the structured data output on search results pages. Please update to the latest version. # Improvement: Regenerate Schema now asks you to confirm first, explaining that it resets per-post values for fields mapped to "New Custom Field" back to the schema defaults and switches off each post's Enable Schema Markup toggle. # Fix: Person schema now includes the Country entered in its address as addressCountry, and a country on its own is enough to output the address. # Fix: Schema names and descriptions taken from the post title, excerpt, or content now show real characters such as & and ’ instead of HTML codes like & in the JSON-LD.

# Improvement: Further UX refinements to the schema setup wizard and the post/page schema box.

# Improvement: Improved the schema setup wizard UX with clearer guidance, search, targeting explanations, and next-step actions. # Fix: Breadcrumb schema now decodes HTML entities in titles, so names containing apostrophes, quotes, or ampersands (e.g. "Martyn's Law") output the real characters instead of codes like ’ in the JSON-LD. # Fix: Schemas whose fields resolve to no data (for example an FAQ schema saved with empty question and answer rows) no longer output an empty JSON-LD block and stray "Schema optimized by Schema Pro" comments on the frontend. # Fix: The author link in Article and other schemas now points to the correct author's archive page, instead of a malformed URL that repeated the username. # Fix: Article schema now outputs its type values in the correct case (Article, Person), so it validates cleanly with structured data testing tools; schemas saved earlier are corrected automatically. # Fix: Opening a Schema Pro settings page from an outdated or mistyped tab link now shows the Schemas list instead of a blank page. # Fix: The setup wizard now saves the correct organization type, so your choice is kept on the Website Information screen and the Organization schema outputs a valid type; earlier selections are corrected automatically. # Fix: Corrected the LinkedIn field placeholder in the setup wizard to use https, matching the other social profile fields.

# Improvement: Updated internal libraries to improve stability and compatibility. # Fix: Migrated the FAQ and How-to editor blocks to Block API version 3, removing the "API version 1 is deprecated" browser console warnings on WordPress 6.9+ and keeping the blocks fully working in the iframe-based editor coming in WordPress 7.0. Existing posts are unaffected. # Fix: Global schema output no longer escapes slashes in URLs, so links in the JSON-LD markup now render in their clean, readable form.

# New: Introduced Dataset schema type with creator, coverage, and downloadable distribution support, per Google's Dataset structured data guidelines. # New: Introduced ProfilePage schema type with Person and Organization profile support, per Google's Profile Page structured data guidelines. # New: Introduced DiscussionForumPosting schema type with author, content, and comment count support, per Google's Discussion Forum structured data guidelines. # New: Introduced QAPage schema type with question, accepted answer, and suggested answers support, per Google's Q&A page structured data guidelines. # Improvement: WordPress 7.1 compatibility. # Fix: Restored the 1-10 rating scale in the schema meta box; ratings above 5 were being blocked since the previous release, so reviews on a 1-10 scale now save correctly again. # Fix: Admin scripts no longer load twice on post edit screens, which caused the repeater "+Add" button to insert duplicate rows and triggered intermittent ACF nonce validation errors when updating a post. # Fix: Admin stylesheet no longer loads twice on post edit screens and is no longer loaded on unrelated wp-admin pages.

# Fix: Page-level Custom Schema Markup added from the editor meta box now takes priority over the Global Schema instead of being overridden by it. # Fix: Rating field in the schema meta box now displays the entered value on the correct 5-star scale, so a rating of 5 shows all five stars filled. # Improvement: Updated internal libraries to improve stability and compatibility.

# Fix: Organization schema now resolves the selected Contact Page to its full URL, lists each social profile only once, and outputs the full-size logo to meet Google's minimum logo size requirement. # Fix: Organization schema @type now always outputs in valid PascalCase format, and contact options such as Toll Free no longer appear when left unselected.

# New: Added SureRank cross-sell promotion in the settings sidebar that auto-hides when SureRank is already installed on the site. # Fix: Preserved FAQ question-answer data when running Regenerate Schema, which previously removed per-page FAQ entries. # Fix: Ensured FAQ schema output remains a valid JSON array when individual entries are skipped, restoring compatibility with Google's structured data validator. # Fix: Preserved backslash sequences and line breaks when saving custom markup schema content and writing to the cache. # Fix: Normalized line breaks in product schema description output. # Fix: Added safety checks for WooCommerce breadcrumb keys to prevent PHP notices on non-WooCommerce sites.

# Improvement: WordPress 7.0 compatibility. # Improvement: Updated Internal libraries to improve stability and compatibility. # Fix: Prevented empty Geo-Coordinates block in Local Business schema when latitude or longitude values are empty or set to "none".

# New: Introduced WebPage schema type with support for WebPage, CollectionPage, AboutPage, and ContactPage variants. # Fix: Global schema settings now properly apply to pages with previous page-level edits; Regenerate Schema resets overrides to enforce global values site-wide. # Improvement: Prevented empty Clip entries in VideoObject schema, improved field handling, and added stronger validation and security to the schema meta box save process. # Improvements: Added Security fixes.