WP GO MAPS
WP Go Maps – Google Map, OpenStreetMap, Leaflet Map translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what WP Go Maps – Google Map, OpenStreetMap, Leaflet Map does, but does not yet establish specific visitor-facing content values that REEID should translate.
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
- Creates maps that can be embedded in posts and pages via shortcode, block, or widget.
- Supports multiple map engines, including Google Maps, Leaflet, OpenLayers, and several tile providers.
- Includes store locator functionality with search restrictions and related map display options.
- Supports map markers, marker editing, marker themes, and marker placement by address or drag-and-drop.
- Supports routes/polylines, polygons, and directions-related map features.
- Supports map customization such as size, zoom, map types, themes, and marker icons.
- Supports compatibility with caching plugins and Cloudflare.
- Supports multilingual and localization-related behavior, including translation-ready and WPML-related functionality.
Distinctive features
Supports multiple map engines and several embedding methods, plus store locator tools, marker management, route and polygon features, and map styling controls. The supplied evidence also notes caching-plugin and Cloudflare compatibility references.
Dynamic content
Dynamic map content is established for embedded maps, markers, store locator behavior, routes/polylines, polygons, and directions-related map features. The supplied evidence does not establish broader runtime content behavior beyond these map-related elements.
SEO and metadata
No SEO or metadata behavior is established in the supplied evidence.
URLs and navigation
URL or navigation behavior is not established beyond map embedding and directions-related map features.
Forms and commerce
Forms or commerce behavior is not established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what WP Go Maps – Google Map, OpenStreetMap, Leaflet Map 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
- Map behavior is documented for embedding in posts and pages through shortcode, block, or widget. Evidence also covers map engines, markers, store locator features, routes/polylines, polygons, directions-related features, customization, and caching-related compatibility. No broader compatibility claims are established beyond the documented map-related behavior.
COMMON QUESTIONS
WP Go Maps – Google Map, OpenStreetMap, Leaflet Map and REEID Translate FAQ.
Does the current evidence establish translation scope for WP Go Maps – Google Map, OpenStreetMap, Leaflet Map?
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.