Works with your stack
Cookie consent for OceanWP
widgets call out early
OceanWP loads Google Fonts by default once you choose one, and the widgets of Ocean Extra contact other sites as the page loads. Videos, Facebook and X widgets are what the visitor’s choice has to cover. Cookie Rocks holds known trackers until the visitor agrees.
By OceanWP · oceanwp.org · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
OceanWP
WordPress theme
- Tested version
- 4.2.8
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
What matters for consent with OceanWP
Google Fonts on by default
A Google font chosen in OceanWP loads from Google’s servers. With Ocean Extra, “Enable Local Google Fonts” copies them to your site. It is off by default: switch it on, and do the same for Elementor fonts if you use Elementor. See Fonts.
Widgets that load on arrival
Ocean Extra’s Video widget writes a YouTube or Vimeo player into the page. Its Facebook widget loads Facebook, its Twitter widget loads X, and its Flickr widget calls Flickr, all on page load.
Adobe Fonts on every page
An Adobe Fonts project ID in OceanWP loads Adobe Fonts on every page.
One small cookie
OceanWP’s own cookie is set only when a visitor clicks the shop’s grid or list switch. The theme sends no consent signal.
What our tests found on OceanWP
Good to know · 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 its code, 1 November 2026, Cookie Rocks.
Depends on a setting · OceanWPOceanWP loads Google Fonts from Google by default
setting “Enable Google Fonts” · by default: on
Enable Google Fonts is on by default on a new install. Enable Local Google Fonts (needs Ocean Extra, off by default) serves them from the site. Neither plugin has WP Consent API or Google tag code.
Read in its code, 16 October 2026, OceanWP 4.2.7 (Ocean Extra 2.6.3).
Full detail
OceanWP 4.2.7 loads a chosen Google font from fonts.googleapis.com because Enable Google Fonts is on by default on a new install; Enable Local Google Fonts (needs Ocean Extra, off by default) has the server download them from fonts.gstatic.com on the first request and serve them from wp-content/uploads. Apply on Elementor (off) does the same for Elementor fonts. Neither OceanWP nor Ocean Extra has WP Consent API or gtag code, and neither moves iframe src.
Set before the choice · OceanWPOceanWP sets one cookie; Ocean Extra widgets contact other sites on load
- gridcookie (session) is set on click of the WooCommerce grid or list switch.
- Video widget: YouTube or Vimeo iframe. Facebook widget: facebook.com iframe.
- Twitter widget: platform.twitter.com script. Flickr widget: request to www.flickr.com.
- An Adobe Fonts project ID loads use.typekit.net on every page.
Read in its code, 16 October 2026, OceanWP 4.2.7 (Ocean Extra 2.6.3).
Full detail
OceanWP's only own cookie is gridcookie (session, set on click of the WooCommerce grid or list switch). Ocean Extra widgets contact third parties on page load: Video writes an oEmbed iframe (YouTube, Vimeo), Facebook an iframe facebook.com/plugins/likebox.php, Twitter a platform.twitter.com/widgets.js tag, Flickr a JSONP request to www.flickr.com. An Adobe Fonts project ID loads use.typekit.net on every page.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- OceanWP 4.2.8, tested on 7 November 2026.
Page builders and themes
Other plugins of the same kind.
Questions
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 OceanWP sites
Keep your widgets, ask first.
widgets call out early
Every feature of the complete plugin for 30 days, no card. OceanWP keeps working as it does today.
- 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

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