Before you put TermsFeed Free Cookie Consent live, run 14 checks in 4 groups: the options, the scripts, the page elements, and a final test of both answers. On a site you already verified, the list takes about 5 minutes.

Run the checks on the live hostname, or on a staging copy on a subdomain of your live domain, with HTTPS. A cookie_domain set for your live domain does not match localhost, so the browser refuses the cookies there.

Read the object you pass to cookieconsent.run() and confirm each option that a test setup often leaves wrong. Every on/off option takes true or "true" to turn on, and false, "false", or a missing key leaves it off.

Check How to confirm
debug is off The options do not hold "debug": true, and the Console tab does not show timestamped Cookie Consent lines
demo is off The options do not hold "demo": true; demo mode does not write cookies and shows the consent banner on every page load
language matches your pages The option holds the code of the page language, such as "de", or is removed so the browser language decides
The legal URLs are absolute website_privacy_policy_url and website_impressum_url start with https://; a relative URL such as /privacy does not show a link
cookie_domain fits your hostnames A site on several subdomains sets the parent domain, such as "example.com", with the same value on every subdomain; a site on a single hostname leaves it out, and a domain the page host does not belong to stops the browser from saving any answer
cookie_secure is on for an HTTPS site "cookie_secure": true on a site served only over HTTPS; leave it off on any http: page

A wrong value in these options stops the browser from keeping the answer, or shows the consent banner in the wrong language or without its legal links. Set the language per page with Cookie Banner Languages, and share the answer across subdomains with Share Consent Across Subdomains.

Confirm that every optional script you tag waits for consent under the default page_load_consent_levels, with the right category, and only once.

Check How to confirm
Every optional script is tagged Each optional script on your list has type="text/plain" and data-cookie-consent, except a Google tag in advanced consent mode and a vendor whose recipe sends a consent command
Each category ID is exact and in use The tags read strictly-necessary, functionality, tracking, or targeting in lowercase, and each category you tag is in notice_banner_purposes_levels when you set that option
No platform or plugin adds a second, untagged copy The tracking settings of your platform, plugins, apps, and any tag manager no longer load the scripts you tagged

A script that still runs before the answer has an untagged copy somewhere. Find its source with Scripts Run Before Consent.

Confirm that the code and the preferences link sit on every page, once. Visitors withdraw consent through the link, so keep it as easy to find as the consent banner.

Check How to confirm
The code is in the template every page shares With every other private window closed, the consent banner shows in a new private window on the home page, a content page, a form page, and an account page your theme shows, where your site has one. Leave out the checkout pages of Shopify and Squarespace, which run none of your code
The code appears once per page The page source holds one cookie-consent.js script tag and one cookieconsent.run() call
The preferences link is on every page The footer, or another place every page shares, holds an element with the id open_preferences_center when no selector is set, or one your open_preferences_center_selector matches, that opens the Preferences Center

A menu item whose editor has no id field works with a class selector. Add the link to a menu or a button with Add a Cookie Settings Link.

Test in express consent with page_load_consent_levels left out or at the generator value ["strictly-necessary"], and the "I decline" button shown; implied consent shows an "OK" button and no "I decline" button. Before each answer, close every private window, open a new one, and open DevTools on the Network tab before you load the site.

Check How to confirm
The "I decline" button holds every tagged script Type -domain:example.com with your hostname in the Network filter box, click the "I decline" button, and load 2 more pages; no request reaches the host of an optional tagged script, requests from an untagged Google tag under Consent Mode carry gcs=G100, and the Application tab does not list a _ga cookie
The "I agree" button runs every tracker Filter on the host of an optional tagged script, load the site, click the "I agree" button, and confirm its requests appear with no reload; under Consent Mode, confirm that the _ga cookie appears in the Application tab

A failed final test points to a check in an earlier group. Run the detailed checks again with Check That Your Cookie Banner Works.