| 开发者 |
codedication
pauloc |
|---|---|
| 更新时间 | 2026年5月20日 18:27 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
@graph array for multiple schemas<head>/wp-content/plugins/cddc-schema-blocks/No. Google decides whether to show rich snippets based on many factors. Proper schema markup improves your chances but doesn't guarantee display.
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.
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.
No! Just add blocks and fill in the fields. The plugin handles all the technical JSON-LD markup automatically.
Yes. All output follows Schema.org specifications and Google's structured data guidelines.
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.
Yes. You can add Review schema to any post type, including WooCommerce product pages.
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.
There is no limit. Add as many Question/Answer pairs as you need. All items are included in the FAQPage JSON-LD output.
__() so strings reach the .pot and translations apply at render time.<script> tag — the dismiss handler is now an enqueued asset (assets/admin/conflict-notice.js) wired via data-* attributes on the notice container. The notice is also gated to the plugin Settings page and plugins.php only.WP_HTML_Tag_Processor-mutated HTML string. The wrapper <div> is composed from escape-aware core APIs, and per-<details> Interactivity API directives are now injected via a render_block filter scoped to FAQ-ancestor renders. Foreign data-wp-* directives on nested blocks are preserved.useSlotFills crash on older @wordpress/components; the Advanced tab now derives its visibility from the internal fill bridge.cddc_schema_blocks_is_settings_screen lets integrations declare authoritatively when the React Settings app should be enqueued.Admin_Integration, dead utils/completeness-score.ts / utils/json-ld-preview.ts modules, the unused HelpTip component family and the divergent PHP Site_Schema::get_completeness_score() (the React UI is now the single source of truth for completeness).Admin_Integration::get_settings_url()) instead of guessing from class_exists(), so the link is correct in the fallback path where the shared admin package exists but its renderer is not yet available.