MAPPRESS
MapPress – Google Maps, OpenStreetMap & Leaflet translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what MapPress – Google Maps, OpenStreetMap & Leaflet 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
- Adds interactive maps to WordPress with Gutenberg map blocks and classic editor support.
- Creates unlimited maps and markers in the free version.
- Supports Google Maps, Leaflet/OpenFreeMap, Mapbox, and OpenStreetMap data.
- Can add maps to posts, pages, and custom post types.
- Supports marker clustering, styled maps, and responsive sizing.
- Supports popups with custom text, photos, images, and links.
- Supports directions, geocoders, KML overlays, GPX tracks, polygons, circles, and lines.
- Includes Pro features for searchable maps or store locators with search, geolocation, filtering, mashups, widgets, custom markers, and ACF integration.
Distinctive features
Interactive map embedding with both Gutenberg and classic editor support, plus broad map data source support and map display features such as clustering, responsive sizing, popups, directions, and overlay shapes.
Dynamic content
The evidence supports interactive map content, markers, popups, directions, geocoders, overlays, and track/shape display. Searchable maps, store locators, geolocation, filtering, mashups, widgets, custom markers, and ACF integration are mentioned as Pro features.
SEO and metadata
No SEO or metadata behavior is established in the supplied evidence.
URLs and navigation
The evidence mentions links inside popups and directions features. It does not establish broader URL handling, routing, or navigation behavior.
Forms and commerce
No forms or commerce behavior is established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what MapPress – Google Maps, OpenStreetMap & Leaflet 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 placement is described for posts, pages, and custom post types. The supplied evidence does not establish support beyond those surfaces. Searchable maps, store locators, geolocation, filtering, mashups, widgets, custom markers, and ACF integration are described as Pro features, so those capabilities should not be assumed in the free version from the evidence provided.
COMMON QUESTIONS
MapPress – Google Maps, OpenStreetMap & Leaflet and REEID Translate FAQ.
Does the current evidence establish translation scope for MapPress – Google Maps, OpenStreetMap & Leaflet?
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.