RICH CONTACT WIDGET
Rich Contact Widget compatibility with REEID Translate
Rich Contact Widget compatibility with REEID Translate is being evaluated from available plugin evidence. Adds microdata and microformats markup to contact information for search-engine use. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Rich Contact Widget.
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
Rich Contact Widget is documented in the SEO category with 7 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 Rich Contact Widget 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
- Adds microdata and microformats markup to contact information for search-engine use.
- Can display contact information for a business or individual below a website in search results.
- Can display a map with the location to support local SEO.
- Links telephone and email fields so visitors can call or send mail from mobile devices or Skype.
- Can display a static image map linked to the address’s Google Maps page.
- Can provide a download link for a vCard.
- Creates a KML file and an associated sitemap file, and can add the sitemap to the Yoast SEO sitemap index.
Distinctive features
Contact-focused SEO markup with local search support, including map display, phone and email links, vCard download, and KML/sitemap output.
CONTENT BOUNDARY
Rich Contact Widget 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
- The available evidence describes contact-information markup and related search features, but it does not establish broader site content handling. Map, vCard, KML, sitemap, phone, and email behaviors are only evidenced for the contact-information features described here. No translation behavior is established.
COMMON QUESTIONS
Rich Contact Widget and REEID Translate FAQ.
What does Rich Contact Widget do according to the available plugin evidence?
Rich Contact Widget has 7 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 Rich Contact Widget?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Rich Contact Widget?
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 Rich Contact Widget in a multilingual WordPress workflow.
REEID documents Rich Contact Widget 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.