WC ENTITY MAPPER
WC Entity Mapper compatibility with REEID Translate
WC Entity Mapper compatibility with REEID Translate is being evaluated from available plugin evidence. Generates and serves a structured entitymap.json file at the site root to provide AI retrieval systems with an entity-first knowledge index No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for WC Entity Mapper.
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
WC Entity Mapper 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 WC Entity Mapper 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
- Generates and serves a structured entitymap.json file at the site root to provide AI retrieval systems with an entity-first knowledge index
- Automatically extracts entity candidates from published posts and pages, using titles as names and pulling descriptions from existing SEO meta or content excerpts
- Creates attributed evidence chunks (up to 600 characters) for each entity, including source URL, page title, and publisher name to maintain brand attribution in AI outputs
- Suggests typed relationships between entities based on shared tags and categories, allowing users to review, edit, or delete these connections via an admin interface
- Injects discovery signals into site output, including a tag in the head, an EntityMap directive in robots.txt, and a footer reference to the HTML companion view
- Provides a human- and crawler-readable entitymap.html companion file alongside the JSON index for broader accessibility and verification
CONTENT BOUNDARY
WC Entity Mapper 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
WC Entity Mapper and REEID Translate FAQ.
What does WC Entity Mapper do according to the available plugin evidence?
WC Entity Mapper 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 WC Entity Mapper?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for WC Entity Mapper?
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 WC Entity Mapper in a multilingual WordPress workflow.
REEID documents WC Entity Mapper 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.