BASIC GOOGLE MAPS PLACEMARKS
Basic Google Maps Placemarks translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Basic Google Maps Placemarks 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
- Embeds a Google Map into WordPress pages/posts via the [bgmp-map] shortcode, with configurable display settings (e.g., map type, center location, width/height, zoom level, navigation controls).
- Creates a custom post type for “placemarks” (markers) that can be added/edited in the plugin’s Placemarks admin UI and assigned to categories.
- Supports marker icons via Featured Image for each placemark, including the ability to use a default icon (and override it via filters such as bgmp_default-icon).
- When a marker is clicked, displays an information window showing the marker’s title and description, and supports using HTML/images inside the information window.
- Provides marker clustering for large numbers of placemarks.
- Supports multiple maps on different pages by using shortcode parameters (e.g., categories, placemark, center, zoom, type) and notes that only one Google Map JavaScript API map can be supported per page.
- Includes an additional [bgmp-list] shortcode to output a text-based list of markers (optionally filtered by categories) intended for mobile/search-engine contexts, with an optional “View on Map” link to open the corresponding marker info window.
- Loads required JavaScript/CSS/markup only on pages where it detects the [bgmp-map] shortcode is called, and documents a filter-based workaround (bgmp_map-shortcode-called) for cases where shortcodes are invoked via do_shortcode() in templates.
Distinctive features
Embeds a Google Map into WordPress pages/posts via the [bgmp-map] shortcode, with configurable display settings (e.g., map type, center location, width/height, zoom level, navigation controls). Creates a custom post type for “placemarks” (markers) that can be added/edited in the plugin’s Placemarks admin UI and assigned to categories. Supports marker icons via Featured Image for each placemark, including the ability to use a default icon (and override it via filters such as bgmp_default-icon). When a marker is clicked, displays an information window showing the marker’s title and description, and supports using HTML/images inside the information window. Provides marker clustering for large numbers of placemarks. Supports multiple maps on different pages by using shortcode parameters (e.g., categories, placemark, center, zoom, type) and notes that only one Google Map JavaScript API map can be supported per page. Includes an additional [bgmp-list] shortcode to output a text-based list of markers (optionally filtered by categories) intended for mobile/search-engine contexts, with an optional “View on Map” link to open the corresponding marker info window. Loads required JavaScript/CSS/markup only on pages where it detects the [bgmp-map] shortcode is called, and documents a filter-based workaround (bgmp_map-shortcode-called) for cases where shortcodes are invoked via do_shortcode() in templates.
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 Basic Google Maps Placemarks 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
Basic Google Maps Placemarks and REEID Translate FAQ.
Does the current evidence establish translation scope for Basic Google Maps Placemarks?
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.