Put a working cookie banner on your site in about 20 minutes
TermsFeed Free Cookie Consent takes 5 stages and about 20 minutes to set up: understand it, install the code, tag your scripts, verify, and check before launch. Cookie Consent shows a consent banner and, in its default express mode, holds each optional script you tag until the visitor accepts its category.
The 5 Cookie Consent setup stages and the time each takes
Follow the stages in order. The times assume a site with a handful of third-party scripts, so a site with many spends longer on tagging.
| Stage | Page | Time |
|---|---|---|
| 1. Understand Cookie Consent | What Free Cookie Consent Does | 5 minutes |
| 1. Understand Cookie Consent | Express and Implied Consent | 3 minutes |
| 1. Understand Cookie Consent | The 4 Cookie Categories | 3 minutes |
| 2. Install the code | Install a Cookie Banner on Any Website | 15 minutes |
| 3. Tag your scripts | Block Scripts Until Consent | Included in the 15 minutes of stage 2 |
| 4. Verify | Check That Your Cookie Banner Works | 5 minutes |
| 5. Check before launch | Cookie Banner Go-Live Checklist | 5 minutes |
Install guides for Shopify, WordPress, Wix, and other platforms
Each platform has its own place for site-wide code, and many add a consent banner or tracking of their own. Pick your platform and follow its guide from Install a Cookie Banner on Any Website.
Cookie Consent use cases, examples, and short answers
Find the pages for your situation, copy a complete page that already works, or read a short answer before you search the manual.
| Page | What you get |
|---|---|
| Free Cookie Consent Guides by Scenario | The pages to read for 7 common situations, in the order to follow them |
| Cookie Banner Examples and Tutorials | 2 complete pages with Google Analytics 4 to copy, and the TermsFeed video tutorials |
| Free Cookie Consent FAQ and Support | Short answers on compliance, platforms, storage, and wording, and where to get help |
Common mistakes when you install Cookie Consent
Check a failed installation for a script that runs outside Cookie Consent, a category ID that never matches, and a saved answer that hides the consent banner during the test.
An untagged script, or a second copy the platform adds, runs before consent. Find it with Scripts Run Before Consent.
A misspelled or capitalized category ID never matches, so its script never runs. Copy the exact IDs from Block Scripts Until Consent.
A browser that holds an earlier answer keeps the consent banner hidden during the test. Rule that out with Cookie Banner Not Appearing.