Skip to content

Works with your stack

Cookie consent for YouTube videos on WordPress: every way to add them

the thumbnail stays at home

← Cookie Rocks for your stack

A YouTube video reaches a WordPress page in many ways: the Embed block, a builder widget, a section background, a lightbox, a slider, a popup or a video plugin. Each one loads YouTube differently, and some build the player with a script rather than an iframe. Cookie Rocks Pro holds each of them until consent, shows a thumbnail copied to your own server, and starts the video without a reload once the visitor allows it.

Cookie Rocks

The ways a YouTube video gets into your pages

WordPress itself
The Embed block, the [video] shortcode, the video widget and the header video set in the Customizer. Each one loads YouTube as soon as the page opens, and the header video uses a script of WordPress, not an iframe.
Builder widgets
The video widgets of Elementor, Divi, Beaver Builder and the add-ons built on them. Some write an iframe, others add the YouTube player with a script before any choice.
Section backgrounds
A YouTube video behind a section or a row, in Elementor, Kadence or Beaver Builder. It plays muted and looped, and loads YouTube on every visit.
Lightboxes and popups
A poster that opens the video on click. Some lightboxes keep the iframe hidden in the page, so YouTube loads anyway. Popup Maker writes every popup into the page, so a video in a popup loads even if the popup never opens.
Sliders and galleries
Smart Slider 3 builds its YouTube layer with a script after the page load. NextGEN Gallery creates the player when the visitor opens a video.
Video plugins
Embed Plus for YouTube adds its own script and YouTube’s player library, and can show its own consent message. Course plugins such as Tutor LMS can swap the iframe for a player built in JavaScript.
Speed and tag plugins
WP Rocket and SiteGround Optimizer move the video address to a data attribute for lazy loading. GTM4WP can track video plays with YouTube’s player library, off by default.

What matters for consent with YouTube on WordPress

YouTube loads before any click

A YouTube frame sets YouTube’s cookies as soon as it loads. The player also loads Google’s anti-abuse check, in normal and youtube-nocookie mode alike, so the nocookie address alone does not wait for consent.

Held wherever it comes from

Cookie Rocks Pro looks for the video address in the iframe, in the data attributes of lazy-load plugins, in the scripts of builders and sliders, and in WordPress’s own players. Each one waits for the visitor’s choice.

A thumbnail from your own server

Before the choice, the video shows a Load the video box with its thumbnail. Your server copies the thumbnail, so the visitor’s browser does not contact YouTube to show it.

Backgrounds wait without a box

A background video shows the section’s fallback image or colour until consent, then starts muted without a reload. A video file hosted on your site is never held and plays for everyone.

No reload after Accept

After Accept all, or a click on Load the video, the video starts on the same page. A refusal keeps every YouTube video held.

What our tests found on YouTube on WordPress

  • Good to know · About Cookie RocksAfter a refusal, Cookie Rocks erases the cookies of active plugins

    After a refusal, cookies of the active plugins are erased; nothing is erased after Accept all.

    Seen in our tests, 15 November 2026, Cookie Rocks.

    Full detail

    The script that erases cookies after a refusal is smaller and is loaded only after a refusal. It receives the names of the cookies found by your site analysis and the names of the plugins active on the site. With Elementor active, a refusal erased elementor, popup-<id>-impressions-count and <id>-evergreen_due_date within seconds and kept the banner's own cookie; after Accept all, nothing was erased.

  • A setting to know · Bricks, DiviBricks and Divi 5 Interactions can write keys you name yourself

    Bricks Interactions (Browser storage: Add or Count) and Divi 5 Interactions (effect Cookie) write a key whose name and value the site builder chooses: local or session storage for Bricks, a cookie of 365 days for Divi. Nothing is written unless the site uses such an interaction. As their purpose is unknown, Cookie Rocks treats them as needing consent.

    What to do: If the key only remembers a dismissed notice or a layout choice, keep it as a preference; if it counts visits for a promotion, class it as marketing. Reclassify it on Cookie Rocks' Cookies screen.

    Read in the code of Bricks, Divi 2.2, 5.11.1, 12 November 2026.

  • Before the choice · popup-makerPopup Maker 1.25.0 and Google Fonts

    Popup Maker 1.25.0 loads Montserrat from Google Fonts before any choice, through a generated stylesheet (pum-site-styles.css). Cookie Rocks Pro 2.11.2 copies it to the site: no call to Google remained in our test.

    Seen in our tests, 7 November 2026, popup-maker 1.25.0.

  • Good to knowYouTube and Vimeo background videos wait for consent
    • Held without a box: the section shows its fallback image or colour.
    • After consent: muted, looped, no reload.
    • A video hosted on the site (MP4, WebM) plays for everyone.

    Read in the code, 4 November 2026.

    Full detail

    A YouTube or Vimeo background video of a section or container (Elementor, Kadence, Beaver Builder) is held without any box until consent: the section shows the builder's fallback image, or its background colour. After consent it starts muted and looped, without a reload; visitors who refuse never see it. A background video hosted on the site (MP4 or WebM) is never held and plays for everyone, so it is the better choice for a hero section, with a fallback image set in any case.

  • Good to knowHeld maps wait behind a « Load the map » box

    A « Load the map » box until the click or the consent; the map then loads without a reload.

    Read in the code, 4 November 2026.

    Full detail

    Before the choice, Cookie Rocks Pro replaces an embedded Google map with a « Load the map » box. Nothing is requested from Google until the visitor clicks the box or accepts the category; a click allows this one tool and the map loads without a reload.

  • Good to knowHeld videos show their thumbnail, copied by the site

    A « Load the video » box with the video's thumbnail, served by the site; one click starts the video without a reload.

    Read in the code, 4 November 2026.

    Full detail

    Before the choice, Cookie Rocks Pro replaces a YouTube, Vimeo or Dailymotion video in the page with a « Load the video » box that shows the video's thumbnail. The site's own server copies the thumbnail once and refreshes it every 30 days, so the visitor's browser never contacts the video platform. A click on the box allows this one tool, and the video starts at once, without a reload.

See the 38 other findings
  • Good to know · Divi Supreme ProWhat Divi Supreme Pro popups store in visitors' browsers

    Divi Supreme Pro: dsm-*-popup-cookie-<id> (preferences, life set per popup), on load, scroll or exit.

    NameKept inCategoryWhat it is for
    dsm-load-popup-cookie-*cookiePreferencesRemembers that a popup opened on page load was shown
    dsm-scroll-popup-cookie-*cookiePreferencesRemembers that a popup opened on scroll was shown
    dsm-exit-popup-cookie-*cookiePreferencesRemembers that a popup opened on exit was shown

    Read in the code of Divi Supreme Pro, 4 November 2026.

    Full detail

    Divi Supreme Pro popups set dsm-load-popup-cookie-<popup id>, dsm-scroll-popup-cookie-<popup id> or dsm-exit-popup-cookie-<popup id> (value dsm-<trigger>, SameSite Lax) when the popup opens, with a life in days set per popup (data-dsm-popup-cookie-expiry). An « on load » popup sets its cookie as soon as the page loads. They stop the popup from showing again.

  • Good to know · WP RocketWhat WP Rocket stores in visitors' browsers when it delays JavaScript

    WP Rocket: rocketCSPIssue (session storage, necessary) after a CSP block.

    NameKept inCategoryWhat it is for
    rocketCSPIssuesessionStorageNecessaryRemembers that the site's security policy blocks delayed scripts

    Read in the code of WP Rocket, 4 November 2026.

    Full detail

    When WP Rocket delays JavaScript, it sets rocketCSPIssue = true in session storage after a Content Security Policy blocks one of its data: scripts, and reads it on the next pages. The Audit 2.9.11 lists it without a category.

  • Good to know · Beaver Builder LiteBeaver Builder background videos start after consent, without a reload

    Held until the choice, then the YouTube or Vimeo background starts without a reload.

    Seen in our tests, 3 November 2026, Beaver Builder Lite 2.11.1.2.

    Full detail

    With Cookie Rocks Pro, a YouTube or Vimeo background video on a Beaver Builder row loads nothing before the choice. After Accept all, without a reload, the player script loads and Beaver Builder builds the muted background player in the row; on the next page it starts at once. Beaver Builder waits for the YouTube player script on its own, so no extra code is needed.

  • Good to know · ElementorWhat Elementor stores in visitors' browsers

    Elementor: 1 cookie(s) or browser key(s) for visitors, recognised by Cookie Rocks from 2.9.8.

    NameKept inCategoryWhat it is for
    elementorlocalStoragePreferencesRemembers which pop-ups the visitor has seen, to show them only as often as set
    elementorsessionStoragePreferencesRemembers which pop-ups the visitor has seen, to show them only as often as set

    Read in the code of Elementor, 2 November 2026.

    Full detail

    Elementor can store these in a visitor's browser: elementor (browser storage, preferences: Remembers which pop-ups the visitor has seen, to show them only as often as set). Cookie Rocks recognises them from 2.9.8, with this category and purpose, and lists them in the cookie policy when it sees them.

  • Good to know · DiviDivi's onboarding keys stay with the site team

    Divi's onboarding keys are for the site team only; visitors never get them.

    What to do: Nothing to do. Cookie Rocks 2.9.7 listed them under « Found only in the code » to classify; from 2.9.8 it recognises them as site-team keys and leaves them out of the cookie policy and of the points to fix.

    Read in the code of Divi 5.8.1, 2 November 2026.

    Full detail

    remainingSteps, siteCustomizationInfo and unprocessedPagesDetails are browser storage keys of Divi's onboarding and AI website builder. Divi loads that code only on its own admin page, so the keys are stored only in the browsers of people who build the site, never in visitors' browsers. They hold the steps left in the setup, the chosen starter pack and the pages still to create.

  • Good to know · About Cookie RocksThe audit names the local fonts setting of your theme

    When the home page loads Google Fonts, the Cookie Rocks 2.9.5 audit names the setting of the active theme or plugin that serves them from the site: Elementor, WP Rocket, Spectra, Kadence Blocks, OMGF, Local Google Fonts, Astra, Kadence, OceanWP or Neve. Otherwise it suggests a plugin such as OMGF. Divi, Bricks, Oxygen and Beaver Builder have no such setting. With Cookie Rocks Pro, it points to « Serve Google Fonts from this site » instead.

    Read in the code of Cookie Rocks, 1 November 2026.

  • Good to know · About Cookie Rocks ProCookie Rocks Pro leaves local fonts alone

    Cookie Rocks Pro 2.9.5 reads the page as it is served. Fonts that a theme or another plugin already serves from the site leave no Google address in the page, and the Pro does not touch them. It copies only what still points to Google: for example when Elementor falls back to Google after a failed download, or when OMGF is still in test mode.

    Read in the code of Cookie Rocks Pro, 1 November 2026.

  • Good to know · About Cookie RocksCookie Rocks classes Divi's visitor cookies itself

    Cookie Rocks 2.9.5 classes two Divi cookies as preferences: divi_module_views (how many times a section was seen) and divi_post_visit (pages already visited), set for one year only when the site uses these display conditions. ACF's acf local storage key is also preferences. Names that only Divi's builder and WordPress editors use (et-*-post-* cookies, et_pb_templates_* keys, DiviCloud and others) are left out of scans and never to classify.

    Read in the code of Cookie Rocks, 1 November 2026.

  • A setting to know · About Cookie Rocks ProCookie Rocks Pro serves Google Fonts from the site

    setting “Serve Google Fonts from this site (local_fonts)” · by default: on

    • Copies only fonts.googleapis.com and fonts.gstatic.com.
    • At most 120 files, 2 MB each; a failed copy waits 7 days.
    • Nothing to do on pages without a Google font.

    Seen in our tests, 1 November 2026, Cookie Rocks Pro.

    Full detail

    Cookie Rocks Pro 2.9.5 serves Google Fonts from the site, on by default (« Serve Google Fonts from this site », Consent page). The first page that still loads a Google font starts a background task. It copies each stylesheet and font file into wp-content/uploads/cookie-rocks/fonts/, then pages use the copies: links to fonts.googleapis.com and font files written in the page, as Divi's inline fonts. Once all is copied, preconnect and preload links to Google are removed and page caches are cleared. Google Fonts then leaves the cookie policy.

  • A setting to know · DiviDivi's Improve Google Fonts Loading does not host fonts

    setting “Improve Google Fonts Loading (divi_google_fonts_inline)”

    Divi's « Improve Google Fonts Loading » copies Google's stylesheet into the page, but the font files still come from fonts.gstatic.com, so the visitor's IP address still goes to Google. On eight live Divi 4.27 sites, the inline style (id et-builder-googlefonts-cached-inline) pointed to Google in every case. With the setting off, Divi links fonts.googleapis.com instead. Divi 4 and Divi 5.15.1 have no option that hosts Google Fonts on the site.

    What to do: Host the fonts with an extension such as OMGF, upload them in Divi, or turn off « Use Google Fonts ».

    Seen in our tests, 1 November 2026, Divi 4.27.9.

  • Good to know · DiviFonts uploaded in Divi are served by the site

    Fonts uploaded in Divi are served from the site itself (/wp-content/uploads/et-fonts/, declared in a style with id et-divi-userfonts): no request to Google for them. On a live site, uploaded fonts sat next to a Google font loaded from fonts.gstatic.com by the same theme: whether a page sends data to Google depends on each font, not on the theme.

    Seen in our tests, 1 November 2026, Divi 4.27.9.

  • Before the choice · ElementorElementor YouTube background videos load YouTube before the choice

    setting “Background type: video”

    Elementor's own script builds these videos, not the Video widget. Cookie Rocks 2.5.0 holds them and starts them after consent, muted and looped, without a reload.

    Seen in our tests, 16 October 2026, Elementor.

    Full detail

    Elementor's YouTube background video of a section is built by Elementor's own script, not by the Video widget, and loads YouTube before the choice unless the banner handles it. Cookie Rocks 2.5.0 holds it and starts it after consent, muted and looped, without a reload.

  • Good to know · ElementorElementor Element Caching can skip filters that rewrite one widget

    setting “Element Caching”

    Elementor stores the HTML of elements in the database, so a filter on one widget may not run again. Holding embeds from the full page output is not affected.

    What to do: Hold embeds from the full page output rather than from per-widget render filters.

    Read in the code of Elementor 4.3.5, 16 October 2026.

    Full detail

    Elementor's Element Caching (setting elementor_element_cache_ttl) stores the rendered HTML of elements in the database. A filter that rewrites one widget at render time may not run again on cached elements, while processing of the whole page output is not affected.

  • Before the choice · ElementorElementor writes Vimeo, Dailymotion and Google Maps frames in the page

    A banner that reads the page sees these frames. In the Video widget's lightbox mode, the video address waits in the page and loads only on click.

    Read in the code of Elementor 4.3.5, 16 October 2026.

    Full detail

    Elementor's Video widget writes Vimeo and Dailymotion videos as iframes in the page HTML (player.vimeo.com, with dnt=true in Privacy Mode), and its Google Maps widget writes a maps.google.com or google.com/maps/embed iframe with loading="lazy". In the Video widget's lightbox mode, the embed address is stored in the data-elementor-lightbox JSON and loads only on click. A banner that reads the served HTML sees these frames.

  • Before the choice · ElementorTwo Elementor YouTube forms load nothing from YouTube on first view
    • Video widget in lightbox mode with an image cover: the video waits until the cover is clicked.
    • The atomic YouTube element of the V4 editor (e-youtube).
    • In a test with Cookie Rocks, nothing from YouTube loaded and no cookie was set before the choice.
    • A click on the lightbox cover before consent was not tested.

    Seen in our tests, 16 October 2026, Elementor 4.3.5.

    Full detail

    Two Elementor YouTube forms load nothing from YouTube on first view: the Video widget in lightbox mode with an image overlay (the embed address waits in its data-elementor-lightbox JSON until the cover is clicked) and the atomic e-youtube element of the V4 editor (an empty div with data-settings, whose youtube-handler.js loads www.youtube.com/iframe_api). In a test with Cookie Rocks, first page, no click, page scrolled to the bottom, nothing from YouTube loaded and no cookie was set before the choice. A click on the lightbox cover before consent was not tested.

  • Good to know · Kadence BlocksCookie Rocks holds a Kadence Blocks YouTube background video

    Before the choice nothing reaches YouTube. After Accept all, without a reload, the video loads from youtube-nocookie.com.

    Seen in our tests, 16 October 2026, Kadence Blocks 3.8.0.

    Full detail

    Tested: a Kadence Blocks row with a YouTube background video is held by Cookie Rocks. Before the choice the iframe carries data-cr-src and nothing reaches YouTube; after Accept all, without reload, its src becomes youtube-nocookie.com/embed.

  • Before the choice · Kadence BlocksKadence Blocks background videos are written as YouTube or Vimeo frames
    • Row background video: autoplay frame from www.youtube.com (not youtube-nocookie) or player.vimeo.com.
    • Video Popup: frame created on click, from youtube-nocookie.com or Vimeo with do not track.
    • Video Popup: Plyr keeps a plyr key in localStorage.
    • Google Maps block: a lazy-loaded frame or maps.googleapis.com.

    Read in the code of Kadence Blocks 3.8.0, 16 October 2026.

    Full detail

    A Kadence Blocks row with a YouTube or Vimeo background video writes an autoplay iframe with src www.youtube.com/embed (not youtube-nocookie) or player.vimeo.com in the HTML. The Video Popup block writes no iframe: GLightbox and Plyr create it on click, using youtube-nocookie.com and Vimeo dnt by default (attribute youtubeCookies), and Plyr keeps a localStorage key plyr. The Google Maps block uses a native loading=lazy iframe or maps.googleapis.com; no iframe src is moved to data-src.

  • Good to know · KadenceKadence sets first-party cookies for countdowns and the shop layout
    • Evergreen countdown: <site name slug>-<campaign id>, 30 days, from the first page.
    • Shop grid or list toggle: <site name slug>-shopLayout, 30 days, only after a click.
    • No WP Consent API or Google consent code in the theme or Kadence Blocks.

    Read in the code of Kadence theme 1.5.2, Kadence Blocks 3.8.0, 16 October 2026.

    Full detail

    Kadence Blocks' evergreen countdown sets a first-party cookie named <site name slug>-<campaign id> for 30 days on the first page to keep each visitor's deadline. The theme's grid or list toggle sets <site name slug>-shopLayout for 30 days only after a click. Neither the theme nor Kadence Blocks has WP Consent API or gtag('consent') code. Form captchas (reCAPTCHA, Turnstile, hCaptcha) are required to submit.

  • A setting to know · KadenceKadence loads Google Fonts directly unless local fonts are turned on

    setting “Load Google Fonts Locally” · by default: off

    The theme's Load Google Fonts Locally setting is off by default. Kadence Blocks follows it, and without the theme has its own local setting, also off by default.

    Read in the code of Kadence theme 1.5.2, Kadence Blocks 3.8.0, 16 October 2026.

    Full detail

    The Kadence theme loads fonts.googleapis.com (with a preconnect to fonts.gstatic.com) as soon as a Google font is chosen; Load Google Fonts Locally (Customizer > General > Performance) is off by default. Kadence Blocks prints its Google Fonts as direct link tags in wp_head (priority 85) and wp_footer without a style handle, follows the theme's setting, and without the theme has its own local setting, also off by default.

  • Before the choice · Popup MakerPopup Maker loads hidden popup content and Google Fonts with every page

    setting “Don't Load Google Fonts (disable_google_font_loading)”

    • A video, map or form in a popup loads with the page, even unopened, unless a banner holds its iframe.
    • A Google font in a popup theme loads from Popup Maker's stylesheet, out of reach of a banner.
    • The Don't Load Google Fonts setting stops the font.

    Read in the code of Popup Maker 1.25.0, 16 October 2026.

    Full detail

    Popup Maker writes every popup into the page at load, hidden: a video, map or form placed in a popup loads with the page even if the popup never opens, unless a banner holds its iframe. A Google font chosen in a popup theme is loaded by an @import at the top of Popup Maker's generated stylesheet pum-site-styles.css, on every page that loads it, out of reach of a banner; the Don't Load Google Fonts setting stops it.

  • Before the choice · NextGEN GalleryNextGEN Pro video galleries create players a banner reading the HTML cannot hold

    The player is created by script when the lightbox opens: YouTube (not youtube-nocookie), Vimeo without dnt, Dailymotion, Twitch, TikTok and others. The page only carries the video address.

    Read in the code of NextGEN Gallery 4.5.3, 16 October 2026.

    Full detail

    In NextGEN video galleries (Pro), nextgen_video_helper.js creates the player iframe with document.createElement when the visitor opens the lightbox: www.youtube.com/embed (not youtube-nocookie), player.vimeo.com without dnt, Dailymotion, Twitch, VideoPress or fast.wistia.net; TikTok galleries create www.tiktok.com/embed/v2. Thumbnails only carry data-video-url, so a banner that reads the HTML does not hold these iframes.

  • A setting to know · WP RocketWP Rocket's Combine JavaScript can run a held script before consent

    setting “Combine JavaScript files” · by default: off

    It does not check script types, so a script held by a consent plugin can be pulled into the combined file. Local files with data-no-minify are spared; external ones only via the exclude list.

    Read in the code of WP Rocket 3.23.5.1, 16 October 2026.

    Full detail

    WP Rocket's Combine JavaScript files (usable only when Delay JavaScript execution is off) does not check the type of a script with a src, so a local or external script held as type="text/plain" by a consent plugin can be pulled into the combined file and run before consent. Local files with data-no-minify are spared; external ones only through the exclude list or the rocket_minify_excluded_external_js filter.

  • Before the choice · WP RocketWP Rocket YouTube preview image loads from i.ytimg.com before the choice

    setting “Replace YouTube iframe with preview image”

    With the preview image option, the image loads from i.ytimg.com when the page shows, and YouTube only on click. Cookie Rocks 2.5.0 holds iframes that WP Rocket lazy loads.

    Read in the code of WP Rocket 3.23.5.1, 16 October 2026.

    Full detail

    WP Rocket's lazy load only rewrites iframes that have a src attribute (data-no-lazy or skip-lazy excludes them). With Replace YouTube iframe with preview image, the preview image loads from i.ytimg.com as soon as the page shows, and YouTube only on click. Cookie Rocks 2.5.0 reads an iframe address waiting in data-lazy-src and holds it.

  • Before the choice · ElementorElementor loads Google Fonts before the choice; Cookie Rocks does not hold them

    This includes the kit's Roboto fonts and any Google font chosen in a widget. The local fonts setting works only once the styles are regenerated.

    What to do: Host the fonts on the site (Elementor's local fonts setting, then regenerate the styles, or a local fonts plugin).

    Seen in our tests, 15 October 2026, Elementor 4.3.4.

    Full detail

    Elementor loads Google Fonts from fonts.googleapis.com before any choice: the kit's Roboto and Roboto Slab, and any Google font chosen in a widget. Turning on Elementor's local Google Fonts setting made no difference in our test, because the fonts are only downloaded when the styles are regenerated. Cookie Rocks does not hold fonts.

  • Good to know · ElementorElementor free sets no cookie for visitors and serves its icons locally

    Elementor stores nothing in the browser for visitors, and its icons come from the site. In the editor preview, the Cookie Rocks banner does not show and nothing is held.

    Seen in our tests, 15 October 2026, Elementor 4.3.4.

    Full detail

    Elementor itself (free version) set no cookie and nothing in the browser's storage for visitors, and its icons (Font Awesome, eicons) came from the site, with no request elsewhere. In the Elementor editor preview, the Cookie Rocks banner does not show and nothing is held.

  • Before the choice · ElementorCookie Rocks holds Elementor Video and Google Maps widgets until consent

    On its own, the Video widget adds the YouTube player before any choice. With Cookie Rocks, the video keeps its size, shows a Load the video button, then loads from youtube-nocookie.com.

    Seen in our tests, 15 October 2026, Elementor 4.3.4.

    Full detail

    On its own, the Elementor Video widget adds the YouTube player with a script before any choice. Cookie Rocks holds the YouTube and Vimeo videos of the Video widget and the Google Maps widget until consent; the YouTube video keeps the widget's size, shows a Load the video button and, once allowed, loads from youtube-nocookie.com.

  • Good to know · WP Rocket, PerfmattersWP Rocket and Perfmatters delayed scripts stay held until consent

    setting “Delay JavaScript execution”

    Tested with an imitated loader, not the paid plugins. Delayed scripts wait for consent, run once the visitor accepts, and never run after Reject all.

    Seen in our tests, 15 October 2026, WP Rocket, Perfmatters.

    Full detail

    Tested with an imitated loader, not with WP Rocket or Perfmatters themselves (paid plugins): scripts delayed as rocketlazyloadscript or pmdelayedscript stay held by Cookie Rocks until consent, even after the first gesture, run as soon as the visitor accepts, and are handed back to the optimiser on the next pages; after Reject all they never run. Cookie Rocks adds its scripts to WP Rocket's delay, defer and combine exclusions and marks its head script nowprocket.

  • Before the choice · DiviDivi loads Google Fonts before the choice and after a refusal

    This sends the visitor's IP address to Google. On a real Divi 5 site, these fonts were the only request to Google before the choice.

    What to do: Host the fonts with an extension such as OMGF, or upload them in Divi: Divi has no option that hosts Google Fonts on the site.

    Seen in our tests, 8 October 2026, Divi 5.15.0.

    Full detail

    Divi loads its fonts from Google Fonts on every page, before any choice and after a refusal, which sends the visitor's IP address to Google. On a real Divi 5 site with Google Tag Manager, YouTube videos and Cookie Rocks in basic mode, these fonts were the only request to Google before the choice and after Reject all. The Divi contact form sends normally after Reject all.

  • Good to know · DiviCookie Rocks replaces an old cookie policy stored in a Divi 5 module

    Divi 5 stores shortcodes in a form that plugins searching the page content may miss. The Cookie Rocks dashboard finds the previous plugin's policy there and replaces it in one click.

    Seen in our tests, 8 October 2026, Divi 5.15.0.

    Full detail

    Divi 5 stores a shortcode placed in its modules inside JSON, with encoded quotes, so a plugin that looks for a shortcode in the page content may miss it. The Cookie Rocks dashboard finds a previous cookie plugin's policy stored this way in a Divi 5 module and replaces it with the Cookie Rocks policy in one click (checked on a real Divi 5 site).

  • Good to know · Site Kit by GoogleDelayed JavaScript can stop Site Kit restoring a saved choice

    Site Kit support says that delaying or combining JavaScript (WP Rocket) can make Site Kit set its denied default before WP Consent API declares the saved choice, so consent is not restored on the next page; excluding the consent scripts from the delay helps.

    Confirmed by the developer, 7 October 2026, Site Kit by Google. Source: Site Kit support forum, 07/10/2026 Source

Galleries, feeds and maps

Other plugins of the same kind.

KadenceBackground videos held, Google Fonts to host yourself.tested 1.6.0Envira Gallery LiteYour own images, nothing loaded from elsewhere.tested 1.17.0Adds: Google Analytics / Google Ads (gtag.js), Meta Pixel, YouTube, Vimeo, IPinfoFooGalleryImages from your site, frames only on request.tested 3.3.37NextGEN GalleryImage galleries stay at home, video players call their provider.tested 4.6.0Smart Slider 3Google Fonts by default, video players built by script.tested 3.5.1.40Smash Balloon Instagram FeedFeed images come from Meta unless GDPR mode is on.tested 6.16.0Smash Balloon Custom Facebook FeedMeta pictures and Like Box, unless GDPR mode is on.tested 4.16.0Embed Plus for YouTubeIts own script loads YouTube, so it waits with YouTube.tested 14.2.6.1Adds: YouTubeWP Go MapsMap code and tiles from other servers, before the choice.tested 10.2.02Widgets for Google ReviewsReviews wait for Trustindex, images load anyway.tested 15.0Galleries and slidersImages stay at home, videos and fonts call out.Feeds and embedsContent from Meta, YouTube, Google or Trustindex, before the choice.Popup MakerIts own cookie is harmless, its content is not always.tested 1.25.0Download ManagerDownloads from your site, with one session cookie.SpotlightInstagram feeds served from your own site.Widget for Google ReviewsPhotos copied to your site by default: nothing goes to Google.MapPressGoogle, OpenFreeMap or Mapbox tiles, held until consent.GravatarNo cookie, but data goes to the United States: serve avatars from your site.All-in-One Video GalleryOne cookie for random order, necessary.Presto PlayerYouTube and Vimeo videos wait for consent, then play without a reload.DiviContact forms with reCAPTCHA, videos and maps in modules.tested 5.15.0ElementorThe Video widget loads YouTube with a script.tested 4.4.1WP RocketCan delay every script until the visitor interacts.

Every plugin and theme we test →

Questions

Is youtube-nocookie.com enough?

No. The nocookie player still loads Google’s anti-abuse check and other calls as soon as the frame loads. It waits for consent like a normal YouTube video.

Why does my background video show only an image?

A YouTube background video waits for consent, so visitors see the fallback image you set. For a hero section that plays for everyone, upload the video to your site as MP4 or WebM.

Do I need to change how I add my videos?

No. Keep the block, widget or plugin you use. Cookie Rocks Pro holds the video wherever it is, and the free Audit lists the pages where YouTube loads before the choice.

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For sites with YouTube videos

Your videos stay on the page, and wait for the choice.

thumbnails from your server

Every feature of the complete plugin for 30 days, no card. Your videos keep their place and their size.

  • During the trial: everything, including the full settings and the scans
  • After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
  • What waits for a key: most settings, updates and support

How the trial works, in detail

Cookie Rocks

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.