BREADCRUMB BLOCK

Breadcrumb Block translation compatibility with REEID Translate — evidence review.

Official plugin evidence describes what Breadcrumb Block does, but does not yet establish specific visitor-facing content values that REEID should translate.

Visit Breadcrumb Block ↗

AWAITING VERIFICATION

Translation scope is not yet established.

Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.

AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.

TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.

PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.

PRACTICAL WORKFLOW

Translation workflow

01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.

02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.

03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.

04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.

PLUGIN INTELLIGENCE

What the official plugin evidence shows

Plugin capabilities

  • Provides a single Gutenberg block for rendering a breadcrumb trail, usable in the Page Editor, Site Editor, and template files.
  • Supports JSON-LD structured data for the breadcrumb trail (explicitly stated as “supports JSON-LD structured data”).
  • Generates breadcrumb items based on multiple context/object types (e.g., front_page, home, shop, page, post, term, taxonomy, 404, paged, author, date parts, attachment), as reflected in the documented filter context values.
  • WooCommerce compatibility is explicitly claimed (“compatible with Woocommerce”) and the plugin includes a hook to prepend the blog page to single posts using the `page_for_posts` option.
  • Allows customization of breadcrumb item inclusion, labels, and attributes via the `breadcrumb_block_get_item` filter (including returning `false` to remove an item).
  • Allows customization of the breadcrumb trail markup via the `breadcrumb_block_get_breadcrumb_trail` filter and customization of the full items list via `breadcrumb_block_get_items`.
  • Allows customization of breadcrumb separator and related rendering arguments (including container/before/after/list_tag/item_tag/item_before/item_after/separator) via the `breadcrumb_block_get_args` filter, with an example requiring inline SVG separator markup.

Distinctive features
Provides a single Gutenberg block for rendering a breadcrumb trail, usable in the Page Editor, Site Editor, and template files. Supports JSON-LD structured data for the breadcrumb trail (explicitly stated as “supports JSON-LD structured data”). Generates breadcrumb items based on multiple context/object types (e.g., front_page, home, shop, page, post, term, taxonomy, 404, paged, author, date parts, attachment), as reflected in the documented filter context values. WooCommerce compatibility is explicitly claimed (“compatible with Woocommerce”) and the plugin includes a hook to prepend the blog page to single posts using the `page_for_posts` option. Allows customization of breadcrumb item inclusion, labels, and attributes via the `breadcrumb_block_get_item` filter (including returning `false` to remove an item). Allows customization of the breadcrumb trail markup via the `breadcrumb_block_get_breadcrumb_trail` filter and customization of the full items list via `breadcrumb_block_get_items`. Allows customization of breadcrumb separator and related rendering arguments (including container/before/after/list_tag/item_tag/item_before/item_after/separator) via the `breadcrumb_block_get_args` filter, with an example requiring inline SVG separator markup.

Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.

SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.

URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.

Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.

CONTENT BOUNDARY

Keep plugin capabilities separate from translation scope.

Current evidence documents what Breadcrumb Block does, but no specific visitor-facing content values have been approved as translation scope.

Structure, configuration, logic, integrations and runtime behavior are not translation claims.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

COMMON QUESTIONS

Breadcrumb Block and REEID Translate FAQ.

Does the current evidence establish translation scope for Breadcrumb Block?

No specific visitor-facing content values are currently approved as translation scope for this integration.

What does the plugin intelligence section describe?

It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.

What is required before translation scope is published?

Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.

RELATED GUIDES

Continue through the compatibility library.

INTEGRATION EVIDENCE

Explore REEID Translate for multilingual WordPress workflows.

REEID separates factual plugin intelligence from evidence-backed translation scope.

No specific visitor-facing content values are currently approved for this integration.

Explore REEID Translate
View integrations
Shopping Cart
Scroll to Top