Autoblocking Checklist
Autoblocking is built so that it requires no coding and works automatically. However, there are cases when this does not happen. In some sites using certain plugins / setups, there are “techniques” used by 3rd parties like Google and Facebook so that any blocking mechanism leaves them unaffected.
First script on site
The main technical requirement is that the Cookie Compliance scripts should be the first scripts on the web page, located in the “head” tag.
In order to check the position of the scripts, open the Developer Tools in your browser window and go to your website. Right click and “Inspect Element” to access the HTML elements. When a “head” tag is opened you should be able to find a two scripts, followed with a “<!–Cookie Compliance–>” comment.
Before it there can be various other elements, HTML tags – “meta” or “link”, but not “script”.
Autoblocking and Caching
It is often the case that script position problems are due to aggressive caching. The root of the issue may be in the usage of minification / compression, or script deferring. Some of these features can change the order of how scripts are loaded on a website, or can generate unexpected behavior on the JavaScript (JS) side
If you are using a caching plug-in (e.g. WP Super Cache, WP Total Cache, WP Rocket, WP Fastest Cache) try to locate and disable the following features one by one and check if that fixes the positioning issues:
- script deferring
- script aggregation
- script minification
- script compression
The name of these options may vary, depending on the plug-in, but you should be able to locate them by reading the option descriptions or documentation.
Once disabled, clear the site cache and Publish your banner to check whether blocking is working as expected.
Logged in users
Please make sure you are logged-out and viewing your website as an unregistered / anonymous user. We do not block scripts for logged-in users. If someone has an account on your site, with a username and password, then they have agreed to your Terms of Service, which is a form of consent that supersedes the Cookie Consent.