Is Omea Consent safe to install?
Good choice: actively maintained
- Pass: Actively maintained Last updated 3 days ago (version 1.0.10).
- Pass: Compatible with current WordPress Tested up to WordPress 7.1; the current release is 7.1. Needs PHP 7.4+.
- Note: Few reviews so far No ratings on WordPress.org yet.
Check every plugin on your site with the free WordPress plugin checker →
Based on WordPress.org data, checked Nov 19, 2026. Always keep plugins updated and test changes on a staging site.
Overview
Omea Consent describes itself as: “Free cookie consent banner with Google Consent Mode v2, auto-blocking, a consent log and a cookie scan. GDPR, US opt-out & GPC, 12 languages.”
Developers can extend it through 6 actions and 58 filters, listed below.
Downloads & growth
How often Omea Consent is downloaded from WordPress.org each day, over the last 90 days.
Source: WordPress.org download statistics. Downloads include updates on existing sites, so tall spikes usually mark a new release. See what's trending →
How to install Omea Consent
- Open the plugin installer. In your WordPress dashboard go to Plugins → Add New Plugin.
- Search for it. Type “Omea Consent” and pick the one by Cultmetrics.
- Install and activate. Click Install Now, then Activate.
Install with a zip file or WP-CLI
Download the zip from the WordPress.org plugin page, then go to Plugins → Add New Plugin → Upload Plugin, choose the file and click Install Now. Or from the command line:
wp plugin install omea-consent --activateRequirements: WordPress 6.0+ · PHP 7.4+ · tested up to WordPress 7.1.5
Hooks & customisation
Omea Consent 1.0.10 fires 6 actions and 58 filters. Use them from your child theme or a snippets plugin to change how it behaves without editing its files.
// This filter is documented in omea-consent.php (render_scripts_location).
apply_filters( 'omea_consent_managed_scripts', self::get_scripts(), $location, false );
// Filters the admin screens that load the Omea shell (Pro adds its own pages).
apply_filters( 'omea_consent_admin_shell_hooks', $allowed_hooks );
// Renders the Custom CSS field (Omea Consent Pro). Fields use the settings form,…
do_action( 'omea_consent_appearance_custom_css' );
// Below the cloud scan result (Omea Consent Pro: monthly scan setting).
do_action( 'omea_consent_cloud_scan_after_result' );
// Lets Omea Consent Pro scan with its license (no free-scan limit).
apply_filters( 'omea_consent_cloud_scan_credentials', null );
// A cloud scan finished (Omea Consent Pro compares it with the last one).
do_action( 'omea_consent_cloud_scan_done', $state['result'] );Omea Consent: frequently asked questions
Is Omea Consent free?
Yes. Omea Consent is free to download from the official WordPress.org plugin directory and is licensed under the GPL, so you can use it on as many sites as you like. Some developers sell a separate Pro version or paid add-ons; check the developer's website for details.
Is Omea Consent safe to use?
Omea Consent is actively maintained: the latest version was released 3 days ago. As with any plugin, keep it updated and only install it from WordPress.org or the developer.
Does Omea Consent work with WordPress 7.1?
Yes. Omea Consent is tested up to WordPress 7.1, the current release. It requires WordPress 6.0 or later and PHP 7.4 or later.
What are the best alternatives to Omea Consent?
Plugins that do a similar job and are actively maintained include CookieYes (1+ million installs), Complianz GDPR/CCPA Cookie Consent Banner (1+ million installs), WPConsent (200,000+ installs).
Can I customise Omea Consent without editing its code?
Yes. Omea Consent 1.0.10 fires 6 actions and 58 filters that you can use from a child theme or a code snippets plugin, so your changes survive plugin updates. Browse all 64 hooks with examples.
Done for you
Need Omea Consent to do more?
Clear starting prices, an exact quote before any work, and changes built so plugin updates never wipe them.
Plugin customisation
from $149
New features or changed behaviour, without editing the plugin’s files.
- Built as a companion plugin, so updates never wipe it
- Exact quote before we start
- Tested on staging, then deployed
Typical turnaround: 3–7 business days
Choose thisCustom hook snippet
from $49
A small, update-safe change built on the plugin’s own hooks.
- Code written against the plugin’s actions and filters
- Tested on a staging copy of your site
- Install instructions included
Typical turnaround: 2–3 business days
Choose thisBug or conflict fix
from $79
Errors, broken layouts or two plugins that don’t get along.
- Find the cause on a staging copy
- Fix without breaking updates
- Explain what was wrong
Typical turnaround: 1–3 business days
Choose thisNot sure which fits? Describe what you need and we’ll suggest the simplest option.
Need Omea Consent customised?
Tell us what you want changed, added or fixed and we'll reply with an estimate.
WP EXPERTS is independent and not affiliated with Cultmetrics. Plugin names and logos belong to their owners. Version, rating and install figures from WordPress.org, checked Nov 19, 2026.