The same r/elementor thread that had everyone debating Elementor One pricing also had a quieter, more practical question buried in it: people just wanted a compliant cookie banner on their Elementor site without signing up for a £444 a year plan to get it. That is a reasonable thing to want, and the good news is you do not need Elementor One, or any paid plan, to do it properly.
I have set these up on enough client sites to know the steps that actually matter, and the one step most people skip that quietly breaks compliance. Here is how to add a GDPR cookie consent banner to an Elementor site using free tools, step by step. If you want the full breakdown of which tool to pick first, our comparison of GDPR cookie consent options for Elementor covers that side by side.
What your banner has to do to count
Before touching a plugin, hold the finish line in view. Under the GDPR and the ePrivacy rules, a banner only counts if it does four things: it blocks non-essential cookies and scripts until the visitor opts in, it offers granular category choices rather than one accept-all button, it makes rejecting as easy as accepting, and it keeps a record of each consent. Everything below is in service of those four outcomes.
Step 1: Pick your free route
You have two honest free paths. The first is Elementor’s own Cookie Consent, which has a free tier covering up to 800 consents a month for one site, with a scanner and exportable logs built in. The second is a dedicated free plugin from WordPress.org, and that is the route I lean toward for most sites because the specialist tools are more mature. Complianz is the most beginner-friendly thanks to its setup wizard, Real Cookie Banner has the deepest template library, and Moove GDPR Cookie Compliance is the lightest. Any of them works with Elementor, because cookie consent runs at the WordPress level, not inside the builder.
Step 2: Install and activate the plugin
From your WordPress dashboard, go to Plugins, then Add New, and search for the tool you picked. Install it, activate it, and let any first-run setup wizard open. This is the same flow whether you chose Complianz, Real Cookie Banner, or the Moove plugin. There is nothing Elementor-specific here, and that is the point: the banner loads site-wide, including on pages you built in Elementor.
Step 3: Scan your site for cookies
You cannot get consent for cookies you have not found. Run the cookie scanner so the plugin can detect what your site actually loads, from Google Analytics to embedded YouTube videos to your contact form. Elementor Cookie Consent and Real Cookie Banner both include a scanner on their free tier. Complianz keeps its scanner on the premium plan, so on the free version you list cookies manually, which is workable for a small site but slower. Whatever you use, scan after your site is mostly built, since every new embed or tracking script adds cookies.
Step 4: Sort cookies into categories
Group every detected cookie into the standard buckets: strictly necessary, functional, analytics, and advertising. Necessary cookies can load without consent because the site cannot work without them. Everything else has to wait for opt-in. Good plugins pre-categorize known services for you, which is where Real Cookie Banner’s template library earns its keep, but always review the result rather than trusting it blindly.
Step 5: Block scripts before consent (the step people skip)
This is the one that quietly breaks compliance. A banner that asks for consent but still fires Google Analytics or the Meta pixel on page load is not compliant, no matter how good it looks. Turn on the script blocking or content blocker feature so non-essential scripts are held until the visitor agrees. Every tool here can do this: Real Cookie Banner calls it a content blocker, Complianz and the Moove plugin block scripts by category, and Elementor Cookie Consent blocks automatically once categorized. Do not skip it.
Step 6: Design the banner so reject is as easy as accept
Style the banner to match your site, but keep one rule front of mind: the reject button must sit next to accept with equal visual weight. A giant green Accept next to a faint text link that says Manage is exactly the dark pattern regulators have been fining sites for. Set your colors and position, then check that a visitor can decline in one click as easily as they can agree.
Step 7: Publish, then test it properly
Publish the banner, then test it like a visitor would. Open your site in a private window, clear cookies, and reload. The banner should appear before any tracking fires. Open your browser developer tools, go to the Network or Application tab, and confirm that analytics and advertising scripts do not run until you click accept. Then click reject and confirm they stay blocked. This two-minute check catches the most common mistake, which is a banner that displays correctly but does not actually gate anything.
Step 8: Keep your consent records
If a regulator ever asks, you need proof of who consented to what and when. Confirm your tool is logging consents. Elementor Cookie Consent retains logs for 30 days on the free tier and lets you export them, Complianz keeps records of consent on every plan, and CookieYes logs centrally. On the Moove plugin, consent logging is a premium feature, so if you chose that one and you need documented proof, plan for the upgrade or switch to a tool that logs for free. This was the exact gap one agency owner flagged in that Reddit thread: some free plugins do not give you consent logs until you pay.
So, did you need Elementor One?
For the banner itself, no. A free dedicated plugin, or Elementor’s own free Cookie Consent tier on a small site, gets you a compliant setup without the subscription. Elementor One makes sense when you also want its other tools, like AI and image optimization, and you would rather manage everything under one plan with no per-site fees. If that bigger trade-off is what you are actually weighing, our honest breakdown of Elementor One versus Elementor Pro walks through the math.
Wrapping up
A compliant cookie banner comes down to four things done in order: find your cookies, categorize them, block the non-essential ones until consent, and keep the records. Do those, test the block with your own browser, and you are covered without paying for a bundle you do not need. That lean approach is how we think about The Plus Addons for Elementor too: add only what a page genuinely needs, and keep the rest off.
