WP Go Maps Block vs Map Block for Yandex

The easiest to use Google Maps and Open Layers Map Plugin is now available as a standalone map block! Create a custom map block with high-quality markers and add them to your WordPress posts and pages effortlessly. Perfect for contact pages, business locations, event venues, and more! Map blocks are lightweight and deliver optimal performance, ensuring a seamless experience for your WordPress site. They’re easy to customize, allowing you to quickly add and configure maps to suit your needs without compromising site speed or performance. If you need more features like multiple markers, shapes, and a store locator, our full (free) WP Go Maps plugin might be perfect for you. Block Features Add unlimited map blocks to your posts/pages Choose between Google Maps or OpenLayers for each block Edit your marker directly from the block editor Set marker location by free location search, or by right-clicking on the map preview Preview your map in real time, within the block editor Easy to use and customize without any coding experience Control width, height and alignment of your maps From the team that brought you the most popular Google Maps plugin on WordPress Lightweight for optimal performance No database queries or tables Basic info-window for your marker Control zoom level of your map Support for localization Latest Google Maps API Latest OpenLayers API Already using WP Go Maps? You can still use this block for single locations, as it is fully integrated with both our basic and Pro versions! References We make use of a various libraries and 3rd party service providers in order to render maps in your preferred mapping engine. This section will describe each of these in more detail and when they are used. OpenLayers: Served from a local library file (lib/ol.js & lib/ol.css), provided by OpenLayers. We use this library when you set your block to use OpenLayers (default). You can find the source files on the OpenLayers GitHub. OpenStreetMap: When you select the OpenLayers engine, a default map tile server is used, which is provided by OpenStreetMap. This is a 3rd party service provider that we rely on to render your map. They may also make use of MapBox for some of their assets. Google Maps API: If you decide to use Google Maps as your map engine, we will include the Google Maps API as a 3rd party service provider that we rely on to render your maps. In this case, admin map previews are still rendered by OpenLayers and OpenStreetMap. Nominatim (OpenStreetMap): If you perform an address search within the admin area, we will make use of the OpenStreetMap Nominatim to lookup locations and suggest addresses to you. This is a 3rd party service provider that we rely on for address searches.

Map Block for Yandex is a native WordPress block powered by Yandex Maps JavaScript API v3. Create independent, responsive maps and configure them from the block inspector with a live Gutenberg preview. Highlights Add multiple independent maps to any post or page. Keep each map isolated in a Web Component with Shadow DOM so theme styles cannot break it. Update center, zoom, camera and appearance live from the Gutenberg inspector. Keep the editor preview locked against dragging, wheel zoom and other direct map gestures. Use responsive width, height, minimum height, aspect ratio, wide and full-width alignment without horizontal overflow. Configure center, zoom range, tilt, azimuth, map mode and automatic, light or dark theme. Enable selected map behaviors and lightweight zoom, geolocation and fullscreen controls. Add, duplicate, search, reorder and remove structured markers. Customize marker coordinates, labels, descriptions, links, colors, icons, images, sizes and stacking order. Group markers with optional client-side clustering. Apply bounded Yandex vector-map customization rules. Lazy-load maps near the viewport or require a visitor click before connecting to Yandex. Disable the loading overlay, or customize a spinner, bouncing-dots or pulse preloader and map reveal. Provide keyboard-visible controls, accessible labels, useful error states and a no-JavaScript fallback link. Preserve and migrate blocks created by versions 1.0.0 and 1.0.1. The plugin does not enqueue the Yandex SDK site-wide. A shared loader is used per document and each block owns an independently disposable map instance. Optional clustering is loaded only when required. Inline marker data is normalized and limited to 1,000 markers and an approximately 1 MiB rendered configuration. You must supply a Yandex Maps JavaScript API v3 browser key and select a Yandex plan suitable for your use. Restrict the key by HTTP Referer in the Yandex developer dashboard. Browser API keys are necessarily visible to browsers and must not be treated as secrets. External services This plugin connects to Yandex Maps JavaScript API v3 only on pages containing a map block. By default, the connection begins when the map approaches the viewport. Administrators can enable click-to-activate mode so the connection begins only after visitor interaction. Requests are made to https://api-maps.yandex.ru/v3/ and include the configured browser API key and map locale. Yandex receives ordinary technical request data such as the visitor’s IP address, user agent and referring page according to its policies. Map tiles and enabled map interactions may make additional requests to Yandex. Browser geolocation is requested only after a visitor activates the geolocation control and grants permission. Yandex Maps API terms: https://yandex.com/dev/commercial/doc/en/ Yandex privacy policy: https://yandex.com/legal/confidential/en/ The service is required for the interactive map. An accessible fallback link remains available when the service cannot load or JavaScript is disabled. Editors may optionally specify an external marker-image URL. The visitor’s browser then requests that URL, and its host receives ordinary technical request data. Built-in marker icons are served locally by the plugin. Privacy The plugin does not create visitor profiles, set tracking cookies, contact a license server or send post content to the plugin author. Marker content remains in WordPress. The configured public browser API key is sent to Yandex as described above. Site owners should disclose their use of Yandex Maps in their privacy notice and use click-to-activate mode where prior consent is required.