GEOVERSE MAPS
GeoVerse Maps – Google Maps Block for WordPress compatibility with REEID Translate
GeoVerse Maps – Google Maps Block for WordPress compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a native “Google Maps” block for the WordPress block editor (Gutenberg), inserted into posts or pages rather than using shortcodes. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for GeoVerse Maps – Google Maps Block for WordPress.
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
GeoVerse Maps – Google Maps Block for WordPress is documented in the Media category with 8 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 GeoVerse Maps – Google Maps Block for WordPress 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
- Provides a native “Google Maps” block for the WordPress block editor (Gutenberg), inserted into posts or pages rather than using shortcodes.
- Renders an embedded/basic Google Map for a chosen location without requiring a Google Maps API key to start.
- Supports adding multiple markers on a single map, including custom marker icons and marker categories.
- Can display marker info windows with rich text content such as hours, phone numbers, links, and short descriptions.
- Optionally enables visitor-facing location search, marker filtering, and a clickable marker list view alongside or below the map.
- Can enable turn-by-turn “Get Directions” routing from a visitor’s location to a marker, when an API key is configured.
- Supports map style presets and the ability to paste custom Google Maps style JSON for theming.
- Offers optional Google Maps layers (traffic, transit, and bicycling) and includes fullscreen mode plus responsive height controls (desktop/tablet/mobile).
CONTENT BOUNDARY
GeoVerse Maps – Google Maps Block for WordPress 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
GeoVerse Maps – Google Maps Block for WordPress and REEID Translate FAQ.
What does GeoVerse Maps – Google Maps Block for WordPress do according to the available plugin evidence?
GeoVerse Maps – Google Maps Block for WordPress has 8 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 GeoVerse Maps – Google Maps Block for WordPress?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for GeoVerse Maps – Google Maps Block for WordPress?
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 GeoVerse Maps – Google Maps Block for WordPress in a multilingual WordPress workflow.
REEID documents GeoVerse Maps – Google Maps Block for WordPress 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.