Adds an animated +\/\u00d7 icon to FAQ items (CSS-only, accessible). No breaking changes.<\/p>","1.0.2":"
Translatable Review block labels reach the Fixes the Settings page appearing empty under the centralized admin. Saved values now hydrate correctly. Recommended upgrade.<\/p>","1.0.0":" First release \u2014 FAQ Block with FAQPage schema and Review Block with star ratings and JSON-LD output.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3537180,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3537180,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3537180,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3537180,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3648514,"resolution":false,"location":"assets","locale":"","contents":"{\"$schema\":\"https:\\\/\\\/playground.wordpress.net\\\/blueprint-schema.json\",\"landingPage\":\"\\\/wp-admin\\\/post.php?post=1&action=edit\",\"preferredVersions\":{\"php\":\"8.2\",\"wp\":\"latest\"},\"login\":true,\"steps\":[{\"step\":\"installPlugin\",\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"codedication-schema-blocks\"},\"options\":{\"activate\":true}},{\"step\":\"runPHP\",\"code\":\"\\\\n\\\\n Yes \\\\u2014 this plugin automatically generates FAQPage JSON-LD from your FAQ items.<\\\/p>\\\\n\\\\n<\\\/details>\\\\n\\\\n\\\\n\\\\n It uses the WordPress Interactivity API for a keyboard-accessible, JavaScript-powered accordion.<\\\/p>\\\\n\\\\n<\\\/details>\\\\n\\\\n\\\"; $review = \\\"\\\\n Schema Blocks adds FAQ schema<\/strong> and Review schema<\/strong> directly to the WordPress block editor \u2014 no shortcodes, no custom fields, no coding required. Each block automatically generates valid JSON-LD structured data<\/strong> that Google can read to display rich results<\/strong> in search: FAQ dropdowns, star ratings, and review snippets.<\/p>\n\n Built for Gutenberg. Works with Yoast SEO, Rank Math, and AIOSEO.<\/p>\n\n Schema markup helps search engines understand your content better, resulting in:<\/p>\n\n FAQ Block<\/strong> \u2014 Google FAQ Rich Result<\/a><\/p>\n\n Review Block<\/strong> \u2014 Google Review Snippet<\/a><\/p>\n\n Settings Page<\/strong> \u2014 Site-wide structured data from a single dashboard<\/p>\n\n Built for SEO workflows<\/strong>\n* Automatic JSON-LD output in the page head \u2014 single Schema Blocks works alongside<\/strong> your existing SEO plugin \u2014 it does not replace it:<\/p>\n\n If you already have a plugin generating FAQ or Review schema for entire pages, we recommend disabling that specific schema type to avoid duplication.<\/p>\n\n All schema output follows Google's structured data guidelines. Test your pages with:\n* Google Rich Results Test<\/a>\n* Schema.org Validator<\/a>\n* ValidGraph<\/a> \u2014 connect your site for one-click validation right inside the editor: completeness scoring, AI discoverability checks, and rich-result eligibility, without ever leaving WordPress.<\/p>\n\n\n No. Google decides whether to show rich snippets based on many factors. Proper schema markup improves your chances but doesn't guarantee display.<\/p><\/dd>\n Schema Blocks focuses on content-level schema (FAQ, Review) which complements site-wide schema from SEO plugins. We recommend disabling duplicate schema types if your SEO plugin also provides them. See the \"Compatible with Popular SEO Plugins\" section above for plugin-specific guidance.<\/p><\/dd>\n Yes. Schema Blocks uses the standard Gutenberg block API and works with any block theme, including FSE themes like Twenty Twenty-Four, Kadence Blocks, or GeneratePress.<\/p><\/dd>\n No! Just add blocks and fill in the fields. The plugin handles all the technical JSON-LD markup automatically.<\/p><\/dd>\n Yes. All output follows Schema.org specifications and Google's structured data guidelines.<\/p><\/dd>\n Schema is output as a single JSON-LD script in the page head. It's lightweight and doesn't affect page load time or Core Web Vitals.<\/p><\/dd>\n Yes. You can add Review schema to any post type, including WooCommerce product pages.<\/p><\/dd>\n Yes. The Settings page includes a Site Identity section where you configure Organization or Person schema with name, logo, description, email, phone, address, social profiles, and founding year. A completeness indicator shows your progress.<\/p><\/dd>\n There is no limit. Add as many Question\/Answer pairs as you need. All items are included in the FAQPage JSON-LD output.<\/p><\/dd>\n No, not by default. All JSON-LD is generated and output entirely on your own server. The only exception is the optional ValidGraph integration: it only activates if you explicitly connect an account with your own API key, and until you do, nothing ever leaves your site.<\/p><\/dd>\n ValidGraph is an optional companion service that checks your schema for completeness, AI discoverability, and rich-result eligibility right inside the block editor. It's entirely opt-in \u2014 connect it under Settings \u2192 Schema Blocks, or skip it and validate manually with Google's tools instead.<\/p><\/dd>\n Yes. Assign a post type to \"Article\" or \"Blog posting\" under Settings \u2192 Content and matching posts automatically emit an Article node \u2014 headline, dates, author, publisher, primary image \u2014 merged into the same JSON-LD graph as your FAQ and Review blocks.<\/p><\/dd>\n Yes. The Settings page includes a Breadcrumbs section that outputs a site-wide BreadcrumbList schema, with configurable separator and home label.<\/p><\/dd>\n Yes. Settings \u2192 Schema Blocks \u2192 Block management lets you enable or disable the FAQ and Review blocks individually.<\/p><\/dd>\n Yes. All strings are translation-ready, and every FAQ and Review schema automatically includes an .pot<\/code> and apply at render. Tested with WordPress 7.0.<\/p>","1.0.1":"Do FAQ blocks support Schema.org markup?<\\\/summary>\\\\n\\\\n
How does the accordion work?<\\\/summary>\\\\n\\\\n
Schema Blocks<\\\/h3>
Frequently Asked Questions<\\\/h2>\\\\n\\\\n\\\" . $faq . \\\"\\\\n\\\\n
Product Review<\\\/h2>\\\\n\\\\n\\\" . $review; wp_update_post( [ 'ID' => 1, 'post_title' => 'Schema Blocks Demo', 'post_content' => $content, 'post_status' => 'publish' ] );\"}]}"}},"all_blocks":{"codedication\/schema-review":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"codedication\/schema-review","version":"1.0.0","title":"Review Schema","category":"schema-blocks","description":"Create a review with star ratings and Schema.org markup for rich snippets.","keywords":["review","rating","stars","schema","seo"],"textdomain":"codedication-schema-blocks","attributes":{"blockId":{"type":"string"},"itemName":{"type":"string","default":""},"itemType":{"type":"string","default":"Product","enum":["Product","LocalBusiness","Movie","Book","Restaurant","Thing"]},"itemImage":{"type":"string","default":""},"itemDescription":{"type":"string","default":""},"itemUrl":{"type":"string","default":""},"ratingValue":{"type":"number","default":0},"bestRating":{"type":"number","default":5},"worstRating":{"type":"number","default":1},"authorName":{"type":"string","default":""},"authorType":{"type":"string","default":"Person","enum":["Person","Organization"]},"authorFromSiteIdentity":{"type":"boolean","default":false},"datePublished":{"type":"string","default":""},"reviewBody":{"type":"string","default":""},"publisherName":{"type":"string","default":""},"publisherType":{"type":"string","default":"Organization","enum":["Organization","Person"]},"reviewAspect":{"type":"string","default":""},"positiveNotes":{"type":"array","default":[],"items":{"type":"string"}},"negativeNotes":{"type":"array","default":[],"items":{"type":"string"}},"ratingExplanation":{"type":"string","default":""},"bookAuthor":{"type":"string","default":""},"bookIsbn":{"type":"string","default":""},"bookFormat":{"type":"string","default":"","enum":["","EBook","Paperback","Hardcover","AudiobookFormat","GraphicNovel"]},"bookNumberOfPages":{"type":"number","default":0},"bookPublisher":{"type":"string","default":""},"bookDatePublished":{"type":"string","default":""},"bookSameAs":{"type":"array","default":[],"items":{"type":"string"}}},"supports":{"html":false,"anchor":true,"className":true,"align":["wide"],"spacing":{"margin":true,"padding":true},"color":{"background":true,"text":true},"typography":{"fontSize":true}},"render":"file:.\/render.php","editorScript":"file:.\/index.js","editorStyle":"file:.\/index.css","style":"file:.\/style-index.css"},"codedication\/schema-faq":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"codedication\/schema-faq","version":"1.0.0","title":"FAQ Schema","category":"schema-blocks","description":"Create an FAQ section with Schema.org markup for better SEO.","keywords":["faq","questions","answers","schema","seo"],"textdomain":"codedication-schema-blocks","attributes":{"closeOthers":{"type":"boolean","default":false},"description":{"type":"string","default":""}},"supports":{"html":false,"anchor":true,"className":true,"align":["wide","full"],"spacing":{"margin":true,"padding":true},"color":{"background":true,"text":true},"typography":{"fontSize":true,"lineHeight":true,"letterSpacing":true,"textTransform":true,"fontStyle":true,"fontWeight":true,"textDecoration":true,"fontVariant":true},"interactivity":true},"render":"file:.\/render.php","editorScript":"file:.\/index.js","editorStyle":"file:.\/index.css","style":"file:.\/style-index.css"}},"tagged_versions":["1.0.1","1.0.2","1.1.0","1.2.0"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3537180,"resolution":"1","location":"assets","locale":"","width":2560,"height":1440},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3537180,"resolution":"2","location":"assets","locale":"","width":2560,"height":1440},"screenshot-3.jpg":{"filename":"screenshot-3.jpg","revision":3537180,"resolution":"3","location":"assets","locale":"","width":2560,"height":1440},"screenshot-4.jpg":{"filename":"screenshot-4.jpg","revision":3537180,"resolution":"4","location":"assets","locale":"","width":2560,"height":1440},"screenshot-5.jpg":{"filename":"screenshot-5.jpg","revision":3537180,"resolution":"5","location":"assets","locale":"","width":2560,"height":1440},"screenshot-6.jpg":{"filename":"screenshot-6.jpg","revision":3537180,"resolution":"6","location":"assets","locale":"","width":2560,"height":1440},"screenshot-7.jpg":{"filename":"screenshot-7.jpg","revision":3537180,"resolution":"7","location":"assets","locale":"","width":2560,"height":1440}},"screenshots":{"1":"FAQ Block styling \u2014 Color, Typography and Dimensions controls in the Inspector sidebar","2":"FAQ Block with a custom theme \u2014 fully stylable to match your brand","3":"FAQ Block frontend output \u2014 clean accordion rendered on the published page","4":"Review Block in the editor \u2014 star rating, item type selector and review body with 4.5\/5 rating","5":"Review Block author & publisher \u2014 date, Author (Person) and Publisher (Organization) fields for valid Review schema","6":"Review Block frontend output \u2014 headline, rating, review body and positive\/negative notes","7":"Settings page \u2014 Site Identity (Organization\/Person), JSON-LD preview, completeness indicator and \"Test in Google Rich Results\" shortcut"}},"plugin_section":[],"plugin_tags":[178627,2516,230403,2293,1121],"plugin_category":[],"plugin_contributors":[263511,162622],"plugin_business_model":[],"class_list":["post-302780","plugin","type-plugin","status-publish","hentry","plugin_tags-faq-schema","plugin_tags-json-ld","plugin_tags-review-schema","plugin_tags-star-rating","plugin_tags-structured-data","plugin_contributors-codedication","plugin_contributors-pauloc","plugin_committers-codedication"],"banners":{"banner":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/banner-772x250.png?rev=3537180","banner_2x":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/banner-1544x500.png?rev=3537180","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/icon-128x128.png?rev=3537180","icon_2x":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/icon-256x256.png?rev=3537180","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/screenshot-1.jpg?rev=3537180","caption":"FAQ Block styling \u2014 Color, Typography and Dimensions controls in the Inspector sidebar"},{"src":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/screenshot-2.jpg?rev=3537180","caption":"FAQ Block with a custom theme \u2014 fully stylable to match your brand"},{"src":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/screenshot-3.jpg?rev=3537180","caption":"FAQ Block frontend output \u2014 clean accordion rendered on the published page"},{"src":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/screenshot-4.jpg?rev=3537180","caption":"Review Block in the editor \u2014 star rating, item type selector and review body with 4.5\/5 rating"},{"src":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/screenshot-5.jpg?rev=3537180","caption":"Review Block author & publisher \u2014 date, Author (Person) and Publisher (Organization) fields for valid Review schema"},{"src":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/screenshot-6.jpg?rev=3537180","caption":"Review Block frontend output \u2014 headline, rating, review body and positive\/negative notes"},{"src":"https:\/\/ps.w.org\/codedication-schema-blocks\/assets\/screenshot-7.jpg?rev=3537180","caption":"Settings page \u2014 Site Identity (Organization\/Person), JSON-LD preview, completeness indicator and \"Test in Google Rich Results\" shortcut"}],"raw_content":"\n
FAQ Schema & Review Schema Blocks<\/h4>\n\n
Why Schema Markup Matters<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
\n
\n
@graph<\/code> array for multiple schemas\n* Compatible with Google Rich Results Test and Schema.org Validator\n* Works directly in the Gutenberg block editor<\/p>\n\nCompatible with Popular SEO Plugins<\/h4>\n\n
\n
How It Works<\/h4>\n\n
\n
<head><\/code><\/li>\nValidation<\/h4>\n\n
\n
\/wp-content\/plugins\/cddc-schema-blocks\/<\/code><\/li>\n\n
Will this guarantee rich snippets in Google?<\/h3><\/dt>\n
Does this conflict with Yoast SEO or Rank Math?<\/h3><\/dt>\n
Does it work with Full Site Editing (FSE) themes?<\/h3><\/dt>\n
Do I need technical knowledge?<\/h3><\/dt>\n
Is the schema valid?<\/h3><\/dt>\n
What about performance?<\/h3><\/dt>\n
Can I use this with WooCommerce?<\/h3><\/dt>\n
Does it add Organization or Person schema?<\/h3><\/dt>\n
How many FAQ items can I add?<\/h3><\/dt>\n
Does the plugin send my data anywhere?<\/h3><\/dt>\n
What is ValidGraph and do I have to use it?<\/h3><\/dt>\n
Does it generate Article schema for my posts automatically?<\/h3><\/dt>\n
Does it add Breadcrumb schema too?<\/h3><\/dt>\n
Can I turn off a schema block I don't use?<\/h3><\/dt>\n
Is the plugin translation-ready?<\/h3><\/dt>\n
inLanguage<\/code> property derived from your site's language setting.<\/p><\/dd>\n\n<\/dl>\n\n\n1.2.0<\/h4>\n\n
\n
validgraph.com\/api\/v1\/...<\/code>) \u2014 the previous URL (wp-json\/validgraph<\/code>) never resolved, so validation requests always failed.<\/li>\nWebSite<\/code> node emits description<\/code>, inLanguage<\/code> and author<\/code> from the fields the tab already collected, each omitted when empty. Previously five fields were saved and previewed but never emitted.<\/li>\nWebSite<\/code> node keeps referencing it instead.<\/li>\nReview.author<\/code> reference the site Organization or Person node instead of an anonymous inline author, and the visible byline is resolved at render time, so renaming the identity in Settings updates published posts without re-saving them. Falls back to the inline author when no identity is configured, so a reference never dangles. Extensibility contract bumped to 1.7.0<\/code> \u2014 Schema_Graph::registered_identity_id()<\/code> is now a public seam.<\/li>\n@id<\/code>s are now stable across block reordering \u2014 each Review node derives its @id<\/code> from the block's own id ({permalink}#review-a1b2c3d4<\/code>) instead of its position on the page, and duplicated blocks emit two nodes instead of silently merging into one. Reviews saved before this release keep their current ids; nothing is rewritten.<\/li>\nBook<\/code>, a new \"Book Details\" section adds author, publisher, publication date, format, page count, ISBN and external identity URLs (OpenLibrary, Wikidata, Goodreads). The filled fields are emitted on itemReviewed<\/code> (author<\/code>, publisher<\/code>, datePublished<\/code>, bookFormat<\/code>, numberOfPages<\/code>, isbn<\/code>, sameAs<\/code>) and shown as a metadata line under the item name, so the markup describes visible content. Every field is optional and existing reviews are unchanged.<\/li>\nauthor<\/code> referencing a Person<\/code> node built from the post author's WordPress profile (name, author archive URL, avatar, bio, website). Nodes are minted on demand with a stable, PII-free @id<\/code>, deduplicated against the site Person identity via a new Site Identity \"WordPress user\" picker. Extensibility contract bumped to 1.5.0<\/code> \u2014 new Schema_Graph::ensure_author_person()<\/code> seam (callable by addons) and cddc_schema_blocks_author_person<\/code> enrichment filter for E-E-A-T fields.<\/li>\nArticle<\/code> node ({permalink}#article<\/code>) wired into the unified graph, with headline, dates, publisher, primary image, and category. A new Content settings tab maps each public post type to None, Article, or Blog posting (default: posts \u2192 Article). Extensibility contract bumped to 1.4.0<\/code> \u2014 new cddc_schema_blocks_page_content_type<\/code> filter (per-post type overrides, e.g. NewsArticle<\/code>) and main-entity election API (Schema_Graph::flag_main_entity()<\/code>) so addon content nodes replace the automatic Article instead of competing with it.<\/li>\ninLanguage<\/code> property derived from the site language (BCP-47, e.g. en-US<\/code>). No configuration needed; overridable via the cddc_schema_faq_output<\/code> \/ cddc_schema_review_output<\/code> filters.<\/li>\n<script type=\"application\/ld+json\"><\/code> with a single @graph<\/code> instead of two separate scripts. Adds WebPage (and primary image) anchor nodes linking site identity, WebSite, breadcrumbs, and block schemas together. Extensibility contract bumped to 1.3.0<\/code> \u2014 new cddc_schema_blocks_graph_nodes<\/code> filter.<\/li>\n{permalink}#faq<\/code> node id is retired \u2014 its questions now live on the page's WebPage node (@type: [\"WebPage\",\"FAQPage\"]<\/code>, mainEntity<\/code>). FAQ rich results were retired by Google (2026-05-07), so no SERP feature depends on the old id.<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
window.cddcSchema.ui<\/code> via the cddc-schema-ui<\/code> script handle (SchemaBlockCard, SchemaFormSection, SchemaPreviewInline, DurationInput, and more).<\/li>\ncddc_schema_blocks_settings_url<\/code> filter so a companion hosting the Settings screen elsewhere can correct internal links (admin notices, the plugins-list action link).<\/li>\n.wordpress-org\/blueprints\/blueprint.json<\/code>) powering the Live Preview button on the wp.org plugin directory.<\/li>\nreviewBody<\/code> now falls back to the block's rendered HTML when the attribute isn't set explicitly.<\/li>\nload_optional_integrations()<\/code> bootstrap and Admin_Integration<\/code> companion-coupling code (unreachable without a package this plugin never ships) \u2014 the Settings screen registration is simpler and wp.org-review-clean as a result.<\/li>\n<\/ul>\n\n1.0.3<\/h4>\n\n
\n
details[open]<\/code> state (no JS), mirrored in the editor and respecting prefers-reduced-motion<\/code>.<\/li>\n<\/ul>\n\n1.0.2<\/h4>\n\n
\n
__()<\/code> so strings reach the .pot<\/code> and translations apply at render time.<\/li>\n1.0.1<\/h4>\n\n
\n
<script><\/code> tag \u2014 the dismiss handler is now an enqueued asset (assets\/admin\/conflict-notice.js<\/code>) wired via data-*<\/code> attributes on the notice container. The notice is also gated to the plugin Settings page and plugins.php<\/code> only.<\/li>\nWP_HTML_Tag_Processor<\/code>-mutated HTML string. The wrapper <div><\/code> is composed from escape-aware core APIs, and per-<details><\/code> Interactivity API directives are now injected via a render_block<\/code> filter scoped to FAQ-ancestor renders. Foreign data-wp-*<\/code> directives on nested blocks are preserved.<\/li>\nuseSlotFills<\/code> crash on older @wordpress\/components<\/code>; the Advanced tab now derives its visibility from the internal fill bridge.<\/li>\ncddc_schema_blocks_is_settings_screen<\/code> lets integrations declare authoritatively when the React Settings app should be enqueued.<\/li>\nAdmin_Integration<\/code>, dead utils\/completeness-score.ts<\/code> \/ utils\/json-ld-preview.ts<\/code> modules, the unused HelpTip<\/code> component family and the divergent PHP Site_Schema::get_completeness_score()<\/code> (the React UI is now the single source of truth for completeness).<\/li>\nAdmin_Integration::get_settings_url()<\/code>) instead of guessing from class_exists()<\/code>, so the link is correct in the fallback path where the shared admin package exists but its renderer is not yet available.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
\n