Inline Render Mode
By default the script embed draws an iframe: the embed is a separate page at a Vibemap address, and search engines credit that address with its events and places. Inline mode draws the embed straight into your page. The cards, their titles, dates and links become part of your page, and so does the structured data that describes them.
Turn it on
Add data-render-mode="inline" to the script tag. Nothing else changes.
<div id="vibemap-events"></div>
<script
src="https://web.vibemap.com/load.js"
data-iframe-el="vibemap-events"
data-url="https://web.vibemap.com/embed/grid?list=YOUR-LIST"
data-render-mode="inline"></script>
Inline mode serves these embeds:
| Embed | data-url path |
|---|---|
| Grid | /embed/grid (and /embed/events) |
| Carousel | /embed/carousel |
| Map and grid | /embed/map-grid |
| Single event or place | /embed/single |
Any other embed, and short links such as /list/<slug>, keep their iframe and the browser console says so.
What lands on your page
- Cards as real links. Each card is an
<a href>to the item's page: your own item page when your theme sets one, otherwise its page on web.vibemap.com. - Structured data in your
<head>. AnItemListfor the list and anEvent(orLocalBusiness) for each item, the same data the framed embed publishes. When your Vibemap theme names your site, your page is the publisher. A single item is credited to your page's own?slug=address, so each item counts as its own page. Two embeds of the same list on one page publish it once. - No iframe. Your page's height, scroll and Back button behave as for any other content.
- No index for a missing item. A single item that was deleted or unpublished marks your page
noindex, follow, so search engines drop it rather than list an empty page. As for a framed embed,data-no-robots="true"on the script tag opts out.
Search engines that run JavaScript, Google among them, index this content as part of your page. Link previews in Facebook, Slack or iMessage do not run JavaScript, so they never see it; that holds for every script embed.
Styles
The embed brings its own stylesheet, scoped to the embed: your page's classes and elements are untouched, even
where a class name matches one of ours. Your theme's bare element rules (h4 { … }, img { border: … },
button { text-transform: … }) do not reach the cards either. Text inside the embed uses the framed embed's
font unless your Vibemap theme sets its own.
The map-and-grid embed is 90% of the window tall, as it is in a frame. Set mapHeight in data-url to change
it, for example mapHeight=600.
Loading and page layout
As with a framed embed, the script holds the embed's space from the moment it runs: 600px, the map's height
for the map-and-grid embed, or your data-height. It hands the space back once the cards are drawn, so your
page doesn't jump while the embed's files download. An embed further down the page loads a little before the
visitor scrolls to it; add data-loading="eager" to load it at once.
Analytics
Inline embeds report like framed ones: each event reaches your page's own Google Tag Manager as
dataLayer.push({ event: "vibemap_<name>", vibemap: { ...parameters } }), or your gtag.js as
gtag("event", "vibemap_<name>", { ...parameters }), with the same events, parameters and privacy rules as
Embed Analytics. surface is "inline" and embed_type is "inline-list" or
"inline-single"; with two embeds on a page, each event names the embed it came from. Inline mode loads no
Vibemap Tag Manager container and adds nothing else to your dataLayer.
Turn analytics off with analytics=off in data-url or data-analytics="off" on the script tag; nothing then
loads or reports.
Single-page apps
When your app removes the embed's container, call window.VibemapEmbed.unmount(container) first. It removes
the cards and the structured data the embed added, and hands your page's title back.