SCHEMA BLOCKS
Schema Blocks compatibility with REEID Translate
Schema Blocks compatibility with REEID Translate is being evaluated from available plugin evidence. Emit structured data as a single JSON-LD @graph containing stable entity IDs for WebPage, Article, Organization, and Person nodes. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Schema Blocks.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Schema Blocks is documented in the SEO category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Schema Blocks compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Emit structured data as a single JSON-LD @graph containing stable entity IDs for WebPage, Article, Organization, and Person nodes.
- Provide nine Gutenberg blocks (FAQ, Review, Recipe, Product, Event, Local Business, How-To, Job Posting, Breadcrumb) that render visible content while simultaneously generating corresponding schema markup.
- Automatically map public post types to Article or BlogPosting schema by default, with per-post overrides for content and page types via the document sidebar.
- Extend WordPress user profiles to generate rich Person entities including job titles, credentials, social profile URLs, and organizational relationships like worksFor and founder.
- Offer site-level configuration for Organization identity, WebSite metadata, and global BreadcrumbList settings with live JSON-LD preview.
- Detect conflicts with other SEO plugins emitting identical node types and provide toggles to suppress site-level nodes to avoid duplication.
CONTENT BOUNDARY
Schema Blocks capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Schema Blocks and REEID Translate FAQ.
What does Schema Blocks do according to the available plugin evidence?
Schema Blocks has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Schema Blocks?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Schema Blocks?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Schema Blocks in a multilingual WordPress workflow.
REEID documents Schema Blocks functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.